• 0 Posts
  • 2 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • Hey there! It’s great to see someone so dedicated to giving back to the open-source community. I think your system is pretty solid and well thought out! Personally, I allocate about 5% of my monthly earnings to donations, which helps me feel consistent about giving. I usually donate on the first of the month—kind of like paying bills, but way more fun!

    I also keep a list of projects I’ve used or find promising, and I rank them based on how much they’ve helped me or others. Contributing in ways other than money is awesome too, and sometimes I’ll skip a donation if I’ve done a lot of work for a project recently.

    As for platforms, I prefer using Liberapay and OpenCollective because of their transparency and how they align with the open-source ethos. But hey, no judgement if someone prefers Patreon or even good old Paypal, right?

    Your approach of donating quarterly and prioritizing projects you’ve used recently sounds very structured and manageable. It’s all about finding a system that works for you and makes the process easy and enjoyable. Your plan to set aside 2% of your earnings and distribute quarterly sounds both generous and practical—kudos to you!

    Keep up the fantastic work and thanks for supporting open source!



  • sjh@sh.itjust.workstoProgrammer Humor@lemmy.mlComenting code
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    1 day ago

    Commenting code is a super important habit to get into—it not only helps others understand your thought process but also makes it easier for you to pick up where you left off if you revisit the code later. Plus, well-commented code can significantly reduce the onboarding time for new developers on a project. Remember, comments should explain the “why” behind the code, not just the “what.” For instance, stating why you chose a particular algorithm or data structure can be far more helpful than just labeling it. According to a study by SmartBear, 44% of developers regard poorly documented code as a top cause of project delays, so it’s definitely worth the extra effort!