Building software is difficult and it's easy to make mistakes. To help developers keep the quality of their code high, developers have created an array of tools to help. From testing tools to ensure the code works to code styling tools to ensure code is consistently readable to Linters.

So this has been a rather busy week. I took part in the half-day build and built a Micro-SaaS in 12-hours, wrote a solid blog post.

Marketing work:

• Wrote Deptrac blog post
• Wrote a blog post comparing Parthenon with SaaS Pegasus
• Pushed my eBook to get newsletter subscribers
• Sent an newsletter emails
• Tweaked the landing, adding CTAs and making things clear

Development Work:

• Released an updates of Parthenon
• Added a new landing page to the Parthenon Skeleton application
• Added PDF to the QA applications
• Change the checkout process so that it's clear what the options are

Other business:

I've found a new payment provider to add to Parthenon. I'll start development work on a PHP Sdk for Transaction.cloud the new payment provider. This will allow Parthenon users to use Transaction.cloud and let them deal with the nasty and scary VAT.

Today, I'll compare SaaS Pegasus with Parthenon. Nothing is perfect and there will always be something better at some things. This will help you be able to make the decision which system to build your future SaaS on.

Within the PHP ecosystem there are tons of super cool and super useful tools to help you to maintain a good level of code quality. And I use quite a few of them. Today I'm going to go over one of the first code quality tools I added to the Parthenon tech stack right at the start of development - Deptrac.

This is my second scheduled weekly blog post about building in public. While during the week, I felt like I wasn't getting much done by the time it came to this blog post, I think there is some solid achievements. Two significant developments code-wise, and some substantial traffic gained.