I don't mean to downplay Trump's strongarming of industry or the obsequiousness shown by tech leaders, but let's be real, it's not remotely the same level of control.
the government is basically subservient to him, and there isn't anything stopping it from making a company cease to exist other than the status quo. If, for whatever reason, him (or in his absence the rest of the government) decide they don't want it to exist, it won't exist. It might not be as explicit as how the CCP does it, but it will have the same result
This might be true for small companies, but it's delusional to think that Trump could unilaterally put an end to one of the major tech companies. It would be a huge legal, political and financial battle, at a minimum. Either you're overestimating Trump's power or underestimating the power of the tech companies.
Given the Trump administration’s actions against private industry from TikTok, to Anthropic, to a hundred other examples from auto makers to air conditioning manufacturers, is it fair to deem it delusional to think he might possibly succeed?
Good luck suing the White House, sovereign immunity basically makes this impossible in most cases.
While sovereign immunity is a problem in and of itself that must be reformed, the real problem here is the illegitimate supplicants on the Supreme Council.
They're not suggesting that code will go away, but rather that it will be abstracted beneath an LLM interface, so that writing code in the future will be like writing assembly today: some people do it for fun or niche reasons, but otherwise it's not necessary, and most developers can't do it.
Whether that happens or not is a different question, but I believe that's what they're suggesting.
Code is formal and there are basic axioms that grounds its semantic. You can build great constructs on top of those semantics, but you can’t strip away their formality without the whole thing being meaningless. And if you can formalize a statement well enough to remove all ambiguity, then it will turn into code.
Programming is taking ambiguous specs and turning them into formal programs. It’s clerical work, taking each terms of the specs and each statements, ensuring that they have a single definition and then write that definition with a programming language. The hard work here is finding that definition and ensuring that it’s singular across the specs.
Software Engineering is ensuring that programming is sustainable. Specs rarely stay static and are often full of unknowns. So you research those unknowns and try to keep the cost of changing the code (to match the new version of the specs) low. The former is where I spend the majority of my time. The latter is why I write code that not necessary right now or in a way that doesn’t matter to the computer so that I can be flexible in the future.
While both activities are closely related, they’re not the same. Using LLM to formalize statements is gambling. And if your statement is already formal, what you want is a DSL or a library. Using LLM for research can help, but mostly as a stepping stone for the real research (to eliminate hallucinations).
It's probably a modified version of the thinking model. If that's the case, releasing them at the same time would mean delaying the thinking model's release.
Interesting, I've had basically the opposite experience working from home since COVID. I exercise more, cook more, sleep better, go for more walks.
Part of it is just time and energy freed up from my commute. I always felt wiped out after fighting through traffic to get home. But if I lived in a small apartment in a place that wasn't good for walking, I'd probably hate it.
reply