Documentation

Why founders need to care more about software licensing and SBOMs

Learn about the importance of SBOMs and software licensing for your SaaS startup.

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.

Mobile app security: A best practices checklist for startups and scale-ups

Startups and scale-ups are vulnerable to cyberattacks as mobile apps grow. Implementing encryption, multi-factor authentication, and secure communication is crucial. Leadership should integrate security into the product lifecycle to protect both data and reputation.

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

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.

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.

What to do when your team can't deploy continuously?

The software release journey is transformative. While CI/CD excels in fast-paced environments, it's not a universal fit. Discover alternatives to deploying continuously, balancing innovation with meticulous care.

5 things investors and VCs care about before investing

In the eyes of a VC, your startup is more than just lines of code; it's a potential hidden gem waiting to be polished. So, the next time you pitch, think less about impressing with tech and more about presenting a balanced, promising business.

A framework to deal with technical debt

Are there any specific product management framseworks to deal with technical debt?

Tech debt & refactoring an old front-end codebase: a field manual

Improve your front-end project's performance and maintainability with our guide to refactoring a codebase. Learn about tackling technical debt, assessing your code, planning a strategy, and exploring refactoring techniques.

A field guide to modernizing your PHP project — how to avoid a rewrite through incremental development

Sometimes the code really is unmaintainable and non-upgradeable. Other times, it might just be old and written in a technology that’s dated or deprecated. Learning how to work with legacy code is a skill in itself. Here’s our playbook for modernizing that old PHP project.

Why defining a product vision is crucial in ensuring you are building the right things.

A company should have a vision, but a product should also have one. A product vision may sound like something large corporates work on. It may sound like a waste of time. However, a good product vision helps your team make the right choices while building your product.

Subscribe