Hacker News Reader

> in the professional world, what you are going to do is dictated by your manager down to the last line of code. The feature and testing requirements would be specific enough to get rid of all creative freedom.

Maybe I'm just lucky, but I've worked in a large software house for over a decade and I'm enjoying a lot of creative freedom when it comes to the code I'm writing.

To me this reads more like reasons not to work at this person's particular company.

View on HN

Medium-sized company for me, but same here. As long as my code works, there's really no one breathing down my neck or telling me what to do.

As you said, you define your creativity by your code itself. I think some programmers (at least me) want a wider freedom, for example about features, or process, or devops stuff, etc etc. I think the more you're in a big structure with defined roles, the more it's difficult to have this freedom, not only about the way to code, but the way to work.

I'm probably a bit blessed, but I have a voice in all those facets. I think the key for me has been to work on a small product-focused team that defines its own microcosm within the larger org, where the roles aren't too rigidly defined and everyone mostly just does what is needed to move the ship forward.

Reply on news.ycombinator.com