Journal · Series · 5 parts
StellarView Alpha
- Part 1 the plan asked 357 questions and refused to answer 281 of them
We pointed StellarView at Conduit, the most-implemented demo application on the internet, and asked for it as an operated platform rather than an app. It produced ten phases, 106 work units, and 357 questions it would not guess at.
- Part 2 it read a Dockerfile I had committed an hour earlier
A plan for a ten-phase platform produced 357 questions and refused to answer 281 of them. One had opened the repository, noticed docker-compose declared a build for a service whose Dockerfile did not exist, and asked who owned it. I had committed that file an hour before and left it unfinished.
- Part 3 ten issues, three passes each, and the branches are stacked
Twelve hours and eighteen minutes, unattended, including two billing stops and a restart. 268 files, 25,857 lines, ten pull requests. CI green through phase eight and red on nine and ten, which we are leaving in.
- Part 4 it documented the trap, then shipped the default that walks into it
Phase five wrote its own Terraform. Sixty five resources stand in a real AWS account behind a real certificate, and the application returns 503. The reason is a variable whose own description explains, in detail, why its default cannot work.
- Part 5 their suite failed us by one request
The published RealWorld suite: 13 files, 154 requests, no accommodations. It failed on the first run today because our rate limiter allows 20 anonymous writes and the suite makes 21. Then 13 of 13 in 912ms. Plus the part nobody talks about, which is who keeps a spec alive for a decade.