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.
Feedback
29 posts
Communicate or be micromanaged - the engineering edition
Micromanagement rarely starts with bad intent. It usually starts with silence. When nobody knows what you are working on, meetings multiply, trust erodes, and focus disappears. This piece shows how clear, boring communication is your best defence.
Making progress without a technical leader
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.
So you messed up
Everyone breaks production eventually. This guide walks through how to take responsibility, communicate with your team, and make real improvements after something goes wrong. A must-watch for engineering managers and developers.
Why engineers need a voice in the roadmap
A great product roadmap balances business goals with technical sustainability. Ignoring engineering input leads to technical debt and bottlenecks that slow growth. In this video, we discuss how SaaS teams can integrate engineering priorities into the roadmap for long-term success.
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.
Social cohesion in remote companies: how to build solid connections and a collaborative culture from afar?
Today's digital age may seem hyper-connected, but remote work often lacks genuine human connection. We’ve created a culture of cohesion using dedicated bonding, safe spaces, and custom tools to ensure no one feels isolated.
Then it clicked: 3 things that helped me manage stress and anxiety when becoming a squad lead
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.
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.