This thread is great and we can only expect this frontier to accelerate further. a few other tips you'll need to understand to stay ahead of the curve. with these + a few other best practices our 4 person engineering team regularly merges ~1M lines a week. - Computer use has become exceptionally powerful, especially for modern frontend apps when agents can access source code. every surface of your product interface must be easily testable. You'll need scripts to put agents in every scenario accessible by your end users. - any time any engineer opens an ide is an unacceptable devex failure. I maybe open mine once a week. your agents should be able to test every change end-to-end with high confidence across all important dimensions (UI, performance, resource use, etc) - as code accelerates, slop compounds. meticulous systems level review of every change becomes the most important job of any serious IC. github's code review isn't nearly high level enough so you'll need to prompt agents to write detailed and referenced reports with every change ready for your review. - Everything must be framework-ed to hell. Agents must be able to easily make meaningful changes to complex systems without guessing what code organization approach you prefer. - for fellow compatriots in the b2b saas mines. hook your customer ticketing system directly to coding agents. build a 1 step triage agent that takes customer queries and formats them into a coding agent prompt. to continue to win. the activation energy for your company to improve your end user product must round to 0