Live data from Hacker News

Development speed is not a bottleneck

pawelbrodzinski.substack.com

131–140 of 153 posts

Re: Development speed is not a bottleneck

#131

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…

> Because just developing the variations would be faster than all of the debate. So the amount of time you waste in meetings and deliberation goes down as well.

Thank you for articulating something I knew but haven't been able to express as eloquently.

It frustrates me to no end to watch half a dozen non-technical bureaucrats argue for days about something that can be tried (and discarded) in a few hours with zero consequences.

"Let's write a position paper so that everyone involved can agree before we do anything."

Noooo! Just do it! See if it works in practice! Validate the marketing! Kick the tyres! Go for a test drive. Just. Get. Behind. The. Wheel.

Re: Development speed is not a bottleneck

#132
post #72

Earlier quoted context omitted.

Trying things and changing if it doesn’t work is the only way I know how to build software. What would you do? Don’t change?

The question is, why doesn’t it work? Erroneous code, erroneous algorithm, missing feature in the underlying infrastructure? The effort it takes to implement a feature makes is more likely you think twice before you start. If the effort goes to zero, so does the thinking. We will turn from programmers to just LLM customers sooner or later. Because testing if it works can be done by none programmers

> Because testing if it works can be done by none programmers

like testing whether a building is structurally sound can just be done by the inhabitants!

Re: Development speed is not a bottleneck

#133

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…

> It's completely absurd how wrong this article is. Development speed is 100% the bottleneck. The current trend in anti-vibe-coding articles is to take whatever the vibe coding maximalists are saying and then stake out the polar opposite position. In this case, vibe coding maximalists are claiming that LLM coding will dramatically accelerate time to market, so the anti-vibe-coding people feel like they need to claim…

> so the anti-vibe-coding people feel like they need to claim that development speed has no impact at all

Strange, I'd been more of the impression that this is an argument from pro vibe-coders. As more data comes in, the "productivity increases" of AI are not showing up as expected. So as people question, how come things are not getting done faster even though you say you are 10x faster at coding? The vibe-coders answer by saying that coding isn't the bottleneck, as opposed to capitulating and saying that maybe they're not that much faster at coding after-all.

Re: Development speed is not a bottleneck

#134
post #90

Earlier quoted context omitted.

Sure. And yet, last time I checked, we've had plenty of applications for maps. I like this metaphor. Looking at a map, we may get a pretty good understanding of whether it's a place we'd like to spend time, say, on vacation. We don't physically go to a place to scrutinize it. And we don't limit ourselves to maps only. We check reviews, ask friends, and what have you. We do cheap validation before committing to a cost…

The best way to know if you would like a new restaurant or experience is to actually try it. We rely on reviews and maps and directories because trying it is too costly. If trying it wasn't costly, we would just try it instead of relying on proxies.

OK, let's assume you can get food for free (or close enough). Like if you were super rich, and the cost was absolutely marginal for you.

How many dinners a day can you have?

You would still rely on alternative proxies, like recommendations or reviews.

Re: Development speed is not a bottleneck

#135
post #19

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…

This, so much. As an engineer turned PM, I am usually sympathetic to the idea that doing more discovery up front leads to better outcomes, but the simple reality is that it's hard to try anything, make any bets, or even do sure wins when the average development lifecycle is 12-18 months to get something released in a large organization and they're allergic to automation, hiring higher quality engineers, and hiring mo…

> and they're allergic to automation, hiring higher quality engineers, and hiring more engineers to improve velocities

I think there's another issue, but it could relate to your first two statement here. Even to try ideas, to explore the space of solutions, you need to have ideas to try. When entering development, you need clarity on what you're trying. It's very hard to make decisions on even a single attempt. I see engineers working task the entire time simply not sure what really the task is about.

And in a way, the coding agents need even more clarity in what you ask of them to deliver good result.

So even inside of what we consider "development" or "coding", the bottleneck is often: "what am I supposed to do here?" and not so much "I don't know how to do this" or "I have so much to implement".

This is obvious as well, once you throw more engineers, and you can't break up the work, because you have no clue what so many people could even all do. Knowing what all the needed tasks even are is hard and a big bottleneck.

Re: Development speed is not a bottleneck

#136

You have the unbelievably productive programmers - we all know their names, we use the code they wrote every day. Then you have the programmers who want to be there and will try everything they can to be there - except gain depth of knowledge. They tend to be shallow programmers. If you give them a task and spell it out, they can knock out code for it at a really good pace and wow upper management. But they will alwa…

Can't agree more.

> If you give them a task and spell it out, they can knock out code for it at a really good pace and wow upper management.

This is so true. I sometimes spend entire days, weeks, all I do is provide those type of engineers the clarity to "unblock" them. Yet I always wonder, if I had just spent that time coding myself, I might have gotten more done.

But it's also this that I think bottlenecks development. The set of people who really know what needs to be done, at the level of detail that these developer will need to be told, or that coding agents will need to be told, is very small, and that's your bottleneck, you have like 1 or 2 devs on all project that knows what to do, and everyone else need a Standard Operating Procedure handed to them for every task. And now everyone is always just waiting on the same 2 devs to tell them what to do.

Re: Development speed is not a bottleneck

#137

I completely disagree. As a scientist who does a lot of coding, the modern LLM tools give me ability to code something which previously I could not afford, because I simply did not have time for it. Now if I have an idea, I may be able to test it in an hour of tinkering with claude/gemini. I could technically still code it myself, but in some cases that would require maybe a day of work -- and I simply don't have tha…

Im not a scientist, just a freelancer (kind of) and its similar for me. I know probably only 2 langauges fluently enough that i could write in them without constantly checking for syntax/docs, but over my whole programming journey i got to know multiple languages with different syntaxes, coding styles and patterns, so i can easily read code written in multiple languages and know whether given code will do what i want (and even if i wouldn't, LLM can explain the code for me and in the worst case send me to the documentation to validate it by myself).

Asking LLM for a code and then read/review it is a huge speed up for me in a lot of cases comparing to when i would need to write the same thing by myself (but i agree it may not work well in a big/complex systems... yet).

Re: Development speed is not a bottleneck

#139
post #106

Earlier quoted context omitted.

Of course, Big Techs have leverage of their bottomless coffers. What they can't develop, they buy. What was the last successful product idea coming from, say, Facebook? Or on a smaller scale, what's the last genuine Attlassian success? Yet, when it comes to product innovation, the momentum is always on the side of the new players. Always has been. Project management/work organization software? Linear. Async communica…

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 wouldn't be surprised if a couple of companies from this year's cohort made it big. If you look at YC's biggest successes year by year, you will often (but not always) find a household name.

Was there anyone who predicted these would be the greatest hits? Of course not! That's the whole point of having an investment portfolio. You can be wrong a lot of times if you secure an early investment in a unicorn every other year or so.

Also, "one recent example" of poor investment decision doesn't invalidate 2 decades of rather successful investment portfolios (as a whole, not individually).

In no way is it a YC defense. I'm very critical of the whole startup funding ecosystem, and they are a prominent player. Yet, if they were consistently stupid with their decisions, they wouldn't exist, let alone be the most desired accelerator out there.

Also, if it's that simple to copy what they do and what the companies in their portfolio do, why wouldn't Google et al. take their almost infinite funds and get the competing offers for non-BS ideas up and running in no time?

I bet that if you had an idea that could pay off thousandfold, you'd get enough eager ears to hear you out in any big tech. And still, it's the makeshift mass of startups that come through with new products.

One has to wonder why things like Shopify, Stripe, Zapier, or Figma did not come from the big tech. Each would have an ideal match. Even if you look at the AI landscape, how come Lovable made such a career? After all, they repackage the AI capabilities rented elsewhere. Somehow, with all the ingenuity of building ChatGPT, OpenAI and the rest didn't get it.

Re: Development speed is not a bottleneck

#140
post #108

Earlier quoted context omitted.

Big Techs do have ways of rolling out new services step by step. Paul Buchheit's stories about Gmail and AdSense are good examples. I was an early Gmail user when it was invitation-only and invitations were scarcely distributed (only as fast as the infrastructure could handle). So, while I understand the difference in PR costs, it's not like they don't have tools to run smaller experiments. I agree with the huge bure…

Google had 3,000 employees when Gmail launched. Now they have over 100,000 employees! People criticize Microsoft's historical fiefdom model, and it had its issues, but it also allowed orgs to find what worked for them and basically run independently. Of course it also had orgs fighting with each other and killing off good products. Xbox was also a skunk works project at Microsoft (a few good books have been written a…

Sure, it was way easier to move at Google in the early 2000s than it is now. Yet, one has to admit they still keep trying. The list of products that they tried and killed doesn't show signs of stagnation: https://killedbygoogle.com/

And that's only the things that they have released. I'd bet that there are lots more that never make it to the public.

And I expect no less from Microsoft, by the way. Microsoft is, in fact, a great case in point of how failed releases don't hurt the company's PR long-term. How many failures have they scored trying to catch up with the missed opportunities of the 2000s? Smartphones & tablets, search, music players, social media.

They were late to move the Office to the cloud, and kept pumping dollars into the Explorer/Edge lost cause, too.

I don't know enough details, but Xbox seems more like an outlier than a norm.

Yet they rebounded with Azure and made some good bets with AI, and are doing better than ever. However, we don't see a stream of new product bets coming from them.

Oh, and on Apple: I wouldn't discount the role of cult-like following in repeated product success. Neither of the other big techs has such a relationship with its user base. You don't see many raving fans of Facebook or Google. And you definitely have millions of people who would buy any new Apple product simply because it is a new Apple product.

It's like Joel Spolsky but on a global scale. In the 2000s, whatever Joel Spolsky touched turned into gold. Stack Overflow? Check. Trello? Check. Was there something unique about these products? Details, sure. But the biggest thing was Joel's leverage.

Having run a highly popular blog for developers, he could instantly reach out to his early adopters. Given that many of the readers were actual fans, they'd jump on the opportunity, whatever it was. So the early traction was not a problem (which was especially crucial for the developers' forum).

Scale that up to the big tech context, and you get Steve Jobs.

A side note: I wonder how long it will take Tim Cook to dismantle that. You can already see cracks.

Post reply on HN