I saw an interesting heuristic regarding habits recently but I couldn’t find the source anymore. Bear with me while I paraphrase a bit. If you want to build a habit, never skip it twice. Skipping your workout once is okay, we’re all human, we all have changing priorities...
Episode description On this episode of madewithlove’s Pulse podcast, we’ve invited Mike Veerman (Software strategist) to discuss with our own Vinch Battaglia (CTO in residence), Jonas Drieghe (Software engineer), and Dimitri Van Lunter (Engineering manager) things like: * What does it mean to be a software strategist, and what...
I’m sure you’ve heard the statistic that 9 out of 10 startups fail. How can you win against such odds? Is there a secret startup handbook to read or an investment due diligence checklist to follow? Madewithlove has audited over 50 companies, usually as part of an investment...
I love DDD, not domain driven design but instead double diamond design. In fact, I even mentioned it in my colleague.readme. Double diamond design solves many of the problems that I see most startups deal with. Engineers try to write code immediately and end up solving problems that no...
I started a greenfield project this week. I knew it was coming after one of our product managers told me about it during lunch a couple of weeks ago. To be honest with you, I was terrified. I’ve been at madewithlove for a little over 4 years now, working...
ChangeHub has been part of our madewithlove family for a long time. The first-ever commit dates back to November 8, 2014, during our team retreat in Lisbon where it started out as a small proof of concept to make it easier for our product managers and clients to know what...
Building software isn’t easy. Add the opinions and needs of multiple people into the mix and it can feel almost impossible at times. Learning to collaborate with multiple people on the same software is an essential skill for every software engineer nowadays, as almost no software gets built and...
It has never been easier for engineering teams to build and release new features for your customers. This fits well with our philosophy of shipping value to customers on a regular basis but does your customer experience this in the same way? And who should be in charge of releasing...
Just like any other agile team, we meet each day to discuss blockers and what we planned to work on. The goal of the meeting is to get everyone on the same page and make it clear when there is friction. We even tried async written standups. Then we cancelled...