Post

I'm slowly but surely forming a better idea how to do "better specs". The key idea is to make them structured and allowing a spec to contain structured source of truth definitions and rich artifacts such as code-defined diagrams, API/CLI/schema definitions, etc.

Johannes Schickling

@schickling.dev

This could look something like "literate TypeScript". A mixture of TypeScript, Markdown and React. Think Jupyter Notebooks but modern and embracing web technologies. Still early days but I'm already working towards this spec-driven vision.

1/6/26, 2:35 pm0 reposts5 likes

Johannes Schickling

@schickling.dev

1 June

Put differently: specs as code

idea.list

@idealistdev.bsky.social

2 June

That reminds me of Allium language I heard about in the last episode of Developer Voices