I've been thinking about TechArticles, YouTube, the changing value of technical tutorials and why I still want to document what I'm doing, even if fewer people are reading or watching.
I've spent a fair bit of time over the last couple of days reflecting on what the future looks like for the content I produce.
Not necessarily because I want to change everything, but because it's becoming increasingly obvious that the market for technical content is changing, and changing quite dramatically.
We live in a world where AI can explain how to do something, generate the code to achieve it and, increasingly, actually carry out the task for you.
And that creates an interesting question for somebody who has spent years writing technical articles and producing tutorials.
What's the point of showing somebody how to do something when AI can increasingly do it for them?
It's something I'm struggling to find my position on.
I don't intend to stop publishing content on TechArticles, and I don't intend to abandon my YouTube channel.
But I am questioning what those channels look like in the future, what I should be publishing and, perhaps most importantly, what success actually means for them.
It Was Never Really About the Money
I'm quite fortunate in one respect.
Neither TechArticles nor my YouTube channel was ever intended to be a significant revenue generator.
There are affiliate opportunities on TechArticles, and there are ways I could monetise the content more aggressively if I wanted to.
But that was never the reason I started.
I've never particularly wanted to build a website around affiliate commissions, and I've never wanted to produce content simply because somebody was prepared to pay me to promote a plugin.
I write about things because I'm interested in them.
I share the things I'm building, the problems I'm working through, the solutions I've found and the ways I've managed to get different systems working together.
Sometimes that's a detailed technical tutorial. Sometimes it's an explanation of how I've approached a particular problem. Sometimes it's simply documenting something I know I'll forget in six months.
And quite frequently, I'm the person who ends up benefiting from it.
I'll go back to an article I wrote a year or two ago because I can't remember exactly why I configured something in a particular way.
That has always been part of the purpose.
I'm documenting what I know, what I've learned and why I've done things the way I have.
If somebody else finds it useful along the way, that's even better.
AI Is Changing How People Find Answers
There is no point pretending that AI hasn't fundamentally changed the market for technical tutorials.
It has.
Historically, if you wanted to connect two services, configure a plugin or build a particular automation, you'd search Google, find an article, follow the instructions and hopefully end up with something that worked.
If you were lucky, somebody had made a video walking you through the process.
That was the space TechArticles existed in.
But now?
You can often ask AI to explain the process, produce the code, identify the required settings and work through the errors with you.
And increasingly, you don't even need to understand how the individual pieces fit together.
Take automation as an example.
I'm still building and managing hundreds of processes and automations for people. That work hasn't disappeared.
But the way those automations are created is changing.
With tools such as FlowMattic developing AI-driven automation capabilities, the process of building a workflow is becoming less about manually connecting every component and more about describing what you want to happen.
MCPs are pushing that even further, allowing AI agents to interact with products and services through natural language.
Where I might previously have written a detailed tutorial explaining how to connect two systems, map the data and handle the responses, increasingly somebody can simply describe the outcome they want and let AI help build it.
And that's brilliant.
I genuinely think it's a fantastic development.
But it also means that the information I've traditionally documented isn't necessarily being consumed in the same way.
Fewer Readers, Fewer Views, But More AI?
I've noticed something interesting across both TechArticles and YouTube.
Traffic is down.
Article visits aren't what they were, and video views have also been declining.
I can't say that every part of that decline is because of AI, but it's difficult to ignore the wider change in how people are finding information.
What's particularly interesting is that, from the data I can see, AI-related access to the content appears to be increasing.
So perhaps people aren't reading the articles themselves as much.
Perhaps they're asking an AI a question, and that AI is using something I've written as part of the information it provides.
Or perhaps somebody is feeding one of my articles into an AI tool and asking it to help them implement the solution.
I don't know exactly how much of that is happening, and I certainly can't prove a direct relationship between the two trends.
But it does make me wonder whether the audience is changing rather than simply disappearing.
Maybe the value of a technical article is no longer measured entirely by how many people visit the page.
Maybe the information still has a purpose, even when the person benefiting from it never actually reads the original article.
It's a strange position to be in as somebody creating content.
You've produced something useful, but the traditional signals that tell you it's useful are becoming less reliable.
And I'm still trying to work out how I feel about that.
The Things AI Still Can't Do
One of the more interesting things I've noticed is which videos continue to perform well.
You might expect the complicated tutorials to be the ones people still need.
But actually, some of my best-performing content is relatively basic.
One example is my video about setting up wildcard SSL certificates with DirectAdmin.
It's been one of my strongest-performing videos for around the last three months.
I've even recently updated the accompanying written article with additional information.
And I think there's a fairly straightforward explanation for why people are still watching it.
It's a practical task that, in many environments, still needs somebody to go into an interface and configure things themselves.
AI can explain the process. It can tell you what settings to use. It can potentially help diagnose problems.
But it can't necessarily log in to your particular DirectAdmin installation and do everything for you.
You still need to know where to click and what to configure.
I've noticed something similar with videos covering email setup using tools such as Emailit and SureMail.
Again, these are relatively straightforward tasks, but they're tasks that aren't necessarily exposed through an MCP or another interface that allows an AI agent to complete the setup.
So people still need a visual explanation.
And perhaps that's where tutorials will retain some of their value.
Not necessarily in explaining every single step of a process that AI can now complete automatically, but in documenting the parts that still require human involvement.
The interfaces. The configuration choices. The awkward integrations. The things that don't work quite as expected.
Of course, that space will probably continue to shrink as AI becomes more capable.
But for now, it's still there.
Knowing What's Possible Still Matters
There's another part of this that I think is important.
AI is getting incredibly good at producing solutions.
But somebody still needs to understand what problem they're trying to solve.
And, in many cases, somebody needs to imagine that a particular combination of systems is even possible.
That's one area where I feel I still have something useful to offer.
I don't think I lack imagination when it comes to technology.
I can look at different platforms, understand broadly how they work, see how data could move between them and work out how they might fit together.
That's something I do almost every day.
I can see a workflow where somebody else might see three completely unrelated applications.
And while AI can increasingly build that workflow for you, it doesn't automatically mean people know what to ask it to build.
There's a difference between knowing how to do something and knowing that something can be done in the first place.
Perhaps that's where some of my content needs to move.
Less emphasis on explaining every individual setting and more emphasis on showing what's possible.
Here's a problem.
Here are the tools I used.
Here's how the data moves between them.
Here's why I approached it this way.
And here's what the result looks like.
If you want AI to help you recreate it, brilliant.
The important part might not be the exact sequence of clicks anymore.
It might be the idea itself.
But I Still Want to Document the Process
Having said all of that, I don't want to completely abandon traditional tutorials.
Partly because I still think they're useful, but also because they're useful to me.
I document things for future me as much as I document them for anybody else.
When I'm working through a complicated integration or trying to solve a strange issue with a plugin, I often end up discovering things that aren't immediately obvious.
Why a particular API behaves differently from the documentation.
Why one configuration works and another doesn't.
Why I've had to approach something in a way that initially seems unnecessarily complicated.
Those are the things I want to remember.
AI might be able to reproduce the solution, but that doesn't mean I want to lose the reasoning behind it.
And I don't necessarily want my understanding of systems to become entirely dependent on an AI agent remembering or rediscovering what I've already worked out.
That brings me back to my recent thoughts about WordPress.
I'm not ready to abandon years of knowledge and experience simply because a different approach might be quicker.
The same applies to the content I produce.
Just because AI changes the way people consume information doesn't automatically mean the process of documenting that information becomes worthless.
Maybe Notes From Today Is Part of the Answer
One of the reasons I've started putting more effort into Notes From Today is that I still enjoy writing.
But I don't always want to write a finished technical article.
Sometimes I just want to explore an idea.
Sometimes I want to question where the market is heading, reflect on something I've been working on or write about a technology without having to turn it into a structured tutorial.
TechArticles has always had a fairly clear purpose.
It's a place for technical information, explanations, tutorials and practical solutions.
And I want it to remain that way.
But not everything I want to write fits that format.
Sometimes I want something less polished. Less structured. More personal.
Something that doesn't necessarily have a conclusion or a series of steps for somebody to follow.
Essentially, an old-school blog.
And there's something quite appealing about that.
Are We Going Backwards to Move Forwards?
There's a certain irony in where the web seems to be heading.
We're watching the rise of static websites again.
Astro and other modern tools are making static-first development increasingly attractive, and AI makes producing those websites easier than ever.
But static websites aren't new.
I remember building them years ago.
I remember Dreamweaver and FrontPage. I remember working with HTML, CSS and a little JavaScript to build websites long before everything needed a content management system and a database.
And now, in some respects, we're returning to that approach.
The tooling is different. The capabilities are considerably better. But some of the underlying ideas are remarkably familiar.
I wonder whether content is going through a similar transition.
For years, we've moved towards increasingly structured, optimised and polished content.
Articles designed to answer search queries.
Tutorials built around keywords.
Videos designed around algorithms, watch time and engagement.
And now AI is beginning to absorb much of the informational value those formats were created to deliver.
Perhaps that creates an opportunity for something more personal again.
Not necessarily less useful, but less manufactured.
People writing because they have something to say.
Sharing experiences rather than producing another perfectly structured answer to a question an AI can already answer.
In some respects, that's taking us back to the early days of blogging.
And I rather like that idea.
I Don't Know What Success Looks Like Anymore
This is probably the part I'm struggling with most.
When you produce an article, you can look at the traffic.
When you publish a video, you can see the views.
Those numbers give you some indication of whether people are finding what you've created useful.
But what happens when the information is being consumed indirectly?
What happens when an AI reads your article, extracts something useful and gives somebody the answer without them ever visiting your website?
Was the article successful?
I think it probably was, at least in terms of sharing useful knowledge.
But it's much harder to measure.
And I'd be lying if I said declining traffic and views didn't affect my motivation to produce content.
They do.
Even when you're not doing something for money, it's nice to know that people are benefiting from the effort you put in.
Publishing a detailed tutorial takes time.
Recording a video, editing it, uploading it and producing the accompanying written material takes time.
When fewer people appear to be consuming that work, it's natural to question whether it's worth continuing in exactly the same way.
But then I remember why I started.
It wasn't for the views.
It wasn't for the affiliate commissions.
It was because I enjoyed sharing what I was doing.
And I still do.
So What Happens Next?
I don't have a grand strategy.
I'm not announcing that TechArticles is changing direction or that I'm abandoning YouTube.
I'm certainly not planning to stop documenting the things I'm working on.
But I suspect the balance of what I produce will change.
There will still be technical tutorials, particularly where practical demonstrations are useful or where the information is difficult to find.
There will still be videos showing how to configure things, connect services and solve problems.
But I think there may also be more emphasis on what can be achieved rather than simply how to click through the steps required to achieve it.
More examples of systems working together.
More of the reasoning behind my decisions.
More documentation of the interesting problems I'm solving rather than attempting to document every part of the solution.
And Notes From Today gives me somewhere to write about the broader ideas without needing to turn every thought into a polished technical resource.
Perhaps the three channels end up serving quite different purposes.
TechArticles for the technical knowledge and solutions.
YouTube for the practical demonstrations and things that benefit from being seen.
And Notes From Today for everything else: the thinking, the experiments, the opinions and the occasional rambling reflection on where technology is heading.
That feels like a reasonable place to start.
The Audience Might Change, but the Reason Doesn't Have To
I think we're entering a period where a lot of people who have spent years creating informational content are going to have to rethink what that content is worth.
For those who depend on advertising, affiliate commissions or search traffic for their income, that's potentially a very difficult position.
I'm fortunate that I don't.
I can continue producing content because I enjoy producing it.
I can write something even if only a handful of people read it.
I can publish a video even if it doesn't generate thousands of views.
And if the content ends up being used by an AI to help somebody solve a problem, I'm reasonably comfortable with that too.
What I'm less certain about is how that changes the motivation to create new material and what the right balance looks like.
I suppose I'll work that out as I go.
But the fundamental reason I started TechArticles hasn't really changed.
I enjoy technology.
I enjoy understanding how things work.
I enjoy connecting systems, solving problems and discovering things that I didn't know were possible.
And I enjoy sharing that knowledge.
AI might change how people find my work, how they use it and whether they ever visit the website at all. But it doesn't change why I wanted to share it in the first place.
So I'll keep writing.
I'll keep making videos.
I'll keep experimenting.
And I'll probably spend far too much time thinking about what all of this means.
Which, I suppose, is exactly why Notes From Today exists.