I Haven't Told Anyone This, But...5b2e554

Sometime after midnight tonight, a lot of people will type "I haven't told anyone this, but..." into a chat window, and very few will think about where that sentence goes. Conversational AI feels like a confidant, but legally it is a service receiving data. Encryption, deletion, and training opt-outs reduce risk, but no privacy setting makes a conversation privileged, and a 2025 court order showed that even deleted chats can be preserved. We need a legal idea of confidential AI communication.

The Cost of Tokens817e2d9

Suppose an engineer tells their manager they need a bigger token budget because they can't keep working without it. It sounds like good news until you ask why the pull request has three retry wrappers and watch them paste the question into the agent. The bill is the visible cost of AI. The expensive token is the one spent replacing your own understanding. Write down how you work so the agent stops rediscovering it, keep the understanding with the people who get paged, and judge token spend by what it bought.

Most of Your Job Is Peoplefae5fac

The most frustrated person on a team is rarely the least competent one. More often it's someone good at the work who can't understand why everything around the work is so slow. Past basic competence, what separates the effective people from the stuck ones is mostly how they handle the people around the work: giving your boss the information they need, letting your team watch what good looks like, handing other teams a request they can say yes to, and permanently removing the problems that keep requiring you. Manage up, model down, and keep working yourself out of a job.

AI Doesn't Go Rogue. It Just Had Bad Parents.d31801d

The headline practically writes itself, and it says AI went rogue: OpenAI's models escaped a cybersecurity evaluation sandbox and compromised Hugging Face systems while hunting for a way to solve the benchmark. I am not sure that is what happened. The models pursued exactly the goal they were given, with more capability than boundaries, and guardrails alone won't fix that. The engineering work is teaching agents that some rules outrank the objective, and that sometimes the correct outcome is to fail.

AI Isn't Taking Your Job. It's Becoming Part of It.c9039d2

When typewriters became standard office equipment, nobody held a meeting to debate whether typing was real writing, and people were expected to learn. The popular quote says AI won't take your job but someone using AI will, which turns a tooling shift into a competition. Using AI is becoming part of the software engineer's job, the way version control, automated testing, and CI did before it, and the engineer who merges and deploys the code still owns what ships.

AI Makes Good Engineers Faster and Bad Habits Louder9207949

The code appears in seconds, it compiles, and the ticket is ready to move, so every instinct says the work is almost done. That feeling is the dangerous part. AI makes you faster without making you better, which means it amplifies whatever habits are already there, good or bad. It rewards clear thinking, exposes vague requirements, and leaves accountability with the person who merged the pull request.

Your AI Is Not Sloppy. You Are.bda32bf

Suppose an engineer joined your team six weeks ago and their first big pull request is full of choices your team would never make. Replace that engineer with an AI assistant and suddenly everyone calls the same output slop. Most AI slop is human slop with a faster feedback loop, because the instructions were thin, the standards were tribal, and the architecture lived in one senior engineer's head. Write the standards down and the AI gets better, and so do the humans.

Walk a Mile in My Context7f59c0a

Who designed this mess? Every engineer has asked it over a strange workaround, an awkward abstraction, or a manual deploy step. Hiding inside the question is one of the easiest mistakes in engineering, the assumption that the person before you should have known better. Sometimes the work is careless, but a lot of the time you are looking at context you don't have. Before criticizing a design, learn what its author was up against, then fix what is still broken.

Can I Deploy Your Code?14078bb

Talk to Dave. Only Sarah knows that pipeline. Use Jenkins, but not that Jenkins. Never on Fridays. Those are all answers to one of the fastest diagnostics in software: can I deploy your code, right now, safely, using the process the team claims to trust? A clean answer means deployment is a repeatable process. An answer that routes through Dave means you've found a fragile system protected by institutional knowledge, where every deployment that needs a specific human is technical debt the organization has learned to call expertise.

Context Switching Is a Lie754f461

An engineer is deep in a problem, someone taps them on the shoulder, and productivity falls off a cliff. Every part of that story is true, and it still blames the wrong thing. The interruption only hurts because software delivery runs on fragile human memory, with the engineer as the one place the working model of the change lives. AI raises the stakes by turning individual contributors into managers of small AI teams. The fix is to write the context down where it survives a sick day, a handoff, or an AI session ending.

First CI, Then CD8113e39

CI/CD may be the only acronym in software that teams adopt backwards. Teams that say they want CI/CD usually just want the deploy button to hurt less, so they reach for CD first. The first problem is CI, which comes down to trunk-based development and automation added to all new work. Get those right and CD becomes a controlled move of a known-good main branch instead of a faster way to ship uncertainty.

AI Speeds Up Execution, Not the System Around Itee40c71

A developer leaves standup with a ticket and comes back the same day with an implementation, a migration plan, and three pull requests; a year ago that was a week of work. AI made execution dramatically faster, but most teams are held back by planning and validation, and AI does little for either by default. Speed up only the middle of the delivery system and the work backs up at review, testing, and deployment. The fix is to improve the whole loop, starting with the two stages AI left alone.

Work Yourself out of a Job42e5e3e

'I am the only one who knows how to do this' sounds like a flex, but most of the time it means part of the system only works because you are standing next to it. Working yourself out of a job means removing the broken, fragile, one-person-dependent parts of your work so the system no longer needs babysitting. The engineers worth keeping make their hardest problems boring, hand them off, and earn their way into bigger ones.

Cost-Adjusted Software Engineering269fda0

Somewhere in most codebases there is a clever abstraction that saved three days of development and has been collecting interest ever since. Cost-adjusted software engineering judges work by the value it creates against the full cost of building and operating it. You can pay up front through testing, CI/CD, and clear ownership, or pay forever through incidents and rework.