Opinion
AI Doesn’t Replace Developers — It Replaces Bad Developers
A candid examination of what AI actually changes about software development, and why the best developers should welcome — not fear — the revolution.
Software Architect, Engineer & Leader
Sharp perspectives on AI, architecture, and the changing landscape of software engineering.
The discourse around AI and software development has become almost comically binary: either AI will make all developers obsolete, or it is merely a fancy autocomplete. The truth, as always, lives in the uncomfortable middle ground. AI is a force multiplier — and force multipliers are only as good as the force they are multiplying.
Developers who have built their careers on genuine problem-solving, system-level thinking, and a deep understanding of the “why” behind their code are finding AI to be an extraordinary accelerant. Those who have coasted on memorizing syntax and copy-pasting from Stack Overflow are discovering that their most valuable skill has been automated.
Editor’s Note
“AI is a force multiplier — and force multipliers are only as good as the force they are multiplying.”From the article
A candid examination of what AI actually changes about software development, and why the best developers should welcome — not fear — the revolution.
An unflinching look at vendor lock-in in the Microsoft ecosystem, and a practical argument for why Spring Boot offers a path to freedom without sacrificing enterprise capabilities.
A methodical walkthrough of every parallel between ASP.NET Core and Spring Boot — DI, configuration, data access, security, testing, and deployment — proving the move is evolution, not reinvention.
A profile of the person keeping the ship on course — the unsung role that connects strategy to execution in a high-performing software team.
First impressions of a new squad — the mix of personalities, skills, and shared purpose that makes a team worth writing home about.
Walking into a new role and a new codebase simultaneously. On finding your footing when everything is unfamiliar and every choice feels consequential.
A first post on a new journey — discovering what it feels like when work stops being a transaction and starts being something you genuinely care about.
An overview of Fred’s most notable open-source GitHub projects — from REST utility libraries and deployment tooling to file organizers and auth helpers.
Links to fredlackey.com, restutils.com, cicd.sh, and a direct email address. The short version of where to find Fred online.
The uncomfortable truth that not all code deserves a test suite. A pragmatic framework for deciding when testing adds value and when it just adds overhead.
On the sudden reversal of remote-work culture and what it reveals about which companies actually trusted their people — and which ones never did.
A reflection on embracing change in a career and a craft that never stands still. Why stagnation is the real risk, and movement the only constant worth trusting.
A practical roadmap for breaking into software development — from support roles to network administration to developer career tracks, with honest notes on detours and wrong turns.
The new bike arrived. After a GSXR-1000 and a Fat Boy 114, the Scout Bobber is something different — lighter, cleaner, and exactly right.
Answers to the questions Fred gets asked most — about hiring, learning to code, working remote, career advice, and what actually matters when building software.
The people who shaped your career deserve to hear it from you. On the underrated professional habit of expressing genuine gratitude before it’s too late.
A straightforward walkthrough for containerizing Node.js applications with Docker — from Dockerfile setup to multi-stage builds to running in compose.
Clearing up the confusion between HTTP status codes, application errors, and thrown exceptions — and why treating them as interchangeable is a design mistake.
Two small open-source tools for taming file chaos — one for normalizing date formats buried in filenames, one for reorganizing files by actual date metadata.