The quirks and quacks of software development.
They’re passing up the thrill of a lifetime. At least they have experienced the joys of actually writing code.
Neither an art nor a science, writing software is more akin to carpentry or watchmaking. We’re going to miss it.
What Claude does is eye-opening. One thing he has taught me is that the future belongs to the APIs and CLIs.
Something big is happening, all right. But there is reason for optimism in the AI turmoil.
We are fast approaching the day when anyone with an idea will be able to create an application or a website in hours.
Coding agents make software developers more productive today, and will change their jobs dramatically tomorrow.
There is probably a more direct route from AI models to the software we want than having agents work with code.
If AI continues to trample the creators of new code and frameworks, then where will our new code and frameworks come from?
What if writing code becomes something that happens over days and weeks, rather than weeks, months, or even years?
Like the loom, AI may turn the job market upside down. And enable new technologies and jobs that we simply can’t predict.
Are you a programmer, coder, developer, or engineer? The names for software makers tell us what it means to be in the software business.
Soon LLMs will write better code than any human, for several simple reasons. Developers should rejoice.
Maybe you do truly understand one or two of these areas of coding mystery. Most of your fellow programmers are faking it.
Soon AI agents will be writing better, cleaner code than any mere human can, just like compilers can write better assembly.
Seven opinionated tips for navigating the treacherous trail of coding an application with a minimum of snags, missteps, and misadventures.
Decade after decade, software and software business models keep changing. But the economics never really do.
Large language models are astonishingly good at coding and getting better. What will this mean for software and software developers?
Before REST/JSON made exchanging data and code between networked computers routine, we had arcane standards, brittle integrations, and lots of miserable developers.
Working in a flow state is precious and meetings are a dime a dozen. Software developers and their managers need to set boundaries.
Collaborating on code used to be hard. Then Git made branching and merging easy, and GitHub took care of the rest.