In this note, I dig into what changed when Runbook went Cloud-Native™: YAML parsers betrayed me, Go contexts stopped working, logs got messy, and yet... orchestration got real. Also, I'm pattenting the BORE acronym, and I still don’t have a database.
A design-first case study in software engineering, told through the process of building my workflow engine. This post explores how deferring decisions, starting from minimal constraints, and focusing on orchestration over tooling can lead to more adaptable systems.
A lighthearted, brutally honest rant about Python from the perspective of an old timer who’s dabbled in too many languages to count. From tuple weirdness to PEP8 gripes, this post pokes fun at Python’s quirks while offering a cautionary tale for those new to the language — or just wondering why their loop variables won’t go out of scope.
Knowing a bit of math, and some set theory, and knowing how computers store numbers, I'm making this bold statement: Computers can't store most numbers. And by
In informal Albanian slang there's a saying. Whenever you want someone to explain a topic in the most simplistic terms, you ask them to "explain it using apples". We had a similar case in my Software Engineering class at UNYT last week, where students didn't totally comprehend the difference between monitoring and observability, not knowing where one ends and where the other begins. So as a good storyteller, if I do say so myself, I came up with the following parable.
If you've followed me for a while, which most likely is the reason why you're reading this, you are familiar with my RLFO newsletter. If not, RLFO (Ralph-o) was my Random Links Found Online newsletter; a newsletter on software and engineering and everything related to it, comprised of articles I found during my usual online scrolling on different platforms, read, and considered interesting enough to share with others.