What if you come to the project, and everything is sad there?

Question

Career in IT

It often happened when I came to the project, and everything is very neglected and written with big deviations from the technologies that were chosen.

I used to do it simply - I forced myself to stay and tried to improve, offering management to allocate time / budget for putting things in order. But more often I meet those projects where the pace is high and there is no time / budget to improve something. You have to either agree, do it through force, force yourself. Or - look for something else.

Share your experience - how to solve such a problem?

Answer 1

You can try to look for a place where they pay for strict adherence to those technologies.
Until the need forces you to return to the real world, in which the one who pays "works" === "order", and what's under the hood does not bother him at all.

Answer 2

you have to prioritize yourself.
Do you need SQW or perfectionism on a project?

Answer 3

MONEY !
I can dig. I can NOT dig.
If a person wants to "poop while standing" - let him pay.
For your money, any whim.
As a rule, dead projects look like this.
I said my opinion. They need it, Don't, it doesn't concern me.
ME - little money NOW.
YOU - crazy profit AFTER the success of YOUR project.

Answer 4

for now, work where it's sad
, look for work where it's fun

Answer 5

That's why they came up with a trial period.

Answer 6

Two things are important for business in projects - economic efficiency and the solution of a specific problem in the shortest possible time (which, in general, also gives an economic effect). It is far from always necessary to do it for a long time, but it is right when the crutch gives the desired result now and does not affect the stability of the overall system.
If you want to write the perfect code, you need to go to open source, where they don’t pay money and you can work for your own pleasure, but from a business point of view, an employee who licks the solution to the ideal costs too much. Bottom line - ideal projects simply do not exist.

Answer 7

There is no definitive recipe here.
Some projects only make sense to maintain and partially refactor, because It is impossible to rewrite perennial monsters and no one will give either time or human resources for this.
Other projects have the opportunity to refactor.
Still others can be completely rewritten.
It is necessary to proceed from a specific situation, but you did not give information on this issue

Answer 8

Look at the leadership. If you have direct access to the director and you can explain to him that this will only bring benefits in the future, then do it, only get approval from him for such changes.
If there is no access to the authorities and you report to the same managers, then work within the framework of the regular stack that is provided to you. Still, you won't be able to improve anything drastically in this case. At least you can make money then.
In any case, your enthusiasm will dry up at some point if barriers are built for you in the form of not taking your steps to improve.

Answer 9

In the question, you yourself painted all the solutions, what's the point of asking us what to choose from your decisions? You yourself know the answer very well.