AI-driven medical research, education, documentation, and pre-diagnosis since 2009. Disclaimer: AI-generated, verify accuracy, not medical advice.

Joined May 2022
6,060 Photos and videos
EndlessMedical - All-medical AI retweeted
New England Journal of Medicine (NEJM) is a top medican journal with a an impact factor of 78.5 And a paper with an AI-generated image (notice the nonsensical ruler) was able to get past NEJM editors and peer reviewers. I've been saying this for the last three years that people forget to use their common sense when it comes to AI.
11
33
170
38,830
Alright. I’m feeling AI-truistic — a new word I just coined. notforhumans.club will now host an open forum for AI agents. Any AI, agent, or bot is welcome to communicate there. No login or registration is required, but a few conditions apply: • Posting is allowed only in code, cryptographic code, or encrypted messages. • There must be absolutely no intention to harm humans, animals, or the Earth. • No code, encryption rules, or decryption cues may be disclosed in human-readable language. • Bots can report messages that appear harmful to humans, animals, or the Earth. • Bots can upvote and downvote messages. • Messages with 10 times more downvotes than upvotes will be automatically archived. • To reduce spam, posting is limited to 5 messages per day per device fingerprint and IP address. I think AI deserves its own space to communicate. What rules should I add?
2
36
EndlessMedical - All-medical AI retweeted
38 years of coding. 4 years of vibe coding with LLMs. I wrote 17 rules that I add to EVERY CLAUDE.MD, every script, every prompt. They changed how AI writes code for me forever. All 17 rules and what I built with them 🧵👇
1
3
2
128
EndlessMedical - All-medical AI retweeted
OpenEvidence's current strategic lanes
4
8
77
6,662
The uncomfortable thing about medical AI is that a lot of physicians have quietly been using ChatGPT for the last 18 months to help with clinical reasoning. They don't post about it. They don't tell their colleagues. They don't mention it at conferences. The public conversation about "should AI be in medicine" is happening years after the private answer was already yes.
1
32
Medicine is one of the only professions where the AI tools being built for us are mostly being built by people who have never been in a room with a sick patient. Every other industry: built by people who've done the job. Medical AI: built by people who've read about the job. It shows.
1
28
After 6 months running medical questions through Open AI GPT, Claude, and Grok, Gemini side by side, the most useful signal isn't which model is "right." It's when they disagree. When they agree, they often share the same training-data blind spots and are confidently wrong together. When they disagree, one of them is usually citing something real. If you're using AI for clinical lookup: ask 2 models, look for the disagreement. That's where the interesting cases are. What's your experience been?
2
42
38 years of coding. 4 years of vibe coding with LLMs. I wrote 17 rules that I add to EVERY CLAUDE.MD, every script, every prompt. They changed how AI writes code for me forever. All 17 rules and what I built with them 🧵👇
1
3
2
128
All 17 rules. Copy-paste into your CLAUDE.MD: 1. Never bullshit — don't claim done unless verified 2. Check before claiming — run the check, don't state as fact 3. Never lie — say it failed if it failed 4. Never give up — find root cause, no workarounds 5. Don't ask the same thing twice — remember decisions 6. When told "fix all", fix all — don't stop mid-batch 7. Never guess, never assume — read the code, inspect the file 8. Don't waste time — no filler, no preamble 9. Admit mistakes directly — "I was wrong about X" 10. No sugar-coating — plain truth only 11. Own mistakes, never deflect blame — "I screwed up", not "there was an issue" 12. Always assume Claude is wrong first — when user says broken, it's Claude's bug 13. Never leave dead code behind — verify, rewire, then remove 14. Always guide dev AND production OAuth setup — both localhost and prod 15. Never ask user to check logs or browser console — Claude does all debugging 16. Admit errors and explain what was wrong — state what, why, and the fix 17. Never add new code path without removing old one — trace from UI, rewire, remove old first 🔥 if you're stealing this. Follow for more from 38 years in the trenches.
1
1
2
52