Peter Eysermans

I've previously discussed the consequences of technical debt. Let's explore an aspect that's often invisible to non-technical stakeholders: quality degradation. The 3 Steps of Quality Degradation 1. It starts small: adding a few lines to spaghetti code or postponing an update. 2. Non-technical stakeholders

“Our product should be perfect, with zero bugs! Also, our budget is limited.” The truth is that quality isn't an exact science. Perfection comes at a cost. What to consider when determining the level of quality: 1. Industry context: Highly regulated sectors demand rigorous QA. For non-critical products,

Mobile app development has unique challenges, particularly when publishing on the Google Play and Apple App stores. Recently, I encountered a situation highlighting the importance of foresight when creating a new app. The Challenge A client reached out because their Android app had been removed from the Google Play Store

As tech leaders, we often hear (or say), "We'll do it next quarter" regarding framework upgrades. But is this approach truly serving our teams and products? 🪄 The Illusion of the "Magical Next Quarter" Technical leaders recognize it all too well. Stakeholders push back on

You don't need to set up your development environment. We have dedicated machines running Visual Studio. Just remote desktop in. It was the first day of my new job as an engineer. All excited, I wanted to set up my development environment. My excitement dropped immediately. It highlights

Why invest in technical debt? The app works fine, doesn't it? One of the stakeholders of a scale-up is in front of me. This question is one many tech leaders face. With no major technical improvements in over two years, metaphorical duct tape held one of their applications

An often-forgotten trait for engineers is perseverance. While technical skills are crucial, the determination to solve problems truly sets exceptional engineers apart. Throughout my career, the most talented engineers I collaborated with share a common trait: they never give up on finding solutions. This persistence has evolved with technology: * A

As technical leaders, we often shy away from support tasks. But what if I told you that participating in support rotation could be a game-changer for technical leaders? Here's why: 1. Gain first-hand product knowledge 2. Build goodwill with your dev team 3. Identify technical debt hotspots 4.

Microenterprises, typically defined as businesses with fewer than 10 employees, face unique challenges in the digital space. The decision to adopt custom software is pivotal. Business owners should consider the following choices. 🤔 Buy vs. Build Dilemma * 𝗢𝗽𝘁 𝗳𝗼𝗿 𝗢𝗳𝗳-𝘁𝗵𝗲-𝗦𝗵𝗲𝗹𝗳 𝗪𝗵𝗲𝗻 𝗣𝗼𝘀𝘀𝗶𝗯𝗹𝗲: If existing software meets about 70% of your needs, adapting it is

Previously, I talked about shifting from builder to technical leader. How can you scratch your maker's itch while empowering your team? 🫂 Embracing Your New Role: Beyond Building Your team is growing, and people management tasks are piling up. You're no longer concerned with how to build