• Ogmios@sh.itjust.works
      link
      fedilink
      arrow-up
      42
      ·
      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.

  • 𝘋𝘪𝘳𝘬
    link
    fedilink
    arrow-up
    80
    ·
    9 months ago

    The difference is: One you do for fun and one you’re told to do for money.

  • mogoh
    link
    fedilink
    arrow-up
    80
    ·
    9 months ago

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

  • AlolanYoda@mander.xyz
    link
    fedilink
    arrow-up
    65
    ·
    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

  • Rednax@lemmy.world
    link
    fedilink
    arrow-up
    59
    arrow-down
    2
    ·
    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.

    • pineapple_santa@feddit.de
      link
      fedilink
      arrow-up
      4
      ·
      9 months ago

      Just say no. Decline meeting requests. Set your own priorities. It’s not like they can fire the guy who operates the CI and apparently the physical security systems as well while still writing code for high priority projects.

    • psud@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      9 months ago

      I had a team of contractors working on some code. They had learnt in their previous jobs to document everything in the work wiki (aside from the design documents which have their own repository)

      And it was good they did, since the project was put on hold due to too much mismatch between backend and front, and all the contractors were fired (a day before Xmas) leaving the useless doco as the best reference for whoever needs to resurrect our code

    • Alph4d0g@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      Agreed on all of that. As I understand it, periods of better worker markets make for less of that nonsense people are willing endure. I’ve seen a recent trend of corporations turning up the BS because the job market has been tightening up and people are less willing to take risks.

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      That’s exactly it. When I code for my own projects, I don’t have to deal with any of that shit.

  • ExLisper@linux.community
    link
    fedilink
    English
    arrow-up
    26
    ·
    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
      6
      ·
      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
    18
    ·
    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
    14
    arrow-down
    3
    ·
    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.

    • intrepid@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      9 months ago

      The result is still the same, isn’t it? (in language you like vs in language you’re forced to use)

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

        It also really depends on what is being made. My Assembly programs are specific homework assignments. My JS project is designed entirely by my will.

  • aubertlone@lemmy.world
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    9 months ago

    The funny thing is, both of these are JavaScript for me.

    I mean I guess TypeScript if I’m doing coding for work.

    • InputZero
      link
      fedilink
      arrow-up
      6
      ·
      9 months ago

      My first job right out of college I was writing assembly for some epically old industrial equipment. That shit runs on its own language that was only ever used on that piece of equipment. Usually x86 but with some wacky modifications. There’s no compiler for that, just a manual the size of a textbook and a million chicken scratch notes in it that’s half covered in grease. I’m so glad I don’t do that anymore.

  • Elise@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    9 months ago

    I like my coding job as long as I have the space to do what I need to do. Without that I just get stressed out and way less productive. The older I get the better I am at setting boundaries and finding the right kind of jobs.