Iain Cambridge

During my exploration of AI and code generation I created a series of guidelines for the AI agent to follow to allow me to automate as much of the process as possible.

Like any startup code there has to be decisions made about where you’re going to spend time working and what you’re going to leave for latter when you have the time and money to resolve the issues you choose to ignore.

I recently learnt about atomic commits after spotting an unusual note on a pull request someone asked me to review.

I just watched Pauline Vos’ “The Business of Bisecting” talk, and one of the questions from the audience really stuck with me.

Using AI to help with programming is becoming increasingly popular as time goes on, with developers across the industry embracing tools like Junie, GitHub Copilot, ChatGPT, and Claude to accelerate their workflow.

So you want job security in software development.

One of the core concepts within BillaBear is creating workflows for events such as creating or cancelling a subscription and receiving payments.

When I first heard of Not Invented Here (NIH) as a junior developer, I always thought it meant that the company wouldn’t use anything external.

One of the decisions that had to be made early on was how to handle the input and output for the API endpoints.

Decision A Parthenon method should not throw exceptions that don’t belong to Parthenon.