Problem and solution

27 posts
AI overdose: When developers stop thinking and start prompting

AI overdose: When developers stop thinking and start prompting

AI tools are reshaping how junior engineers approach problems, often replacing simple solutions with overly complex ones. Here’s why foundational thinking still matters. A real-life case of AI over-engineering gone wrong highlights why understanding problem domains still beats prompting.

The hidden cost of API migrations

The hidden cost of API migrations

Forced API migrations without a rollback plan? That’s how businesses lose trust—and money.

Death by a 1000 tweaks: the absurdity of maintaining your own UI library

Death by a 1000 tweaks: the absurdity of maintaining your own UI library

The best products aren’t built by obsessing over pixels but by delivering real value. Without a clear UI framework, teams drown in design tweaks instead of shipping features.

Making an existing Laravel application multi-tenant with Tenancy for Laravel

Making an existing Laravel application multi-tenant with Tenancy for Laravel

Transforming a legacy application into a multi-tenant powerhouse is no small feat. Learn how we tackled the challenges of adding multi-tenancy to a Laravel app, from infrastructure planning to custom bootstrappers, and discover practical tips to future-proof your applications.

Beyond junior and senior labels: Push and Pull developers

Beyond junior and senior labels: Push and Pull developers

Labels like "junior" and "senior" often fail to capture a developer's true value. True impact comes from initiative, ownership, and proactive contribution—not just years of experience. We value "pull developers" who actively seek improvement, ensuring the product's success beyond assigned tasks.

Do we even need a moat?

Do we even need a moat?

A technical moat is often seen as a product's defensive edge, but does every product really need one? For AI products, the choice between building proprietary tech or leveraging existing solutions like OpenAI is complex. True value lies in solving customer problems—not just in owning the technology.

What is a retrospective, and how to run one

What is a retrospective, and how to run one

Reflecting on work through retrospectives helps software teams improve by identifying what went well and what didn’t. This promotes continuous growth, stronger collaboration, and better performance. Creating action plans from these insights leads to higher-quality results and a more cohesive team.

Pragmatic ways of keeping documentation up to date

Pragmatic ways of keeping documentation up to date

While documentation is vital, too much can lead to outdated or duplicate content. To manage it, consolidate docs in one platform, separate live from historical content, archive outdated ones, move technical docs closer to code, and encourage sharing links to foster a documentation culture.

Core Protocols: improving communication within your team

Core Protocols: improving communication within your team

Efficient communication is important for SaaS teams. Core Protocols can unlock great potential in communication. Implementing these protocols can significantly improve a team's output and overall satisfaction by creating a shared vision and setting clear expectations.

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.