Top
Best
New

Posted by vaylian 9 hours ago

Some things just take time(lucumr.pocoo.org)
431 points | 143 commentspage 4
tbrownaw 7 hours ago|
> We know this intuitively. We pay premiums for Swiss watches, Hermès bags and old properties precisely because of the time embedded in them. Either because of the time it took to build them or because of their age.

Oh, I thought it was because they're a way to show off about being rich.

> We require age minimums for driving, voting, and drinking because we believe maturity only comes through lived experience.

Even if she could reach the pedals, my 4yo doesn't have the attention span to drive. This isn't a "lived experience" thing, it's a physical brain development thing. IIRC the are effects with learning math, where starting earlier had limited impact on being able to move to certain more advanced topics earlier; ie there's more going on than just hours of experience.

The standard age for voting is also the age for being a legal adult. There are sound logical reasons that these ages should match.

The standard drinking age is due to pressure by activists, and AIUI is lower in other countries.

sodapopcan 7 hours ago|
> Oh, I thought it was because they're a way to show off about being rich.

Maybe for some. I think these examples were carefully chosen. Hermès are made in France, "Swiss watch" doesn't automatically mean Rolex, though in that case Rolex does own most of their manufacturing (though there is a whole world of carefully made watches out there that don't cost 10K). As for old properties... there is a huge range there, but unless you are living in a castle, most people, at least my city, are likely silently thinking: "I'm so sorry for them that they have to live in that old house."

mocamoca 3 hours ago||
Can someone ELI5 what Earandil purpose is?
sledgehammers 6 hours ago||
Also you know, for programmers, say a 3 day work week is right there up for grabs. Even still employers would see big productivity increases.
tonyedgecombe 6 hours ago||
Programmers no longer have any leverage now they can all be replaced by machines. It doesn't matter how productive you are, the system will always demand more.
OtomotO 6 hours ago||
This hype too will pass. It's always ebb and flood...
hedayet 6 hours ago||
you know what most of us end up doing on those other days? we start side tech projects that require even more effort for even little return.

You can't trust us with self-care. There's just too many shiny toys out there!

mrknmc 6 hours ago||
Speak for yourself!
whateveracct 5 hours ago||
lots of things take days, not hours. And idt AI changes that much. It does let you (or - let's be real - your middle management) try to make it happen with hours tho :P
jsisto 6 hours ago||
great article. reminds me of the saying “9 women can’t make a baby in a month”
bushido 5 hours ago||
I feel for the larger companies and the people who started 10 years ago, though.

They have spent the last decade building processes and guardrails for getting consistent average performance from people. But now, some talented people who worked at those companies are building their own new companies without the overhead and moving much, much more quickly.

I think what we assume is "vibe slop at inference speed" is not as simple as people make it out to be. From a perspective, I think generally it might be people trying to save jobs.

I'm seeing more slop come out of larger, older companies than the new ones (with experienced operators).

And the speed is somewhat scary. For smaller team it doesn't take as much effort to build deep, beautiful product anymore.

The bottleneck was never the ability for a engineer to code. It was the 16 layers between the customer and the programmer which has vanished in smaller companies and is forcing larger ones to produce slop.

felubra 6 hours ago||
"So welcome to the machine"

I'm reading Against The Machine by Paul Kingsnorth, and now reading this blog piece is hard not to make connections with the points of the book: the usage of the tree as a counter-argument for the machine's automation credo exposed in the blog post very much aligns with I've read so far.

mayukh 3 hours ago||
Go slow to go fast.
aantix 4 hours ago||
Everyone is obsessed with speed.

But no one wants to go out of their house.

Social connections. Trust. Facetime. All matter more than ever.

Want a moatable software business? Know your customers on a personal level. Have a personal relationship. Know the people that sign the contracts, know their kids names, where they vacationed last winter, their favorite local restaurant.

Get out of the house.

scuff3d 4 hours ago|
We're gonna have to learn some lessons from other engineering fields in this regard. Electrical, civil, mechanical, aerospace... They've all had to put processes in place to intentionally slow things down for a long time. I could throw a circuit board layout together 1000x faster then a team of engineers could have 50 years ago, but that industry has developed a culture of rigorous review processes to ensure quality, which means I couldn't actually move nearly as fast as possible.

Undoubtedly a lot of that comes down to production cost and safety. A plane is far more likely to kill people and it costs a shitload more to produce then an app (though plenty of software is mission critical). But now in software we can move quick enough up front that if we don't start applying some discipline it's going to bite us in the ass in the long run.

More comments...