Been laid off recently. Did really heavy lifting for a project for 3 years, completely re-writing the app after multiple major framework updates, making it more modular and actually maintainable and testable, reducing deployment times from 40 to 5 minutes and allowing for multiple teams to work on it without getting merge conflicts all the time. Because those technical tasks had no clear business benefits, the HR guy told me I was the worst developer on the team. They are not filling my position in the future, instead rely on "nearshore outsourcing". When I joined the team, it took quite a while to understand what is going on due to spaghetti code and code duplication. The recent foreign hires appreciated the new structure and how easy it is to write a new part of the app with the new UI library and service dependency injections. They could write code with confidence because there were finally meaningful tests too.

Now, I am working on a team that uses its own framework instead of industry standards and has 0 tests. Let me tell you, these guys will have a job for at least another 10 years, no matter how good AI gets. Whatever the code does is highly dependant on the data in DB, the interfaces do not reveal enough, even if AI could scan the whole project. It can never implement anything incrementally because the outcome needs to be tested manually.

TLDR: don't be like me and shoot yourself in the foot by being a good employee, unless you code for your own startup

Of course it has clear business benefits if development and deployment are improved. They just made up some bullshit to cut labor costs.

It's not the fault of the offshore workers either, who appreciate your work, it is upper management wanting to report profits by cutting corners.

It's not wrong to do your job well, they just wanted to find an excuse to replace you with cheaper labor. In the long-term, this approach of writing shitty code for job security will cause you to stagnate in a profession that requires constant learning.

>>105591254
The thing is, the people who set up the app the way it is (for example using Javascript instead of Typescript despite it being clear that it would grow to be huge in the future), have been promoted since to do tasks which have more to do more with domain/business and less technology. They did everything right. They were asked for fast results and they delivered. Now, they could not care less because they don't even write code anymore. Improving yourself is a meme unless you hop between companies every few years.

>>105591213 (OP)
It depends entirely on your environment. There's an analogy with driving here. If you're driving a bit above the speed limit you aren't at any more risk than if you were driving below the speed limit, as long as you drive at the same pace as other. Risk to you only increases if your speed is significantly different from the other cars on the road. If your company's code base is using outdated frameworks, has terrible or no test coverage, and with every change becomes more mired in tech debt that's due to systematic failure that incentivized that sort of behaviour and/or low barrier to entry. If you try to come in change that you probably won't be rewarded and might even be resented by others.

Basically my advice boils down to "don't rock the boat", but there are many people out that simply can not stand inefficiency. If you are like me just use the job to boost your resume and get the fuck out of there later on.

>>105591213 (OP)
excellent point, tech workers need to learn a few tricks from the unions, they've been surviving under capitalism for a long time, they know what they're doing.

>>105591447
It is not a meme to be diligent, it is a virtue. To do the best you can in whatever you do. In programming especially, if you do not constantly learn, your skills will become obsolete.

no good deed goes unpunished. better work less next time

>Did really heavy lifting
stopped reading there
>>>/fit/
>>>fit
>>>fit/