Dividing Tech Responsibilities and Leveraging AI Tools
Ready for Phase 2 of our AI product development experiment! Getting away from cowboy vibe-coding, we restart with more traditional best practices - dividing core backend development and front-end vibe-coding. Both with much more rigor.
Post hedonistic vibe coding extravaganza, I reconnected with the team and discussed what the next steps might be.
Full disclosure: “The team” at this point was myself and my childhood friend, Christian. Definitely more Poppy and Ian from Mythic Quest than Band of Brothers.
Phase 1: Christian’s Tech and Data Pillars
The plan was to start from scratch and to break out responsibilities into two areas.
Christian, as the tech and data savant, would work on the core, tech-heavy pillars of Burrow using console-driven AI coding-assisted tools.
Initially, this would include populating our database with local places and events using rigorous engineering best practices and proper code review. Down the road, he would own other pillars that require rigorous engineering oversight, such as search algorithms.
Phase 1: My Frontend Development Approach
I would dust off whatever software development skills I could remember, return to Replit, and take a more methodical approach to development - supercharged with AI.
Our foundation would be strong (thanks to Christian), and we’d see what happened with my more methodical frontend development approach.
Fingers crossed.
