> Your post feels like the last generation lamenting the new generation [...] There's so much plumbing and refactoring bullshit in writing code [...] I've had my excitement
I don't read the OP as saying that: to me they're saying you're still going to have plumbing and bullshit, it's just your plumbing and bullshit is now going to be in prompt engineering and/or specifications, rather than the code itself.
> in any other threat model, security is an advantage of closed source
I think there's a lot of historical evidence that doesn't support this position. For instance, Internet Explorer was generally agreed by all to be a much weaker product from a security perspective than its open source competitors (Gecko, WebKit, etc).
Nobody was defending IE from a security perspective because it was closed source.
> Building physical buildings is a much simpler, much less complex process with many fewer degrees of freedom than building software.
I don't...think this is true? Google has no problems shipping complex software projects, their London HQ is years behind schedule and vastly over budget.
Construction is really complex. These can be mega-projects with tens of thousands of people involved, where the consequences of failure are injury or even death. When software failure does have those consequences - things like aviation control software, or medical device firmware - engineers are held to a considerably higher standard.
> The private market is perfectly capable of performing this function
But it's totally not! There are so many examples in the construction space of private markets being wholly unable to perform quality control because there are financial incentives not to.
The reason building codes exist and are enforced by municipalities is because the private market is incapable of doing so.
The Indian authorities has blamed the pilots in every single crash. AND there is not enough evidence to guarantee that was the case. It is one of many possibilities.
"Need blind" here just means that your ability to pay the fees doesn't factor into the admissions decision, not that the admissions office doesn't know how wealthy you are (...since as you note, this is often easily inferred).
In other words, you won't be refused an offer simply because the university thinks you can't afford it.
The point being made here is that while the university claims they don't factor in the applicant's ability to pay the fees, they also conveniently ask for information which helps them infer your social status, making their claim somewhat more difficult to take at face value.
Bear in mind this is a thread discussing how UK universities are claiming in the face of overwhelming evidence that they are not being influenced by foreign governments. So we should be able to accept that universities are capable of lying about their internal practices.
"So we should be able to accept that universities"
We absolutely should. As of now, universities tend to get away with practices that would be called out in the private sector. Entshittification of some services plus greed plus willingness to bend your morality around someone's golden glove (which hides a fist...).
> Can I now build my app in Xcode with an Android target and use that binary in the Play Store?
No. The vision document[1] lays out the direction of travel. Currently the focus is on shared business logic and libraries, rather than full native applications (although that's certainly a goal, albeit a very long term one).
> These tasks aren’t business priorities and had no impact on customers and other teams
...the author has reached the wrong conclusion from this. The problem is they weren't able to articulate why the modernization tasks were business priorities, not that the modernization wasn't a business priority in the first place.
If the tech debt is problematic, fixing it will presumably bring a number of benefits (faster development cycles, reduced defect rates, etc). They were doing the wrong work - they were doing a terrible job explaining why that work was necessary.
In many ways, tech debt and modernization is a near guaranteed way to have business impact, in a way product work is not. If you're at Meta and you figure out how to save 1% of total CPU time on the server by fixing some tech debt you can expect to be showered with money.
> I wonder what the technical details will look like
It’s already a thing, the EMVCo standard predates ubiquitous internet connectivity. Mass transit systems typically use it, airlines used to for in-flight purchases before the advent of reliable WiFi.
It is somewhat common to maintain a denylist of known fraudulent cards, but as you note the main mitigation is on the bank to track the card down. One of the key things you need to figure out with an offline payment system - and what I imagine is needed here - is a consensus on who has the liability for offline transactions and what the dollar limits are.
It's a new space, everyone is coming up with their own protocols. It's really no different than Stripe offering an API so you can use them as a payment provider. You need to implement this API on your website so ChatGPT can allow users to buy stuff from you.
You need some amount of strictness in the API here, LLMs are not actually sentient. You could say that this is a failure on OpenAI's part in comparison to their marketing, sure.
I don't read the OP as saying that: to me they're saying you're still going to have plumbing and bullshit, it's just your plumbing and bullshit is now going to be in prompt engineering and/or specifications, rather than the code itself.