this post was submitted on 18 Feb 2025
678 points (99.4% liked)

Technology

63010 readers
5070 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 4 points 2 days ago* (last edited 2 days ago)

git gud.

And it's not that hard. Here's a primer:

  • git clone - download a copy of a repo (do once)
  • git checkout - change branches (-b to create a new branch); a branch is a set of changes (commits, state of the code) and you can easily jump between them
  • git add - select files you want to commit (submit to the project)
  • git commit - do the commit; etiquette for the message is one line brief summary of the change, then a blank line, then optional additional paragraphs with more explanation
  • git push (-u origin <branch name> the first time for a new branch) - send the changes to your online repo

When you run into problems, ask for help. Each team does things a little differently, so you'll want to ask your lead before doing most other git operations.

I'm a lead and I'm happy to sit with new team members for a half hour and walk them through the basics and with their first few commits. Everyone seems to catch on pretty quickly.

being a developer is about seeking out problems in the world and solving them with science

Eh, let them try and fail at starting their own thing. It turns out, writing software is hard, and writing good software is even harder, especially when you need to build it from scratch. FOSS is a wealth of pretty good code that you can build off of to make cool stuff quickly.

But it doesn't build itself, FOSS needs people to maintain it, and at some point you'll need something nobody else wants to build. But maintaining that thing takes time, and people out there will help you with it once you build it. So build your thing in such a way that it can solve other use cases, and people will start using it, and some will contribute to it, solving their own use cases because it's easier than making their own thing.

That's what FOSS is, it's a community effort to share solutions to problems so others help you make it better. You benefit from their work, and they benefit from yours, and everyone is better off. Businesses are easier to build on FOSS, as are hobby projects, so share as much as you can so you don't have to maintain it yourself.

I honestly don't see a business case for not using and contributing to FOSS extensively. It's just too expensive to build or buy everything yourself.

You don't need to gate keep to only those with a quest to solve problems, just appeal to human nature and demonstrate that FOSS is good for selfish pursuits as well. It turns out that a rising tide (FOSS) lifts all boats.