Sometimes I think a good day is actually made up of very small things.
Good music playing.
The weather behaving itself.
Eating something I actually wanted.
Getting one annoying thing off my to-do list.
Having somewhere nice to go later.
A random message that makes me laugh.
Nothing dramatic.
Just enough little things going right that you catch yourself thinking,
“Okay. I like today.”
I’m starting to think I don’t actually want to be known for one technology.
I want to be the person you give a messy problem to and I can figure out what needs to happen.
Maybe that’s backend.
Maybe that’s automation.
Maybe there’s an AI workflow somewhere in the middle.
Maybe the problem is actually the database.
Maybe the whole process needs to be redesigned.
I like having a toolbox more than having one favourite hammer.
Sometimes I think the hardest part of a technical interview isn’t the technical question.
It’s trying to figure out what the interviewer actually wants from your answer.
You answer the question.
They stare.
You start wondering if they wanted a different answer.
You explain further.
Now you’re talking too much.
You stop.
They say:
“Okay.”
And you’re sitting there thinking:
Okay WHAT? 😭
There are few things that annoy me more than asking someone a question and getting:
“That’s just how it works.”
😭
No.
That is not an answer.
Now I have two problems.
The original problem…
and the fact that you have refused to explain why it exists.
Please continue.
I write code and I write fiction, and I’ve noticed something slightly annoying.
Both activities make me incapable of leaving things alone.
In a codebase:
“Why is this behaving like that?”
In a story:
“Why would this person say that?”
Same problem.
Different victims. 😂
My browser tabs are currently giving:
PostgreSQL
Docker
Deployment
AI
Documentation
One completely unrelated thing I opened three hours ago
Another thing I swear I’m going back to
And approximately 14 tabs that I am emotionally attached to.
At this point, closing my browser feels like deleting part of my personality. 😂
I’ve been seeing Lagos Life everywhere and I have to admit, it gave me a very specific feeling.
First: “This is so cool.”
Then: “Wait… a Nigerian person actually thought of this and built it?”
Then, unfortunately:
“Why didn’t I think of something like this?” 😭
And that last one stayed with me longer than I expected.
Because I have ideas too.
WellReport AI started because I saw a problem and thought, “surely this process can be better.”
I’ve had other little ideas sitting in my head too.
But there’s a huge difference between having an idea and watching thousands of people actually use something that started as somebody else’s idea.
It made me feel inspired.
And a little overwhelmed.
Like maybe I should be thinking bigger.
Maybe I don’t need a perfect million-dollar idea.
Maybe I just need to stop waiting for the idea that feels big enough to deserve being built.
There are some evenings where I don’t want to be productive.
I don’t want a new skill.
I don’t want a five year plan.
I don’t want to optimise anything.
I want good music, something nice to watch, food I actually enjoy, and to be left alone for a little while.
And honestly?
Those evenings are underrated.
I love spontaneous plans.
But please don’t tell me at 4:30pm that we’re going somewhere at 6.
I need time.
To mentally prepare.
To decide what I’m wearing.
To imagine where we’re going.
To imagine what could possibly happen.
To be ready to be spontaneous.
Yes, I know how ridiculous that sounds. 😅
The older I get, the less impressed I am by “cool business ideas.”
I want to know:
Who is currently paying for this problem to disappear?
Because if the answer is “nobody yet, but imagine if…”
I have already lost interest. 😂
The expensive part of a business problem is not always the software.
Sometimes it’s the 17 tiny things people have been doing manually for years because nobody stopped long enough to ask:
“Why are we doing this this way?” 🤔
The weird part about learning software is that sometimes you spend three hours trying to fix something…
and then the problem turns out to be one tiny thing.
A missing environment variable.
A connection string.
A port.
One stupid little typo.
And suddenly everything works.
I don’t know why, but the relief after finding it is always disproportionate.
I’ve started noticing how often businesses use humans as middleware.
Someone receives the information.
Someone copies it somewhere else.
Someone checks it.
Someone calculates something.
Someone sends it to another person.
Someone turns it into a report.
Then everyone wonders why the process is slow.
Sometimes the biggest automation opportunity isn’t a complicated AI system.
It’s the person who has quietly become the API between five different systems.
A lot of software problems don’t start with software.
They start with:
“We’ve always done it this way.”
Then someone spends three hours copying information from one place to another.
Someone else checks it.
Someone sends it to another person.
Someone turns it into a report.
Someone asks why the numbers don’t match.
And eventually somebody says:
“Can we automate this?”
That question is usually where I become interested.
Not because automation is cool.
Because by that point, there is usually a real problem hiding underneath all that repetition.
There is a special kind of workplace conversation that goes:
“Send the report before 8.”
Okay.
Except the data sheet is not with me.
And I am not physically where the data is.
And the report requires the data.
So now we’re having a meeting with reality.
😂
I think this is one of the reasons I like automation.
Sometimes the biggest problem isn’t that people are slow.
Sometimes the process itself makes speed impossible.