For most of college, I’ve kept it simple: I’d create a directory in my home folder for each project, then eventually move older or inactive ones into ~/programming/. When I change devices or hit file size limits, I’ll compress and send things to my NAS.

This setup has worked pretty well so far. But now that I’m graduating and my projects keep stacking up, I’m starting to wonder if there’s a more efficient system out there.

Curious—how do you all organize and store your projects? Any tips or methodologies that have made your lives easier over time?

The only person I’ve talked to about this is my mentor who’s been programming since the 60s (started on the IBM 1620 and Bendix G15) and he just mostly keeps projects in directories in his home directory and uses his godly regular expressions skills to find things that way. Makes me wonder if I’m overthinking it…

  • TimeSquirrel@kbin.melroy.org
    link
    fedilink
    arrow-up
    5
    ·
    13 days ago

    As an addition to your post, I’m also in the process of learning C/C++, and I’m curious also how others arrange their actual project files and include directories. Like, for example, if there’s a bunch of classes having to do with UI elements, do you just group them each under their own file all in their own directory? I’ve also seen projects where everything was just thrown into the top level directory, both headers and implementation files together in a giant pile of source files.