It’s fine, you only ever need to replace it like once a decade or so
It’s fine, you only ever need to replace it like once a decade or so
“Clearly” is also subjective. What might be perfectly clear to me reading my own code may be really confusing to someone else, and vice versa. Especially if the person reading the code isn’t as familiar with the language as the person who wrote it, or if the code is using some syntactic sugar that isn’t super common, or plenty of other reasons.
I wish my brain worked half as well as guys like that.
Yes. And also comments :-)
Ummmm…Baldur’s Gate 3, anyone? How about Dragon Age: Veilguard? Those are just off the top of my head.
Caveat: I know nothing about 3D printing.
That being said, couldn’t you just print it on its side?
I’ll get right on that, as soon as I wrap up these 3 defects
Hi it’s me, your colleague
I had free laundry for most of my freshman year of college. We had coin operated machines, and somebody quickly figured out that you can strip 2 wires and just touch them together, or touch a coin to both of them, and every time you did that the machine would think a coin had been inserted. Eventually the college caught on and one day I went down there and all the machines were taken apart with maintenance guys working on them, and after that there was a heavy duty housing for the coin acceptor with no exposed wires. It was nice while it lasted!
Code monkey like Tab and Mountain Dew.
I try to write documentation/instructions for dummies, because often, I’m the dummy when I have to dig back into the code again after not touching or thinking about it in months or years.
The worst part about Bitbucket is the horrible, godawful, practically useless search
Let’s not look a
giftGit horse in the mouth.
FTFY
Old habits die hard