TL;DR
For a long time, I told myself I would start documenting my journey later. I thought I needed better projects, more knowledge, or more confidence before anything I did was worth sharing.
Looking back, I realize it was never really about documentation.
I was afraid of being judged, afraid of getting things wrong, and afraid of putting something imperfect out into the world.Because of that, I spent years waiting for the "right" time to start.
What I didn't realize was that while I was waiting, parts of my journey were quietly disappearing.
Today, there are projects, lessons, experiences, and versions of myself that I wish I could revisit but can't, simply because I never captured them when they happened.
If I could go back and give my younger self one piece of advice, it wouldn't be to learn a different technology or build a different project. It would be to document more, share more, and spend less time waiting to feel ready.
Table of Contents
- The Version of Me I Can No Longer Visit
- It Wasn't Just About Documentation
- The People Starting Today
- The Things That Never Made It Into a Resume
- More Than a Portfolio
- The Unexpected Part
- It's Never Too Late
- I'd Love to Hear Your Story
- 🤝 Let's Stay Connected
The Version of Me I Can No Longer Visit
Every now and then, I find myself wondering what my first thoughts about tech looked like.
Not the polished version I would write today, but the real version. The student who was excited after finishing a small project, the person who spent hours debugging something simple and felt incredibly proud when it finally worked, and the version of me who was trying things for the first time without any idea where the journey would eventually lead.
I wish I could go back and read what that person was thinking.
The problem is that I can't.
Like many people, I assumed I would remember those moments. I thought the lessons, the projects, the discoveries, and the experiences that felt important at the time would naturally stay with me. Over the years, I completed projects, joined communities, applied for opportunities, attended events, and learned countless new things. At the time, each experience felt significant enough that I couldn't imagine forgetting it.
But memory has a way of smoothing over the details.
What surprises me now is that I don't miss the projects themselves nearly as much as I miss the person I was while building them.
I miss the excitement of discovering something new for the first time, the curiosity that came with not knowing the answer, and the satisfaction of solving a problem that had felt impossible only a few hours earlier.
Those versions of ourselves don't stay forever. We grow, our priorities change, and the things that once felt monumental slowly become distant memories. That's why I've started thinking about documentation differently. It's not just a record of what we built or accomplished. Sometimes it's a way of preserving who we were while we were becoming who we are.
It Wasn't Just About Documentation
Looking back, I don't think the problem was that I forgot to document my journey.
The truth is that I was afraid to.
At the beginning of any journey, it's easy to feel like you have nothing worth sharing. When you're surrounded by people who seem more experienced, more accomplished, or more confident, it's hard not to compare yourself to them.
You look at impressive portfolios, polished projects, successful creators, and people who seem to know exactly what they're doing, and before long you start telling yourself a familiar story:
"Maybe I'll start when I'm better."
At the time, that thought feels reasonable. You convince yourself that you're waiting for the right moment, but what you're really waiting for is permission. Permission to be inexperienced. Permission to be imperfect. Permission to share something before it's polished.
The problem is that the feeling of being "ready" rarely arrives the way we expect it to.
There's always another skill to learn, another project to improve, another reason why now doesn't feel like the right time. As soon as you reach one milestone, a new one appears in front of you. The version of yourself you thought would finally feel confident enough to start keeps moving further away.
For a long time, I told myself that I would start documenting someday. I imagined a future version of myself who would have more experience, more knowledge, and more confidence than I did.
What I didn't realize was how quickly time passes while you're waiting.
Before I knew it, years had gone by, and many of the moments I wish I had documented were already behind me.
The People Starting Today
One thing I genuinely admire today is seeing people document their journeys from the very beginning.
Whenever I scroll through LinkedIn, X, GitHub, blogs, or developer communities, I come across students sharing what they're learning, what they're building, and what they're struggling with in real time. Sometimes it's a small project they finished over the weekend. Sometimes it's a lesson from class that finally clicked. Sometimes it's simply a reflection on something they learned that day.
What stands out to me isn't how impressive the work is. It's that they're willing to document the process before they have everything figured out.
They're not waiting until they become experts. They're not waiting until they land internships, build an impressive portfolio, or reach some milestone that suddenly makes their journey feel worth sharing. Instead, they're capturing the journey as it happens, with all of its uncertainty, mistakes, questions, and small victories.
And honestly, I wish I had done more of that.
Not because every post becomes popular or every project changes someone's life. What I admire is that years from now they'll have something I wish I had more of: a record of how they became who they are.
One day they'll be able to scroll back through old projects, applications, posts, and reflections and see the path they took to get where they are. Many of those moments probably feel ordinary today. Some of them might even feel insignificant.
But stories are rarely built from a single defining moment.
They're built from hundreds of small moments that only become meaningful when you look back and see how they connect.
That's what I think these people are preserving, often without even realizing it.
The Things That Never Made It Into a Resume
When I think about the parts of my journey I wish I had documented, it's rarely the big achievements that come to mind.
I don't find myself wishing I had written more about a particular line on my resume or a milestone that looks impressive in hindsight.
Instead, I think about the smaller moments that quietly shaped me along the way. The first time I solved a problem that felt impossible. The excitement of getting accepted into a program I wasn't sure I was qualified for. The project that taught me far more than it ever produced. The conversations that changed how I thought about myself, my career, or what I was capable of achieving.
I think about the moments when I doubted myself and kept going anyway.
Those experiences never became bullet points on a resume, and most of them would probably never stand out to anyone else. Yet they're some of the moments that shaped me the most.
They influenced how I think, how I approach challenges, and who I've become over time.
Looking back, those are the memories I wish I had captured while they were happening. Not because they were extraordinary, but because they were meaningful. They're the moments I find myself wanting to revisit, and the ones I wish I could see through the eyes of the person I was back then.
More Than a Portfolio
When people talk about documenting their work, the conversation usually revolves around visibility. We talk about building a portfolio, growing an audience, creating opportunities, attracting recruiters, or finding jobs. Those things absolutely matter, and for many people they become valuable outcomes of sharing their work.
But the older I get, the more I think there's another benefit that gets talked about far less.
Documentation preserves growth.
Looking back, I don't think the biggest value of documenting our work is that it helps other people see what we've done. I think it's that it allows us to see how far we've come. It captures versions of ourselves that would otherwise disappear and gives us a way to revisit old ideas, old challenges, old failures, and old wins.
When progress feels slow, documentation can become proof that progress is happening at all.
That's one of the reasons I view things like GitHub repositories, blog posts, notes, and LinkedIn posts differently now. They're not just artifacts of work. They're snapshots of a particular moment in time. They capture what we were learning, what we were struggling with, what excited us, and what we believed at that stage of our journey.
Years later, they become something much more valuable than a portfolio.
They become evidence that we were there.
Learning.
Building.
Struggling.
Growing.
And sometimes that's exactly what we need to be reminded of.
The Unexpected Part
The funny thing is that when you start sharing your journey, something else happens.
You find people.
That wasn't something I expected when I first started writing.
For a long time, I worried about whether my thoughts were worth sharing at all. I worried about being judged, saying the wrong thing, or simply putting something out there that nobody cared about. Looking back, that fear probably kept me quiet much longer than it should have.
I was a silent reader far longer than I was a writer. I spent years reading articles, learning from communities, and admiring people who seemed confident enough to share their experiences publicly. I benefited from what others were willing to contribute, but I rarely contributed anything myself.
I still remember publishing my first article on DEV. To be honest, I wasn't expecting much. I wasn't thinking about followers, engagement, or any of the things people usually associate with publishing online. I was mostly wondering whether anyone would read it at all.
When I finally hit publish, it felt uncomfortable. A thought that had existed only in my head was suddenly visible to everyone else.
The article didn't receive comments or reactions, but people did read it. I remember checking the views and realizing that actual people had spent time reading something I wrote. That small realization meant far more to me than I expected.
I published a few more articles after that and then eventually drifted away from writing for a while. When I returned this year and started publishing again, the experience felt completely different. People started commenting, sharing their own stories, offering encouragement, and giving thoughtful feedback.
Over time, some names became familiar. People who started as strangers gradually became a small but meaningful part of my journey, and I found myself looking forward to hearing from them whenever I published something new.
What's funny is that I've never met most of them in person.
Yet they continue to support me anyway.
When I first started sharing online, I worried about negativity. What I didn't expect was kindness.
I didn't expect strangers to celebrate my progress, encourage me to keep going, or take time out of their day to leave thoughtful comments. I certainly didn't expect to feel supported by people from different countries, backgrounds, and stages of their careers.
But that's exactly what happened.
And honestly, that support has changed me too. Every encouraging comment, every shared opportunity, and every small act of kindness reminds me of the kind of person I want to be. It makes me want to encourage someone else, share something useful, or help someone who might be doubting themselves the same way I once did.
Because sometimes the smallest moments end up staying with us the longest.
It's Never Too Late
I know many people build incredible careers without ever sharing publicly, and I genuinely respect that. This isn't the only path, and I don't think documentation has to be public to be valuable. It can be a journal, a folder of notes, a document filled with lessons learned, or a collection of project write-ups that nobody else ever sees.
What matters is leaving yourself a trail. Something that helps future you remember who you were, what you learned, what excited you, and how far you've come.
The reality is that I can't go back and document the beginning of my journey. I can't recover every lesson, every thought, or every moment that slowly disappeared with time. But I can document today. I can write about what I'm learning now, capture experiences while they're still fresh, and leave behind something that my future self can look back on years from now.
These days, I still feel nervous whenever I share something online. I still wonder what people will think, and I still worry about getting things wrong. The difference is that I no longer wait for those feelings to disappear before I act. If I waited until I felt completely confident, I would probably still be waiting.
Over time, I've realized that courage isn't the absence of fear. It's choosing not to let fear make every decision for you.
I'm still scared sometimes, but I don't want that fear deciding which projects get shared, which lessons get written down, or which parts of my story are worth keeping.
And if sharing publicly feels intimidating, start privately. The goal isn't to become a content creator, grow an audience, or build a personal brand.
The goal is simply not to lose your story.
Whether that's a blog, a GitHub repository, a journal, a folder of notes, or a post that only a handful of people ever read, it all counts. Years from now, you'll have something I wish I had more of - a record of the journey itself.
Because one day, you might want to look back and meet the person you used to be.
And you'll be glad you left a trail.
I'd Love to Hear Your Story
Writing this made me realize how many parts of my own journey I wish I had captured while they were happening.
At the same time, it also made me appreciate the things I did manage to save, whether that's an old project, a forgotten post, or a memory that somehow stuck around.
I'm curious what your experience has been like.
Have you documented your journey in some way, or do you ever find yourself wishing you had started earlier?
Maybe you have old projects, notes, blog posts, journals, or even screenshots that take you back to a different version of yourself.
I'd genuinely love to hear your story and how you think about documenting your own journey.
🤝 Let's Stay Connected
One of the best parts of sharing online has been meeting people from different backgrounds, experiences, and stages of their journeys.
If you'd like to connect, share your story, or continue the conversation, I'd love to hear from you.
Transparency note: I used AI (Gemini) to create the banner image for this article.
Top comments (149)
I believe it's never too late to start something new. And you've already taken that first step. You're no longer just someone being supported by others, you're already in a position to support and inspire others as well. I'm looking forward to your future activities! 😄
Thank you so much 😀
That means a lot coming from you. You've been one of the familiar names I've looked forward to seeing in the comments, and I'm glad our paths crossed through DEV.
And thank you for all the encouragement along the way. It's been wonderful following your journey too, especially the AI Avatar project. I'm looking forward to seeing where you take it next 😄
This resonated with me for a slightly different reason.
The line about missing "the person I was while building them" hit particularly hard. Lately I've realized that I don't just miss some of my old projects, I miss the version of myself that used to build them.
Back when I was a student, I'd spend weekends making random small tools just because I thought they were fun. Most of them weren't impressive, some barely worked, and none of them would make it onto a resume. But they captured a kind of curiosity and freedom that feels harder to find now.
Reading this made me wonder how many of those moments I've already forgotten simply because I never documented them. Not the projects themselves, but the excitement, the ideas, and the way I thought at the time.
Really thoughtful article. I hadn't considered documentation as a way of preserving old versions of ourselves rather than just preserving our work.
I think that's exactly what I was trying to capture with that line. Over time, I've realized that what I miss most isn't always the project itself, but the curiosity, excitement, and mindset I had while building it.
I could relate a lot to what you shared about building things simply because they were fun. Those moments often end up meaning more than we realize at the time.
Thank you for sharing your thoughts, Aryan. You've become one of the familiar names I look forward to seeing in the comments, and I always enjoy reading your reflections. I also appreciate all the support you've shown along the way 😃
Thank you and likewise Hemapriya. I really appreciate your support as well... And your blogs are always a good read. Excelsior.
I really feal that this week... What started as a comment asking whether the OP had tried Kimi K2.7 on his benchmark, to me writing a simple handler for it so I can test it for him, using cloudflare's worker AI... I really didnt expect the rabbit hole to end up this deep. In the past week, I've went from a simple extension, to a full-blown agentic IDE, to writing a custom quantization for LLMs, a custom cache format, a custom file format, which is now turning into a custom programming language... All because every step speeds it up considerably and yet, the next bottleneck is staring me right in the face, so I fix it, by building a better alternative. The current state is a 2 bit quantized 0.5b model that's both written in and writes in NDA, my format, which shrank KV-cache by 4x and improved latency, but now... It doesnt even need cache anymore, because of the deterministic way it's written, it can execute on live-codebases and it's history tracks every change ever made and why it made it, so it learns continuously as it codes... It's translating languages (rust, python, C#) into NDA format, so it can learn it, then picks the fastest pattern for each step when it does a new write, or a polymorphic rewrite. 1 format, that uses the individual optimized opcode patterns from each language, to produce a JIT compiled app that self-optimizes to the system at runtime...
I just wanted to know if he tried Kimi 😭 Now I'm stuck in the rabbit hole until it's fully optimized to the point that I'd need a FPGA to boost it further.
I'll write a full post about the journey this weekend. Like I'm happy, all the things I developed and optimized are astonishing and performance is incredible, I just wish I documented it better as I went through the motions, at the moment the comment section has the full-scope as I got to checkpoints, but it's a fraction of the work that went into it and it's honestly incredible how far it's come 😂
I actually smiled reading this because it's such a perfect example of what I was trying to talk about in the article 😄
It's incredible how one small idea can turn into something much bigger before we even realize it.
I'm really looking forward to reading your post this weekend. Even if you couldn't capture every step along the way, I'm glad you're writing about the journey now.
Right? It's mostly cuz as I went about it, it took so many turns, things that worked incredibly well that I just ditched cuz I found something better. Eg. using the NDA format for b1.78 ternary weights, it worked, it got about 3x the performance vs 1.58, but I ditched it for 2 bit, because while it's a flawless conversion of 1.58, it didnt allow me to quantize float models to it. Whereas 2 bit handles float and ternary weights without issue, with marginal loss as it's not a standard int4 quantization. These are the kind of things I wish I had documented thoroughly, because it's incredible, yet didnt fit my bill, so I moved on and while it's in the git-history, it's something that deserves a look at on it's own too, because that's pretty groundbreaking for bitwise LLMs... 3 performance at 27% size increase, which is more than compensated by the NDA-KV-Cache that compresses 4x, merkel rooted so it doesnt actually forget what was in cache and it improves latency. I mean any one of those is enough to write a full-fledged masters thesis on. Each groundbreaking discoveries in how we develop LLMs, yet they're footnotes on the project?
That's such an interesting way to look at it.
I think that's exactly why documenting along the way can be so valuable. Sometimes the ideas we move past end up having stories of their own, even if they don't make it into the final version.
I'm sure there are a lot of people who would enjoy reading about those discoveries too 😄
It's never too late. I wish I had started earlier too...I have a couple of rules:
I really like those rules, especially the second one.
Looking back, I did document some things, but there are definitely lessons and experiences I wish I had written down at the time. That's something I'm trying to be much more consistent about now.
So many of the things that take us time to figure out end up being the exact things we want to remember later. That's a great reminder 😄
Really well written Hemapriya, kept me reading till the end.
Documentation also helps during the bad patches nobody talks about.
When you're stuck on something for 3 days straight and everyone around you seems to be shipping things effortlessly, motivation or advice from someone else doesn't really do much at that point. What actually helps is your own past self showing you that you've figured hard things out before.
But those are exactly the moments you have nothing to look back at. Because you never wrote it down.
I felt that recently and wished I had even just rough notes, not polished posts. Just "today I was stuck on X and here is how I got unstuck." Simple as that.
I really loved this perspective. I hadn't thought about documentation through that lens when I was writing the article, but you're absolutely right.
Sometimes it's not the big achievements we need to remember. It's the reminder that we've been stuck before, figured things out, and kept going.
Thank you for sharing this, Shubhra. It added another layer to how I think about documentation 😀
Really glad it did. Felt like something worth sharing after reading your post.
😅14 years old, searching the dark web for malware kits, so I can make a keylogger (for myself), so I stop forgetting my passwords... Uhm, 15 years old, trying to make a game in CryEngine, thinking I'm the shizz when all I did was play sims with the placeable objects... Oh wait, 16, wrote an app that deletes explorer.exe (as a joke, it actually just moved it to desktop). 17, cracked my first software (Billquick surprisingly still uses the same SQL db for product key expiry as where the data goes). 19, wrote my first AI (not fancy stuff, literally half a million if-else loops), 20, my first trading bot (400% profit MoM for 4 years straight of backtesting) sadly my nvme died the night I ran the test, I still have it incase I someday find a way to retrieve it. 22, started Doccit (autonomous accounting suite) and since then it's been too chaotic to track, Git would do a better job than I can
Reading through it feels like a timeline of your journey, and honestly, that's one of the things I wish I had more of from my own early years.
Even if it wasn't all written down in a journal somewhere, you still seem to have a record of those different chapters, projects, experiments, and lessons along the way.
Thank you for sharing this 😄
Yeah, just memories of what I did along the way, the few things that stand out. It'd be a tough 1 for me to even track what I've done the past 2 months (Around 1M LOC, 13 repos) and that's just my personal projects, ranging from a .Net infrastructure, to my own (way faster and more secure) whatsapp, anydesk and file share systems. So it's not at the rate where keeping track is best done via Git, cuz it'd take me too long to journal it all.
That's fair 😄
At some point, Git probably does a better job of tracking things than any of us could. Sounds like you've had a busy couple of months.
same here, and it's the regret that keeps coming back for me. most of what I wrote for years was the how...build this, ship that, here's the productivity setup. almost none of it was the journey...the decisions, the lessons, the problems I clawed through. I wish I'd kept even a private record of those.
what finally stuck was a second brain (after reading How to Take Smart Notes by Sönke Ahrens...a few years of notes on lessons learned, problems solved, projects built. it's been worth more than I expected because it compounds. you end up with something you actively reach back into and reuse, not just a record of who you used to be.
and that's the quiet answer to the fear you named. fear of imperfection is really fear of being judged, and it mostly disappears when the only audience is you. the most valuable documentation I have was never meant for anyone else to read...so "imperfect" just stops being the point
Thank you, Jake!
I loved your perspective, especially that your most valuable documentation was never meant for anyone else to read. I think that's such a beautiful reminder that documentation doesn't have to be public to be meaningful.
The idea of a second brain also sounds really interesting. I'll definitely check out the book you mentioned. Thanks for sharing it here 😀
Reading this felt like a message from my future self 😅. We always think we'll remember what we learned, but six months later even our own code looks like it was written by a stranger. Great reminder to start documenting today!
"When I wrote this code, only God and I understood what I did. Now only God knows."🤣
First time I'm laughing 😂
Mission accomplished then 😂
I genuinely don't think I've laughed this hard at a DEV comment before 😂😂😂
Mission accomplished then 😂again
Thank you so much, Divyanshi 🧡
That made me smile because it's so relatable. Sometimes even our own code can feel unfamiliar after enough time has passed.
Wishing you all the best with documenting your journey. I'm looking forward to seeing what you share along the way 😃
Documentation is compound interest for learning. You don't notice the value immediately. Then one day you're incredibly grateful you wrote something down.
I love that analogy.
I think that's part of what makes documentation easy to underestimate. The benefits don't always show up immediately, but over time those small notes, posts, and reflections can become surprisingly valuable.
Thank you for sharing that perspective 😀
the stuff that feels too rough to share is usually the stuff that’s most useful to someone else. the polished posts explain the result; the rough ones explain the gap where most people get stuck.
That's such a great point, Mykola.
I think the rough moments are often the ones people relate to the most because they're still in that gap themselves. It's easy to share the outcome once everything works, but the uncertainty, mistakes, and lessons along the way are usually the parts that help others the most.
Thank you for sharing that perspective 😄
that gap is the real thing, yeah. once it's polished it stops feeling like the thing that would've actually helped you when you were stuck in it.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.