Websites

Why I built yet another website when the internet already has plenty

Why I want a place of my own for notes on the web, development and AI. What I'll share here, what I don't intend to publish, and how I want to keep opinion separate from fact.

Yet another website. I understand the question. There is no shortage of sites, blogs and profiles competing for our attention. I don't need a new place just to have somewhere to put my name and a photo either.

I built one anyway. Because I want a space where I can think about my work a little more broadly. Where not every topic has to be tied to a service, a product presentation or the question of what someone could order from me. Sometimes I just want to say why a certain solution seems good to me. Or why something everyone is talking about hasn't convinced me yet.

That is what this blog is for. I don't expect it to have an answer to every question. I would like it to be clear, with every post, why it was written in the first place.

I needed a place for my own view

At GE-KO, my web development and SEO business, I work on web solutions. I also build my own digital products, Bizko among them. These are different parts of my work, but the questions that interest me don't stay neatly in their own drawers.

A website quickly raises the question of content. Content raises the question of search. Search raises the question of artificial intelligence. And with an application you often find that the problem isn't the technology at all, but the way the process the application is supposed to support was designed.

On a company site it is right that a visitor understands the offer quickly. With a product, they want to know what they can do with it and whether it will be useful to them. My personal blog has a different job: it connects the thinking that comes out of these topics and leaves room for questions I don't have a final answer to yet.

So I don't want to repeat project presentations here. Those have their own place. I'm more interested in what sits behind the decisions we make in digital work.

I don't want to publish just because something is new

There are enough new tools and announcements to write a new post every day. But novelty by itself is not a good reason for an article, at least not for me.

I'm more interested in whether something makes the work easier. Whether a user understands faster what they need to do. Whether a solution still makes sense once the first excitement has passed. And whether I would still choose it if there weren't so much interest in it.

I'd like to write when I have something to say. That might be a finding after a test, a view on a change in search, or a thought about a perfectly ordinary problem on a website. The topic doesn't have to be big. Sometimes the most useful post is the one that clears up a single small decision.

I'm not going to promise myself a schedule that would then force me to fill empty slots. A reader gains nothing from an archive with more dates in it if there is nothing behind them worth stopping for.

I'm interested in things that can actually be used

I want to write about the web, development, applications and digital business. About SEO and AI search too, because they shape how people get to information at all. And about development tools that let us turn an idea into something tangible faster.

But I don't want this to be just a list of technologies. The questions behind them are more interesting to me. What does a website have to tell someone who doesn't know the company yet? When does a new feature improve an application and when does it only complicate it? What do we actually save with automation if we then spend a long time fixing the result?

Questions like these don't always have one right answer. A small business has different needs from a large system. One person needs a simple presentation, another needs a tool their daily work depends on. Advice that ignores this isn't particularly useful to me, even when it is technically correct.

So when I write about a specific solution, I also want to say what kind of problem I think it suits. And where I would choose something else myself.

I'll try to keep opinion separate from fact

This is a personal blog, so my opinion will be on it. But I don't want to present every hunch as a finding that applies to everyone.

If I describe my own test, I want to say what I actually checked. If I rely on documentation, I'll link to it. If I'm only thinking something through, it's fair to write it that way. The difference between these things matters more to me than a confident tone.

With AI this line blurs especially fast. A convincing answer can sound like a finished explanation even though it contains an assumption nobody has checked. I don't want to carry the same problem into my own writing. I would rather leave a question open than close it with a sentence I can't defend.

It also means I can change my mind. If it turns out I judged something too quickly, or the technology has moved on, a correction makes more sense than sticking with an old post just because my name is under it.

Even enthusiasm needs a little distance

New technology interests me. I use AI in my work and I can see how much tools like these can help. Pretending it's all unimportant, or that it will be gone tomorrow, doesn't seem sensible to me.

At the same time I'm interested in the other side: how much of what was promised actually remains when you try to build something concrete. A nice demo is not a finished product. A good first answer is not a verified solution. A tool that does something quickly is not necessarily a tool that will be simple to maintain.

I don't want to be automatically enthusiastic or automatically sceptical. I'd like to keep the option of trying something, working out what suits me, and writing a normal post about it. Without every experiment having to prove the future of an entire industry.

Who I'd like to be useful to

I picture a reader who has a website or a digital product and wants to understand their decisions better. Maybe they build things themselves. Maybe they work with a contractor. Maybe they are simply wondering whether something would be worth doing differently.

I'd like them to find it easier, after reading, to ask a question, judge a proposal or notice something they had overlooked. They don't have to agree with me. If a post helps someone think more concretely, it has already done enough.

So I'll try to explain technical details where they help you understand a decision. I don't want to hide them, but I don't want to use them as proof of expertise either. A good explanation should open something up for a person, not convince them that the whole thing is too complicated for them.

For a start, that is my reason for yet another website: a space of my own for considered notes on work that interests me. No promise of always being first. I'd rather write something I can still stand behind after I close the editor.

Photo of the author

I build web solutions and digital products. At GE-KO I work on web design, development and SEO; with Bizko I look for simpler ways through everyday business. I am interested in how technology saves people work, and in how AI is changing the web.

One step further.