Part 1: Boring Maven
As I have laid out in Part 0: About ‘Boring Technology’, there are a few properties that make a technology a ‘Boring Technology’. A prime example of such a technology is - in my opinion - the build tool Maven. Explaining what it does is fairly easy. Explaining how to use it (mvn verify) is almost ridiculously simple (for ~90% of the use cases). Replacing it with another build tool is, depending on the plugins you’re using, not trivial, but in general feasible.
Part 0: About Boring Technology
When I started working at Sparkteams about two years ago, I was enthusiastic about programming. I thought, maybe Functional Programming, Haskell, Strong Type Systems (and many other things) would change how we write software as an industry. If there was only an opportunity to use these things! At a company dinner, I remember quite vividly, another junior developer and I, boasted how Rust and Haskell can rule out whole classes of bugs!