Hah, this is pretty funny.<p>The official AWS account posted a thread to promote their podcast interview with Charity Majors: <a href="https://art19.com/shows/aws-for-software-companies-podcast/episodes/59a5e52f-411e-4017-9bd9-6dc0b9aee027/embed?stretch=true&type=artwork" rel="nofollow">https://art19.com/shows/aws-for-software-companies-podcast/e...</a><p>But they forgot that users who are NOT signed into Twitter don't see threads at all, so it looks to anyone who's follows the link that they just took an official AWS position at odds with the entire industry that they're trying to make billions of dollars from.<p>Here's the full text of that thread:<p>> More AI-generated code doesn't make your team faster. It might actually slow you down.<p>> The real bottleneck was never writing code. It's releasing it, debugging it, & keeping it running well. So when @Honeycombio CTO Charity Majors set a productivity target, she didn't chase 10x. She chose 2x, & built from there.<p>> Her team also skipped the mandates & built a set of AI values instead:<p>> "Every AI output has to have a human owner. If you don't want your name on it, it's probably not good work."<p>> Quality first, quantity second.<p>> Hear how @mipsytipsy built it on the AWS for Software Companies podcast.
No. It makes you faster. You can prove it by looking at the lines of code.<p>Source: Gary Tan, who can write more code than Jeff Dean and John Carmack.<p>If you want to go really fast, you put a Ralph Wiggum dungeon. It's where you orchestrate a team of Ralph Wiggum loops together using subagents to win the economic Darwin Award which companies are handing out for who can burn the most tokens.
You still need domain knowledge and a solid understanding of what you're doing/what you want to achieve.<p>If you don't have that, now that writing code is basically zero-cost now (in terms of time), you'll still be slow.
Yes, we know. Good teams increase the likelihood of success with AI code generation the same way they increased the likelihood of success during hypergrowth: better infra, better devops, better internal abstractions/frameworks/building-blocks/golden-path-tooling that make the "easiest" way the "best" way to do antyhing. Otherwise, you get bogged down in garbage and everything breaks and catches on fire forever.<p>I'm a huge fan of Charity Majors and the quoted line in the next tweet in the thread is one of our team's rules, too:<p>> Every AI output has to have a human owner. If you don't want your name on it, it's probably not good work.
I did not realize it's possible that AI could engage with a project in such a way that Brooks' Law becomes applicable. Fascinating.
This is one sentence.<p>Is this notable because AWS is commenting this?
Ha-ha, I got more:<p>'Skipping tests doesn't make your team faster. It might actually slow you down.'<p>'Developing without requirements doesn't make your team faster. It might actually slow you down.'
`Using AWS services doesn't save you money. It might actually lead to you burning more money.`
'Making your team faster doesn't make your team faster. It might actually slow you down.'
[dead]
How did this get to the front page?
From the FAQ:<p>> How are stories ranked?<p>> The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way. Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action.