Bringing up, configuring, debugging and moving files between game servers, setting up and managing backups, automating complex and non deterministic jobs between multiple servers with changing files, deployment of personal projects on their respective vms. Far better deep research and prototyping of questions I have that require cloning repos or spinning up vms. I could think of more.
Issue with @mattpocockuk to-issues style of coding is the fact that an agent will take a vertical slice too literally. E.g. for me, it just plonked something in main.c, and when I poked it, it said "yeah this is just to get issue 05 done but should be refactored later". It takes every issue as a small separable slice and assumes that you will be refactoring it into a good architecture later rather than doing it right then first time.
@otecart@haydendevs I think that may be worse as your comment makes no sense haha. I think my initial comment is relatively clear, and everyone knows what "making architectural decisions means"
@codeHusky OH NO NOT AN AI COMPANY HOLY CRAP BRO YOUR KIDDING?!? AN AI COMPANY?? A COMPANY THAT IS AI? THIS GUY OWNS A COMPANY WHOCH IS FOCUSED ON AI?! YOU ARE KIDDING RIGHT? AI?!! BRO THINK OF THE WATER I CANT BELIEVE THIS GUY ISNT THINKING OF THE WATER