It is very possible to use these tools in the wrong way. Companies that understand how to use AI will do better, those that have these 4 problems won't.
- AI should accelerate your understanding of the codebase and technical concepts.
- Skills should ensure a higher quality of code than you could create without AI
- Engineers should stay responsible for the code they product.
- The available time freed up should be used for communication, product and marketing research. The definition of an engineer who just writes code is something that's going away.
Unless something is so simple that the AI can run it autonomously. There are actually many projects like that these days. And in those cases not looking at the code like DHH does is also a viable strategy.
this is exactly it. smart companies create entire platforms with normalized, context-specific conditions and ever-evolving context for teams to operate effectively with AI in. that means artifacts, tests, ADRs, EDDs, etc. the actual engs are in-the-loop for reviewing all of the outputs, validating it against their taste and judgement, and given sufficient time to do so
seeing AI as an individualized tool for single people to labormax with just means throwing spaghetti at a wall and seeing a lot of failures and incidents (much like my old workplace). it's very different from having a driven and iterative system in place with new processes and checks with clear leadership direction
tschellenbach · · focus · HN ↗
- AI should accelerate your understanding of the codebase and technical concepts. - Skills should ensure a higher quality of code than you could create without AI - Engineers should stay responsible for the code they product. - The available time freed up should be used for communication, product and marketing research. The definition of an engineer who just writes code is something that's going away.
Unless something is so simple that the AI can run it autonomously. There are actually many projects like that these days. And in those cases not looking at the code like DHH does is also a viable strategy.
paimapi · · focus · HN ↗
seeing AI as an individualized tool for single people to labormax with just means throwing spaghetti at a wall and seeing a lot of failures and incidents (much like my old workplace). it's very different from having a driven and iterative system in place with new processes and checks with clear leadership direction