Why I keep a logbook

I solve a problem, and three weeks later I no longer know how.

That is the main reason I keep a logbook. Preparing an exam alone is easy to drop. Writing leaves a trace and forces me to finish. I write it first for myself. If someone else reads it, welcome.

Who I am

I have been a digital project manager for more than ten years. I plan, I follow up, I ask engineers when something will be done. I learned most of it on the job, and I now want written proof of what I know. That is why I am going for certifications.

I am aiming for three of them:

Why the technical side

For ten years I talked about other people’s work. I wanted to do part of it myself.

I also wanted to judge a number or an architecture instead of accepting it as it was given. Starting with the cloud, I can finally do that.

Where I start

I am not an expert and I will not write like one. After ten years on IT projects, I understand how applications fit together and what a change does to the rest of the system. I can read SQL, write a test plan and follow bugs through to production. What I have not done is build and run things myself: I have never set up a server, a network or a database on a cloud provider. That is what this logbook is for. Mistakes will be in the entries too.

What an entry looks like

Each entry follows the same format:

If you are a project manager who wants to get closer to the technical side, this may be useful to you.

Next entry

How I built this blog, with Astro and GitHub Pages. I may move it to AWS later, as a project of its own.

--
By jlnrcs