I’m just generalizing, like if you want to copy some cleaver feature or modify some Python program you came across, what are the red or green flags indicating how well your (or particularly some hobbyist’s/your early learning self’s) results are likely to turn out?

Also how can you tell when reading into such a project is going to be a major project that is beyond the scope of you ultimate goals. For instance, I wanted to modify Merlin 3d printer firmware for hardware that was not already present in the project, but as an Arduino copy pasta hobbyist, despite my best efforts, that was simply too much for me to tackle at the time because of the complexity of the code base and my limited skills.

How do you learn to spot these situations before diving down the rabbit hole? Or, to put it another way, what advice would you give yourself at this stage of the learning curve?

  • @[email protected]
    link
    fedilink
    39 months ago

    A section in the README about how to setup a dev environment - without that it’s often just a guessing game I don’t have time for

    Software brittleness

    Preferable to not require a special setup.

    • @[email protected]
      link
      fedilink
      69 months ago

      Even if you don’t have a special setup, having a section telling you that is still a helpful thing to quickly assess a new project.

      I appreciate knowing that a project should Just Work with minimal setup so I don’t have to guess or make assumptions