On this episode of madewithlove’s Pulse podcast, Vinch Battaglia, CTO in residence, welcomes Wouter Sioen, software engineer, and Jonas Drieghe, software engineer, all members of the madewithlove team. We use PHP in-house and on our client projects so we decided to discuss why that is. Listen to this Pulse...
The madewithlove team dives into their first Between Us session where they discuss problems that they encounter through their daily work. Today’s topic is refactoring. Vinch Battaglia, CTO in residence, is joined by Jonas Drieghe, software engineer, and Dimi Van Lunter, engineering manager, to gain their insights. Listen to...
As you (might) know, our current website is built on Gatsby. I love the fact we’re generating a super cacheable, fully static site with every build, but this adds a couple of limitations. One of the limitations of this setup is having no backend (I know that sounds funny)...
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...
While snapshot testing has been around for a while in the form of visual snapshots (used in visual regression testing), it’s clear that the introduction of textual snapshots in Jest a few years ago had a big impact on testing, not only in JavaScript but in other languages as...
As I was browsing through Twitter the other day, I saw someone complaining about abstractions among the lines of “we add abstraction layers on top of more abstraction layers and expect the system to be easy to maintain.” I understand this feeling because I’ve also felt that way before....
Creating branches in git is blazingly fast and having a bunch of them is pretty cheap. This means we get to merge them quite often. But how is a branch represented internally and what does it mean to merge them? Understanding how this works internally will help you understand why...