Live data from Hacker News

Development speed is not a bottleneck

pawelbrodzinski.substack.com

141–150 of 153 posts

Re: Development speed is not a bottleneck

#141
post #92

Earlier quoted context omitted.

No, it's because reading code is slower than writing it. The only way these tools can possibly be faster for non-trivial work is if you don't give a shit enough about the output to not even read it. And if you can do that and still achieve your goal, chances are your goal wasn't that difficult to begin with. That's why we're now consistently measuring individuals to be slower using these tools even though many of the…

"Consistently"? Is there more than just the one METR study that's saying this?

I have measured it myself within my organization, and I know many peers across companies who have done the same. No, I cannot share the data (I wish I could, truly), but I expect that we will begin to see many of these types of studies emerge before long.

The tools are absolutely useful, but they need to be applied in the right places and they are decided not a silver bullet or general-purpose software engineering tool in the manner that they're being billed at present. We still use them despite our finding, but we use them judiciously and where they actually help.

Re: Development speed is not a bottleneck

#142

Earlier quoted context omitted.

So you want Aider, Claude Code or opencode.ai it seems. I use opencode.ai a lot nowadays and am really happy and productive.

I really wanted to use Aider. But it's impossible. How do people actually use it? Like, I gave it access to our code base, wanted to try a very simple bug fix. I only told it to look at one service I knew needed changes, because it says it works better in smaller code bases. It wanted to send so many tokens to sonnet that I hit the limits before it even started actually doing any coding. Instant fail. Then I just ran…

I don't know about Aider, I am not using it because of lack of MCP and poor GitHub Copilot support (both are important to me). Maybe in the future that will get better if that will be relevant. I am using opencode.ai with Claude Sonnet 4 usually. Sometimes I try to switch to different models, e.g. Gemini 2.5 Pro, but Sonnet is more consistent for me.

It would be good to define what's "smaller code bases". Here is what I am working one: 10 years old project full of legacy consisting of about 10 services and 10 front-end projects. As well tried it on project similar to MUI or Mantine UI. Naturally on many smaller projects. As well tried it on TypeScript codebase where it has failed for me (but it is hard to judge from one attempt). Lastly I am using it on smaller projects. Overall question is more about task than about code base size. If the task does not involve loading too much context when code base size might be irrelevant.

Re: Development speed is not a bottleneck

#143
post #139

Earlier quoted context omitted.

Again let’s look at YC’s latest batch of companies. How many of them are doing anything “innovative”? An innovative product is one where customers in aggregate are willing to pay more for it than it costs to create and run. Any idiot can sell a bunch of dollar bills for 95 cents. Going back to the latest batch of YC companies, there value play can easily be duplicated by any company in their vertical either by throwi…

The last YC batch was like ~170 companies, correct? Each year, there are like 150 million startups. So let's not take YC stable for the whole startup ecosystem. And I'm with you with a critical view on their all-in move toward AI. It's just what all the VCs do, and it's hard to say who's parroting who in this setup (I think that others are parroting YC, but feel free to challenge me on that). Having said all that, I…

Let’s look at YCs “successes” as far as the companies that have gone public.

https://medium.com/@kazeemibrahim18/the-post-ipo-performance...

Re: Development speed is not a bottleneck

#144

It's completely absurd how wrong this article is. Development speed is 100% the bottleneck. Just to quote one little bit from the piece regarding Google: "In other words, there have been numerous dead ends that they explored, invalidated, and moved on from. There's no knowing up front." Every time you change your mind or learn something new and you have to make a course correction, there's latency. That latency is ju…

> The way to find the right answer isn't to think very hard and miraculously come up with the perfect answer. It's to try every goddamn thing that shows promise.

I have found that spending more time thinking generally reduces the amount of failed attempts. It's amazing what "thinking hard" beforehand can do to eliminate reprioritization scrambling.

Re: Development speed is not a bottleneck

#145
post #92

Earlier quoted context omitted.

> I almost feel less productive using modern GPT-5/Claude Sonnet 4 for software dev than prior models, precisely because they are more hands off and less supervised. That is because you are trained in the old way to writing code: manual crafting of software line by line, slowly, deliberately, thoughtfully. New generations of developers will not use the same workflow as you, just like you do not use the same workflow…

No, it's because reading code is slower than writing it. The only way these tools can possibly be faster for non-trivial work is if you don't give a shit enough about the output to not even read it. And if you can do that and still achieve your goal, chances are your goal wasn't that difficult to begin with. That's why we're now consistently measuring individuals to be slower using these tools even though many of the…

> No, it's because reading code is slower than writing it.

This feels wrong to me, unless we qualify the statement with: "...if you want the exact same level of understanding of it."

Otherwise, the bottleneck in development would be pull/merge request review, not writing the code to do something. But almost always, it's the other way around - someone works on a feature for 3-5 days, the pull/merge request does not really spend the same time in active review. I don't think you need the exact same level of intricate understanding over some code when reviewing it.

It's quite similar with the AI stuff, I often nitpick and want to rework certain bits of code that AI generates (or fix obvious issues with it), but using it for the first version/draft is still easier than trying to approach the issue from zero. Ofc AI won't make you consistently better, but will remove some of the friction and reduce the cognitive load.

Re: Development speed is not a bottleneck

#146
The argument that the article uses to critique AI coding is that coding is not the bottleneck, instead the testing and validation of ideas is.

This is a first-degree smart argument. It presents a seemingly non-obvious idea that makes sense in retrospect.

However I happen to work at the experimentation team of a hyperscaler so I have a different perspective.

First, we aren't always saturating all of the potential experiments we could be running. The reasons are different, but essentially it takes time and effort to build those experimental features. If that cost trended to 0, we could make sure to have a queue of experiments deep enough.

Also in our side we need to do development work to support new features and products. We have a backlog long enough to keep us perpetually busy. If dev cost trended to 0, we could always be ready to provide our customers what they need.

Speaking of new products, each one our company comes up with comes with extra effort to support in our side, and yet more effort to produce dozens of AB test to validate new functionality.

This is not talking about ongoing maintenance effort. Bugfixes, upgrades etc. take a non-trivial amount of effort to keep up.

And this is only inside our little experimentation team. What about security, reliability, scalability, efficiency... it makes me wonder if OP has experience running products at scale.

Instead I'd like to think that dropping the cost of development by orders of magnitude changes the equation of how we create products.

Re: Development speed is not a bottleneck

#147

Earlier quoted context omitted.

The verbose LLM approach that Cursor and some others have taken really annoys me. I would prefer if it simply gave me the results (written out to files, changes to files or whatever the appropriate medium is) and only let me introspect the verbose steps it took if I request to do so. That’s what slows me down with AI tools and why I ended up sticking with GitHub Copilot, which does not do any of that unless I prompt…

So you want Aider, Claude Code or opencode.ai it seems. I use opencode.ai a lot nowadays and am really happy and productive.

At the end of the day I want what my job is willing to pay for, which is a few different flavors of AI tools

Re: Development speed is not a bottleneck

#148
post #139

Earlier quoted context omitted.

The last YC batch was like ~170 companies, correct? Each year, there are like 150 million startups. So let's not take YC stable for the whole startup ecosystem. And I'm with you with a critical view on their all-in move toward AI. It's just what all the VCs do, and it's hard to say who's parroting who in this setup (I think that others are parroting YC, but feel free to challenge me on that). Having said all that, I…

Let’s look at YCs “successes” as far as the companies that have gone public. https://medium.com/@kazeemibrahim18/the-post-ipo-performance...

YC couldn't care less how well these companies fare post-IPO. Post-IPO, their job is essentially done, and they cash their investment.

They're probably busting champagne if the peak valuation is instantly after IPO. That means they maximized the potential payoff.

You're right that one perspective to consider how well these companies are doing is to look at their continuous growth, and that includes post-IPO valuation.

At the same time, YC backed a couple of dozen unicorns. Including those that, despite having a valuation lower than at the time of their IPO, are still in the 10-digit range. Well, I'd be the last one to complain if I got to seed fund a company that ended up at $50B+ valuation.

Having said that, it's just a financial aspect of the argument, and it's only focused on post-IPO, whereas most YC-backed unicorns have not yet done so.

If you look at product innovation, you'll see Dropbox, Airbnb, Gitlab (save for Airbnb, all failures by your standards), Stripe, Deel, Zapier, all household names in my world. Why weren't these products developed by big techs?

You could easily point to one that would be especially interested in taking over that part of the pie.

Re: Development speed is not a bottleneck

#150
post #148

Earlier quoted context omitted.

Let’s look at YCs “successes” as far as the companies that have gone public. https://medium.com/@kazeemibrahim18/the-post-ipo-performance...

YC couldn't care less how well these companies fare post-IPO. Post-IPO, their job is essentially done, and they cash their investment. They're probably busting champagne if the peak valuation is instantly after IPO. That means they maximized the potential payoff. You're right that one perspective to consider how well these companies are doing is to look at their continuous growth, and that includes post-IPO valuation…

Dropbox as Steve Jobs says is a feature not a product. For the price of 2TB of storage from Dropbox, you can get the entire GSuite or Office 365 or a slew of services from Apple including 2TBs of storage. In the case of O365, you get 1TB of storage for each of 6 (5?) users and Office on an unlimited number of devices for multiple users.

What BigTech company would it have made sense to get into the AirBnb market?

Gitlab has never been the industry standard for hosted Git. It was always GitHub. Even then, I guess it would have made sense for Microsoft to compete better. They did have Team Foundation Services and after many name changes Azure DevOps (unrelated to Azure. It was more of a git compatible hosted version of TFS).

Also none of the BigTech companies are in payments aside from Apple Pay/Google Pay and Amazon mostly cares about internal payments.

Deel is also a company that wouldn’t have made sense for any of the large tech companies.

I know AWS has its own orchestration service and I’m assuming GCP and Azure have it also. What motivation would they have to offer a product that works outside of their cloud platform?

I wouldn’t be surprised if AWS Step Functions get more usage than Zapier (which I had never heard of before today).

Post reply on HN