[hinata08]

Yes ! As Harryhirsch said, change of position !

DO DEV OPS

You will most probably not be able to change the culture of a company on your own. So you could just leave before they realize the code is unmaintainable. (plot twist : you often realize this in some hard way)

if you have these engineering skills, I suggest you do DevOps ! designs, modeling, docs, manage a codebase, Tests, version control, policies, static analysis... perfectly match what they have to do

Keep the mindset, learn some gitlab pipelines, and you'll be a rock star for employers

[tarsinge]

Too much focus on software quality and zealous DevOps before product market fit can kill startups too (I even experienced it). Nobody cares about a useless product with good quality. Nothing wrong with that, as others have said maybe change for a larger company and a more mature product.

[quickthrower2]

I am about a month into devops / platform role and enjoying it alot for these reasons. Of course ymmv but the job of making other developers lives easier is quite nice. But it is not really about application code architecture, maybe that should be a team/thing too.

[hinata08]

yes, devops teams are chill as well

Their actual tech work is made by code. And it leaves them time to chat with anyone else at the company, or at the customer, to figure out new things that could serve them.

I also love to just teach someone about the tools. When the needs can be served super easily and the guy is interested, it's great not to do the work yourself, but to guide them into this culture of 'automation&chats over teas'.

The more ppl do pipeline on their own, aim for value and clean, simple code, go for high added value work, and drink tea with coworkers and customers, the more your company starts to gain.