The hidden cost of multiple repositories
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
Professor Quacks is back with five more principles for better engineering: build tools that help, move with healthy urgency, plan wisely, work well with others, and lead by example. These aren’t just coding tips, they’re culture-shaping lessons.
Startups without a technical co-founder can still build great products, but only if they avoid the usual traps of overengineering, needless infrastructure, and late developer involvement.
Madewithlove combines interim CTOs and staff engineers to help SaaS scale-ups align strategy with execution and build resilient tech teams.
Selling bespoke features to customers might seem profitable, but it changes your SaaS business model. Instead of a scalable product, you become a service provider, stuck maintaining one-off features. Learn why this approach is risky and how to build for long-term success.
In small teams, front-end engineers can bridge gaps in product clarity by refining goals, collaborating effectively, and using flexible tools to deliver features efficiently.
Learn how to navigate the challenges of becoming a squad leader as an introverted senior engineer. Discover strategies for effective 1-1s. Overcome the anxiety of leadership by focusing on clarity, communication and creating an inclusive atmosphere where your team can thrive.
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.
In SaaS, shifting priorities and changing teams cause stress. Stable teams focus priorities but may lack roles, leaving floating members to juggle demands. A one-person service team can offer clarity, but careful prioritization and team restructuring are vital.