|
I honestly don’t understand what people are on about. As a dev with 40+ years behind me, I apply the same skills and tools to LLMs as I would to a small team of junior devs, except with a higher degree of rigor. I don’t feel that my skills are atrophying, in fact I’ve learned a bunch of new stuff in the process. Depending on the work, I’m producing about 4x what I would have with a small team, and it is better code, better documented, more modularity, and less bugs than I was shipping with humans. You have to keep a tight OODA loop, and write the code in specifications, protocols, interfaces, and implementation plans before the first executable
line is put down. Iterate the code and docs together to minimize and document drift. Treat a context window as a session. When it’s full, you start over with a new session, bring in the onboarding documentation, and go to work. I never cross context boundaries midstream, it’s always a disaster. 1m context is critical, I burn 150k just onboarding and orienting a new session. Still shipping 4x at 1/10 the cost, and less bugs in the field (greenfield firmware development) |