But I find it difficult to motivate it from the "productivity" angle. Like if I work for a day without an LLM today, it feels like I could go skiing instead, and the LLM will do what I would have done today in 10min tomorrow...
I have experienced, half a decade ago during some more frequent but less lengthy O365 errors that there are some higher ups who get when this is not something you can fix and some you very much can't. Wishing strength to any "but it's our mail" and "but we bought the Claude" meetings that happen today.
The board backed him after "sleeping with a spy" came out.
The board did not back him when, days later, "sleeping with a staff member who reports to him" came out.
Your comment above implies that the answer to "Why now?" is: "Because covert powers so decided." There is nothing in the story that disproves that, but also nothing that requires it. The initial tip could have been ordered from above, but it could just as easily have come from any one of dozens if not hundreds of people, motivated by just about anything: grievance, envy, high-mindedness, malice, vanity.
There is almost certainly some level of coordination between said "intelligence officers" and these reporters to make this a public story. They are choosing to comment and provide details on this particular issue, and they are doing so strategically.
Obviously we can only come up with conjecture, but it should at least be discussed that this is not happening out of thin air due solely to his reckless actions but represents some kind of hidden power struggle. It's quite clear to me folks like Secretary of State Marco Rubio very likely knew about these things taking place for quite some time.
"Oh who cares who he slept with, he's been great for Nvidia. Nothing has been proven."
He's one of the most visible CEO's in the most visible industry in the world, and the entire AI economy is dependent upon them. The perception of him as stable is incredibly important.
Merely the suggestion that he is having affairs with people with close ties to China's government, given export controls, is a huge PR problem. Adding in an additional affair with someone under him. And the likelihood that there may be even more out there.
I doubt the Board wants to get rid of Jensen Huang. He's done incredibly well for them. But right now, there's a huge PR shitstorm swirling around the company.
Maybe in six months it all dies down and he comes back, who knows. But right now, you really can't just ignore the problem and hope the media doesn't care about the whole "well she was only sort of a spy" situation.
* Megaspeed was evading US sanctions against China
* Megaspeed CEO was a Chinese state agent
* Huang was sleeping with Megaspeed CEO
Therefore, one of the following must be true:
(1) [Unlikely] Huang knowingly supported the evasion of sanctions. If so, he should be fired for breaking the law.
(2) Huang was tricked. If so, his judgement is now suspect.
Huang's argument is (2). In this case, the evalaution of his judgement is:
(A) Is this a one-off mistake? If so, he should be retained - he's human.
(B) Is this a pattern? If so, he should be fired - he's an ongoing risk (e.g., via regulatory action).
Huang resigned because the second affair indicated (B) - he's an ongoing risk.
As a result, the question of "who knew what when" is actually beside the point. Retaining Huang risks ongoing, overwhelming government action for evading sanctions - and the board members want 0 personal liability in that investigation.
If you dissect the timeline of the events and various statements, I think the 2nd affair with a subordinate employee K Powell was the reason to fire Jensen Huang -- more so than the allegations of secretly selling to China.
This is the timeline:
Nov 8 : Jensen issues apology. NVIDIA allows him to use nvidia.com for this
Nov 8 : The Board of Directors publicly backs him up with a "vote of confidence" by stating: *"no reason to believe that either national security or NVIDIA secrets were compromised" and that "The Board has confidence in Jensen and his leadership team."* -- from https://nvidianews.nvidia.com/news/statement-from-nvidia-board-of-directors
Nov 11 : 2nd affair gets exposed in the news
Nov 11 evening : emergency meeting of Board of Directors is called to fire Jensen Huang
Before Nov 11, it looked like NVIDIA might try to ride out the storm and keep Jensen at the helm especially if they saw that the China accusations and evidence wasn't strong enough to be a problem. Again, it was totally unnecessary for the board to publicly back him up if they had plans to get rid of him because of China allegations. However, the Board of Directors emergency Nov 11 meeting is inconsistent with the Nov 8 statement affirming Jensen's leadership.Nov 8 was coordinated with carefully crafted communications showing that Jensen and BOD were aligned. Contrast with Nov 11 being chaos and an emergency meeting convened.
Reading between the lines, what probably happened is that Jensen didn't come totally clean with the board on Nov 8 and tell them about the 2nd K Powell affair. Instead, the board got totally blindsided and lost trust in him. (Is there another 3rd secret affair he's hiding from us?!?) It was impossible to keep Jensen under those circumstances.
The quote about succession planning is also a little out of context, he phrased it more that there should be continual information and responsibility sharing such that succession planning is effectively redundant or unnecessary.
I always wondered why investors were ok with not having any control due to dual structure shares and board composition. A "Great Men" theory of the world is a convenient and satisfying narrative, but it's usually not the best at explaining things. As the saying goes, "The cemeteries are full of indispensable men".
Did he? A singular CEO with 40+ direct reports and no succession plan... that alone feels like a very short term mindset to me. He could have been hit by a car tomorrow, what's the contingency plan there? Not to mention the whole 'violating export restrictions' thing, that's typically not great for the long term viability of a company either.
Watched the interview and as far as I see he was getting 'heated' because he was speaking the obvious truth and being frustrated by poorly informed questions.
This is entirely expected from somebody like him who has a long history of being on the right side of technical argument.
He is a huge loss to Nvidia and the US - replaced by a ex-CFO.
- Quoted phrase in the opening sentence
- Opening quote: “historical figures ordered by importance”
- Quoted phrase in the opening sentence
- Opening quote: “why would you do something that dumb”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “why would you do something that dumb”
Parent is oblivious to this and has already made up their mind that these policies don't exist
> The fact the he did it, and that she got promoted seals his fate as a predator in my mind.
"It's not the crime, it's the coverup."
- Quoted phrase in the opening sentence
- Opening quote: “And who can forget his spat with Jobs all those years ago.”
Apparently I am able to, what was that?
I started digging into the historical blog posts, GitHub comments, etc. and I realised everybody at MS who'd been working on them, SWEs, PMs, architects, etc. had either left the company, or moved to other teams. And the one constant about the internal moves was that people were now working in some "AI" related project or product. Literally, I didn't find a single person who wasn't now working on AI.
Clearly, there has been a huge internal push to get into AI. Resources have been reallocated, and anything non-AI related has been starved. And since working on an AI project is probably considered the only route to advancing your career, anybody with any ambition has moved to a team doing something AI-related. The result is that huge numbers of products and teams doing vital but non-AI related work have been hollowed out, and now we're seeing the consequences.
- Quoted phrase in the opening sentence
- Opening quote: “Office 364”
I’ve seen the chats about cascading failures and it’s impossible to not expect AI is involved somehow (likely brain drain and what not), but what are the options?
It sure looks like “fired everyone who knew what they were doing” but I feel like at this point you’re breaking open the check book and calling them, and even if they did that I’m assuming this shouldn’t be a “normal” event?
- Quoted phrase in the opening sentence
- Opening quote: “So email uses something called Microsoft Exchange Server”
Is this what it feels like to be old?
Note that the infra for M365, Azure etc is different. They would be running on servers hosted in MSFT DCs but have completely different CI/CD pipelines. M365 services have their own deployment pipelines and it takes on the order of weeks to deploy your changes to production.
Considering the fact that Outlook is down, clearly email doesn’t seem to be working. So email uses something called Microsoft Exchange Server, there used to be an on-premises version of this but MS stopped supporting it to run the cloud version hereby called M365. Email is one big “macro-service”, if you’re running Windows Server, look at the process called “EdgeTransport.exe” this is responsible for sending/receiving email on Windows Servers. There are probably multiple 100s of services supported by 100s of teams that are run while email is routed from sender to receiver via MSFT Exchange servers. My recollection is that even if one of these services goes down or introduces latency in the pipeline, it caused a major incident. When I was working in M365 Security in 2024, this Exchange Server pipeline was called “legacy” because it’s one big .NET Framework service. I don’t know if they upgraded to .NET core but developing on this was as HN comments say, very janky.
The reason Teams doesn’t seem to be down is that Teams services are completely different and are written using .NET Core and have their own separate release pipeline. It was much easier to interact with Teams services. I actually worked closely with the team that was responsible for ingesting Teams messages to the customer’s data store. Their code base was much more modern and easy to understand. Exchange Server not so much.
I don’t know if what I said is accurate but know that Exchange server code was like a fossil that didn’t change as much, over the ~5 years I worked on it from 2019-2024.
Story time over.
It's been hours, and the status updates still feel like there is an undertone of frantic panic (understood if you can't determine the root cause). When I think of past major outages, they may have been down for hours but usually folks knew what the root cause was relatively early, even if remediation took some time.
I wouldn't be surprised if AI coding and release pressure was a primary cause, so I really hope the future post-mortem is made publicly available.
- Quoted phrase in the opening sentence
- Opening quote: “goodwill”
And the other part is the "goodwill" you mention - if you jettison people for nothin en masse, word gets out, and make it hard to hire in the future
- Ordinary term used more than once in the same comment
- “lump” appears 2 times
People do this intuitively with payments (negative). They'll buy a timeshare or a boat (expensive, "lump" cost) when it would be much cheaper on net to stay at resorts or rent a boat and pay by usage.
They'll pay for subscriptions (automatic payments) rather than pay per experience. Many people will pay $20/mo for Netflix, watch it twice a month, but would never rent movies for $3 on Amazon.
They'll pay a big premium for "unlimited" data plans when this actually makes little sense for anyone vs. paying by usage.
This isn't to discount the issues with NVIDIA and whether they knowingly participated in circumventing chip bans. Or conflict of interest issues. But running a business that benefits China as a Chinese national and making some reports to the nation just doesn't seem like "spy" to me any more than being part of the British East India company made a Brit a spy.
But Jensen Huang has admitted to a longstanding affair with the CEO of a company that appears to exist only to evade ITAR restrictions. It's just impossible to believe that Jensen did not know what MegaSpeed was doing. While by all appearances he facilitated and benefited from it personally.
And one can also believe that ITAR restrictions on GPU sales are dumb, but evading them still counts as selling sensitive weapons to the enemy, both legally and politically.
My understanding is, the thing that got him effectively fired, [0] is not the affairs themselves, it was not being candid with his board about the extent of the problem–he admitted to them the affair with Alice Huang, but didn't tell them about his other affairs (including at least one with a direct report) until after the board was made aware of them independently.
A board can put up with a CEO who cheats on his wife. It can't put up with a CEO who hides things from it.
[0] formally speaking he resigned, but it seems likely the board communicated to him "if you don't resign, we'll fire you"
The hot patching is unusable. It takes 11s to compile the patch after a simple change: (Some("hi") -> None), and then relax gets a compiler error when refreshing the page.
The project where it miscompiles only has a few very basic dependencies; a clean compile takes 1.3s, incremental just 0.25s and tests take ~0.1s. Relax takes a whole 1.4s to run the tests (unsuccessfully).
The PE-150 is a great example of the absurdity/sadness of the embroidery world: today, you can have those machines for $100 on eBay, completely functional, but being sold/abandoned because they use a proprietary cartridge holding proprietary data that no one wants to deal with.
Even novel Brother machines that have USB connectors still force you to use terrible apps and lock you into subscriptions. This entire world - which is/should be full of twee and about making beautiful things with your hands - is somehow corrupted with this merchandising/everything-software-should-have-a-price mentality which is just so sad.
Nothing to announce announce, but I 100000000000000000000000000000000000% want to make embroidery machines more accessible, open, and free of this balagan.
A few more links on this topic:
- https://github.com/CreativeInquiry/PEmbroider !! Check the "Motivation" section of the readme!
- https://emberdesign.net/ - a startup by another friend, with a really great online editor, and which exports a variety of formats
[0] https://owentrueblood.com/blog/2024/12/10/reverse-engineerin...
When I'm doing stuff like this, I always have this thought in the back of my head like "man, this is awesome- I bet they try to stop people from doing stuff like this soon". Like there'll be an in-built "do not assist in reverse engineering or circumventing subscription-based services" instruction.
- Quoted phrase in the opening sentence
- Opening quote: “China hawk”
I have no idea whether this is legit or not (there's no link to any code), I'm mentioning this because all the comments here are assuming truth without verifying the contents.
It’s only weird if you come from languages like Java where “primitives” are distinct from “objects”, which is a self-imposed limitation the language imposes.
But a new Flash model is very welcome. Argon and Carbon are very slow. In the time it takes for them to complete a single task, Opus already managed to complete multiple things. They’re so slow, I started using 3.8 Flash over them. (A lot of it is also because of how terrible agy is. Before doing any task, Gemini feels the need to hover up a bazillion files into its context when the task is something simple like “update the docs of this controller”)
Also this sounds like Argon is dead now
Apple has anti-spam app policies that basically limit innovation and competition in certain product categories. An extreme example would be Apple not allowing any more "sleep music apps" b/c there is enough in the store.
An investor actually approached me about buying a couple mobile apps I made b/c they are "aged" and don't need to go through the rigorous first-review approval process
Not all, very likely not even most, of course, do this, and it's not always truly mutual or healthy, but surprise surprise, not every couple wants strict monogamy. They just don't want society to judge them for it.
- Quoted phrase in the opening sentence
- Opening quote: “where there's smoke, there's fire.”
Three different news orgs have reported the different affairs.
Your claim that supply is effectively fixed also seems false. Transmission investment driven by new demand grew 17x in five years. The problem is that capex deployed to serve data centers is being paid for by households, not that it cannot be deployed.
Real-world data also cuts against you. New York and New England are among the hardest places in the country to build energy infrastructure, yet the study found no clear price increase there from data centers.
The bill you cited would fix much of this, but it would do so via provisions forcing data centers to pay for the costs they cause, instead of forcing households to subsidize them.
If your point is “it’s policy,” fine. But the policy causing this is cost allocation, not permitting.
Your comment doesn’t engage with the article’s central finding at all: who pays.
- rsi won't happen immediately, and is inherently unpredictable, so they need to bridge the gap
- it makes it easier to trade their shares/ownership with their suppliers. they're fighting over compute allocation like everyone else.
- their "public benefit" plans have always involved trying to share the upside with the public before it goes "exponential"
- Quoted phrase in the opening sentence
- Opening quote: “Markets can remain irrational longer than you can remain solvent”
Anthropic and OpenAI will have to become more of the end user application stack. Files, calendars, emails, photos, and much more have to pass through them for them to keep making money. Else they cannot make money like the way they have been in this early era of LLMs.
Classifications impose structure on a collection of celestial objects, and we can derive relationships, commonalities, understand their development, the physics governing these objects, and build useful physical and mathematical models to widen our understanding of the universe.
Most reasonable scientists understand that some of these objects will blur the edges—like many moons being more massive and larger than Mercury. Or like the largest super-Earth exoplanets being nearly as massive as Neptune, or the largest gas giant exoplanets being 30-80 times as massive as Jupiter and hence having a surface temperature of ~2000 K. But that is part of science, and possibly even where the most interesting work is.
- Ordinary term used more than once in the same comment
- “dwarf planet” appears 2 times
I don't agree that "its obviously true that it was the right move". Instead of demoting Pluto, they could have promoted Ceres, and let Eris, Haumea, Makemake, etc, be planets too. Under that proposal, they could even have the category of "dwarf planets" encompassing them, it is just that "dwarf planet" would be a subcategory of planets rather than a disjoint category from them.
Thanks any Googlers who had a hand in this
This model naming scheme works for separate products, but using elements, molecules, etc. for products you're supposed to compare with each other... Not very helpful.
If anything, my intuition would say that Hydrogen is more powerful than Argon... I don't know. Not liking this naming scheme trend.
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “entry level”
But it is priced the same as the non-discounted 3.8 Flash, considerably higher than what anyone is paying today for 3.8 Flash or 3.5 Flash Lite or the deprecated 3.0/2.x Gemini models. How does this work? Is Google abandoning the “fast and cheap” tier? That seems like a mistake since plenty of workflows are absolutely price inelastic, meaning when the 3.8 Flash discount ends at EOY, lots of current enterprise Gemini customers would have to take their business to another shop??
- Quoted phrase in the opening sentence
- Opening quote: “soneshot”
So to get any model working on $OLD_HARDWARE, the hardest part of the task is now sourcing the hardware itself and giving the agent ssh access -- a modern agent will be able to source a compiler, write the implementation, optimize it, test in qemu (or any other simulator) and push it onto the device.
Example prompt: "write an inference engine for qwen3 0.6b in pure assembly that runs on this device. Write a script to attach the weights to the resulting binary. Prefix is supplied as a stream of u32 token IDs on stdin. The engine streams u32 token IDs on stdout."
In general - I am wondering how engineering interviews change in the age of LLMs, Jane Street, tech-wise is a "thought leader", at least having opinions, sharing them is part of how they recruit "the best", i think oxide does this too.
So in some way, in this time of change it makes sense that they are noisy... It also makes sense that the noises they make may filter down...
first, a coding problem that is solved live (right now, online) -- it's not a hard one and most LLMs can easily one shot it.
BUT: if you are not a senior developer, you need to do it without LLM, and if you are a senior+ and do it via LLM, the bar is super raised and now you need to explain in details everything the LLM wrote as if you wrote it yourself.
the main component here is to know if the candidate understands coding in general, understands problem solving and how to dive into an existing (although quite small) codebase. solving the problem is not really the goal -- in fact, most candidates we hired did not solve it 100%, but were able to understand and explain everything that they put it on code. this usually takes 1h30.
(we also ask the candidate to open a PR against the repo just to see if they know the basics of git -- you would be surprise how many people cannot do it).
the second is an architecture interview, where we build a system together BUT instead of doing the whole spec, miro board, whatever, we do it in more of a free way: we start with a really simple, MVP level, spec and we ask how the candidate would build it. then, we add another feature, and we ask how they would go for it. during this whole thing, i ask random questions like "why would you use x instead of y?" or "why do you prefer this approach?".
one important thing: we allow the candidate to say "i don't know" and we tell the candidate that there's no gotcha questions (which is true, i hate these kind of questions). this lets the candidate be super comfortable (feedback we had from real people).
in general, this flow helped us a ton and i really really like running it :)
(edit: spelling)
- Quoted phrase in the opening sentence
- Opening quote: “Given the opportunity, players will optimise the fun out of a game”
I have a bunch of plants on my window sill, and considered getting moisture sensors and automating watering, but I realised that kind of defeats the point of looking after the plants myself. On top of the satisfaction of manual work, I recently realised that it's taught me an intuition - the quirks of how much water each plant wants at different times of year (even cacti are thirsty in summer!), and how soil composition and pot size affects water retention. It's probably not generally transferable knowledge, but it was fun to realise I'd come to know my plants really well.
The joke is that people wanting to write Python like Java - with an implicit reference to an object's instance - would attempt to import Java's `this` keyword.
Instead of getting Java-like behavior, they're presented with the Zen of Python. You wouldn't be wrong to think that it was as much a commentary on other popular languages of the day as it was a guiding ethos of Python itself.
"Beautiful is better than ugly. Explicit is better than implicit."
- Quoted phrase in the opening sentence
- Opening quote: “A Plan for Spam”
(EDIT: Robert Woodhead apparently shares in the credit, too: https://www.ceas.cc/papers-2004/136.pdf https://ceas.cc/papers-2004.html . Apparently Rob Hooft was another implementor? I can't find a good source for that though.)
Another thing that made me feel close to him was his work on the Python Cookbook 2nd Edition, in which he (and other big names in the community) delightfully talks the reader through intricacies and insights of programming, "We read Knuth so you don't have to".
Watching Tim do his thing was a pleasure. He'd go from long, deep technical dives (that he'd make as approachable as possible) into comic relief and human connection in the fractional wink of an eye.
The brief interactions we had will always be cherished as high points in my Pythonista trajectory.
One favorite of mine was this response: https://www.python.org/doc/humor/#id15. I also like https://www.python.org/doc/humor/#id19 very much.
I was an active participant in the comp.lang.python Usenet channel in the late 1990s.
I learned much from reading Tim Peters' posts. To many, including me, he was affectionately referred to as "Uncle Timmy."
One of the things I learned was that I still had much to learn about the art of programming.
Much of the little I know about numerical methods comes from reading his posts. It was fun to read his stories about Kendall Square Research and the (for me) old days of computing.
I remember posting questions about things I didn't understand, which he figured out and explained. [1]
I remember bringing up concepts I thought were specialized and esoteric, only to find that it was actually just my lack of experience. He gently corrected misapprehensions like mine. [2]
He wrote a lot on comp.lang.python. If I recall correctly, at the 7th International Python Conference in Houston, November 1998, there was Festschrift in his honor. He would use <wink> in his messages, and often end with something like "let's-hear-it-for-lambda-in-curly-assignment-stmts-ly y'rs - tim" (that's from the posting where he outlines the Zen of Python). I wondered if they were collected by looking for messages containing an '-ly' only to have Andrew Kuchling remind me about the "From" header. <wink>
Here is Guido van Rossum starting the thread on "In Memoriam: Tim Peters", at https://discuss.python.org/t/in-memoriam-tim-peters-1952-202... .
Here's an interview of him at PyCon 2006, https://www.youtube.com/watch?v=1wAOy88WxmY
[1] In one case, I was parsing a file format where a field was usually three spaces, but was sometimes an integer. I couldn't figure out why one parser was so much faster than the other. The answer was that one tested for three spaces first, and if that failed tested for the int, while the other did the int test first.
Yes, this is something a senior developer knows. I bring it up now to highlight how hotshot-me didn't have that experience, learned that experience, and learned it from someone who was kind about sharing his knowledge.
[2] I was doing bioinformatics back then, and learned about dynamic programming as way to do sequence alignment. I didn't think others knew about the technique, and thought I was bringing esoteric new information to the discussion. Uncle Timmy had used dynamic programming techniques for speech-to-text software at Dragon Systems, and politely pointed out it was more widely known. He also implemented Python's 'difflib'.
- Quoted phrase in the opening sentence
- Opening quote: “import this”
$ python -c "import this"
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!I noticed that the quality of email text has gone up around my work these days. everyone is sounding like a master of drafting emails. Ofcourse Ai has a role in it. But real cool thing about this is, this is pulling up people's thinking to have a structure, minimalism and sequencing of expression. Same as how textile industry has enabled people to have an style and expression in clothing.
- Quoted phrase in the opening sentence
- Opening quote: “massively illegal”
NVIDIA is licensed by the United States government to sell GPUs to China, and they do so at a rate well under their licensed quantity.
Read up on 91 CFR 1684 which directly contradicts your claims.
Your most important argument is categorically false and completely unresearched.
Your subsequent claims also have no basis: you cite a bunch of cases in which people leaked sensitive information as equivalent to the Jensen case, where the affair was with the CEO of a customer they were legally selling product to, and where we have no evidence that any leaks occurred.
Why not just sell to not-sanctioned entities, ensure compliance to the best of your abilities and otherwise keep your head down? Again, wasn't like they struggled to find buyers for their chips.
Considering Megaspeed, I now see this in a very different light. Him cheating is personal and I wish the affected members of any family of a cheater the best, but not relevant for us outsiders.
Being honey trapped very bad securities wise, but he'd be a victim (and evidence for why we shouldn't discount Mistral in the frontier lab race [1]). If sanctions avoidance went all the way to the top, that is hard to negate even for a board that is interested in keeping him. At that stage he was neither honey trapped nor "merely horny"...
[0] https://www.youtube.com/watch?v=1H3xQaf7BFI
[1] https://time.com/archive/7146565/hollandes-popularity-goes-u...
On the other hand, many people claim that machine-generated software STINKS. That it is extremely verbose, that it reimplements similar methods over and over again. That it would rather cut corners at a low level than build high-level abstractions. That it pulls in libraries and makes serious security mistakes. That it writes tests that are basically incomplete. That it is unable to synthesize and keep context. In short, it has the same flaws as humans.
I think these are binary points of view, and both are right. We have vampires that are incredibly fast, super-strong, super-intelligent and super-agile, that suck your blood (your money), and that die as soon as the sunlight of security or complexity hits them.
There has to be another way. Nobody questions the versatility LLMs provide, or the boldness they give you to take on new projects. But I am not convinced that programmers or software engineers are going to disappear. I am not convinced that a manager can ship a new feature in a couple of afternoons and then lay off, or skip hiring, a junior or senior developer. There is a line near the beginning of Dune that goes something like this: "there was a time when men handed their thinking over to machines in the hope of being freed, but that only allowed other men with machines to enslave them."
We need to find a new path between smartphone addiction and being dumbed down by LLMs.
- Quoted phrase in the opening sentence
- Opening quote: “I want it to be true that perfectly deterministic tooling is still important.”
Of course it is. The AI coded apps only (debatably) work as end-user apps. They are thin little bumps on top of the software mountain. So much, including all the AI tools, depends on efficient, perfectly deterministic tooling.
It is almost hypocritical for AI enthusiasts to say we don't need to look at code anymore, while everything they do is build on piles and piles of infrastructure and tools that are carefully hard-coded, deterministic building blocks. The whole thing would come crashing down if everyone embraced vibe coding at every level.
I am just constantly baffled by people thinking that because we can make (crappy) end-user apps and one-off tools, no one needs to code anymore. Does anyone build solid tools and libraries? Does anyone still get pleasure from building a rock solid, snappy app?
I can feel all the AI coded apps and website turning to ever buggier sludge under my fingertips, and people are rejoicing that this is the way of the future.
I refuse. I will not touch Claude.
My reasoning was that that he had become too powerful while largely avoiding politically charged positions, or other "stuff" that can be used to "control" him.
The political and intelligence establishment doesnt particularly like powerful individuals who remain politically independent.... outside of their control.
But the extramarital affair with Alice Huang is quite different. NYTimes reports that Alice Huang is a Chinese spy, with whom Jensen Huang may have conspired to break the law, selling advanced NVIDIA chips to China. That affair puts the whole company at extreme legal risk. Gates, Bezos, and Brin have nothing like this on their records that I'm aware of.
As I write this, the top post on HN speculates that this is "the tip of the iceberg," indicating that there at least may be more affairs yet to be uncovered, and, plausibly, Jensen Huang may have committed even more enormous mistakes with serious consequences for NVIDIA.
It's perfectly sufficient to have a CVE for just memory corruption, so the "RCE" framing here feels overstated. Particularly when an LLM should easily prove RCE out if it is in fact present.
>As of the time of this blog’s publication, no exploit is available and there are no reports of exploitation in the wild.
Since when does "memory corruption" = "RCE"? Last week I found and reproduced a memory corruption (a use-after-free) in PHP's runtime after running an on-premise agent for just 30 minutes. There's nothing about it on the internet. Should I write a blog post about a scary new vulnerability? :)
Learn to read and don't spread these editorial title lies.
A better title: "TSMC reports employee data found in public to SEC" or something like that.