Seven lessons from my renovation that also apply to software development

I'm in the middle of a renovation. A new layout, flooring, installations, the whole house is being overhauled. And as I walked through our home again yesterday to admire the progress, something struck me: this renovation actually has a lot of parallels with software development. Because just like with a good construction project, software isn't just about what you build, but especially about how you collaborate.

1. A good design starts with the right questions.

In the preliminary phase of the renovation, we worked together with an architect (Haajee architectuur). He didn’t just think along with what we wanted, but also asked exactly the right questions: What’s important to you? What do you want to be able to do that you currently can’t? Through those conversations, we arrived at a design that’s not only beautiful but also makes sense in terms of functionality, light, space, and layout.

It’s no different in software. A good preliminary phase is more than just creating wireframes. It’s about jointly exploring what the core of the application should be, which processes matter, and what users really need.

At Leukeleu, we often start with a "sprint 0" or technical analysis. Not to cause delays, but to build faster and more purposefully on a solid foundation.

2. Good communication means better understanding

Our contractor (Bouwbedrijf de Graaff) explains what he’s doing, why something needs to be done a certain way, and what the impact is. As a result, we understand what’s going on, even if we’re not experts ourselves. The same applies to software. When developers communicate clearly about decisions, dependencies, and risks, the project not only improves, but trust also grows. Because only when everyone understands things together can the right choices be made.

3. The cheapest option is rarely the best choice

We didn’t go with the lowest quote, but with a contractor who is realistic about costs, timing, and risks. No surprises afterward, just clear agreements and openness when things turn out differently. The same goes for software development. Too often, projects are started on the cheap, only to later get stuck in technical debt, unforeseen extra costs, or poor maintainability. Transparency and realism are more valuable than a low entry price.

4. There are always surprises

You remove a wall and discover there’s no steel beam where the original blueprint said there would be. Not everything can be predicted in advance, and yes, that can be a bit stressful. But with a good contractor, you solve it together. In software development, you also always run into surprises. Unexpected dependencies, unclear business logic, bugs. The point isn’t whether it happens, but how you deal with it. An open, flexible attitude is worth its weight in gold.

5. You can recognize craftsmanship by the joy in the work

What stands out? Our contractor and his team enjoy what they do. You can tell by everything: how they communicate, how they finish things, how they handle setbacks. The same is true in software, you notice the difference when people are energized by their work. You don’t just get a minimum viable product, but something crafted with care, with that extra touch. Craftsmanship isn’t just about skill; it’s also about dedication.