If I had a dollar for every time I proposed spending more time on something to make it flexible and able to grow but being told to “hard code it” to save time, I’d have several dollars. If I had a dollar for every time I had to patch that 6 months later, I’d have several more dollars.
You couldn’t pay me enough dollars to cover the therapy caused by having to maintain the “flexible” code that added complexity and abstraction for a single use case that was never expanded to handle more.
My bank requires your password to contain NO vowels. I always forget when I update the password (forced to every 3 months) and the error never mentions it.
I’m struggling to think why this would be a thing. The only guess I have is someone was told to enforce “no dictionary words in a password” and saw that as an ‘easier’ way to implement?
Same for C, & yields a pointer to a value, and * allows you to access the data. (For rust people, a pointer is like a reference with looser type checking)
my favorite name origin for a bit of software relates to the text editor nano. nano was written as a standalone clone of Pico, as a play on metric prefixes, but Pico is actually Pine compositor, part of Pine, an email client. Pine itself was based on an earlier email client called Elm, and has been attributed as various recursive acronyms such as ‘Pine Is Nearly Elm’
honestly with Go in general I’m in a perpetual cycle of being annoyed with it and then immediately being amazed when I find some little trick for efficiency - with stringer interfaces and the like
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.