Feb 24
Loading video player...
I decided to Open Source my config/skills: https://github.com/nathnotifia/ai-coding-workflow - also since this video I have added a pre-dev stage called 'Engineering Manager' that has been pretty good. Telegram Group for AI Developers: https://t.me/+Rsq5TI9nWUA5MjEy This video covers some of the workflows I've come up with for bulk managing agents in software projects. I may do another video on this but one of the other major things I didn't speak about is implementing automated check (CI) whenever you write/deploy new code. I think this is something most new Vibe Coders won't have any experience with so I will leave some notes on best practices that have worked for me. 1. Use a lint tool, I'm currently using Ruff for my Python project but loads exist for JS too. 2. Hard Limit max file size to 800 lines, and max function length to 80 lines. This limits your agents making files that are 2000+ lines that they simply can't work with or understand due to limited context window. Instead get them to break down 'god files' into clean and module designs. Do this from day 1, it's very time intensive to refactor your entire project to meet these requirements and you also create risk of things breaking (I've been dealing with this for the past week) š. 3. Use an engineering manager to pre-review all specs immediately before they are assigned to the dev agent, the engineering manager review implementation plan and how this change will effect other code and give a higher level scan before passing on to the coding agent. 4. Use a QA agent prior to merging code with its own isolated context window. 5. Build a Script that checks folder structure / layout at deployment time. If you are doing an AI only workflow, as the project grows it become almost unmanageable and a complete mess. CI scripts helps enforce a clean and logical folder structure and layout that agents cannot bypass and will follow automatically. 6. Write a lot of tests. I'm currently enforcing 80% test coverage. Also by breaking up the function size (see point 2) so each function has a specific purpose it becomes easier to run tests. 7. Use BetterStack/Sentry for in production error tracking, you can give your agents MCP access so they can see exactly what's going on. Happy building :) ____________ š Links - Email Newsletter: https://nathaston.beehiiv.com/subscribe š Most Popular Videos - Building an OnlyFans Agency: https://youtu.be/50e0cZtcWjg - Growing a OnlyFans Model to $2k/day in 11 days: https://youtu.be/PbiJln6QP9s - How I became an Entrepreneur: https://youtu.be/hkAhrQiBudI - Ultimate Notion System: https://youtu.be/InxxJYS1_RI