mplorentz on Nostr: Day 2 using Github's spec-kit for development did not go as well. The AI and I got ...
Day 2 using Github's spec-kit for development did not go as well. The AI and I got lost trying to write reams of overly generic TDD test stubs. It felt like the AI couldn't really get a clear picture from just the spec requirements what it should be testing before the actual implementation code was written.
So today I changed course and changed my constitution (the like underlying spec doc for the repo) to use an outside-in development approach instead of TDD and we made a lot of progress. I also got a new playwright MCP set up for browser automation and it's working a lot better than the last one I had. After some considerable setup the LLM was generally able to run the app in the web browser and click around to test its own changes.
Published at
2025-09-24 21:05:25 UTCEvent JSON
{
"id": "c74a158f71ce3bc8260a65c0c617093cf763169e5373e7a18181b58bdc0c9306",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1758747925,
"kind": 1,
"tags": [],
"content": "Day 2 using Github's spec-kit for development did not go as well. The AI and I got lost trying to write reams of overly generic TDD test stubs. It felt like the AI couldn't really get a clear picture from just the spec requirements what it should be testing before the actual implementation code was written.\n\nSo today I changed course and changed my constitution (the like underlying spec doc for the repo) to use an outside-in development approach instead of TDD and we made a lot of progress. I also got a new playwright MCP set up for browser automation and it's working a lot better than the last one I had. After some considerable setup the LLM was generally able to run the app in the web browser and click around to test its own changes.",
"sig": "12ad32b83a9d2fa7aa21af9ccc4e677addfdf71c25f5a49a6155b6f5936f605c69746f74762aea6aced6749d4e4f141bdd986c1f4db84a79fc3650c0061f4eab"
}