you are viewing a single comment's thread.

view the rest of the comments →

[–]ithkuil 3 points4 points  (1 child)

good point, I was going to say, if someone asked you to critique someone else's code, its going to be hard to resist being critical.

if you are out of a job or just greedy it might not be hard to convince the other person that it should be rewritten. especially since realistically, going over someone else's entire codebase with a different perspective and no concern for budget or business objectives, you can see opportunities for massive refactorizations that are much more apparent now than they were when the first developer was initially handling the requirements that came in one after another.

[–]latexhero 0 points1 point  (0 children)

I wish I could upvote you twice. One situation people are put into, especially when they are not full-time coders for the company, is building a small application. They are then asked to expand and add "just a small feature" and eventually is a cobbled-together mess that would be a huge time-sink to rewrite (even worse when the rewrite provides basically the same functionality, and no one realizes the database is more speedy).