Earlier quoted context omitted.
sorry, but this just sounds like a rationalisation for "we built the wrong thing". we should just be straightforward, say "we built the wrong thing" and then ask how we built the right-er thing.
No, optionality very literally has value. If I buy an option to purchase some commodities at some price, and the market moves against me, I lose the price of the option. By your logic here, the thought should be "buying the option was wrong, because it didn't go my way and I lost the price of the option". But it's often the case that actually buying that option was a good move. The kind of optionality I'm talking abo…
Lines of code got a better publicist
291–300 of 309 posts
Re: Lines of code got a better publicist
#292Earlier quoted context omitted.
Story time. small business. less than 30 people. ceo had invested £1 million to build a data analytics platform. "democratising data analytics" in a very specific domain. essentially, competing with someone like databricks in a niche. although they had never heard of databricks before i showed up. For that million pounds they got a job scheduler written in pure django with a halfway finished react frontend. the whole…
Yes, thanks for the story. This is what I was trying to say. The idea that it's completely okay for companies to misallocate billions of dollars across the industry while people are legitimately suffering do to myriad of reasons is just bonkers level of selfishness. I worked at a company that had an $80,000 monthly AWS spend when the total users in question was less than 100,000. The most concurrent users was This ob…
But that doesn't imply that every project that does not ship was a poor investment of time and resources.
Re: Lines of code got a better publicist
#293Earlier quoted context omitted.
> If it were so easy to decide what the right thing is to build before you build it then business would be easy. It's not easy. That's why it's important to be straightforward and just move on without all the navel gazing. > ... hoping you hit the lottery with product-market fit. There's this thing called "research" where you talk to real people, instead of guessing. > That doesn't retroactively make their effort wor…
I don't understand why you interpret "we should recognize that it's worth paying for optionality and sometimes we decide not to exercise the option and that's normal and fine" as naval gazing. I think it's the opposite, that feeling butt hurt about the projects you work on not shipping is what is naval gazing. To me all your "I prefer being plain and direct" just sounds like someone who hasn't thought much about why…
I'm not.
> But you're just saying "don't make me think about why we agree about this!"
My position is that you're overcomplicating it with business doublespeak.
----
edit
> someone who hasn't thought much about why building the wrong thing is not worthless, and why those continuous mistakes in life are worthwhile, and isn't really interested in thinking about things at more than the surface level.
I have just spent the last two years writing over a thousand pages of very heavy introspective stuff about a bunch of stuff i've done, and things that have happened to me, over the last thirty years.
"surface level" is most definitely not the person you're speaking to.
Re: Lines of code got a better publicist
#294Earlier quoted context omitted.
No. This is like saying "shouldn't scientists figure this out before wasting tons of money running experiments?".
Not the same. Every corporation I've worked at (several dozen in my career across the F500) has had numerous stories about obscene waste in regards to building things in software. Waste at all levels. I've worked at insurance companies that spent $100million on development where only 200 customers signed up (estimated to be 20,000 at start). I've worked at telecoms that spent $25 million developing internal tools tha…
"It only got 200 users" is the business version of the null hypothesis.
Re: Lines of code got a better publicist
#295Earlier quoted context omitted.
sorry, but this just sounds like a rationalisation for "we built the wrong thing". we should just be straightforward, say "we built the wrong thing" and then ask how we built the right-er thing.
No, optionality very literally has value. If I buy an option to purchase some commodities at some price, and the market moves against me, I lose the price of the option. By your logic here, the thought should be "buying the option was wrong, because it didn't go my way and I lost the price of the option". But it's often the case that actually buying that option was a good move. The kind of optionality I'm talking abo…
Re: Lines of code got a better publicist
#296Earlier quoted context omitted.
I don't understand why you interpret "we should recognize that it's worth paying for optionality and sometimes we decide not to exercise the option and that's normal and fine" as naval gazing. I think it's the opposite, that feeling butt hurt about the projects you work on not shipping is what is naval gazing. To me all your "I prefer being plain and direct" just sounds like someone who hasn't thought much about why…
> It does seem like you aren't really disagreeing with us here. I'm not. > But you're just saying "don't make me think about why we agree about this!" My position is that you're overcomplicating it with business doublespeak. ---- edit > someone who hasn't thought much about why building the wrong thing is not worthless, and why those continuous mistakes in life are worthwhile, and isn't really interested in thinking…
Re: Lines of code got a better publicist
#297Earlier quoted context omitted.
> It does seem like you aren't really disagreeing with us here. I'm not. > But you're just saying "don't make me think about why we agree about this!" My position is that you're overcomplicating it with business doublespeak. ---- edit > someone who hasn't thought much about why building the wrong thing is not worthless, and why those continuous mistakes in life are worthwhile, and isn't really interested in thinking…
Yes I understand that. The tendency of engineers to willfully refuse to understand what's going on in their businesses and scoff at the things they are refusing to understand by dismissing them as "overcomplicated" and "business doublespeak" is what my comment that started this thread was about.
https://news.ycombinator.com/item?id=48497153
i get the sense that you think i'm "one of those engineers". I am not.
Re: Lines of code got a better publicist
#298Earlier quoted context omitted.
Not the same. Every corporation I've worked at (several dozen in my career across the F500) has had numerous stories about obscene waste in regards to building things in software. Waste at all levels. I've worked at insurance companies that spent $100million on development where only 200 customers signed up (estimated to be 20,000 at start). I've worked at telecoms that spent $25 million developing internal tools tha…
> $10,000 a month on licenses when only 12 devs existed Depend, depending on the licenses in question, this could be a fantastic deal
Re: Lines of code got a better publicist
#299Re: Lines of code got a better publicist
#300> But! Hold my beer… in February 2026 METR effectively walked it back : their follow-up estimates flipped to a speedup (with error bars wide enough to ride a Moto Guzzi, with panniers, through!), and they abandoned the study design entirely - because developers now refuse to work without AI, and can’t reliably self-report time on agentic work. Their latest position: AI probably speeds developers up in 2026, and we ca…
Author here. Thanks, this is a useful addition I'd missed. The 40-point overestimate from their early-2025 work is exactly why I read METR's current position as "we can no longer cleanly measure this" rather than "AI definitely speeds you up now"; self-reports are doing a lot of load-bearing work in every direction, including in my own sense of my productivity.