Simple, correct, fast: in that order July 9, 2018 on Drew DeVault's blog

The single most important quality in a piece of software is simplicity. It’s more important than doing the task you set out to achieve. It’s more important than performance. The reason is straightforward: if your solution is not simple, it will not be correct or fast.

Given enough time, you’ll find that all software which solves sufficiently complex problems is going to (1) have bugs and (2) have performance problems. Software with bugs is incorrect. Software with performance problems is not fast. We will face this fact as surely as we will face death and taxes, and we should prepare ourselves accordingly. Let’s consider correctness first.

Complicated software breaks. Simple software is more easily understood and far less prone to breaking: there are less moving pieces, less lines of code to keep in your head, and fewer edge cases. Simple software is more easily tested as well - after all, fewer code paths to run through. Sure, simple software does break, and when it does the cause and appropriate solution are often apparent.

Now let’s consider performance. You may have some suspicions about your bottlenecks when you set out, and you should consider them in your approach. However, when the performance bill comes due, you’re more likely to have overlooked something than not. The only way to find out for sure what’s slow is to measure. Which is easier to profile: a complicated program, or a simple one? Anyone who’s looked at a big enough flame graph knows exactly what I’m talking about.

Perhaps complicated software once solved a problem. That software needs to be maintained - what is performant and correct today will not be tomorrow. The workload will increase, or the requirements will change. Software is a living thing! When you’re stressed out at 2 AM on Tuesday morning because the server shat itself because your 1,831st new customer pushed the billing system over the edge, do you think you’re well equipped to find the problem in a complex piece of code you last saw a year ago?

When you are faced with these problems, you must seek out the simplest way they can be solved. This may be difficult to do: perhaps the problem is too large, or perhaps you were actually considering the solution before considering the problem. Though difficult it may be, it is your most important job. You need to take problems apart, identify smaller problems within them and ruthlessly remove scope until you find the basic problem you can apply a basic solution to. The complex problem comes later, and it’ll be better served by the composition of simple solutions than with the application of a complex solution.

Have a comment on one of my posts? Start a discussion in my public inbox by sending an email to ~sircmpwn/public-inbox@lists.sr.ht [mailing list etiquette]

Articles from blogs I read Generated by openring

Status update, July 2021

Hi! This status update comes a bit late, because I was on leave, biking in the south of France for a few days. This month I’ve released mako 1.6, to try to make up for the long delay for the last release. mako 1.6 brings quality-of-life improvements: modes a…

via emersion July 21, 2021

The mythical 10× programmer is just a good leader

There is some truth to the idea that some programmers are more productive than others. In practice, this is mainly a function of the breadth and depth of their experience, rather than an expression of innate talent. Under the right circumstances, the differe…

via Blogs on Sourcehut July 17, 2021

Summary of changes for June

Hey everyone! This is the list of all the changes we've done to our projects and apps during the month of June. We'll also be reporting in our on position in the world, and on our future plans. Summary Of Changes Nasu, released a nasu guide, and…

via Hundred Rabbits July 1, 2021