21–30 of 209 posts
what sucks though is that its super inconsistent whether the thing is gonna throw an error and ruin the flow, whether thats synchronous or async.
The main thing that changed is that the CTO is in more of a "move fast, break things"-mood now (minus the insane silicon valley funding) because he can quickly vibe-code a proof-of-concept, so development gets derailed more often.
That 50% is unit tests.
its really fun, like learning to code again to see what all can be done, an how much more power is available at your fingertips. what sucks though is that its super inconsistent whether the thing is gonna throw an error and ruin the flow, whether thats synchronous or async.
I like that it makes it easy to learn new things by example.
I don't like that I have no idea if what I'm learning is correct (or at least recent / idiomatic), so everything I see that's new, I have to validate against other resources.
I also don't really know if it's any different from "tutorial hell".
As a person I'm increasingly worried about the consequences of people using it, and of what happens when the bubble bursts.
I don't really see it replacing us in the near future though, it would be almost useless if I wasn't there to guide it, write interfaces it must satisfy, write the tests it uses to validate its work etc. I find that projects become highly modularised, with defined interfaces between everything, so it can just go to work in a folder satisfying tests and interfaces while I work on other stuff. Architecting for the agents seems to lead to better design overall which is a win.
I'm just writing crud apps though, I imagine it's less useful in other domains or in code bases which are older and less designed for agents.
My next experiment is designing a really high level component library to see if it can write dashboards and apps with. It seems to struggle with more interactive UI's as opposed to landing pages.