Senior->Junior mentoring has completely changed.
Experienced engineers now get fewer questions. Instead, people will ask their AI.
So the question you should ask yourself is: "How do I leverage all of my experience now?"
People ask how you trust code an AI wrote that a junior can't fully explain. The answer is that you don't just “hope.” You put up bumpers. Test suites, CI checks, AI reviewers, human reviewers, seniors on architecture. At this point, the job is keeping AI in its lane.
When users need help docs to understand a setting, we designed it wrong. And every option we add creates technical complexity, but it also gives the user one more decision to make. Good product design respects both of these factors, in my opinion.
At the moment, it does set a floor but only in the highest of risk areas. We are actively changing this so that parts of the app that were historically high risk can be analyzed as lower risk given their coverage.
A mixture of known risk (e.g. for us the booking page is crazy high risk) + how many edits the file has received recently and how many reverts have been needed + the coverage of tests/guardrails around the area being changed.
Ask yourself today: “who am I truly happy for?”
Then ask yourself: “what have I done recently to show them that?”
Stop waiting or forgetting to show you are interested and care.
Big congrats to the @useblacksmith team. They’ve built really nice systems for CI.
Crazy fast cache and sticky disks alone can knock off huge % of your CI wall times. Definitely recommend.
@sequoia is leading our Series C at a $1B valuation.
We started Blacksmith in 2024 to make CI faster and less painful. In January we ran 5 million CI jobs a week. Today it's over 90 million and growing, and we’re still early.
ALT Line chart of weekly CI jobs run on Blacksmith, growing from 5.4M in January to 90.5M in October 2026.
AI is reshaping software engineering into two increasingly distinct paths: product engineers focused on what to build and why, and foundational engineers focused on the deep systems, infrastructure, security, and scale that make it possible.
As AI handles more of the "how," engineers will have to decide where they want to create the most impact.
We had a couple lapses in internal processes for reviewing heavy DB hits and firewall changes. Those have since been rectified.
99.92% uptime this year. Highest we've ever had at @calcom , by far. We could ship faster and let users eat the bugs. Some big names in our space do exactly that. But that's just not how we roll anymore. If people are relying on us to run their scheduling, it has to actually work. In fact, I want this number to be 99.99% soon.
Keith Williams retweeted
There will come a time when how code is written won't matter. But for now, I still care that the code looks and reads right.
I'm not ready to let go :)
I still spend a LOT of time figuring out the right abstractions and interfaces (user and programming).
I recently built two components for shadcn/react. Each took weeks of UX research, experimentation, and iteration to get right.
AI hasn't accelerated this part yet, at least for me.
What it has done though, is help me fail faster. I can now go through many more failures before a component or code is ready.