First, for the project I’m doing the certification, I’m using a different laptop than I did for my previous assignment. Today was the first day with that other laptop at home. This laptop needs power, lots of powers. The combination of the USB-charger from the old laptop, and an USB-charger for my phone wasn’t enough to keep it running for long. It was however quite enough to charge it when turned off. Hence, I’ve been working with pen and paper today. Tomorrow I will bring the charger home from the office.

Also, where are my drawing-skills? Why do I all of a sudden find it so hard to draw the flow charts? It’s pretty clear in my head, and I know the first draft doesn’t need to be perfect (believe me, it will not be perfect), yet I’m having a hard time starting. Oh well, tomorrow I’ll do the basics.

Since almost everything about this project is unclear, I’ve asked the CEO for a meeting, to talk about the Business Model Canva. Sure I have ideas of my own but that’s definitely not enough.

What the hell have I gotten myself in to? Is this just imposter syndrome or do I actually suck? Why can’t I remember anything from the courses?

But also, it’s finally started, and I’m in. It’s all up to me now. I’ve attended the required courses, I have the slides, I have the motivation. Let’s do this!

Have I read the yearly report? Yes I have, but it’s really not relevant in this case, since the company is pivoting.

I’ve been reading up on BMC, FMEA and STRIDE, and I’m looking forward to start working on these.

The naive architecture has two major parts, the web application where users login and handle their assets (to not reveal too much). The other part is the actual work engine.

The work engine is developed by an external developer, and is pretty much a black box, that we need to scale without it being scalable. Kubernetes came to mind, but since we need one instance per execution, I’m thinking something like an Azure Container App.

The web application has a naive architecture with an Angular frontend and a C# backend. For the naive architecture everything is served by a SQL Server, but that is already questioned.

Also, I’ve missed blogging.

At first glance, the business problem seems obvious. The SEO-guru has actually specified what he looks at in a site, technically, when analyzing SEO performance, and ranked different details to make it “easy” (possible at least) to create a program that does the technical analysis of a site. This tool needs to be cloudified, and sold.

Customers are companies (mostly) that does SEO for clients. The business case is that the application will replace the advanced technical site analysis, and free time, potentially hours per execution, for the team.

Since this is a startup, time to market is key. Also, in the words of the founder, there is no other application like this today, but I’ll be surprised if nobody thought about it.

We need an architecture that will allow us to hit the market fast, but still allow us to scale.

The focus from the founder is, at least for now, to get clients first, and investors later.