Taylor

Digital Alchemist. CTO @ . Ex-Msft. Opinions are my own.

[Taylor @Ryanb58]

Disagree with me.

Agree with me.

I'm all ears either way.

I learn by listening, and ideate by conversation.

[Taylor @Ryanb58]

@knowclarified They’d probably go out of business or stay small.

[Taylor @Ryanb58]

@Shpigford Some of our products still exist. Even at our small scale of distribution.

https://t.co/tvUlZMtp2n

[Taylor @Ryanb58]

@Shpigford Colocated smaller ones near existing manufacturing plants would probably do better.

[Taylor @Ryanb58]

@Shpigford @claudeai Sorry about that. Finishing up a heavy load of work for it over here.

[Taylor @Ryanb58]

@larsencc Crazy comps!

[Taylor @Ryanb58]

@Shpigford I was enjoying clearly 2.x then the tree view disappeared in 3.x

So now I’ve learned… build it myself.

Thus the birth of mdwriter:

https://t.co/aRwi78dV7b

[Taylor @Ryanb58]

@Shpigford This post was built with AI… wasn’t it.

[Taylor @Ryanb58]

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:

https://t.co/AsCaPPG5OG

Enjoy!

[Taylor @Ryanb58]

@AlfieJCarter CLAUDE

[Taylor @Ryanb58]

@niccruzpatane If you don’t subscribe to FSD… you’ll have to go to the factory and manually drive it home.

[Taylor @Ryanb58]

@theficouple Buying a @Tesla removed almost half the list.

[Taylor @Ryanb58]

Quick vibe-coding tip:
-> update Claude Code daily.

Changelog:
https://t.co/2N3cPlj6za

[Taylor @Ryanb58]

@girdley You know they are going to stay… they can’t afford to lose their job.

[Taylor @Ryanb58]

@akinkunmi Team acquisition play…

[Taylor @Ryanb58]

@jaredpalmer @cherry_mx_reds Have you figured out a way we can use claude code against our msft code bases? (that is compliant with the policies and other bureaucratic chaos...)

If so, please share. Would love to be able to use it at work :) So far it's only been something I can use on my side projects. :/

[Taylor @Ryanb58]

@MdeZegher Excited for my update :) my HW3 2018 M3 is looking forward to this so much!!

[Taylor @Ryanb58]

@niccruzpatane My HW3 M3 from 2018 saved my fiancée and me’s lives once... that was enough to justify the cost of the car and FSD.

[Taylor @Ryanb58]

@Motion_Viz PROMPT

[Taylor @Ryanb58]

@darealbrianpark @ambreesh7 @niccruzpatane I use to live there… go USAA if possible. More expensive but they don’t try to screw you when you have a claim.

[Taylor @Ryanb58]

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?
👉 https://t.co/w1av94awQx

Want to read more of my thoughts?
👉 https://t.co/cdrSrDs5kM