Pulse madewithlove

Discover how modern workplaces are shifting from traditional command structures to trust-based, purpose-driven teams.

In this episode, Andreas talks with Clive Foley, the CTO in residence at madewithlove, about trust, autonomy, and high-performing teams.

Learn how empowering your team with autonomy and purpose can lead to higher performance and greater innovation, especially in remote settings.

Explore the role of leadership in nurturing an environment where every mistake is a stepping stone to success.



Join us as we delve into the keys to building resilient and successful teams in today's fast-paced business world.

In this episode of Pulse, Lotte Geldermans (Pitchdrive) and Andreas (madewithlove) share their invaluable insights into what early-stage startups should prioritize technically and how VCs and investors can help startups navigate the complex waters of growth and investment.

In today's episode, we have an extraordinary story to share with you. Joining us is Arnout van den Meulebroucke, the founder of Phished, a European market leader in cybersecurity and cyber awareness.

Arnout started Phished as a solo founder, juggling multiple roles, from CEO to CTO, and even sales. But the real twist in the tale came when their main vendor suddenly gave them a shocking 30-day notice to leave their premises. Arnout and his team faced a challenging transition, and we'll dive into how they navigated this unexpected turn of events.

So sit back, relax, and enjoy this conversation with Arnout from Aalst, Belgium, currently residing in my hometown, Leuven. Welcome to the podcast, Arnout.

In this episode, Jason Fried (Founder of 37signals, makers of Basecamp and HEY) discusses the concept of the "trust battery," a metaphor for the level of trust between individuals in a company.

Together with Andreas, they delve into the idea of "rehiring," where managers should ask themselves if they would hire a person again after a year or not. Jason also shares insights into Basecamp's hiring process, emphasizing the importance of enthusiasm and fit rather than just skills.

They also talk about the company's history, products, the rare instances of rehiring former employees, the importance of mentoring, and the philosophy of "hiring slow, firing fast."

This episode of Pulse is all about the relationship between employees and the company, aiming for a sense of enthusiasm and growth potential.

Hope you'll enjoy it!

Today, Andreas and Steve talk about the Evolution of Technical roles in software teams. What does the ideal team look like? What is the role of the CTO, CEO, and VPoE? What is the role of the Engineering Manager? Do you need pods? What about shipping vertically? What happens with the CTO when the product or the team grows? Find out right away!

In this new Pulse podcast, Andreas Creten talks to his colleague Jonas Drieghe of madewithlove, a senior developer that excels in working in legacy code. They discuss the topic of technical debt in this episode.



Technical debt refers to suboptimal decisions made under the pressure of time, lack of knowledge, or skills, resulting in the difference between what was created and what could have been created in ideal circumstances.



Technical debt is categorized as managed or unmanaged, with the former being covered by tests and allowing for controlled changes. The latter is often invisible and can be like a black hole.



Managing technical debt properly is crucial because it can lead to more significant problems, such as the team leaving, creating a cascading problem that becomes a nightmare for a company. While engineers are closest to the issue, everyone is responsible for solving it. However, management teams often prioritize new features over technical debt, so allocating a percentage of time for engineers to work on technical debt can prevent it from becoming a significant obstacle to product development. It's important to differentiate between legacy code and technical debt, as not all legacy code needs to be fixed, but technical debt can hold back progress. The key is to focus on cleaning up the areas blocking progress while introducing new features.



Check out our other podcast episodes.