A senior engineer shares lessons from building a new Go/WebAssembly project (watgo) with significant LLM agent assistance. Key takeaways: keep CLs small and reviewable, maintain a solid test suite before relying on agents, prefer Go for agent-written code due to its readability, and always keep a human in the loop for projects you intend to maintain. The post warns junior engineers against over-relying on LLMs for learning, and cautions that vibe-coding is only appropriate for throwaway prototypes — not production-grade maintained projects.
Table of contents
The processKeeping the human in the loopKeeping the CLs smallTesting strategyLanguage choice - Go for agent-written projectsFinal thoughts98K Impressions2 Comments