One of the exciting things to me about the ai agents is how they push and allow you to build processes that we’ve always known were important but were frequently not prioritized in the face of shipping the system.
You can use how uncomfortable you are with the ai doing something as a signal that you need to invest in systematic verification of that something. As a for instance in the link, the team could build a system for verifying and validating their data migrations. That would move a whole class of changes into the ai relm.
This is usually much easier to quantify and explain externally than nebulous talk about tech debt in that system.
bitwize · 50m ago
Coming up next on Hackernews: Field Notes from Eating Real Pizza Made with Claude:
"The glue adds a flavor and texture profile that traditionalists may not be used to on their cheese pizza. But I've had Michelin-star quality pizzas without glue in them that weren't half as delicious as this one was with. AI-mediated glue-za is the future of pizza, no doubt about it."
sdorf · 21m ago
The whole point seems to be how to get the most out of today's tooling without "glue getting in your pizza". It's a little flag-wavy (probably because of the author's company) but overall seemed like a pretty candid peek into how it's being used. Did you have a specific critique?
But, there are a few nuggets we figured are worth sharing, like Anchor Comments [1], which have really made a difference:
‘’’CLAUDE.md
### Anchor comments
Add specially formatted comments throughout the codebase, where appropriate, for yourself as inline knowledge that can be easily `grep`ped for.
### Guidelines:
- Use `AIDEV-NOTE:`, `AIDEV-TODO:`, or `AIDEV-QUESTION:` as comments for both AI and developers.
- *Important:* Before scanning files, always first try to *locate existing anchors* `AIDEV-…` using grep in relevant subdirectories.
- *Update relevant anchors* when modifying associated code, after finishing any task.
- Make sure to add relevant anchor comments, whenever a file or piece of code is:
‘’’[1]: https://diwank.space/field-notes-from-shipping-real-code-wit...
You can use how uncomfortable you are with the ai doing something as a signal that you need to invest in systematic verification of that something. As a for instance in the link, the team could build a system for verifying and validating their data migrations. That would move a whole class of changes into the ai relm.
This is usually much easier to quantify and explain externally than nebulous talk about tech debt in that system.
"The glue adds a flavor and texture profile that traditionalists may not be used to on their cheese pizza. But I've had Michelin-star quality pizzas without glue in them that weren't half as delicious as this one was with. AI-mediated glue-za is the future of pizza, no doubt about it."