• Holytimes@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    22 hours ago

    Fighting your tool is how you figure how what you actually want to make to a large degree. Limitations is how you are pushed to actually decide what is actually worth it to you. Otherwise you just create endless slop with got bits mixed in cause your never challenged.

    Sure after a long enough time you can still get there but it takes so much longer if you have no challenge.

    • Nalivai@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      I work in embedded my whole life so I’m no stranger of fighting over scraps of resources and spending days trying to squeeze in something that doesn’t fit. It made me better at fighting this specific hardware limitations, and now instead of spending 10 times more time on making something that takes no time at all on a capable hardware, I spend only 5 times more.
      I don’t know if for creative work it does something, but for programming it’s like chopping wood with one hand behind your back. Sure you can do it, sure you can get better at it, sure it forces you to adjust your ways, but it doesn’t make the wood better chopped, it just makes you slower and more prone to mistakes for no reason