Explained: Agentic AI

It is 11:40 pm and a deploy is blocked by one failing test. You paste the stack trace into a chatbot. It suggests a fix. You copy the fix into your editor, rerun the suite, get a new error, and paste that back. Nine round trips later, the test finally passes. The model did the thinking, but you did everything else: running commands, reading output, deciding whether to keep going. Now picture the same night with a coding agent. You type one senten… Read More

Explained: Kerberos

It is 9 a.m. on a Monday. You type your password once to log into your work laptop. Then the day just happens: the shared drive opens, the intranet loads, Outlook connects, you print to the machine down the hall, you SSH into a build server. Not one of those systems asked for your password. Somehow, they all know who you are. That quiet magic is, in most corporate networks, Kerberos . It has been running underneath Windows Active Directory since 2… Read More

Architecture: NATS

A microservice publishes an order event. Three other services need to know about it: inventory has to decrement stock, billing has to charge the card, and shipping has to queue a label. In a lot of systems, that fan-out means standing up a broker, provisioning disks, tuning partitions, and running a coordination service alongside it. Then you check the memory footprint and realize the messaging layer is heavier than the services it connects. NATS … Read More

Explained: SASL

You're wiring up a new mail server. You reach the part where clients log in, and you open the SMTP docs to find not one login method but a menu of them: PLAIN , LOGIN , CRAM-MD5 , SCRAM-SHA-256 , OAUTHBEARER , GSSAPI . Then you open the IMAP docs for the same server, and it's the same menu again. Then LDAP. Then XMPP. The same names, the same handshakes, described separately in four different specifications. That repetition is exactly the probl… Read More