Maybe it was an elegant one like 184bdd8e5dd39de66d48cd8b5e48d64c1a78d7ef or a more prosaic one like 8834fc4b992220d3eb2679557eccb6654453bfb1, but the result is the same. For me personally, I went as far as pinging all 300 developers on our Slack instance that I wanted adf3e0e8c5ffdc913ccf62cd3b349a1ece09f578, and a couple days later someone took it anyway. And when I asked them [ ]
These days when I’m reviewing a pull request it feels like I’m talking to an AI bot, because I am. When I ask questions like “Why did you decide to do it this way?” I usually get a response (from a human) that has all the tells of AI-speak. But I’m not mad at the human, I’m mad at my tools. I can’t ask the human “Why did you decide to use this library?” because the human didn’t make that decision,…
Oh I just needed something random but also human-readable you said, as you casually called .Substring(8) on a UUID. You probably also casually mutilate animals like you did to that poor UUID. Great job on that name, too, Shakespeare. Item_019b1999 is going to be the next buzzword all the youths are yelling. Very human-readable. Length [ ]
In 2016, Microsoft made a pull request to Node.js that added almost 3 million lines of code. The Node.js maintainers were actually super cool about it, since it enabled Node.js to use Microsoft s pretty decent Javascript engine (ChakraCore) optimized for Windows. They were in a bit of a pickle, however, since they didn t really get [ ]
(Featured image by Camille Couvez on Unsplash) When a measure becomes a target, it ceases to be a good measure But AndyG, doesn t this just encourage a race to the bottom? Aren t we sacrificing quality for speed?
His HolinessCasa Santa Marta00120 Vatican City
I ll compose a new type that holds a Doohickey and also indicates whether the fetch operation succeeded! If you couldn t have a utopia in the real world, then dammit you d have one in your obscure codebase! It shall have clean logic untarnished by dirty, filthy hobbitses error-checking. Something like this:
If there’s an if condition inside a function, consider if it could be moved to the caller instead Finally, I want to briefly return to the notion of testing: Well, the answer to that is the same as the answer to exceptions; strengthen the type returned by the function, and let callers ignore scenarios they [ ]
*I m pretty sure the only way to really tell if an email address is valid is to send an email to it and hopefully not get it bounced back as undeliverable. Regular expressions be damned. *In Haskell, this is only true if you ask it to
Cars People 0 0 1 1 2 4 3 9 4 16 5 25 Number of people on the first N train cars