You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i run a pretty massive obsidian vault. it’s my second brain, my dumping ground, and most importantly my daily journal. i’ve got the whole thing wired up with the git plugin to sync to a private repository. free backup, version history, total ownership. the usual pitch for why plain text is king.
but looking at the commit history is weird.
i pushed the first commit to this specific journal structure on 2021-11-05 at 1:15pm.
back then, the commit messages were hopeful. that date marks the exact moment i decided to take being a self-taught dev seriously. i wanted "the job." i wanted the career. i was grinding tutorials, building projects, and documenting everything in that vault.
i even started a newsletter on linkedin called code tone. it was going to be my "thought leader" outlet, sharing cool tech and resources i found while researching. it was very public, very polished, very "hire me."
spoiler: i haven't updated code tone since i left my corporate job.
the funny thing about keeping a daily log in a git repo is that you can see exactly when the dream shifted. you can diff the files and see the tone change. i got the job i wanted. i did the thing. and then, slowly, the daily entries started to realize... this wasn't actually it.
so now i have this massive private repo full of ghosts of who i thought i wanted to be.
managing the weight
managing a "large git repository" isn't really about the file size or the lfs tracking. it's about managing the weight of the context you're carrying around.
i'm still writing in it every day. but i figured it was time to open a public issue and actually write something real again, not just "corporate compatible" tech takes.
Note
technically, this post is about version control.
i run a pretty massive obsidian vault. it’s my second brain, my dumping ground, and most importantly my daily journal. i’ve got the whole thing wired up with the git plugin to sync to a private repository. free backup, version history, total ownership. the usual pitch for why plain text is king.
but looking at the commit history is weird.
i pushed the first commit to this specific journal structure on 2021-11-05 at 1:15pm.
back then, the commit messages were hopeful. that date marks the exact moment i decided to take being a self-taught dev seriously. i wanted "the job." i wanted the career. i was grinding tutorials, building projects, and documenting everything in that vault.
i even started a newsletter on linkedin called code tone. it was going to be my "thought leader" outlet, sharing cool tech and resources i found while researching. it was very public, very polished, very "hire me."
spoiler: i haven't updated code tone since i left my corporate job.
the funny thing about keeping a daily log in a git repo is that you can see exactly when the dream shifted. you can diff the files and see the tone change. i got the job i wanted. i did the thing. and then, slowly, the daily entries started to realize... this wasn't actually it.
so now i have this massive private repo full of ghosts of who i thought i wanted to be.
managing the weight
managing a "large git repository" isn't really about the file size or the lfs tracking. it's about managing the weight of the context you're carrying around.
i'm still writing in it every day. but i figured it was time to open a public issue and actually write something real again, not just "corporate compatible" tech takes.
so, hello world. again.