3 ms·
I'm not proud of what I did. I was making light of the situation a bit, though. I know intent doesn't carry through the Internet, so I apologize.
by GFischer 13y ago
I'm not proud of what I did.
I was making light of the situation a bit, though. I know intent doesn't carry through the Internet, so I apologize.
- ramses0 13y agoYeah, I debated on whether to post the comment or not, but I felt it was an important point to make, and an opportunity to self-reflect on whether you're proud / happy of your work and how to move forward. I'm also working on a 10+ year old code-base and while I can't always make things "perfect", I always aspire to make things better, and there is no excuse for not documenting (absolutely none, here!), or not writing (unit) tests. In the future: Documentation is CHEAP! Document your functions at least, there is no excuse, and it is helpful to do "README.txt/DESIGN.txt" style documentation / notes and check it in. Unit tests can be expensive, but even simply (1 == expected("input1", "input2") || print "FAIL";) is a 100% valid unit test framework in a pinch. These are very valid techniques to internalize and much better than "but the CTO did it to me first" rationalization.