HERE, HERE!!!
Who wrote this shit?
61–70 of 300 posts
Re: Who wrote this shit?
#62The Dunning-Kruger effect is real.
Re: Who wrote this shit?
#63My favourite is when you're a solopreneur working in your own repos and still asking yourself "who wrote this shit?!"
I'm not a solopreneur but instead a corporate drone, and every time I git-blame questionable code, it's mine. But like others have said, if you're not embarrassed of something you wrote a year ago, that's not good.
Re: Who wrote this shit?
#64I find it a refreshing experience to look at your own code from 10 years ago, or even 5 and think "Who wrote this shit?". If I ever look at some of my old code and feel good about it, that means I have failed to improve.
I find that half the time I'll wonder who wrote it, realize I wrote it, start to rework it, and then realize why I wrote it that way in the first time, add a comment and move on.
Same here. Sometimes I add comments like "don't change this shit!" to remind myself that there is a reason why it is like that.
Re: Who wrote this shit?
#65Let's face it: often (a) getting it done is more important than (b) getting it right. Often (a) is not only faster but also is the only way to get to profitability. Unless you write code that is touched many times or is performance critical, (b) will only add costs in the short term. Even if you spend more time fixing (a) later, it's often worth it because it made more money than it costs to fix it or your company wouldn't even be there, if all code would have to be of type (b)
Re: Who wrote this shit?
#66I was surprised you didn't find your name, because I did and it was like 6 months ago and for the life of me I couldn't understand why I did this stupid thing I did then.
I found that usually code written around and after 4pm tends to be like that and generally try to avoid more serious stuff in late PM.
Re: Who wrote this shit?
#67Re: Who wrote this shit?
#68I think it is generally a sign of maturity when a developer recognizes the flaws with their software and desires to improve them rather than piling on new features. Cynically asking "who wrote this shit?" is probably not a very mature way of expressing that, though. In my experience, finger pointing does more harm than good. If a particular developer is consistently producing bad work that is hurting the project, that should be evident by reviews of their new work - not their legacy code. IMO once code has passed review and entered master/trunk/production it should be considered the team's code - not an individual's.
Re: Who wrote this shit?
#69My favourite is when you're a solopreneur working in your own repos and still asking yourself "who wrote this shit?!"
While I am not solo, I have still been around for longer than anyone and the primary maintainer of a few repos. I tend to skip straight to "WTF was I thinking", because if its weird it was definitely me.
Re: Who wrote this shit?
#70Asking who wrote this shit is useless.
However asking "what is this shit" is a perfectly valid thing to do.
There are good developers producing crap due to constraints.
There are also other developers producing crap because they can't produce anything else or just don't give a damn.
Being able to differentiate between the two is often helpful, hence the "what" question.