Radiologists are not getting replaced by AI. Just as accountants were not replaced by Excel and just how software engineers are not being replaced by Claude.
2
148
You can fine-tune an open-weight model, or have your organisation’s trade secrets harvested by the leading AI companies.
Choose your brawler.
52
Clerking and discharging are two sides of the same coin.
Your ED will continue to be full to the rafters unless these two are sufficiently addressed.
89
The secret to hospital flow is supercharging the doctors.
Tools that give a resident the clerking speed and accuracy of a veteran consultant.
66
It cannot be the case that Britain has such a density of AI talent whilst most of our institutions are crumbling and starved of the benefits.
80
Daniel Kamel retweeted
What Is To Be Done?
I propose a simple plan:
Big AI companies should be allowed to build AI as fast and aggressively as they can – but not allowed to achieve regulatory capture, not allowed to establish a government-protect cartel that is insulated from market competition due to incorrect claims of AI risk. This will maximize the technological and societal payoff from the amazing capabilities of these companies, which are jewels of modern capitalism.
Startup AI companies should be allowed to build AI as fast and aggressively as they can. They should neither confront government-granted protection of big companies, nor should they receive government assistance. They should simply be allowed to compete. If and as startups don’t succeed, their presence in the market will also continuously motivate big companies to be their best – our economies and societies win either way.
Open source AI should be allowed to freely proliferate and compete with both big AI companies and startups. There should be no regulatory barriers to open source whatsoever. Even when open source does not beat companies, its widespread availability is a boon to students all over the world who want to learn how to build and use AI to become part of the technological future, and will ensure that AI is available to everyone who can benefit from it no matter who they are or how much money they have.
To offset the risk of bad people doing bad things with AI, governments working in partnership with the private sector should vigorously engage in each area of potential risk to use AI to maximize society’s defensive capabilities. This shouldn’t be limited to AI-enabled risks but also more general problems such as malnutrition, disease, and climate. AI can be an incredibly powerful tool for solving problems, and we should embrace it as such.
To prevent the risk of China achieving global AI dominance, we should use the full power of our private sector, our scientific establishment, and our governments in concert to drive American and Western AI to absolute global dominance, including ultimately inside China itself. We win, they lose.
And that is how we use AI to save the world.
It’s time to build.
Daniel Kamel retweeted
I've drawn a line chart that shows an AMU's fullness through the hours of the week. I've then applied a colour gradient to the line to show the length of stay of the patients included in each fullness snapshot. The darker the line, the 'heavier' the AMU.
Daniel Kamel retweeted
The reaction people are having to AIs that can find bugs in code is fascinating. Finally, we have the capacity to fix the crisis in computer security we’ve had for decades, and everyone is treating it like it’s a tragedy.
A central mistake here is that people regard this as “no one will ever be safe again” rather than “there will be a brief period when we get rid of most of the problems.”
People seem to be acting as though there will always be more security holes for these systems to find, forever, and so there can never be safety, but that’s not the way this works at all.
There are not an infinite number of computer security bugs in existence. It is only felt that way because we haven’t had the ability to carefully audit absolutely everything. There are also techniques that we could never afford to use before, like formal verification, that will let us vanquish a lot of the problems forever, but which require AI to really take advantage of because they are simply too labor-intensive for human beings.
This is not the beginning of some era of permanent insecurity where no one can ever feel safe again. It’s the end of a long period of insecurity where no one had any safety.
The problem is, certain companies are hyping this as “these tools are too dangerous to let anyone have!” Which of course means that people won’t be able to audit their own code to get rid of their bugs before they release software. Hopefully that too is also temporary. It would indeed be tragic if it wasn’t.
Daniel Kamel retweeted
I’m starting to think software engineering won’t die, it will just expand in role responsibilities as coding shrinks.
You will be a software engineer + security engineer + data engineer + AI/BI engineer all rolled into a single role. That is a minimal expectation.
Doomers: now that AI can write code all the software engineers will be out of work.
Reality: more software is being written than ever before, everyone is becoming a ‘software engineer’. There are more people writing software than there ever has been.
97
Finally!! An app for Copts who want to track the feasts of their favourite Saints.
Agios is live on the App Store.
New Saint icons each day according to the Synaxarium, liturgical readings, reminders for upcoming feasts/fasts and much more:
apps.apple.com/app/agios/id6…
4
180
Seeing this more and more on my timeline. Small groups of people going back and forth with Grok on the same topic within the same thread.
Definitely a new social behaviour.
1
1
348
Daniel Kamel retweeted
Here’s a reframe.
AI doesn’t take your job.
AI allows you to do any job.
So a coder can now make films.
And a filmmaker can now write code.
It allows a non-specialist to get started.
But a specialist will be needed for polish.
Grok's killer feature is that it lives on the X timeline.
All focus should be on nailing this integration.
1
224
The xAI button acts as a way to get the post inside the chatbot interface, what if I never needed to leave my feed to do this... this is nicely done on desktop but would be epic on mobile/tablet.
2
157
Good mobile solution:
- replying to a post w @grok is by default private.
- back and forth between grok and user continues
- conversation is private, only appears in grok tab history
93









