Andy G's Blog

https://gieseanw.wordpress.com/ (RSS)
visit blog
Why that one coworker got fired for no reason
24 Oct 2024 | original ↗

(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?

How to make Product give a shit about your architecture proposal
10 Oct 2024 | original ↗

His HolinessCasa Santa Marta00120 Vatican City

You probably wrote half a monad by accident
25 Jun 2024 | original ↗

“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:

Don’t push ifs up, put them as close to the source of data as possible
24 Jun 2024 | original ↗

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 […]

Smart Constructors
30 Nov 2023 | original ↗

*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

Uniform random sampling on a disc
15 Oct 2021 | original ↗

Cars People 0 0 1 1 2 4 3 9 4 16 5 25 Number of people on the first N train cars

Friendly reminder to mark your move constructors noexcept
29 Aug 2020 | original ↗

Just put noexcept on your move constructors. Better yet, let the compiler do it.

Cracking the code review (Part 4): Conflict management
26 Jun 2020 | original ↗

*There is an excellent documentary called Behind the Curve where you can witness Flat Earthers do this exact thing when their experiments only continue to prove the earth is round.

Cracking the code review (Part 3): Be proactive
26 Jun 2020 | original ↗

Next entry: Conflict management

Cracking the code review (Part 2): Make them seem small
26 Jun 2020 | original ↗

*Purely from an understandability point-of-view. As a side effect, you often end up with code that’s easier to test and maintain. *It turned out the developer both didn’t know that standard functions existed for all of this *and* they thought that even if the functions did exist, the developers’ code would be faster (it wasn’t). […]

Cracking the code review (Part 1): Smaller is better
26 Jun 2020 | original ↗

Next entry: Make them seem small

↑ these items are from RSS. Visit the blog itself at https://gieseanw.wordpress.com/ to find other articles and to appreciate the author's digital home.