• asyncrosaurus@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    Programming is mostly research. Researching curses to cast on the guy who wrote the Incomprehensible mess you’re currently debugging.

  • Zachariah@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    I am keenly aware that most management still subscribes to the idea that motion is work. They are fairly convinced that a lack of motion is a lack of work. That makes sense in a lawn care service, a factory assembly line, or a warehouse operation.

    • Sir_Kevin@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      This is so true. Oddly enough, if you’re motionless but looking through a microscope, those same exact managers will think you’re killing it.

      • Eager Eagle@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 months ago

        brings a microscope to work and starts using it

        Manager: What the heck are you doing?

        Eagle: Trying to solve that deserialization bug in the code base, boss.

  • Reddfugee42@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    Programming is just inventing machines where the components are words. Of course it’s just thinking. What else could it have ever been?

  • A_A@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    This article was motivating for me by highlighting how much research, learning and cogitation are more important than typing programs.

  • thanks_shakey_snake@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    Tbh I think alot of the “thinking” still looks like visible work though. I feel like the article makes it seem a little too much like there’s nothing observable, nothing to show or demonstrate, until POOF the code comes out.

    But I find that I often need to be doing visible stuff to make progress… Like devising little experiments and running them to check my assumptions about the system (or discover something new about it), and making little incremental changes, running them, using the output to guide the next thing I do… Even occasionally spending the time to write a failing test that I plan to make pass.

    So I’m 100% on board with letting managers believe this “80% of the work is invisible” thing… But I think as advice for programmers, it’s really important to not get too stuck in your head and spend too much time not kinetically interacting with the system that you’re trying to change.

    • LesserAbe@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      You’re right, and other intellectual “design” jobs will have physical or visible manifestations of the design process. In video you have a storyboard, set design. In music you have notation, lyrics, demo recordings, and so on.