Check the Logs
This website is a log – by design.
Case studies · Decisions · Proof of thinking
Welcome to my log. This is where I document how I work with technology: which decisions I make, which trade-offs come with them, and what turns productive in the end. Not explainer articles, but case studies – decisions, trade-offs and results from real work.
Discuss your technology project
I don't write about what technology can do in theory – I write about what happens once it is actually put to use.
Where this log comes from
A log or a logbook? Exactly – that was the original plan: a WordPress installation as a repository for my R&D work during my time as CTO & CDO. For a long time I lacked both the time and the occasion to prepare the content; the company website covered the online presence anyway. Over time, though, the log became increasingly important – as a place for transferring information, for references to current hard- and software developments, and for what I take away from projects.
One note upfront: here I'm publisher, editorial team and proofreader in a single person. The content is as good and as complete as time and perfectionism allow – no claim to completeness or scientific accuracy. Some pages deliberately remain in draft state until their turn comes.
How the log works
- Pages & posts — Pages carry the evergreen content (profile, references, this info page). Posts are log entries on specific topics: decisions, trade-offs and impact rather than how-to tutorials.
- Cases — my own projects in a consistent structure: problem → role → decision → implementation → result → learning.
- Categories & tags — clickable above the posts and the fastest way into a topic; each tag generates its own feed.
- Search — goes deeper than tags but isn't tracked: no marketing analytics, no personal search profiles.
Why Ghost – and no longer WordPress
Websites have been the most efficient interface for online communication since the start of my career – so the choice of stack is a deliberate one. The log ran on WordPress for years. A formative experience from that time: my startup's website being completely hacked. Mistakes like that cost energy, but they teach you frontend and backend structure from both perspectives. Two lessons stuck: never run WordPress without hardening – and a backup only saves you when files and database are both covered.
Today the log runs on Ghost: open source, reduced to publishing, no plugin ballast. And since I develop Ghost themes myself, the site doubles as my testbed. The same skepticism toward unhardened default stacks is behind the infrastructure work I do today – self-hosted services, documented hardening, controlled handovers.
This website also has a job
Full disclosure: this log is not just a working notebook, it's also my storefront. Reading is free – and anyone who wants to go deeper can gauge here how I think, decide and execute: the posts make decisions and trade-offs visible, the cases show results.
The concrete offer is on the profile page – from assessment and architecture through engineering, integrations and infrastructure to a controlled handover into operations. This page provides the context for it.
Visuals and licensing
Images and visuals created by me can be used on request and by arrangement under the CC BY 4.0 license. Some of the visuals are AI-assisted – the tools and insights behind them are covered in the post Add creative value to use AI effectively.
Why this log exists
The structure deliberately follows Simon Sinek's Why–How–What: this page explains the why and the frame, the posts and cases deliver the how and the what. And the why is simple: technological progress only unfolds when the conditions are right – which includes making new possibilities understandable and showing what they deliver in practice. Thanks for spending time in the log.
Let's talk about your project
A digital project on the table where strategy, product and technology need to come together? Then a conversation is worthwhile → ingmar@konnow.de · LinkedIn