|
|
|
|
|
|
by zionsati
2 days ago
|
|
|
I think that's all correct what they're saying. It's not contradictory - writing code has become a commodity to a certain extent. But someone's still responsible for the production systems when it fails. AWS had a couple of big outages last year because of AI. Even with humans reviewing it, review is review. If you're not writing the code, you'll not have spent enough time thinking about edge cases. That's where the most expensive part of software engineering, not coding. Coding being a commodity is indeed analogous to robots in the production line, but those robots have huge teams of mechanical engineers to keep them running. The calibration, the servicing etc. What's most interesting is now that vibe coding is expensive, will the AI slop go away, gradually? |
|
|
"But someone's still responsible for the production systems when it fails. AWS had a couple of big outages last year because of AI. Even with humans reviewing it, review is review. If you're not writing the code, you'll not have spent enough time thinking about edge cases.". This is true and we cover software quality in the age of AI (https://youtu.be/oOt_0N1yQEw?t=2915).
"What's most interesting is now that vibe coding is expensive, will the AI slop go away, gradually?" As we said in this episode, "sometimes, AI is getting more expensive than paying a salary to a software engineer". We cover it here as well (https://youtu.be/oOt_0N1yQEw?si=r5tSHicWpJGWLQDL&t=3890) about AI real cost and AI cost effectiveness