Re: On why good developers should use bad computers
Martín Morales caught my attention with his take on a video arguing that developers should use bad computers because their end users can’t always afford better ones. On the other hand, Martín disagrees and explains why — I highly recommend reading his post first.
It reminded me of a Reply All episode where they mentioned that at Spotify, they used to have a day where everyone had to use the product on the free plan. It’s a great topic, but one for another post.
This made me think about where web development stands today. Yes, the work of a web developer has become more complex, requiring more powerful tools. However, I still argue that no technology is more democratic than the web. All you need is a browser and a connection. Websites are supposed to be fast and shouldn’t require a high-end machine to load. Projects like Arc from the Browser Company of New York give hope that we can continue to improve the browser experience.
That said, here I am writing this post on my 16GB MacBook from 2019. Not the best machine in the world, but certainly not the cheapest. Should I, as a web developer, simply use the cheapest machine possible? After all, I create interactive content for a newspaper website, and I should definitely make sure it works on my readers' old computers.
I don’t have a definitive answer to this question. I’m a big believer in the "eating your own canned food" theory: media executives, for example, should browse their own sites without ad blockers, just to experience how frustrating it is to read news when 90% of the screen is filled with ads.
When I had to use a super old Android phone to test a news app I was working on, I noticed how much a fancy blur effect was slowing down the site. Since the project was about the inflation crisis, it felt a bit like I was the Marie Antoinette of web developers—so I removed the effect. It looked nice, but the performance improvement was worth it.
On the other hand, should a web developer take a franciscan vow of poverty just because our projects should be the fastest and most accessible in the world? I can’t imagine working in media as a journalist/developer on a slow machine, trying to meet a tight deadline while watching the infamous Mac color wheel spin endlessly.
I completely agree with Martín when he says:
"One reason I disagree is that when you hire a professional, like a construction worker, plumber, or electrician, you’ll notice they have specialized, often expensive tools. These tools reduce complexity and save time. The same applies to developers."
Let’s be honest—our jobs are hard enough already. A bug can keep you awake at night because it’s impossible to reproduce consistently, and we deal with impossible deadlines all the time. I don’t think it’s wise to make it harder by using a slow computer.
But maybe, just maybe, it’s a good idea not to sell your old phone or computer. Or, if possible, ask your company to keep one of those outdated computers lying around, waiting to be taken to the electronics graveyard. Turn it on every once in a while and test your product there. You might think twice before implementing that awesome WebGL effect you have in mind.