# Random Scala Tip #534: Adopt an Error Handling Convention for `Future`
7 min read
When working with `Future` be explicit about your error handling convention, and make sure your whole team and codebase are aligned to it.
# Make Illegal AI Edits Unrepresentable
32 min read
These are strange times we're living in. We have unleashed an army of junior developers on our codebases while changing little else, yet we expect everything to just be okay.
# First Make It Correct
73 min read
Way back in December, in the spirit of the times (it seems that everyone was either solving Advent of Code or looking for a job), like an elephant in a china shop, I found myself solving a…
# Random Scala Tip #624: The Pitfalls of Option Blindness
7 min read
Before wrapping anything in `Option`, consider whether you should use a more meaningful domain-specific data type instead.
# Whiteboxish Macro Powers with Named Tuples
11 min read
I've recently stumbled upon a post on Scala Contributors by Kit Langton describing how he managed to create the illusion of adding automatically derived (publicly visible) members to a companion of a…
# Random Scala Tip #568: Beware of Leaking Iterators
5 min read
Beware of leaking `Iterator` instances outside the scope you initialized it in.
# Random Scala Tip #697: Avoid Anonymous Functions as Dependencies
6 min read
Avoid using anonymous functions as class dependencies.
# Purify Your Tests Episode IV: The Monoids Strike Back
21 min read
Welcome back to yet another episode of test purification. In the last part we explored another benefit of adding type parameters to our code, the ability to work with very lean mocks. It's been a…
# ANY Overloading Considered Evil
18 min read
This is not just clickbait, I really do mean that ANY form overloading in programming should be considered evil.
# Purify Your Tests III: Lean, Mean Testing Machine
13 min read
In the last part we saw how to make our code more declarative, and the tests more functional by introducing type parameters for the inner data flowing through our code. In this part we are going to…
