Polyglot, autodidact. OSS author and contributor. Addicted to writing code, seeking my next 'fix'. Love communicating with an audience whose eyes don't glaze over when I get to the 'good parts'.
I tried many complicated systems to separate by content type, language, platform, etc. They always ended up becoming aggravating over time.
Ironically, this more-or-less reflects the 'feature based' directory convention I use for web dev.
I aggressively curate this; as well as my GH repos.
I never fork a project unless I'm going to contribute to it or I neeed a custom fork. Custom forks should -- ideally -- be killed as soon as I find a workable alternative.
I don't hold on to forks of all the projects I've contributed to. Best case scenario, it becomes a big pile of outdated trash. If I want to look up something I worked on in the past, it's all recorded and reaadily available online.
I don't keep a collection of snippets either
My motto is...
"If it's not in production, it's not maintained. If it's not maintained, it's probably not worth using."
I'd rather master the ability to quickly and efficiently locate info on anything. Than be a master archivist of bit rotten code that only I care about.
Digital hoarding is still hoarding. I treat my local setup like a desktop. Keep it as free of clutter as possible so I have more (mental) space to work.
Incredibly helpful, thanks for a detailed response. I caught myself with lots of forks and created a ruby gem (Dishwasher) to help me bulk delete them.
A *very* seasoned software engineer, I wrote my first basic game, a lunar landing game, in Basic in 1969. Currently I am doing web development in Ruby on Rails, JavaScript, Elm.
~
Code
Sites
Work
I tried many complicated systems to separate by content type, language, platform, etc. They always ended up becoming aggravating over time.
Ironically, this more-or-less reflects the 'feature based' directory convention I use for web dev.
I aggressively curate this; as well as my GH repos.
I never fork a project unless I'm going to contribute to it or I neeed a custom fork. Custom forks should -- ideally -- be killed as soon as I find a workable alternative.
I don't hold on to forks of all the projects I've contributed to. Best case scenario, it becomes a big pile of outdated trash. If I want to look up something I worked on in the past, it's all recorded and reaadily available online.
I don't keep a collection of snippets either
My motto is...
I'd rather master the ability to quickly and efficiently locate info on anything. Than be a master archivist of bit rotten code that only I care about.
Digital hoarding is still hoarding. I treat my local setup like a desktop. Keep it as free of clutter as possible so I have more (mental) space to work.
Thanks for sharing your insights Evan.
I totally agree, the feature-based convection is really cool and easy to use.
Incredibly helpful, thanks for a detailed response. I caught myself with lots of forks and created a ruby gem (Dishwasher) to help me bulk delete them.
I hear you on the digital hoarding— it's a hard habit to break since it's mainly invisible
I am definitely borrowing this method. Thanks sharing
I might borrow from this method. Currently, I store everything by language, but that always gets unwieldy after a while as you have said.