We are moving towards software-on-demand

We have stepped into a world, where information tools can, will, and should be built on-demand for the circumstances and situations at hand.

There were a few years where I followed the Docusaurus project closely. I relied on it to make shipping software documentation relatively easy.

Another tool I adored was Kapa.ai - as close to a “drop-in-and-go” AI developer assistant as you could get.

I relied on them because they were tried and tested purpose-built tools with decent communities supporting them that offered 90-95% of the functionality I needed without me having to build anything myself.

And to be clear, there is no way 1 person could build and maintain custom built systems like that.

At least… that’s how it used to be…

I would say the real deep shifts in how we work started around January and February of 2026.

And then last month, April 2026, it became obvious that the scales had completely shifted.

The golden rule that a company should only R&D its own product and source whats already built for auxiliary systems, at least when it comes to software, has crumbled.

I no longer have to settle for compromises when stringing already-built-tools together.

We have stepped into a world, where information tools can, will, and should be built on-demand for the circumstances and situations at hand.

Last month, it took just 2 days to rip out both Docusaurus and Kapa.ai and replace it with a completely custom built system that makes 0 compromises on desired functionality and level of automation.

A validation harness provides assurances that our information assets are in better shape than ever.

At the moment, you still need someone with software engineering experience to steer the iterations is takes to produce something scalable, reliable, and robust. But that gap is diminishing quickly.