you don’t hire interns because they’re gonna ship mad features
Every intern is an investment in a future hire. Perhaps A modern day apprenticeship.
You don’t hire juniors cause you need that extra 2-3 bug fixes per day. You hire juniors so you can turn them into seniors
When you say “ai will replace juniors” all you’re telling me is you don’t understand mentorship in software careers, or you think of every engineer as a ticket factory.
We do need to rethink how we upskill this new generation of SWEs though. The best engineers are great at AI (coding, context eng, etc) and great at software engineering - (systems, algorithms, debugging, architecture)
More seniors are good at the latter, more juniors are good at the former, but a lot of ai coding takes away the “friction” which, as @badlogicgames so helpfully pointed out, is where you learn
we kinda hit that slop wall in December after doing Ralph and blind RPI all of H2 2025. So this hitting around late April early may tracks.
Lmk if you wanna know what’s next
🍼 Different federal courts are making different AI rules — chaos for anyone who litigates in more than one.
🍼 If a court rules ChatGPT is "practising law," half the legal-AI industry has to redesign its product.
legal-ai.claytonroche.com
🍼 The judge said: "I don't care if a robot wrote it. You signed it. You read it."
🍼 Bad fingerprint science put people in prison. Bad AI might do the same.
🍼 The same week, OpenAI's law firm got caught lying with AI, and OpenAI got sued for being a fake AI lawyer.
What's happening with AI in the legal system:
legal-ai.claytonroche.com
tl;drs for 🍼 babies:
🍼 Suing-people robot is now worth a billion dollars.
🍼 The federal courts are writing rules for robot evidence.
🍼 Robot lied, lawyers begged judge not to be mad.
Both @hal2001 and @mrice32 warned us about Layer Zero's issues 18 months ago. Sad it had to come to come to enriching North Korea.
Any news on other teams taking it seriously? What other protocols are using the same settings?
x.com/mrice32/status…
thank god AI destigmatized and rebranded the term "token", thereby laying the foundation for crypto engineers, the original builders and purveyors of tokens, to be in vogue again someday
My ask is for a human who loves me to tell me if Claude is starting me down a sensible path.
Especially that modularization step--Is that a sensible way to go about this?
Will eagerly watch videos or read articles too 🙏
⚠️ Extract any function you touch out of the God file into a domain-scoped module (db/payments.ts, db/booking.ts, etc.).
Every fix is also a small modularization step. The codebase converges on the spec's structure incrementally — no big-bang refactor.
Wishing a senior dev mentor🤞
Brownfield Next.js/Supabase marketplace, vibe-coded, no spec, six God files, flat route structure.
Did a RPI (Research → Plan → Implement) process across 7 domain modules to reverse-engineer a full application spec from the source code.