How to deal with burnout on a fakap project?

Question

Career in IT

Not so long ago I got a job as a programmer in a web studio. At the very beginning, I got on a fake project, which for 99.9% consists of one legacy, absolutely old approaches to application development. When I was hired, they assured me that everything was written with modern technologies and the most interesting projects. Lately I've been so fed up with the project that I just don't want to go to work and touch the code at all. Although at home I can work on my home projects 24/7 and the field of programming just fascinates me. In general, I completely burned out on the project, I don’t want to do anything, with the full knowledge that you don’t grow as a programmer in any way and don’t get new skills and knowledge. Who will share what to do in such situations? Is it reasonable to leave the company, or is it all just some kind of snot and you have to continue rowing?

Answer 1

completely burned out on the project

and then: mental illness, addiction, impotence, heart attack, stroke, sudden death.

I can work on my home projects 24/7

Turn projects into business.

The field of programming fascinates me

If you do not change your approach to work / life and continue to use yourself as a consumable, then with further burnout, the fascination will pass. And already their projects will not be interesting.

Answer 2

Damn I'm rolling. They didn’t bring me toys, I won’t work. You are paid money for the work, do it well, change what you can. What can not be described with your vision.

Answer 3

In general, I completely burned out on the project, I don’t want to do anything, with the full knowledge that you don’t grow as a programmer in any way and don’t get new skills and knowledge.

Do not confuse work at work and school. Nobody is obliged to raise you as a programmer and give you new knowledge. If you want - after work, do self-study, write your own projects. Complaining that there is no new knowledge at work is some kind of nonsense. Whatever the work, everything that is new on it is quickly studied, and then there is a routine. And this is normal almost everywhere, except in RnD, but there, too, no one teaches you, but you study yourself. Without SO.

Answer 4

At the very beginning, I got on a fake project, which for 99.9% consists of one legacy, absolutely old approaches to application development.

I advise you to remove rose-colored glasses and unicorns from your head :) As a rule, where big money is spinning, the code consists of 40-70 percent legacy. This is the essence of the "bloody enterprise", conditionally - it works - do not touch it.
If you want a beautiful code without legacy, choose startups. The conditional Gitlab with its Vue stack still spins Jquery under the hood, and rewrites. I want a more structured approach to development and approximate uniformity = look for work with Angular.
But a web studio = gallera with a fuckup, you need to grow higher.

Answer 5

If you live alone, then:
1. Drink.
2. Play games (if you suffer from this)
3. Spend your free time as you can / like
If with your wife / girlfriend, then condolences)
And so ...
1. Do not carry work home.
2. You work for your uncle until 18:00, something quick/urgent can still be done for half an hour, but not often. Try to leave at the right time.
3. Fuck X for all this. You're just a cog and doing nobody's work. You live from salary to salary, the rest is within the TC.
4. Burnout is inevitable: from routine, routine, futility of work.
5. Well, yes, she is a galley in Africa and a galley.

Answer 6

Change project or job

Answer 7

It's perfectly reasonable to leave. Especially if you feel confident in the labor market. Of course, it is better to grow than just row.
But there are other options as well. For example, take everything into your own hands and change for the better. This is also growth, only in a different plane. And a good line in the resume.

Answer 8

A programmer's job is 80% code reading, and (surprise!) legacy code. Everything that you wrote today on your latest frameworks will be dense legacy tomorrow. The presence of legacy indicates that the project is working, and, apparently, making money (some of which goes to you in salary). If you don't like legacy code, then rewrite it. Agree with the business some part of the time to work on improving the code base - this is an absolutely normal practice.
It is reasonable to leave the company if the work is not a joy (not satisfied with the project, team, office, salary, etc...)

Answer 9

I sometimes have similar thoughts.
And yes, "if it seems to you that something needs to be changed, it doesn't seem to you."
.
Look at the vacancies, XX! Everyone is proud of the fact that they are introducing top technologies,
so you just need to go there ... ; the joke is that the same controls require that you know all this
by the time of employment (well, for example - Rabbitmg, Radis, Symfony , Docker, ...)
It turns out a vicious circle - they don’t take where they want, but they take everything - they don’t want to .. ..
There is only one way out - to pump yourself at home.
.
PS: For example, I started a whole blog on pumping my own, where I talk about what I learned new:
nujensait.ru/category/notes

Answer 10

The work of a programmer is not * to slander a codewars-sandbox who will write a funnier function, but to maintain the code, fix it, raise it, improve it.
I personally consider programming and any project as a living organism, this is our brainchild. He wants to live and our task is to support him, to revive him. It does not matter that he is an old man on crutches, we must help him to live.
And personally, after leaving, it’s even somehow sad for me to leave him on other shoulders, so that someone doesn’t ruin the project at all.
And everywhere there will be projects with bad code, as well as projects with good code, work is work. If I were you, I would collect juices and try to drag the project, and then shift it onto the shoulders of another, leaving for another company. The main thing is only adequate management, so that more time is allocated for support and they are happy with refactoring.

Answer 11

Form a financial "cushion" for six months and leave to look for what you want.