Best Practices

  • What’s the best way to manage Helm charts (Project A)

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies

    Open

  • AWS Elastic Beanstalk when NOT to use it (Project A)

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies

    Open

  • A painless way to manage secrets in Google Kubernetes Engine

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies

    Open

  • Are you a data exhibitionist why you should protect your sensitive ports (Project A)

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies

    Open

  • Don’t treat developers like mindless pawns — share your business strategy! (Project A)

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies.

    Open

  • How to name your next open source project (Project A)

    A partially toungue in cheek look at the perils of naming an open source project and the art of naming in general. Based on the experiences of the Project A tech team.

    Open

  • How we set up a production CI workflow with GitHub actions (Project A)

    A case study based on the experiences of the Project A tech team. Intended to share knowledge with developers at the Project A portfolio companies.

    Open

  • Why developer documentation needs to be part of your growth strategy (Project A)

    An opinion piece written for Project A based on my own experiences as a technical writer. Designed to help developer-focused startups avoid certain pitfalls.

    Open

  • How we used an NGINX traffic split to run a stress-free website migration (Project A)

    A case study that focused on a specific consulting project run by the Project A tech team. Intended as a means to share knowledge with other Project A portfolio companies.

    Open

  • What frontend engineers should know about user tracking (Project A)

    Transcript and summary of an interview I did with Michael Lande Blau, Head of Front End Engineer at Project A. The interview was an attempt to get new insights from other members of the tech team. It was aimed at developers at the Project A portfolio companies.

    Open

  • How to market to developers —  according to a CTO (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • Do you need to go to CTO School? (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • To roll back or not to roll back How to handle critical incidents in production (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • What should startups consider when outsourcing engineering work (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • What startups should know about observability (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • Post-mortems don’t have to be painful (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • Should you try to measure developer productivity – Project A Insights (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • When hiring a CTO, what qualities should you look for (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • What’s the next career step for a senior developer (Project A)

    Transcript and summary of an interview I did with Stephan Schulze, Project A CTO. The interview was part of a series that I did with him on various aspects of the software engineering process. It was aimed at tech leaders at the Project A portfolio companies.

    Open

  • Do you monitor how third-party apps use your SaaS accounts—You should (Project A)

    Educational piece written for the Project A Ventures’ tech team as a means to share knowledge with the Project A portfolio companies

    Open