by memoryleakgame
0 subcomment
- With spec driven development
We are largely now doing proof of functionality and a skim read and making sure it runs locally and deployed to a lower environment
All in all its still time consuming and we have discussed moving to a dark factory but there is still immense value in at least knowing what each file is for and maintaining good isolation of code
by tonkkatonka
0 subcomment
- Maybe.
Humans just can't thoroughly review the amounts of code AI can produce. But the answer is not YOLO and just ship blindly whatever AI created.
The answer is to move the human review/judgment upstream. You review specs. You review the steps. You review the verification rules. You review the contract the code must fulfill.
https://www.latent.space/p/reviews-dead
- I would actually love to see this happen. Mostly for the potential schadenfreude.
by ClaudiuDasca
0 subcomment
- Most AI slop was subsidized by $100 subscriptions. more limits will be added therefore the quantity of AI generated code will either drop or improve, just because writing code is "not free" anymore
but i do hope we will get to a moment where reviewing the code is not the bottleneck anymore (it has always been - just for different reasons)
by i_love_retros
1 subcomments
- My team are just vibe coding now and code review is non existent. Just hit approve. Why should anyone waste their time and brain cells reviewing a massive pile of slop. If management want us to go all in on AI then we will. Full trust in its output. I'm genuinely looking forward to the first major corporate disaster to happen because no one really pays attention to what code changes are being committed. When everything starts collapsing sell popcorn?
- no mention of scaffolding, upversioning old code, porting to new languages, refactoring. Alot of the things we talk about wanting to do are now greased.
a Still requires the engineering, but there seems , escaping the token mill leaves a powerful.
Hacker News