this post was submitted on 03 Nov 2024
77 points (100.0% liked)

Linux

48178 readers
1403 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

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…

you are viewing a single comment's thread
view the rest of the comments
[–] Nibodhika@lemmy.world 2 points 1 week ago

On my personal computer ~/Projects/<name>, you need to remember that real-life is not like college, you won't be working on a new project every week. If you have more stuff than you can manage like this, you've bitten more than you can chew.

On my work computer it's a bit more complex, because I have to work with other people's projects as well, so I have a ~/Work folder and in it several folders by type of stuff, e.g. ops for operational stuff such as scripts to deploy stuff or grant permissions, code for servers (and client) code, etc. Also if I'm working on something specific that requires multiple repos I create a folder for that project with the repos inside.