Timeline for How do you stay productive when dealing with extremely badly written code?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2011 at 17:56 | comment | added | Dan | @Ramhound, there are no tests for this project, and I don't want to be responsible for ruining the system for the sake of cleaner code. There are many cases when current code implies exceptions being swallowed, or else relies on other kinds of bad behavior which is not obvious. This is one of the reasons I'm adding logging, by the way. | |
| Feb 22, 2011 at 17:44 | comment | added | davidhaskins | @Ramhound I'm betting there won't be any code reviews. I bet there won't be any formal integration testing. I've worked in these positions a few times. Generally people only want code that works good enough, and they want it as quickly as possible. Explaining "best practices" is like talking to a wall, IMHO. | |
| Feb 22, 2011 at 17:43 | comment | added | davidhaskins | @gaearon ah-ha! You're the only coder. So the guy before you was the only coder. You can get away with a lot when you are the only coder (as you've noticed from your predecessor). Keep this in mind when you look for your next job. ;) | |
| Feb 22, 2011 at 17:16 | comment | added | Ramhound | @gaearon - What prevents you from implementing your 2 line solution? You need to figure out how to do what you were tasked to do, the problem with the code can be solved later, when you are not in the client's office. You should keep your notes on what you did, how something works, so you can go back later in the future and implement your changes so code review(s) and integration testing can be done. | |
| Feb 22, 2011 at 17:04 | comment | added | Dan | Yes, I'm working by chunks, and I already have been working on it for some time so I have a rough idea about each component. Still, it doesn't help much because it's the tiny pieces of logic that usually take time to understand—and I get angry when I realize that 30 line method I spent 10 minutes on can actually be re-written in 2 lines. As for the company, unfortunately, I'm the only developer on this project, and I'm currently working in client's office so there's no one I could really talk to. | |
| Feb 22, 2011 at 16:59 | history | answered | davidhaskins | CC BY-SA 2.5 |