What companies and industries value programming that is not fast, not fashionable, but works like a clock?

Question

Career in IT

I am not satisfied with my current job:

- Haste. Figak-figak and in production. I came to the planning meeting in the morning without doing anything - they immediately thought about dismissal. Don't care what you pass in half a day, but the best.

- Aesthetics, not thoroughness. They believe that the code should be easy to read, everything should be concise, done in a fashionable way, and DRY, of course. New team members are sometimes bashed for code style. But ... everything is somehow half. The ideal codestyle is still impossible to follow. And there are no uniform rules for codestyle for all occasions. And the very fact that I'm so bothered makes colleagues think - should I take care of my mental health instead of the code. Meanwhile, by my nature, I try to do everything extremely carefully ... although often not very beautiful, and even more so not fashionable. As for readability - apparently I can easily read much more complex code than my colleagues.

- Bugs. Nobody loves them. But he doesn't do anything to stop them. Unit tests are very imperfect. Moreover, no one checks the code manually properly. They look at the review code for the above-described "beauty", it seems wild to them to use the review to find some bugs.
They say it will take forever. Although I myself do such a review in 10-30 minutes.
Also, according to them, it makes no sense to do something special to find bugs, because "there will still be bugs." However, I have experience working with customers without a team, and I can say for sure that if you look for bugs, then there will be no serious bugs at all (none in a year of work, and several without checks), and there will be almost no small ones. Even if you do everything in a hurry, checks will still save you from any significant bugs. I can't imagine how you can not look for bugs. Many of them are simply inadvertently allowed.

- Love for novelty. I'm biased against new tools, new versions. For example, I hate the Rust language - it is intended to replace C ++, but it does not look like it at all! Why make such a mess? Today I also learned that in the latest versions of Rust, backward compatibility was broken, although they promised that it would always be. Cases like this just piss me off. And they are also frozen out - but they still relentlessly update everything to the latest versions. Whereas I am much more reserved about it.

And as far as I know, this is the case in almost all companies and in all varieties of products.
Where is it wrong?

Answer 1

In the corporate sector, especially banking.

Answer 2

Firmware for telecommunication devices, corporate sector, embedded equipment, automotive industry. If there is an error, you will have to withdraw the batch. From our examples of what is now heard - infotex and security code.

Answer 3

I didn’t quite understand what area you work in, but I will assume that you need:
1. Quality of the result > Speed ​​of writing.
Here I want to clarify that usually normal people require compliance with deadlines: if you say that you will pass on day X, and then a week after day X you add something to your ideal - this is not ok.
2. A clear codestyle supported by configs, linters, etc. 3. Systemic
bug fighting
4. Without Rust
In general, according to the title:
- Banks (and fintech in general, when a bug attracts large fines or losses)
some ancient mainframe that handles transactions.
- Medicine
- Transport
- Weapons (ideally nuclear)
- Industry (factories, machine tools, robots, etc. The more harm a bug causes to health, the tougher the rules for writing code)
If without fanaticism - just large product companies with established practices (in this case, you need to get into some long-existing product, and startup)
PS:

I'm biased against new tools, new versions.

And in vain really. Updates are designed to improve life. In the same case with growth, a breaking change was necessary. Yes, and for the rasta itself, this is the norm - the language is still young.
PPS: write later what company you will get into - I do not want to work with you in the future.

Answer 4

Usually such companies have other disadvantages. This is that their systems are extremely difficult to maintain legacy code, with a large number of dubious architectural decisions or complex optimizations. Plus a lot of duplicate code and a web of dependencies, since it is often easier to write side by side than to deal with what is written.

Answer 5

See AUTOSAR and MISRA
Other than that they didn't mention medicine and science.
But I want to note right away that there is such a shaggy legacy that these machines are still used
https://ru.wikipedia.org/wiki/IBM_System/390

Answer 6

At the Research Institute of Long-Range Radio Communications. Only salary 40t.r. and colleagues from whom sand is pouring, you will not like it.

Answer 7

Yes, wherever production is expensive, it fell there for half an hour, everyone lost a hundred thousand bucks and immediately cheated everyone who loves immediately into production

Answer 8

In Yandex, type in " Choosing the right job or how not to die of a heart attack while working as a programmer ", or a link in my profile, you will find it there, on the site. And in general, read that site, you will understand a lot of new things for yourself .

What companies and industries value programming that is not fast, not fashionable, but works like a clock?

wherever there is no industrial programming. As soon as it appeared, development to order, let's just say - the whole industry is heading into UG.
Until you find a job where you can safely maintain the existing infrastructure of the enterprise, and you are constantly being pushed by deadlines, you will kill your psyche until one fine moment you hoard mentally, and even physically.