Most companies with a software development staff have legacy code that they need to maintain because it runs their business. Even companies that don’t do software as their main business may have internal tools and such that they need to maintain. Many software developers and even product and management would prefer to have new, shiny… Read More »
I have heard this comment in almost every company where I have worked. Without fail, this response occurs when someone on the technical staff suggests adding a practice accepted in other parts of the industry. Some variations are Early in my career, it was used to justify not using version control (yeah, I’ve been at… Read More »
Several years ago I gave a talk at work with the same title as this post. For a while, recordings of these lunch talks were available internally in the company. Over several years, I’ve had people either thank me for the original talk or reference things I said in the talk. Despite the fact that… Read More »
People often claim that with Rust code “when it compiles, it works”. Like most programming aphorisms, it is a slight exaggeration. This is not actually a claim that it is impossible to write bugs in Rust. It is not a claim that any program written in Rust is bug free. It is meant as a… Read More »
I see a lot of development advice that assumes the developer is working on a green field application. Many of the tools that “make a developer’s life easier” are also designed mostly for use in creating new applications. Most of my experience as a professional developer (or whichever title you prefer) has been improving and… Read More »
If you work as a developer, you probably spend a large amount of time in your editor. You are adding features, improving tests, looking for bugs, reviewing changes, and otherwise looking at the code. When I started programming, screens were a lot smaller and almost no one had space on their desk for more than… Read More »
Long ago when I began programming, most programs were standalone executables. Back in those days, almost all programs were run from a command line or executed by clicking on an icon on a GUI. This was before the web existed and most people didn’t even have dial-up access. Things are very different today, with many… Read More »
In a previous post, I spoke a bit about why to you might want to learn vim. Despite the fact that I prefer vim as my programming editor, I would never argue that everyone should use it. For some of people, vim meshes with the way they think. In my case, it wasn’t an immediate… Read More »
The writing of standalone tools is an underappreciated part of software development.
I recently ran across the article Why use Vim: Forget easy-to-use design. Choose something hard instead — Quartz. This article suggests that you should learn to use the vim editor because it’s hard. Although I do think most developers would benefit from using an editor like vim, I feel like the because it’s hard advice… Read More »