• Ogmios@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      9 months ago

      Amazing how much easier it is to motivate yourself when you have the ability to make significant decisions on the fly, based on the immediate feedback you receive from the system, instead of spending half your time hitting your head against a wall attempting to sus out self-contradictory instructions given by people who don’t actually understand how any of it really works.

  • Rednax@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    9 months ago

    But I love coding at work?!

    The problem is that every living entity in a 10 kilometer radius around me, seems to be hellbent on getting me to do anything but coding. Refining work estimates, fixing badge access rights, fixing a driver issue, telling people that you cannot do 1000 things at the same time, teaching the new developer how shit (doesn’t) works, mangling Jenkins into a functional state again, explaning that thing I did a year ago but is only now used (it was very high prio a year ago), writing documentation that noboby ever reads, progress meetings, specialty group meetings, knowledge sharing meetings, company wide meetings, etc.

  • AlolanYoda@mander.xyz
    link
    fedilink
    arrow-up
    4
    ·
    9 months ago

    Amazing how you can work 8 hours without it ever stopping being 1 am. Human beings really are amazing when they are motivated

  • mogoh@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    You can use a JavaScript to assembly converter so you get the same pain on your personal projects.

  • ExLisper@linux.community
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    Yep, programming is fun but working as a programmer not so much. For me writing software is a creative activity. It’s fun to come up with problems and find solutions for them. In my personal projects I decide what problem I want to solve, choose the technology I think will be fun to solve it in and then come up with a solution I like.

    At work you are usually handed a problem you don’t care about (we’re decommissioning X, you don’t have to know why, just change everything to use Y), the solution is described in detail by someone else and you just have to turn it into some code using 5-10 years old stack.

    Fortunately at my current job I mostly do projects without much technical oversight (proof-of-concept type project) so I can choose how I want to do then. I dislike the company culture but I know that moving somewhere else would mean going back to boring coding agian.

    • Flipper@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Where I work there is a hardware test, where the voltage needs to be changed on the power supply like 8 times. Currently it’s done by hand.

      I gave that to a student with the description that I want that automated, let production show you how the test is done. If you have other ideas how to improve it, just do it.

      This was 8 working days ago for the student. She still hasn’t started, because she wants an exact description what needs to be done. If you want me to write down how exactly everything needs to be done, I might just write it myself in python and be done with it.

  • Gork@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    At least with your assembly code it’ll go brrrrrrrt because of how fast it’ll be.

  • SuperSpruce@lemmy.zip
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Why is this literally the opposite for me?

    I have a class where I write in Assembly but instead I’m working on my personal HTML/CSS/JS project.