Most software is dead.
No one ask AI to "build me software."
We'll say "I want to touch up this photo by hand," and our AI will spin up our own Photoshop on the spot.
Each of us will have our own version, customized to exactly how we work.
We'll say "Are sales up or down this quarter across all our ecommerce platforms?" and it'll build a dashboard that hooks into every API and keeps itself updated forever.
No extra subscriptions.
We won't even notice we're building software. Our AI agents will do it for us.
The apps we pay for today won't get replaced by better apps.
They'll be replaced by no app at all.
Tell me I am wrong below!
After being annoyed by having to deal with DNS records directly, I decided it was time to make an agent skill focused on interfacing with porkbun.
It fixed my DNS issues with ease.
You can find it here:
skills.sh/ryanb58/agentskill…
Enjoy!
Quick vibe-coding tip:
-> update Claude Code daily.
Changelog:
github.com/anthropics/claude…
As AI begins to write more and more code, you might start to wonder one of the following:
“Why do we even need Software Engineers anymore?”
“Am I about to be replaced by an LLM that writes cleaner code than I do?”
And honestly… those are fair questions.
But they also miss the bigger picture — and a bit of history.
Software engineering has always evolved alongside automation.
When we moved from assembly to higher-level languages, people said the same thing: “This will replace programmers.”
When frameworks abstracted away boilerplate, the fear was the same.
When cloud platforms automated deployment pipelines, again — the same anxiety.
But each time, engineers didn’t disappear.
They leveled up.
They shifted from syntax to systems thinking. From typing code to designing outcomes.
From how something gets built to why it should exist at all.
And that’s where the next era is taking us again.
The Software Engineer of tomorrow isn’t just writing code.
They’re AI-fluent — orchestrating tools, reasoning about data, understanding trade-offs, and guiding automation toward meaningful impact.
If AI is the new junior developer, then great engineers are becoming the new architects of intelligence — designing, validating, and steering what the machines build.
⸻
We’re not witnessing the death of software engineering.
We’re witnessing its graduation — from code creation to intelligent system design.
⸻
Looking for your next AI-fluent role or team?
👉 provn.co/?utm_source=x&utm_m…
Want to read more of my thoughts?
👉 taylorbrazelton.com
Lately I’ve been noticing something interesting in how companies hire and promote.
They’re not chasing long lists of technical skills.
They’re not obsessed with fancy jargon or perfect resumes.
They’re looking for two things.
And honestly… they’re not even new.
✅ Great communication
✅ AI fluency
That’s it.
But those two skills are changing careers right now.
⸻
Great communication
Not “give a great presentation” communication.
I mean the simple, human stuff:
• explaining your thinking clearly
• giving updates that calm the room
• being honest about blockers
• helping people understand where things stand without digging
It’s underrated.
But it’s the thing that makes teams trust you.
⸻
AI-Fluent
Not AI-expert.
Not “build your own LLM” energy.
Just someone who uses AI the way we all learned to use Google:
• to work faster
• to unblock yourself
• to draft, iterate, refine
• to automate the boring parts
• to make better decisions, faster
AI-fluent people look like they’re working at 2x speed.
Leadership notices that.
⸻
And here’s the real magic:
When someone communicates well and uses AI well…
they instantly show up as the person everyone wants on their team.
They move fast, keep people informed, adapt quickly, and make the whole system smoother.
That’s who gets promoted.
That’s who stands out.
That’s who becomes “the one we can’t afford to lose.”
⸻
If you’re building these two skills right now?
You’re not behind.
You’re early.
Opinion: I think “great communicator + AI-fluent” is the new baseline. The people who embrace both — without ego — are about to unlock some serious career tailwinds.
⸻
Looking for a new role? Check out @AiProvn94864 — the home for AI-first and AI-fluent talent & jobs.
Want more of my thoughts? Follow me here on X or visit my personal blog:
taylorbrazelton.com
For the real ones… 🤣
Please don’t enter in your real passwords!!!!
->
taylorbrazelton.com/password…
Not only did I redesign my personal site recently…
taylorbrazelton.com/
I also posted something new to help people deal with the 💩 storm that is startup land.
taylorbrazelton.com/2025/09/…
Added cool partial effects to the landing page! Question is… are they distracting?
Do they even matter?
HTTPS://provn.co
My favorite time to merge and PR and deploy my code is during peak usage hours. When users are flooding in.
Stress Test.
As someone who struggled to find a reliable browser, I was influenced by @theo to try Zen Browser. However, Zen, being Firefox-based, was frustrating since many sites wouldn’t render correctly.
Then I discovered Orion, made by the @KagiHQ search team, which resolves many of my issues. I love its speed (WebKit-based), simplicity, compatibility with Firefox and Chrome plugins, and sidebar for tabs.
My only complaint is that it isn’t open source.






