3 ms·

- Real products get cruft. Developers always complain about the state of things. - Everybody writes bad code, and you learn and get better as you go along. If

- Real products get cruft. Developers always complain about the state of things. - Everybody writes bad code, and you learn and get better as you go along. If something is bad and you can see that and take responsibility, that sounds good, and it sounds like you have learnt and become better. You don't need excuses like "personal issues". - You aren't always going to be as smart or good as your colleagues, sometimes you just have to come to terms with that. - Major refactors of a product are rarely the right way to go. If you can do it progressively and gradually that is almost certainly the better approach. - Almost zero percent chance you will find a "fresh" codebase in any new job. A change can be helpful, but it doesn't change yourself. Good luck with it. Happy New Year.

Trasmatta 4y ago
> You don't need excuses like "personal issues". For what it's worth, that was not an excuse I would give to anybody on the team, but just an honest look at one of the underpinning factors that I can more easily bring up in an anonymous forum. I can do better than I did, but I was barely keeping it together mentally for large portions of this year. > Almost zero percent chance you will find a "fresh" codebase in any new job I mainly meant fresh as in "fresh / new to me", rather than "fresh / pristine" codebase (which doesn't really exist). > Good luck with it. Happy New Year. Thank you!
- throwawaylinux 4y ago
  I wasn't trying to say that was invalid or made up that you were going through those difficulties and I'm sure it can impact work. My point was more that I don't think it's helpful to consider it a failing due to factors out of your control. If your old code sometimes makes you cringe or think of various things that you would have done differently and better, that's evidence that you've been learning and improving. It's healthy for everyone to feel that sometimes and be able to reflect and critically evaluate their own work (though maybe not to the level that you're taking it).

Trasmatta 4y ago

> You don't need excuses like "personal issues". For what it's worth, that was not an excuse I would give to anybody on the team, but just an honest look at one of the underpinning factors that I can more easily bring up in an anonymous forum. I can do better than I did, but I was barely keeping it together mentally for large portions of this year. > Almost zero percent chance you will find a "fresh" codebase in any new job I mainly meant fresh as in "fresh / new to me", rather than "fresh / pristine" codebase (which doesn't really exist). > Good luck with it. Happy New Year. Thank you!

throwawaylinux 4y ago
I wasn't trying to say that was invalid or made up that you were going through those difficulties and I'm sure it can impact work. My point was more that I don't think it's helpful to consider it a failing due to factors out of your control. If your old code sometimes makes you cringe or think of various things that you would have done differently and better, that's evidence that you've been learning and improving. It's healthy for everyone to feel that sometimes and be able to reflect and critically evaluate their own work (though maybe not to the level that you're taking it).