@lovelacecoding I'll do you one better
@lovelacecoding I feel the same way about code I wrote more than a week ago.
@lovelacecoding Code is a one-way hash of thought. It's a cryptoanalysis effort to get back to the "clear text."
@lovelacecoding funny, it looks exactly like the pie chart of debugging my own code
@lovelacecoding Just last week I was debugging code where some monster used If(var<1) when var was boolean.
@lovelacecoding when approving a junior dev's code
@lovelacecoding I’m not sure to what part I belong to 🤔
@lovelacecoding Let's face it, code is personal and pure magic. It should just work, no to be understood by anyone else.
@lovelacecoding Someone else going through your code
@lovelacecoding You forgot “fucking idiots, all of them”
@lovelacecoding Debugging the code I DID write.
@lovelacecoding I'm 100% at a point in my career where I'm burnt out on building new things and would much rather do code review and debugging issues. That being said... This image rings 110% true still. Just gotta make it work though.
@lovelacecoding Expert advice of the day : print is your friend … (or maybe does not exist in Microsoft land ?)
@lovelacecoding Hahah that’s me reading code -I- wrote
@lovelacecoding I have on multiple occasions said what dumbass wrote that code. Then I looked at the code, it was me, I’m the dumbass.
@lovelacecoding Yeah, could you imagine if people coded with comments first. Everybody would have a happy time.
@lovelacecoding Honestly this is where chatgpt comes in clutch. I could take my time to understand and read the code or get chatpt to do that for me in a second then just double check if that's actually right.
@lovelacecoding Except when you do "git blame" you see that it was you who wrote it 6 months ago.