Yep this is especially true in the pre-product-market-fit phase. Most if not all of that code should be written to be thrown away. Any time you spend writing perfect code instead of your MVP is burnt runway and a chance for competitors to catch up.
Once you show PMF though the balance changes to long-term sustainability and maintainability.
What's going to be interesting is getting to a place where it generates better code than we would from specs. You can get better and better generated code by filling in the context the model infers. Do that long enough, and well, a perfect spec is just code.
That's an incredibly vague standard and courts have repeatedly declined to get involved in second guessing management decisions. Aside from outright fraud or negligence executives can claim almost any business related decision is in the interest of shareholders because they have a reasonable expectation that the future benefits outweigh the costs. Judges aren't going to be delving into financial projections and expense reports to override the leaders of a business.
A widget company could sponsor a soccer team or whatever and say the costs are worth it. Or that same company could not do that and say it's not worth it. Two opposite decisions that both would count as acting in the interest of shareholders.
If you really want to go down that path then AI's are the product of human ingenuity and labor so you have to amortize all of that into AI training. Then numbers become pretty meaningless very quickly. That sand didn't up and start thinking on its own you know.
Deaths in the Great Leap Forward were heavily concentrated as compared to the Industrial Revolution but the death tolls from IR-related famines weren't really all that far off. Industrialization was messy everywhere.
The Irish Potato Famine alone killed 15% of Ireland vs the GLF killing 5% of China.
That's not a reason not to plan 5 years in advance... is it? Any more than the Potato Famine is a reason we should't have capitalism.
I can't say that I've ever heard the argument that a plan led to a famine therefore we should never make plans, when we have great counterexamples that not planning also led to famine. Feels like learning the wrong lesson here.
[edit] I also think it's worth pointing out that America's response to the Dust Bowl was the Farm Bill, which it could be argued is one of the largest-scale examples of central planning in history. It continues to this day, and is part of the reason Americans pay less as a share of their spending on food than any other country on earth.
People say everyone remembers the hits, nobody remembers the misses - but that is the opposite of true for government. Everyone remembers the misses, nobody thinks twice about the hits.
The Irish Potato Famine was a constructed starvation by England to Ireland. All of their real foodstuffs were being stolen by England to run world-level wars everywhere, and the Irish grew what they were permitted to. Potatoes.
It's not pay $45 to go though, it's pay $45 for someone to take you around back and look you up based on secondary identification, and if they can't positively identify you based on that you still can't go through.
This is a system that has been in place for a long, long time. You could always say you don't have ID and they'll look you up. The change is they're now charging for it.
> And don't get me started with all the paid express security lanes. Because of course only poor people can weaponize shoes and laptops.
This is also not accurate. If you're talking about Clear, you just skip to the front of the normal line. If you're talking about Pre, those people are individually background-checked before hand, and it costs $19/yr, so it's not exactly a tophat and monocle only program. Especially since that's half the price of a one-way taxi ride to the airport, let alone the ticket. The airport self-selects for the fairly well off to begin with.
Yeah, Swift started out fairly clear and cohesive and now it's just a katamari of every language feature ever made by anyone plus a whole bunch of home-grown features too. I'm always mixed on this because in isolation the feature is neat and I like it, but the totality of Swift is becoming as overwhelming and inconsistent as C++.
Now some C functions which are indistinguishable from free Swift functions get named parameters, and you can switch on some enumerations from C, and some C objects are ref counted but other ones still need you to do it. It's going to be quite something to keep track of which library is which since there's no way to know apriori.
Yeah, Swift looks like someone started trying to port a C# syntax onto an esoteric object-orientated C-dialect (similar to Vala and GObject) then at the last moment noticed Rust 1.0 had been released, tried to patch on some Rust features, and hit release before they were done.
It's quite deceptive. Rust seems initially hard to learn, but it's a small language, so you arrive at competency faster than you might think. Swift seems initially easy to learn, but is a broad language with lots of edge-cases, so you're never quite as competent as you think you are, or need to be
Ehh I have been using Swift from the beginning and I disagree with you and the parent. Swift was "good" before the addition of property wrappers and the result builder syntax. That's when lots of the weird "features" started being bolted on.
Before that it just felt like what a modern OO language with reference and value types, type safety, some very light "not truly functional but nice to have" functional programming features, and readable, "normal", dot syntax would be like. The language was basically complete at that point for the purposes of writing UI apps with the existing Apple frameworks.
> According to Edwards’ data, 75 percent of truck owners use their truck for towing one time a year or less (meaning, never). Nearly 70 percent of truck owners go off-road one time a year or less. And a full 35 percent of truck owners use their truck for hauling—putting something in the bed, its ostensible raison d’être—once a year or less.
> So what do people actually like about trucks? According to Edwards, the answer is counterintuitive. Truck drivers use their trucks very much like other car owners: for commuting to and from work, presumably alone. The thing that most distinguishes truck owners from those of other vehicles is their sheer love of driving. “The highest indexed use among truck owners is pleasure driving,” says Edwards. Truck drivers use their vehicles this way fully twice as often as the industry average. “This is the freedom that trucks offer,” says Edwards.
The F-series is the best selling car family in the US. Some of them are using it for its intended purpose sure, the majority are just using it as parent said, a luxobarge.
>The F-series is the best selling car family in the US. Some of them are using it for its intended purpose sure, the majority are just using it as parent said, a luxobarge.
A F550 box truck and a crew cab shortbed F150 are both F-series as well as everything in between.
If not the best selling it had better be damn close with all the different vehicles that exist under that one nameplate.
The F-150 alone has been Americas best selling vehicle for 47 years straight until getting dethroned by the RAV4 in 2024 (unless you add any of the other F-series trucks). It appears to be back on top in 2025.
one time a year or less was the suffix for each of these, many more people fall into the once a month or so category. The economical thing to do is buy a civic and rent a truck the one time a year you use it for truck things.
If your argument is that most Americans should be on public transit and save the average $500,000 they spend during their lives on private vehicles then I completely agree.
If you're saying "a less bad thing is still bad!" then your comment reads more like the "We should improve society somewhat. / Yet you participate in society. Curious! I am very intelligent." meme.
The argument seems to ve that trucks are bad because people don't use them to 100% capacity all the time.
People generally buy vehicles for to fit all of their needs not 95% of them. My back seat and trunk are almost always empty and my passenger seat is mostly empty.
> A pickup truck should just be max utility, especially if you're a manufacturer making your first one
> 75 percent of truck owners use their truck for towing one time a year or less (meaning, never). Nearly 70 percent of truck owners go off-road one time a year or less. And a full 35 percent of truck owners use their truck for hauling—putting something in the bed, its ostensible raison d’être—once a year or less.
I wonder if there are any other countries in the world where the best-selling automobile is something completely impractical? Or are Americans unique in that regard?
Serious question. I can't think of any, but I'm also not familiar with car markets the world over. In Japan, for example, the best-selling car is the Honda N-BOX [1], which is an incredibly practical car.
An amendment requires 2/3 of the house and 2/3 of the senate -- or 34 of 50 states to call for a constitutional convention (which has never been done) -- just to float an amendment.
Then 3/4 of the states have to ratify it.
I don't think you could get half of states to agree the sky is blue let alone 3/4.
[edit] The Equal Rights Amendment has been in progress since 1972 and while they somehow managed to get 3/4 of states to agree (Virginia agreed in 2020) the 7- and later 10-year deadline built into the bill had long elapsed. And 5 states later tried to rescind their ratifications which isn't really covered in the constitution in the first place.
That one says simply:
> Equality of rights under the law shall not be denied or abridged on account of sex.
Once you show PMF though the balance changes to long-term sustainability and maintainability.
What's going to be interesting is getting to a place where it generates better code than we would from specs. You can get better and better generated code by filling in the context the model infers. Do that long enough, and well, a perfect spec is just code.
We do live in interesting times.