The best programmers today will be the next generation of product managers.

Companies should stop this non-technical “Product Owner + Scrum Master” nonsense and start empowering their strongest engineers to own, prioritize, and deliver the backlog.
t.co/qGDM3zBUaQ

A pleasure to teach Agentic AI this term at Istanbul Technical University.

We covered 17 agentic patterns: Agentic RAG, ReAct, Memory, Guardrails, multi-agent, Graph-of-Thoughts. Best part: seeing 40 student projects move from "use an LLM" to "design an agent."

RT @dhh: Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.

Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.

Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”

Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.

The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.

Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

RT @ealpaydin: "Scientists undertake basic research to generate new knowledge with no specific end goal in mind. Applied research is different in that it aims to find solutions to real-world problems." t.co/3zQAg87EUy

RT @rohanpaul_ai: "Hallucinations need not be mysterious—they originate simply as errors in binary classification.

If incorrect statements cannot be distinguished from facts, then hallucinations in pretrained language models will arise through natural statistical pressures."

- OpenAI Paper

I really liked this OS analogy for LLMs. Strongly encourage watching the full speech by Karpathy. t.co/df0wB6JqnU