From DEV to Substack: Continuing the Writing Journey
I started writing technology articles in 2021.
My first blog was published on DEV on May 30, 2021. At the time, the intention was simple: document my research and findings in one place, and share what I was learning along the way.
I have always believed that technical knowledge should be free and accessible. That belief is one of the reasons I chose DEV instead of Medium. DEV felt open, community-driven, and aligned with the idea that engineering insights should not sit behind paywalls.
Over the years, writing has helped me in ways I didn’t initially expect.
✅ It forced me to structure my thinking more clearly.
✅ It made me revisit assumptions.
✅ It pushed me to explain production trade-offs more deliberately.
Many of my posts, on resilience patterns, distributed systems, Git workflows, and engineering discipline, started as personal notes or project reflections. Writing turned those notes into structured knowledge.
And for that, I’m grateful to the DEV community.
What I Started Missing
As I continued writing, I began to notice something🤔
While DEV provides visibility and discovery through its feed, I rarely receive direct or ongoing feedback from readers. Conversations are often limited to comments under a post. There isn’t a consistent way to stay connected with people who genuinely want to follow deeper discussions.
Publishing on DEV sometimes feels like releasing something into a stream; it flows through the feed, gets engagement for a while, and then moves on.
There’s nothing wrong with that model. It works well for discovery.
But for topics like:
- Production engineering decisions
- Resilience strategies
- Delivery discipline
- Architectural trade-offs
- The subtle choices that influence DORA metrics
I started feeling the need for a more direct and intentional channel.
Why I’m Expanding to Substack
Recently, I started a Substack publication. ⭐️Substack Publication⭐️
This is not a move away from DEV. I will continue writing here.
But Substack provides something different: direct communication.
When a new article is published, subscribers receive notifications or emails. That creates a consistent and intentional connection between writer and reader. Instead of depending entirely on feed algorithms or timing, there is a direct channel for ongoing dialogue.
For deeper engineering discussions, that matters.
I’m hoping it allows:
⭐️ More thoughtful feedback
⭐️ More structured conversations
⭐️ A recurring audience interested in production-grade engineering topics
It feels like the next natural step in this writing journey.
Still Believing in Free Knowledge
My core belief hasn’t changed.
Knowledge should be free.
Engineering insights should be accessible.
I will continue publishing openly. Expanding to Substack is about communication and continuity — not exclusivity.
DEV remains where this journey started. And it will continue to be part of it.
Looking Ahead
Over the past few years, my writing has increasingly focused on the invisible decisions that shape software quality:
⭐️ Branching strategies that quietly impact delivery velocity
⭐️ Default configurations that hurt production performance
⭐️ Resilience patterns that determine system stability
⭐️ Engineering discipline that influences long-term scalability
Substack gives me room to explore these themes more deeply while building a direct connection with readers who care about production-first engineering.
Starting in 2021 on DEV was the first step.
Expanding to Substack feels like the next one.
If you’ve been reading my posts over the years, thank you!
And if you’d like to continue the journey in a more direct format, you’re welcome to join me there. ⭐️Substack Publication⭐️
Top comments (0)