Enjoyed reading “revo, the programming language” post:
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. It’s an analytics “dashboard” so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
…
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around others’ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
I've linked up my blog (jeff-mitchell.dev) to
textlog. I hope to use the two things together now to build a bit more of a writing habit. The 500 character increase is nice, room to breath but not an essay. Gotta build the muscles slowly :)
