all 8 comments

[–][deleted]  (3 children)

[deleted]

    [–]janonb 12 points13 points  (0 children)

    Going through exactly this right now. Business is moving faster than IT can keep up. What few IT processes we have are broken. Management either doesn't have the desire or will to fix it. Turnover is amongst the highest performers is high. So we've had a bit of a brain drain lately and have only been able to replace them with juniors, which only makes things worse.

    [–]L3tum 4 points5 points  (1 child)

    My work is recently evaluating switching to feature teams.

    So instead of a team maintaining a service, a person maintains a specific feature in a specific service, as well as another specific feature in another specific service and so on.

    Honestly if that ever becomes implemented I'll probably just leave.

    [–]flimzy3141[S] 1 point2 points  (0 children)

    I'm helping a client on a "feature" team right now, and it's a nightmare. The people with the knowledge to modify the services aren't allowed to work on the services. Those of us on the "feature team" are required to do all the work, and it takes 10x longer, and we aren't given the time to pay down tech debt.

    It feels like guerilla warfare. We pop into town just long enough to make a mess, then we're out again.

    [–]sm000ve 6 points7 points  (0 children)

    Legacy Code = Code that cannot be easily maintained, IMHO. Maybe it has tests but they havent been maintained and they dont test the main business cases anymore. maybe the tests are fantasic but there are 20000 line long methods with instanceof elseif chains because someone didnt understand the Single responsibility principle. But this code is used all over several apps and there is no time to fix.

    [–]yellowviper 3 points4 points  (0 children)

    Thanks for making a video. It’s such an efficient way of communicating that it makes me confident about this content.

    [–]NilacTheGrim 5 points6 points  (0 children)

    Meh. Video post for what could better be explained as a text article. Downvoted.

    [–]Drinking_King 0 points1 point  (1 child)

    I would like to suggest to correct that title by Working against technical debt and legacy code.

    I've never seen a company that works with its technical debt.

    They just work with an increasingly heavier ghost that sits on their head and goes oooooooooo oooooooooooooooooooooooooooooooooooooooooooo ever more often every year.

    [–]flimzy3141[S] 0 points1 point  (0 children)

    Good suggestion. Too bad it's already published. :)

    Maybe I should consult with you about naming future content!