Post

Increasingly convinced that specs are now the source and that code is an artifact akin to a lockfile.

Isolating a program from complex systems for testing is a lot of effort. Often solved with dependency injection of mocks, or exterior composition (to mocks). Mocks can drift and DI introduces codepath complexity. So: Build mock env from specs

Distributing software libraries for multiple languages is extremely costly for a software company (such as bluesky). Quality drifts between languages, maintenance burden is huge. So: Build _ API in our teams' lang from specs

This one might be too extravagant so we'll see, but... Writing software for each platform (native ios, native android, web, etc) is extremely costly and requires middleware ecosystems like react native So: Build app for target platform from specs

TFW we all use IDL for specs to make ambiguities clear ftp.kaist.ac.kr/ietf/draft-f... youtu.be/fYw-0Qu0WCo

the qps on this one are pretty comical. you never know what's gonna set people off

I was labelled spam for promoting this idea that the specs are the new valuable artifact. good luck in the comments ;)

one thing that may threaten people: if specs are the valuable artifact, couldn't you 1) have frontier LLM describe all the specs of an enterprise SW app by analyzing its surface, docs, input, output 2) have LLM recreate that enterprise app's full functionality, writing the underlying code itself