• 1 Post
  • 754 Comments
Joined 3 months ago
cake
Cake day: February 13th, 2026

help-circle
  • Yep … the pipeline to becoming an open source developer:

    1: Use open source software.

    2: Get annoyed by some small, incredibly specific bug.

    3: Fix that bug yourself.

    I’ve fallen victim to that a couple times personally.

    And @TotallyWorthLife – it doesn’t take a whole lot of knowledge, as long as you’re working on a project that’s willing to humor beginners’ mistakes. I contributed to OpenRCT2 and KDE, both written in C++ … and I know basically zero C++. (I only knew a bit of Python and some half-forgotten PHP.) But I knew enough to look at the source code, ask devs questions about which files do what, and understand the code enough to zero in on the issue I was experiencing. In both cases, I ended up asking more experienced devs there if I’d gotten the changes right, but in both cases, I actually had. (Admittedly, one of those cases was basically by pure luck. They were using bitwise operators, which I knew nothing about, but I’d copied the line from elsewhere in the codebase where similar operations were done, and it happened to be the right one.)

    Just two pieces of advice I’d have for starting out:

    1: Look for something that should be a very simple fix. In both of my cases, I only needed to change one file, and only a couple lines in that file.

    2: Look into fixing a bug, not implementing a new feature. Or, at least, if you want to add a new feature, you should definitely be talking to that project’s devs first to see if they even want to implement that feature, and if so, get their advice on how they’d want to implement it. Yes, you’re doing free work, but if you’re adding more code for them to maintain and then expecting them to maintain it, you’re kind of demanding that they do free work as well. A simple bug fix, though, is a one-and-done that should (at least in theory) reduce the amount of maintenance work the regular devs of that project need to do.












  • Weight training is great for getting in shape.

    Running burns calories while you’re running. Weight training burns calories while you’re doing it and for hours to days afterward as muscles are repaired and grow.

    Both will do great things for your health in general and help burn off fat. (Though weight training may not be as noticeable on the bathroom scale – muscle weighs more than fat, so if you’re gaining muscle as you lose fat, you might not lose any weight at all; you might actually gain weight. But it will still get rid of fat.) Which type of exercise is right for you depends mostly on what your idea of ‘in shape’ means.

    If you’re just trying to be less fat, anything that burns calories is good … but the main way you lose weight is at the table. Put the fork down. Drink water instead of juice or soda. A small change in diet will be more effective than even a very intense workout regime.

    If you’re trying to be more muscular and attractive, then weight training should likely be a huge part of that.

    And if you’re trying to get into shape in order to be able to do something … well, what are you trying to do? If you’re trying to run faster, you should do running. If you’re trying to be stronger, you should do weight training. If you’re trying to be faster on a bike, you should do biking. Etc, etc, etc. For functional performance improvements, you should mostly just do the thing you’re trying to improve.




  • It won’t remove them in the original condition they were in while still inside the scooter

    Yeah…

    Again, only for academic purposes, I’d like to remove them in good condition so the battery cells inside could function in home-made ebike batteries. 2 or 3 scooters worth of batteries should be able to make a very nice ebike battery pack.