[AndrewKemendo]

> We're not here to write code, but to solve problems.

In my opinion having had multiple technical job roles (car stereo/alarm installer, website builder, military officer, CEO, CTO etc…) this is always the job.

The job is *always* to make the organization more effective and efficient full stop. Your role in that is what you choose and negotiate with your team throughout your life; boundaries change pre/during/post employment.

When you join a company you usually (not always) have a niche role, to fill in a gap that is preventing effective organizational execution.

If you’re mentally flexible to understand that your narrow focus is not the actual output, that is a temporal means to an output, then you transform how you view the concept of work and relationships

[wouldbecouldbe]

In most companies your job is to solve tickets. And the only creative freedom a developer has is how that ticket is solved. Quick fix, properly done, rework etc. Maybe that’s why certain smart developers over engineer, because that’s the only place they can create ownership

[linuxdude314]

Maybe if you’re a junior engineer, but this absolutely not what most SWEs do.

[AndrewKemendo]

As long as you think like this then you’ll always stay in that niche

[wouldbecouldbe]

That’s not how I work. I live from my own saas.

But I worked for a long time as a freelancer in big name corporates in the Netherlands and other large software companies. And that’s just how it is everywhere. Also in house senior devs have little to say. Hope other companies/countries are different