For years, I thought I was building apps. That's what I called them anyway.
A scheduler.
A job bot.
A healthcare platform.
An AI project.
A content tool.
A browser automation system.
Looking at my GitHub, they seem completely unrelated.
Honestly, that's something I've worried about before.
I have over a hundred repositories.
If someone spends thirty seconds scrolling through them, I can imagine them thinking: "Wow. This person is all over the place."
The funny thing is that I eventually realized the opposite was true.
My GitHub is here: https://github.com/ashb4 One of my projects started life as a simple scheduler.
That was the goal.
I hated posting content manually.
Open platform.
Paste content.
Upload image.
Repeat.
Again.
And again.
And again.
It felt repetitive.
It felt annoying.
Most of all, it felt like something a computer should be doing instead of me.
So I built a scheduler.
At least, that's what I thought I was building.
The scheduler worked.
But now I needed content.
Then I needed analytics.
Then I needed to know what content was working.
Then I needed a way to track winners.
Then I needed a way to reuse content.
Then I needed platform-specific strategies.
At some point I looked up and realized I wasn't building a scheduler anymore.
I was building a system.
A system for discovering, creating, publishing, measuring, and improving content.
The scheduler was just one piece.
That's when I noticed the same thing happening in almost every project I'd ever built.
My job application tools weren't really job application tools.
They were systems designed to reduce repetitive effort.
My automation projects weren't really automation projects.
They were systems designed to reduce repetitive effort.
Even my AI projects weren't really about AI.
They were systems designed to reduce repetitive effort.
Different technologies.
Different domains.
Same obsession.
For a long time I thought I had a focus problem. Too many ideas.
Too many projects.
Too many directions.
Then I started looking at the actual problems I was solving.
Almost all of them started with the same thought:
"This is stupid. There has to be a better way."
Job applications.
Content posting.
Data entry.
Decision making.
Workflow management.
The technology changed.
The frustration stayed the same.
This realization changed how I think about my work.
When people ask what I build, I still usually undersell it.
I'll say:
"It's a scheduler."
Or:
"It's a content tool."
Or:
"It's an automation project."
Technically those answers are correct.
They're also incomplete.
Because what I'm usually building is a system.
A collection of tools, workflows, feedback loops, and automation working together to solve a problem.
The app is just the visible part.
For a long time I thought my projects looked random. Now I think they look consistent.
Not because they use the same technology.
Because they're all trying to solve the same problem.
Reducing repetitive human effort.
Helping people make decisions.
Creating systems that keep moving even when motivation disappears.
Once I saw that pattern, a lot of things suddenly made sense.
I still build apps.
At least that's what I tell people.
But somewhere along the way I realized the apps were never the interesting part.
The interesting part was always the system behind them.
And once I saw that, I started understanding my own projects a lot better.
Maybe even myself.