• Septimaeus@infosec.pub
    21·
    20 hours ago

    FYI: it’s typically management who cuts corners, whether in hiring or process. I’ve met a few exceptions but most devs take pride in their work.

    Tips:

    1. if you’re experienced and management insists on cluegy solutions, either refuse or leave a trail of tickets and comments re: technical debt for the next dev.
    2. If you’re not experienced, or if you feel out of your depth and have no senior to turn to, know that you will with time and just try do your best.
    3. In either case, experienced devs will understand the situation and won’t judge you.
    4. Also in either case, fire the client.
    • asdfasdfasdf@lemmy.world
      3·
      19 hours ago

      Another method I’ve used extensively is to block code reviews on unmaintainability. Management has insight into high level stuff, but devs where I work dictate what gets merged.

      • Croquette@sh.itjust.works
        3·
        17 hours ago

        Whenever I can, my code isn’t ready yet, it needs a few tweaks until the code is viable. That way, if I can never touch the code again, it has a chance to not be terrible in the future

  • Randelung@lemmy.world
    66·
    1 day ago

    I was on the receiving end, except the roles are reversed. Dude retired and left an undocumented spaghetti mess.

    But! He worked on a code base by himself for two years, on a subject matter he knew nothing about, in a language he didn’t know, and kept asking management for help. I don’t blame him a single bit, not the tiniest iota. 200% management fault, once for having him do that and once again for ignoring his cries for help.

  • GluWu@lemm.eeEnglish
    70·
    2 days ago

    Oh, were you going to give me a raise that’s more than inflation? No? More than 6 days off a year? Oh, no? Match a 401k? …no. Yeah, good luck with the clusterfuck. The little energy I had beyond just making this function went into purposely obfuscating everything. Just give it to your AI, that’ll sort it out.

  • unexposedhazard@discuss.tchncs.de
    100·
    2 days ago

    I mean, i asked them to allocate time for me to write documentation and they didnt reply to those emails. Its not unmaintainable, but its still not very well documented apart from some comments on the more complex or intransparent sections of the code.

      • Croquette@sh.itjust.works
        30·
        1 day ago

        It’s a rarity because the nano second a prototype works, it never gets touched again because management only heard it works and don’t give dev more times to make it proper.

        So imagine management deciding to ask devs to go back and clean-up a codebase, pure fantasy.

          • bpev@lemmy.world
            2·
            2 minutes ago

            Wish granted. Now management questions why everything “takes you so long”, and you were passed up for promotion in order to promote Jim (just last week, he did a presentation about his new feature that uses fancyAssDB).

            Don’t worry, though. They’ll need your help soon, in order to make Jim’s fancyAssDB pet project sync with our oldAssDB legacy server (which is a completely different User/id structure. TBH might need to refactor most of Jim’s code to fit. Have fun extending all of Jim’s hardcoded features). He quit the company to join a crypto startup. Still no promotion though, since you finish stuff kinda slow (I mean, Jim built it in 2 weeks, so it can’t be too complicated).

            EDIT:

            So now I hear you thinking “well at some point, they’ll notice how much better my code works, and that features are much easier to integrate”.

            But don’t worry, because the next month, your manager will be promoted to head of a new department and forget you exist. Meanwhile, the new head of your department doesn’t know you, and is thinking of promoting Frank. While you were fixing Jim’s code, Frank added some features to yours using fancyAssLib3. He’s doing a presentation on it tomorrow, and management is very interested, because they hadn’t heard about this code yet. It’s Frank’s codebase, right? I mean, he’s doing a presentation on it.

          • Croquette@sh.itjust.works
            1·
            17 hours ago

            I try to do that as much as possible, but comes a point where you can’t push back the task in the next sprint.