I've yet to meet a "Rockstar" that followed any sort of process. I've been in the embedded world for 15 years, and I can churn out code that mostly works in almost no time. Churning out code that is modular, reusable, will survive system test, third party security reviews, deployment to a wide variety of field conditions on potentially out of spec hardware, and give a path to debugging when its not working is a whole different matter. Once I create that code, I need to communicate and document all of this. I guess I probably don't look so Rockstar after I spend the time to do all this. Even when I do this really well, and fast, I can only do so much as a single person. I also don't want a 60 hour work to be a normal thing. If I can empower a team of 5-10 people to do this almost as well as I can, that's where the real multiplicative power comes in. The Rockstar isn't the person who churns out code fast, its the person that raises the level of an entire team. Anybody that tells you otherwise is a business type who has never been in the trenches and experienced it first hand.