Member-only story
You will be a patching monkey, get rid of it and do this (Especially to junior dev)
Beginning
After 14 years of work. I have seen enough s**t happening. And many times, when It happens to a developer, who does not even realize it.
In this post, I want to highlight one of the most dangerous situations I have seen which could happen to any developer right now. especially to those junior devs.
If you are in such a situation, get out, and change the project or team, or company.
Whatever It takes.
This is why.
What is patching hell
As you can see. when S**t happens.
- Only one dev involved, (yes, poor dev)
- Fix immediately, poor fix without enough testing
- knowledge is NOT shared with anyone, so when It happens again, this same poor dev is the only one who knows how to fix it
- and continue this poor life for many cycles
- After a few months
- No teamwork, alone.
- Learned nothing, documented nothing, poor quality of code, no test
- A patching mindset created