My favourite is when you're a solopreneur working in your own repos and still asking yourself "who wrote this shit?!"
On the other end, it's fun when you encounter a bug and go search for an answer and end up reading an answer on Stack Overflow that _you wrote_ 5 years ago and totally forgot about it.
Who wrote this shit?
121–130 of 300 posts
Re: Who wrote this shit?
#122In my first corporate job out of college (a NOC at an ISP) I was asked to update the documentation for troubleshooting quality of service issues. I checked our wiki for what was already there and it horrendous. I started to mentally thrash the person and was going to go confront them about it. When I checked the edit history I was greeted by a single edit and my username a week after I started the job. I learned a gr…
Re: Who wrote this shit?
#123Re: Who wrote this shit?
#124Re: Who wrote this shit?
#125Re: Who wrote this shit?
#126Re: Who wrote this shit?
#127Re: Who wrote this shit?
#128Re: Who wrote this shit?
#129My favourite is when you're a solopreneur working in your own repos and still asking yourself "who wrote this shit?!"
On the other end, it's fun when you encounter a bug and go search for an answer and end up reading an answer on Stack Overflow that _you wrote_ 5 years ago and totally forgot about it.
Re: Who wrote this shit?
#130Earlier quoted context omitted.
I heard a saying once: "all developers should be embarrassed about code they wrote more than a year ago" as a (cheeky) measure of ongoing growth and development. :-)
I've seriously considered removing some of the older semi-popular projects from my github solely because I would be embarrassed to show them to a prospective employer, or even other developers. In the end I think it's actually kind of fun to look back through the code though, and think "surely I should have known about X back then... Why didn't I just do that instead."