There has been a suspicious amount of silence from this account.
My last DEV.to post was in July 2026.
And then...
Nothing.
No Linux deep dives.
No project updates.
No technical write-ups.
No carefully constructed "10 Things I Learned From..." article.
The internet survived. Somehow.
But if you're wondering why I went quiet, the answer is much simpler than "I was secretly building the next revolutionary startup."
I was dealing with life.
I didn't stop being a developer
Not publishing doesn't mean I stopped learning.
I was still working with Linux. Still thinking about software. Still working on personal projects. Still experimenting, troubleshooting, breaking things and figuring out why they broke.
That last part remains a fairly reliable developer tradition.
But my priorities changed.
Career decisions, job hunting, personal responsibilities, uncertainty and everything else happening outside a terminal window started taking up most of my attention.
There are periods when you have plenty to write about.
Then there are periods when you're mostly trying to figure out what comes next.
I was in the second category.
July was the beginning of a different phase
After leaving my previous role, the focus shifted toward figuring out my next step.
The job hunt became a full-time activity of its own.
Applications.
Interviews.
Resume revisions.
Technical discussions.
Researching companies.
Thinking about salaries.
Applying again.
And occasionally staring at a job description wondering whether the recruiter actually wants a human being or three certifications, seven years of experience and the ability to function without sleep.
During that period, writing simply wasn't my priority.
And that's okay.
My projects didn't disappear
One thing this break reminded me of is that a project doesn't become meaningless just because you haven't pushed a commit recently.
I've continued thinking about my personal projects, including Archangel Security Suite.
Some things moved forward.
Some things moved slowly.
Some things are still sitting there waiting for me to return to them.
That's normal.
There is an interesting pressure in developer communities to constantly ship.
New project.
New release.
New framework.
New blog post.
New GitHub contribution.
Repeat.
But software development isn't always a straight line.
Sometimes you're building.
Sometimes you're researching.
Sometimes you're learning.
And sometimes you're simply trying to get your life back into a stable state.
I didn't want to post just for the sake of posting
This was probably the biggest reason for the silence.
I could have written another generic tutorial.
I could have made another listicle.
I could have written something purely because I hadn't published anything recently.
But I didn't want to.
If I'm going to write here, I'd rather have something meaningful to share.
Technology is a huge part of my life, but so is the journey around it.
The career changes.
The projects.
The experiments.
The failures.
The lessons.
The strange decisions that somehow make sense three months later.
Those stories are worth documenting too.
Sometimes you need to step away from the keyboard
There is a strange expectation in technology that we're supposed to constantly produce.
Code.
Articles.
Projects.
Certifications.
GitHub contributions.
Conference talks.
Posts.
At some point, it starts to feel like developers are expected to operate as content-generation systems with keyboards attached.
But life doesn't work that way.
Sometimes you need to step away from the keyboard.
Sometimes your attention needs to go somewhere else.
And taking a break doesn't mean you've stopped being a developer.
It means you're a person before you're a GitHub graph.
So, what's next?
I'm writing again.
Not because I suddenly have everything figured out.
I definitely don't.
I'm writing because I'm still curious.
Still learning.
Still building.
Still interested in Linux, security, software, infrastructure, open source and all the wonderfully strange corners of technology that keep pulling me back.
The next posts may be technical.
They may be about projects.
They may be about Linux.
They may be about lessons from my career transition.
And some may simply be about things I've learned along the way.
That's the kind of writing I want to do.
The silence wasn't the end
Looking back, the gap since July doesn't really feel empty.
A lot happened during it.
Some things were difficult.
Some were frustrating.
Some were exciting.
Some are still unresolved.
But the important part is this:
I never stopped moving.
The blog went quiet.
The learning didn't.
The projects didn't.
The curiosity didn't.
And now the writing is starting again.
So this isn't really a comeback.
It's simply resume.
The journey continued while the blog was quiet.
Now I'm documenting it again.
Back to writing. Back to building. Back to breaking things and figuring out why they broke.
See you in the next post. 🚀
