NX is build software. You write your code on your laptop, you press “build”, it runs NX, and you get a built version you can put onto your web server. If you could hack NX, you could hit a lot of p…
  • NotMyOldRedditName@lemmy.worldEnglish
    3·
    6 days ago

    It can be good, but depending on how much it is, can get pretty monotonous fixing the same problem repeatedly. This was a multi year thing in this case.

    • owenfromcanada@lemmy.caEnglish
      6·
      6 days ago

      Hopefully you at least got some measure of free reign with it. The main times I find cleanup jobs soul-destroying is when I’m getting micromanaged or otherwise harassed by clueless managers.

      But given space to breathe and work, I often enjoy tidying up code messes. Gives me the same sensation as when I used to rewire spaghetti data closets in college.

      • NotMyOldRedditName@lemmy.worldEnglish
        6·
        6 days ago

        Ya, they let me do it how i wanted and I mostly got to choose what I’d work on next for the clean up task.

        It was great to start, but it’s size just eventually made it tedious. Oh, I’m doing this again, and I know exactly what my week is going to look like, because the other screen I just did is wrong in exactly all the same ways from top to bottom.

        If a new feature was needed in an area and it wasn’t urgent I’d say I’m fixing that area first, and then make the new feature. If there were serious bugs that needed fixing, unless it was a easy hotfix with other priorities, I’d fix that whole area instead first.

        Edit: Watching the crash rate tick down with all the progress though was great.