Eliminating SPOFs: the importance of documentation
Single points of failure (SPOF) in startups lead to lost revenue, delays, and investor concerns. Building a documentation culture early reduces risk and ensures scalability.
Technical documentation
12 posts
The hidden cost of API migrations
Forced API migrations without a rollback plan? That’s how businesses lose trust—and money.
How to minimise the impact of developer onboarding
Discover strategies to optimise developer onboarding, minimise costs, and improve time-to-market. Learn how to tackle challenges like code complexity, technical stack adaptation, knowledge transfer, and team integration while fostering a supportive and productive environment for new hires.
Things we do in our first weeks as Fractional CTO
A fractional CTO can transform a company by addressing urgent technical issues while developing a long-term strategy. Beyond firefighting, a fractional CTO focuses on building a sustainable, self-sufficient team that can thrive independently after their involvement ends. This is how to get started.
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.
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.
Five documents every startup should have
Documentation is vital in remote organizations. Companies with little documentation often struggle to get started. With this pragmatic advice however you can get the ball rolling. These are five documents every startup should have, and you can get started with them today.
Be boring
In discussions with non-tech managers, buzzwords often mask understanding. My view: use tech pragmatically, focusing on proven tools. Innovation matters, but clarity and long-term stability are key. Managers should demystify tech jargon and ensure meaningful application.
A framework to deal with technical debt
Are there any specific product management framseworks to deal with technical debt?