Alex Kladov

  1. Mechanical Habits

    My schtick as a software engineer is establishing automated processes --- mechanically enforced patterns of behavior. I have collected a Santa Claus bag of specific tricks I've learned from different people, and want to share them in turn.

    Published

  2. Size Matters

    TigerStyle is pretty strict about some arbitrary limits:

    Published

  3. TigerBeetle Blog

    Continuing the tradition, I've been also blogging somewhat regularly on TigerBeetle's blog, so you might want to check those articles out or even subscribe (my favorite RSS reader is RSSSSR):

    Published

  4. Readonly Characters Are a Big Deal

    I like Emacs UX as exemplified by Magit. I consider it to be a user interface paradigm on the same footing as UNIX pipes: An Engine for an Editor

    Published

  5. Error ABI

    A follow-up on the strongly typed error codes article.

    Published

  6. Error Codes for Control Flow

    Two ideas today:

    Published

  7. On Async Mutexes

    A short note on contradiction or confusion in my language design beliefs I noticed today.

    Published

  8. Look Out For Bugs

    One of my biggest mid-career shifts in how I write code was internalizing the idea from this post: Don't Write Bugs

    Published

  9. Vibe Coding Terminal Editor

    I wrote a small tool for myself as my biannual routine check of where llms are currently at. I think I've learned a bunch from this exercise. This is frustrating! I don't want to learn by trial and error, I'd rather read someone's blog post with lessons learned. Sadly, most of the writing on the topic…

    Published

  10. Ads Are a Positional Good

    Non-technical armchair economics post, where I explain my pet theory for why everything on and outside of the internet is absolutely infested with ads.

    Published