Being able to take an idea and turn it in to a product is a brilliant skill that startups absolutely need, but equally, once the product is out there being used, you need the other skill set to maintain the product and add new things without annoying the users. Having people around who can do both is exceptionally useful because it means the team continues to do productive work for much longer without having to bring new people in.
To that end, I always recommend people get at least a few years experience at an established company before joining a startup.
But guess who gets the glory? :(
In my opinion, it's amazing what you can accomplish when you don't care who gets the credit. You're stronger with others than on your own.
Not sure I understand.
Anyways, I've been around engineering teams for a while now and here's what I mean: there's always some principal engineer or fellow (in the terms of a title) that is greatly esteemed and admired because of decades of progressively larger and larger feature creation and system architecture/leadership.
If all I ever do is fix bugs -- forever in my career -- it means I'm not going to build anything and I don't get to be on the team that gets the people to the stars because that team is reserved for aforementioned team of people who have built a lot.
I probably shouldn't be a programmer anymore since all I'm good for is fixing bugs.
If you're working for someone else, and it's their name on the product, ignore glory and insist on money.
You say this like I've not thought about it or tried it myself. :)
It's difficult since I don't know what I don't know. I stumble around trying to figure out what I need to figure out and come to realize that I don't know what goes where.
It's also difficult because of sheer time. I spend 13-14 hours going to work, being at work, or coming home from work. Whatever suggestion you have I've probably thought about or tried, so do be considerate if you decide to reply. ;)
That's how I interpreted what was being said rather than expecting fame in the hacker community.
The actual day to day work though, was pretty routine. I was mostly fixing bugs and rebuilding parts of features that had to ship in yearly timelines. Every project I worked on that wasn't canceled was spent in refactor mode for a good portion of the year. Let's rewrite this for 64-bit for example, or let's rework this for this new framework. The actual customer should never notice a change in the product, and usually the visual changes are subtle if any. Lucky few got to work on the shiny demo-able new features and even fewer lucky folks got to lead teams from their new products.
Lastly, most of the tooling that I got really good at and used to great advantage was proprietary except for Xcode and Instruments. :(
So leaving to go to a startup I literally had to learn a whole new set of tools and APIs. Then again, I learned so much more about how to build a product from the ground up at a small 11 person startup than I ever did at Apple.
At a company like Apple, I gained skills adding a feature to an existing product. At a startup, I gained skills building a product from nothing but an idea.