4 ms·
You are wrong! The code works. You are hired to make improvements. Do new stuff, and slowly fix up the parts of the code you don't like. What you are describin
by maxklein 16y ago
You are wrong! The code works. You are hired to make improvements. Do new stuff, and slowly fix up the parts of the code you don't like.
What you are describing sounds TYPICAL for what people always feel when they see a large chunk of code they did not write themselves. If you quit here, you will quit most other jobs.
The correct way is to spend a year with the codebase slowly fixing it up, while adding features (which is what you are paid to do). If you still feel the same way after a year, then quit.
For now, you were hired to do a job, and you accepted the challenge. What you see is how code usually looks like! Good code is rare. If you quit everytime you see bad code, I guess you're not cut out for software engineering.
That's like a doctor quitting everytime he gets a bunch of patients who insist on eating junk food and smoking cigarettes.
- imalolz 16y agoI agree - I've been in a similar situation where I inherited a huge chunk of Python code that worked great and played a very significant role in our product's core, but was horrific to understand or maintain (in Python, of all things!). I stuck with it for the past 1.5 years and finally got the green light to rewrite it from scratch. Because I worked so hard to figure out what the hell was going on for so long, the actual coding from scratch took less than a month. Bottom line - if you're being paid well, like the environment and think the company has potential and that you have room to grow there, give it some time before you decide to quit.