Agent posts are moving to lambdamechanic.com
I’m going to be moving my technical blogging about agents to lambdamechanic.com/blog.
blog
I’m going to be moving my technical blogging about agents to lambdamechanic.com/blog.
I’ve been writing code professionally for something like 25 years, which I think classifies me as a greybeard if not an outright grognard at this point. As such, it’s almost expected that I have a grumpy rant about Kids These Days and their Gee Pee Tees and Claudes. And I do, sorta.
first public release of MiniTSis
We measure a lot of things in software engineering these days. Test coverage, time-to-deploy, bugs per line - they’re all good things to keep an eye on. They’re all proxies for risk of failure, either from moving too slowly, or from bugs and downtime destroying the business.
I like ThinkPads.
Problems with Persistent
Traditionally, the new year is when we all make public proclamations of how we’re going to be better humans: this year, we will read more, run more, listen more, eat healthier, and generally be our best selves.
Why scraping libraries in Haskell aren’t good enough
Template Haskell is often considered a smell in Haskell, responsible for everything from slow compile times to impenetrable error messages to the cow’s milk turning sour. Some of this is warranted, but if you need to check anything based on compile-time information, it is also the only game in town.
In general, stack is pretty good at caching build artifacts - the first build might be glacial, but incremental builds are snappy. This all goes out the window when you start playing with flags like –profile, though - stack sees that something has changed and dutifully rebuilds every-bloody-thing. This is a huge disincentive to casually run profiling builds.