I feel this post. I am tired of "directing" agents when in reality it feels more like trying to herd a group of toddlers.
Sure they can mostly write better code than a toddler but this constant nudging and reminding and reiterating and stopping them from using the token budget of the whole company for a one off script. It gets tiring and I feel like I am losing brain power while doing it. Maybe it's faster but explosive diarrhea is also a faster way to produce shit.
> Maybe it's faster but explosive diarrhea is also a faster way to produce shit.
i'm in the midst of a very large global roll out of a new system including about 24 separate erp integrations. My team's system is dependent on another system coming online first then we go then the integrations come online then a massive data migration happens and ends with all the associated testing. So like a huge number of dependencies and I'm second in line. Today we get word that the first system is having issues with a vendor and will not come online as scheduled (our dry run deployment is tomorrow and spans all next week as each dependency gets their turn. Week after next is PROD.
We're not heavily integrated into that first system but we are in spots and so there's a reason why they go first. Writing around that system is feasible but we're looking around 5k lines which isn't a lot but there's still testing and sign off. My offshore team is in bed, meanwhile they, and onshore, all have other shit to do anyway so pulling them just puts everything else behind.
I tasked an agents to make the changes as soon as i woke up to the news, they got it mostly right. It took two rounds of fixes with some offshore testers who stayed up late but the PR got in and merged. We just did (literally like 5min ago) a validation run against our target system and we're green for tomorrow. I told the testers to goto bed and then i pulled up HN and opened a coke.
There's no way in hell that would have happened without the coding agents we had on tap. So, yeah, i find a lot of value in the rate at which AI can work on code even if it's not perfect every time.
True, it would not have happened back in the day. But oftentimes what would happen is that sane, sensible leadership would have a talk about delays on the critical path and adjust the schedule accordingly.
Maybe not as satisfying to people who enjoy being heroes. But it would not have been an automatic disaster.
This is partially driven by the good old enterprise game of not being at fault when things go wrong and being able to communicate that to the stakeholders
It's not fancy but it's necessary in a lot of enterprises
BadBadJellyBean · · focus · HN ↗
Sure they can mostly write better code than a toddler but this constant nudging and reminding and reiterating and stopping them from using the token budget of the whole company for a one off script. It gets tiring and I feel like I am losing brain power while doing it. Maybe it's faster but explosive diarrhea is also a faster way to produce shit.
chasd00 · · focus · HN ↗
i'm in the midst of a very large global roll out of a new system including about 24 separate erp integrations. My team's system is dependent on another system coming online first then we go then the integrations come online then a massive data migration happens and ends with all the associated testing. So like a huge number of dependencies and I'm second in line. Today we get word that the first system is having issues with a vendor and will not come online as scheduled (our dry run deployment is tomorrow and spans all next week as each dependency gets their turn. Week after next is PROD.
We're not heavily integrated into that first system but we are in spots and so there's a reason why they go first. Writing around that system is feasible but we're looking around 5k lines which isn't a lot but there's still testing and sign off. My offshore team is in bed, meanwhile they, and onshore, all have other shit to do anyway so pulling them just puts everything else behind.
I tasked an agents to make the changes as soon as i woke up to the news, they got it mostly right. It took two rounds of fixes with some offshore testers who stayed up late but the PR got in and merged. We just did (literally like 5min ago) a validation run against our target system and we're green for tomorrow. I told the testers to goto bed and then i pulled up HN and opened a coke.
There's no way in hell that would have happened without the coding agents we had on tap. So, yeah, i find a lot of value in the rate at which AI can work on code even if it's not perfect every time.
bunderbunder · · focus · HN ↗
Maybe not as satisfying to people who enjoy being heroes. But it would not have been an automatic disaster.
archagon · · focus · HN ↗
ffsm8 · · focus · HN ↗
> My offshore team
This is partially driven by the good old enterprise game of not being at fault when things go wrong and being able to communicate that to the stakeholders
It's not fancy but it's necessary in a lot of enterprises