This one's neat.

Boundary based development means setup the potential, burn it across a computational boundary, compare the results to your expectations.

i.e test a stateless middleware bit by giving it some context and checking what it returns

I like to see a richer, more artisanal shape to my expects - if the shape looks right, the code probably is too.

Template the tests from set fixtures, then the inputs and outputs can reference the same thing. Keep the tests DRY /and/ useful as documentation

Extend the CLI test runner with a render function to verify and we're off

[now to make the tests pass i guess]

#devops #emacs #platformengineering

From my blog: easy RSS feeds for org-mode websites.

https://thibaut.dev/blog/org-publish-rss.html

#emacs #orgmode #rss

This is cool. I have a system that started as a to-do list and now it's mainly the thing that takes a header and lines. Same shape shows up all over... just go with it when it does.

Take the thing, wrap it in a Web Component, feed it back somewhere else.

In this case, I keep notes about what I'm working on, then occasionally roll them up into a single page with the useful stuff and the constraints the corrections made.

The rest becomes a <task-case> tag at the bottom. The raw work is available, the useful stuff distilled for the next pass.

It's just middleware, your thoughts I mean. When you write you take a thought, compute the next pass, record the output.

Feed forward networks with constraints to funnel the energy

Or markdown with a bit of YAML in it, emacs or web

#wanderland #emacs #orgmode #markdown

So blogmore.el has had a pretty big overhaul with a pretty big breaking change so now we're up to v3.1: https://blog.davep.org/2026/04/05/blogmore-el-v3-1.html

#emacs #lisp #elisp #blogging #ssg #programming

OMG since I have Gnus set up with my email in Emacs, I can store a link to an email, plop it into my personal.org file, and there's a to do list or reminder system!

#emacs #gnus