[hideo]

I admit #9 is fun but I try not to do too much #9, because there's a huge risk to doing too much of that: losing touch with what's important to the bottom line, and indirectly influencing all the other ICs that prototypes get you promoted. That's just not true in my company. My prototypes are usually for exploring something important to the company or validating a tech hypothesis of some sort. I try to spend more time writing production code where possible.

[Apofis]

I meant I love the way you phrased it.

A lot of programmers ignore the fact that they're serving a business function.

[hideo]

Thanks :)

It does feel like some folks ignore the business side of things but I think I enjoy being a part of the larger picture. It's definitely not for everyone. I know several people who are personally happy and have had WILDLY successful careers being hands-on tech specialists and ignoring the business side. It's great that it works for them.

[Apofis]

Not everyone can do the same thing over and over again their whole life. Soon, I'm going to scream if I have to build another website or app... thankfully I'm making a massive career shift into Aerospace.