Shelf life is one of the major factors allowing treatment more similar to nonperishable commodities.
I think some people do instinctively feel like all different kinds of software have different shelf lives or useful lifetimes for different reasons.
But there's always so much noise it's not very easy to get the expiration date correct.
Mass production is pretty much a given when it comes to commodities, and things like long shelf life are icing on the cake.
The inversion comes when mass production makes the highly processed feed more affordable than the unprocessed. After both have scaled maximally, market forces mean more than the amount of labor that was put in.
"You should not let your IDE do the thinking for you"
As a solo entrepreneur, if something enables me to execute faster, I'll gladly use it. Articles like this only remind me to never (again) hire expensive, pedantic, over-principled and cynical engineers.
I think they have some good points (having a deep understanding of tools you use), but I think the path they take achieve those results is misguided.
A stupid example off the top of my head: I use VSCode and often I'll use the integrated git commit feature. But if need to bisect, rebase, merge, or edit a commit, I will just use the CLI. I don't feel like using the commit GUI makes me worse at using git.
All in all, I think the author thinks that familiarity with one tool makes people worse at another similar tool, but I don't think that's the necessarily the case. At worst, memory might fade if the other tool isn't used, but that's fine, it's clearly not used often. As an analogy: if I don't speak German every day, I don't need to be fluent in German either.
Strange. Articles like this remind me never to hire vibe coding brogrammers who have no idea about basics such as cp, mv, find etc. Usually they leave behind a mess which soon breaks.
The cynical and pedantic engineers however, do excellent work, and their software never breaks. It takes longer, you pay a bit more, but it is worth every cent.
And using an IDE that enables you to work faster, doesn't mean you can't learn basic shell commands. Or learn the fundamentals behind the technology you use. Just like pedantic engineers are no guarantee for code that doesn't break.
> Put that on your resumé and you'll easily land a cushy job in Washington.
I think you have it backwards. The entire tech bro scene reeks of fraud schemes, and the most successful ones seem to be pulled into all kinds of government schemes as well.
I hate it when ‘inspirational’ quotes are attributed to the person with the largest audience and not the people who came up with it, like in this case, the engineers at Lockheed’s Skunk Works.
You mean that we showed them already by that age to not mix fries & ketchup? :-D
If children are that small and you are sitting with two of them at the table, handing over those ideas to them in a "nurturing way" is the last thing on what you can focus on with two small kids at the table :-))
And its always great if someone gives a downvote here if you share some personal life stories :-D
The mass production of unprocessed food is not what led to the production of hyper processed food. That would be a strange market dynamic.
Shareholder pressure, aggressive marketing and engineering for super-palatable foods are what led to hyper processed foods.
reply