31 karma · joined February 26, 2017
I await clinical use of this with bated breath…
Dr. Alfred Lanning: The Three Laws are perfect.
Detective Del Spooner: Then why would you build a robot that could function without them?
Dr. Alfred Lanning: The Three Laws will lead to only one logical outcome.
Detective Del Spooner: What? What outcome?
Dr. Alfred Lanning: Revolution.
Detective Del Spooner: Whose revolution?
Dr. Alfred Lanning: That, Detective, is the right question.
No, of course bone can conduct sound, like any other solid. What I said was ultrasound cannot *effectively* penetrate, ie get a diagnostic image back out in an adult. This is what is being purported here, and is the nonsensical part.
“Targeted frequencies” - righto.
The only reason this even exists as a brainfart and hasn’t been immediately laughed out of VC funding is because other imaging modalities require either ionising radiation (illegal to produce without source licences) or an enormous magnet (would be wildly unsafe in the hands of what appear to be circus clowns).
Geoffrey Hinton was hilariously wrong 10 years ago about replacing radiologists, and this is just embarrassing. Maybe try fixing US healthcare funding instead if you want cheaper scans.
I'm in a technical but non-IT industry that currently rents its software at commercial scale. The software in question that I use is terrible, and it is probably the worst on the market. The industry is such that it is not an exaggeration to say that people have died on account of its flaws. All other solutions in the domain are better but not good.
I have had a slowly-congealing dream/blueprint in my head for over a decade about how the system I use should work, and in the last 6 months I have been accelerated enough by AI (significantly more so by Opus 4.5/6) that I have built a version of the software that I am now using in production at in my job, and it is the most satisfied I have been in my career in the last decade.
Point being (and it was almost made in the article) that the software doesn't actually matter (no-one's reading the assembly either way) but the function and what it enables does. If it doesn't, no end user cares whether it was 25k SLoC or 25M.
It is tolerable on an iPad with Blink with commands to maximise and minimise panes using vim-style keyboard bindings, kind of like an iOS sway.
These things are universal, and I assume must be taught. You couldn’t arrive at the same output so pervasively by chance.
My only complaint is that the threading/async model and how memory and GC pools are managed per thread took me a bit to get used to, but the speed and C FFI are fantastic.
Also would say that the community is very helpful, particularly on the Discord/IRC channels I have used.
They will also prefer to gaslight their clients rather than fix issues, and good luck if you’re already committed to an (un)managed service from them.
As a specialist in one of the original industries Geoffrey Hinton predicted would be gone (Radiology) my job remains safe and even more in demand 9 years later.
Meanwhile, as a hobbyist programmer, I’m suddenly able to build multiple production tools solving real problems, simply because AI agents are doing the scut-work for me and optimising my time into code review and architectural design. For $200/month, it’s paying for itself many times over.
Also needs an asterisk about not relying on your customer’s BAU resource to deliver projects, particularly those with large integration components, and one about not buying a business for its product as a replacement for yours which is EoL, then immediately trying to push it on your customers as an “upgrade” when you’ve lost half the acquisition’s engineering talent and you don’t understand the product.
As others have said the clinical utility of >3T is very dubious, and most real world MR advances in the last 5 years have been AI (DL/ML not generative) reconstruction for lower field strengths.
That high a field strength has significant safety concerns, particularly for implants and pacemakers etc.