The quirks and quacks of software development.
The software industry has known for decades that rewriting a system from scratch is never the right solution. The bigger the system, the worse the mistake.
Vibe coding is a new way of coding with AI, where you guide the model only through natural language. It’s going to change everything.
Two years ago, I ditched my Windows laptop and started using a Chromebook for software development. I haven’t looked back.
Imagine a world where you can build web applications in any programming language you like. We’re close.
By coding against abstractions instead of hard-coding the implementation, you can create a flexible, testable, and extensible system that will be vastly easier to maintain.
Complexity makes misery. Folow these hard-earned and time-tested guidelines to keep your code simple, clear, and easy to maintain.
AI isn’t going to replace you. But a developer who knows how to leverage AI in the development process just might.
The best software is built by keeping as many doors open for as long as possible. Resist premature decisions and locking in implementations too soon.
Cloud-based development environments have so many advantages they’re pretty much a no-brainer. We’ve come a long way, developers.
The do’s and don’ts of implementing an authentication process that provides strong security without irritating your users.
A four-step program to swallowing your self-pity and making the most of the convoluted and incoherent code base you inherited.
Convoluted masses of incoherent code have many different origins and many different causes. Let’s explore.
You don’t need a computer science degree, a college education, a state license, or anyone’s permission to write code. Just do it.
It was bound to happen. There was just too much money involved.
JavaScript gives you too many ways to shoot yourself in the foot. Just what you’d expect from a programming language that was created in a week.
10 people and technologies software developers should celebrate this Thanksgiving, from Alan Turing, Anders Hejlsberg, and Tim Berners-Lee to OOP, REST, and GPS.
Back in the day, technology limitations forced software development teams to be disciplined, rigid, and inflexible. Thank goodness for SaaS and CI/CD.
I don’t like scrum, and you shouldn’t either.
Software is a product unlike any other. Forcing developers to track the time on tasks of indeterminate duration has many downsides — and no upsides.
Someone has to eat the turd sandwich, and it usually ends up being the software developers and the QA team.
The not-so-subtle superpower of a web page is that it can basically do whatever it wants when you request it. In other words, social media is irritating by design.
You may have heard it said that ‘All code is legacy code.’ It’s a useful guiding principle — and truer than we want to admit.
The early PC and Internet days were a glorious time for technology, when magical new developments in hardware and software were thrilling and life-changing. Kind of like today.
You probably get an endless barrage of news, information, social media, and who-knows-what-else through several automated feeds every day. How’s that working out?
Sure, Apple is a great company that makes great products. But many of its policies and practices rub me the wrong way.
Big question marks hang over the programming and software development website with all the answers.
Much of what a senior developer does boils down to writing good code. Here are seven tips that make that easier.
Imagine a social network where every post and comment were digitally signed, permanent, irreversible, and verifiable, and where participants who created value were rewarded.
Software has never looked cooler, but user interface design and user experience have taken a sharp turn for the worse.
We do all the work, and they make all the money. It doesn’t have to be that way, does it?
You can plan, strategize, chunk, fold, spindle, and mutilate a project for countless person-hours, and you still won’t know the difficulties that lay ahead in actually writing the code.
Every software developer wants to work on challenging projects that expand their horizons. But it’s better to buy a wheel than reinvent it.
Cubicle farms are breeding grounds for interruptions, and interruptions are the bane of developer productivity.
Why do we spend so much time on a process nobody wants? If you’re doing it right, the performance review process should be unnecessary.
Sponsored Links
