Building teams, crafting code,
making impact.

What’s new?
How to explain your tech debt to your investors

How to explain your tech debt to your investors

Learn how to explain technical debt to investors effectively. This guide simplifies its impact on growth and strategies to manage it, helping you enhance company value and align business goals.

Stop Coding, Start Leading: Shifting dynamics for startup CEOs

Stop Coding, Start Leading: Shifting dynamics for startup CEOs

Once their team starts to grow, technical founders must shift from coding to leading. They often wrongly believe they can build features more quickly independently rather than collaborating with the team.

Cookie-based authentication with Laravel Sanctum

Cookie-based authentication with Laravel Sanctum

This is a detailed step-by-step guide for setting up Laravel Sanctum with cookie-based authentication. It explains the logic behind each step and how to set up Postman. We also tackle the most common CORs issues.

Featured posts Previous posts
Mocking external systems in e2e tests

Mocking external systems in e2e tests

Struggling with a legacy codebase? We used Playwright to automate QA, reducing bugs. By mocking external APIs like Google Maps, we ensured seamless testing. Learn our implementation with Laravel and Playwright for reliable results.

Embracing brownfield projects & legacy code in SaaS

Embracing brownfield projects & legacy code in SaaS

Balancing innovation with stability is key in managing SaaS legacy code. You explore phased implementations, leveraging existing assets, and continuous learning to maximize legacy code potential. Ideal for tech leads and founders.

Understanding and managing technical debt and legacy code: a guide for founders

Understanding and managing technical debt and legacy code: a guide for founders

Discover effective strategies for managing technical debt and legacy code in software development. This comprehensive guide for founders explores the causes, impacts, and solutions to maintain sustainable growth and high-quality code.

Backups. How much is enough?

Backups. How much is enough?

Google Cloud's data loss incident highlights the need for robust backups. Regular backups and storing snapshots are crucial. Practicing data restoration every 6-12 months ensures readiness. Adapt strategies as systems evolve to manage data loss risks effectively.

Leading with fear: these leadership mistakes will break your startup

Leading with fear: these leadership mistakes will break your startup

We’ll discuss some critical, non-technical challenges in leadership, including the impacts of ego and lack of self-awareness, and learn strategies to create a positive and productive work environment. Fear-driven leadership will break most startups.

Why don't you look at the codebase?

Why don't you look at the codebase?

When auditing software companies, we don't only look at the codebase. The value of an audit lies in understanding the broader context of the company. By interviewing, we uncover the real issues.

You might also like
Cookie-based authentication with Laravel Sanctum

Cookie-based authentication with Laravel Sanctum

Mocking external systems in e2e tests

Mocking external systems in e2e tests

Embracing brownfield projects & legacy code in SaaS

Embracing brownfield projects & legacy code in SaaS

Understanding and managing technical debt and legacy code: a guide for founders

Understanding and managing technical debt and legacy code: a guide for founders

Backups. How much is enough?

Backups. How much is enough?

You’ve successfully subscribed to madewithlove
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.