Cook A:
1 - Makes a soup
2 - Leaves a mess

Company: ☺️ What a nice cook, here's your promotion to senior Cook.

Cook B:
1 - Cleans kitchen
2 - Makes soup
3 - Cleans after themself

Company: 😡 What took you so long!? Cook A made it in 1/3 of the time.

This is the pattern I've seen so far in development... and it's sad

  • 14
    Hire a good cook, hire a good cleaner, cash in
  • 14

    Haven't seen "Tech Debt Dev" or "Refactorer" as job positions yet but that might work
  • 2
    @bigmonsterlover seriously I cook great but i hate cleaning.
  • 5
    @wicho "junior" 🙃
  • 1
    I have never made soup at my job
  • 0
    @bigmonsterlover this guy thinks he’s so hot changing his background to red
  • 0
  • 0
    How is the mess committed to master in the first place?

    No PR reviews?
  • 0
    With a simple PR review flow and any kind of board where you see which tickets are in PR I find that both devs and managers quickly get alarmed if someone is churning out PR:s that get stuck in review - and will ask them to stop and finish their work properly before moving on to new tasks
  • 1
    @jiraTicket Code is legacy - Made by the founder or something around those lines - Very typical at least for PHP stuff.

    Let's say, Dev A introduces an if with extra dependencies

    Dev B creates a class, extracts the if and logic, design patters, etc.
  • 0
    @iiii I don't get it 😅
  • 3
    Gal: Jumps into the bedroom naked where the Guy is and yells: Super Pussy!

    Guy: I will have the soup.

    What was the question again?
  • 2
    @wicho juniors will get the job of refactoring the garbage
  • 2
    @wicho I see. Damn these legacy codebases. However based on my experience it's possible to get management to reallt cheer for the poor devs who have to improve a poor legacy codebase, and view any rewrites as a larger accomplishments than new additions to the better easier codebases. so hope is not lost. Might help if all devs during meetings make a big deal out of being impressed whenever someone manages to do something with the legacy codebase - and management might "get" it
  • 1
    You can’t judge a cook by its muddle.
  • 2
    My conscience program won't allow me to leave a mess, so I choose to stay away from places that celebrate the mess.
  • 4
    You forgot about the occasional cook C who only knows how to cook kraft diner, but calls it "macaroni au fromage bleu" and manages to fuck up the clean up part afterwards. Somehow, he gets promoted to manager.
  • 0
    @jiraTicket I know and I'm working on it. Just join the company and I love it and the team.

    But a lot of the tickets I've worked on are regressions created from Team Leads and even higher levels. They think we do not need to spend a lot of time on the legacy code because it's gonna be "thrown away" work.

    However, with the complexity of the app, it's gonna take us several years to fully migrate. So if we keep building up tech debt, we're gonna waste a lot of time fixing "throw away" work instead of actually migrating it.
  • 0
    @PepeTheFrog Dude, that was a manager I had a few years ago. He thought he was a ninja doing procedural PHP and didn't even know Git.

    He created a service in 2 weeks but it was shit and he stored it on a self hosted mercurial server.

    I've seen things
  • 2
    @wicho yeah it's a tough scenario when people feel a project should be hacky because it'll be "replaced soon".
    Especially when "soon" is could be years.

    Been in the same situation myself.
    My team owned a legacy project. A merger happened. Multiple companies had similar projects so a new team was set up to build a new solution to fit them all. At the same time if they didn't do it within 12 months, our site would have to switch to a new database.
    Some managers argued it could be done, we were skeptical.

    Was very hard to guesstimate so we took the safe path and hired someone to just update the legacy site. It's now 2.5 years later and that new project is nowhere near complete.
  • 1
    Here's my variant of your pattern:

    Cook A:
    - Makes soup
    - I warned him of potential issues with his approach to cooking soup
    - He ignored my suggestions

    The soup was delivered, he was promoted to head cook, and no longer made soup. The soup is now my responsibility. The issues I warned him about started to appear. Management be like "what the hell did you do with the soup? It was perfect when cook A was in charge"
Add Comment