Lately, my work has felt quieter but more intentional.
I’ve been spending a lot of time tightening things behind the scenes:
- Cleaning up my portfolio
- Getting more comfortable with backend work
- Documenting decisions instead of rushing past them
One thing that’s become really clear is that it’s about building something that actually holds up over time.
One thing that’s become really clear is how much better the process is when it’s shared, not polished highlights, but the real work. The parts where you’re unsure, adjusting, learning, and figuring things out as you go.
That’s where the best conversations seem to happen.
Because of that, I decided to create a Patreon not as a support page, but as a space for the deeper layer of the work. A place for dev logs, breakdowns, experiments, and honest updates about what I’m building and why. Less finished product, more thinking in progress.
This isn’t a pivot away from what I’ve been doing. It’s more like giving the process a proper home.
If you’re building something right now, whether it’s code, a portfolio, a business, or just a clearer direction, I’d genuinely love to hear what you’re working through.
🔗 [ <a href="https://patreon.com/SorenTech" target="_blank" rel="noopener nofollow">https://patreon.com/SorenTech</a> ]

Developer's Journey is a place where we share our stories, career growth, technical adventures, and personal milestones, no matter where we are in our journey.

Developer's Journey

A developer shares their shift toward documenting their development process and decisions rather than rushing through projects. They emphasize the value of sharing real work-in-progress, including uncertainties and learning moments, over polished highlights. The post announces a Patreon for dev logs, breakdowns, and honest project updates.

Why I Started Documenting My Dev Process Instead of Rushing Projects

Nice idea! I think keeping a diary of your work is a fabulous practice, whether it is your personal work or your hired work. Documenting what you learned helps to reinforce it, and more than once I have searched my own diary when I knew I solved a problem before (such as a Node versioning issue) but could not recall what I did as it was months ago. And if you publish it, it might help others and is also a statement of your ethic! Well done!

This is an habit I’m starting to cultivate but ironically, I tend to pick up my pen and note more often than the keyboard when it comes to documenting anything.

This is cool, I feel like there is somehow a layer of external accountability that helps with momentum and motivation. Does anyone have any advice for documenting private codebases or projects from work that you want to talk about in depth but also not reveal any sensitive or confidential details?

Yeah solid planning, documentation and execution is like a guaranteed luck

To be honest, As a newbie in this tech world I was finding people where they genuinely check my work and give me honest review and support my work. If it is what you are doing I love to join.