• 0 Posts
  • 24 Comments
Joined 2 months ago
cake
Cake day: February 22nd, 2026

help-circle


  • We used to do retrospectives at one of my old jobs, because everywhere loves cargo-culting agile and scrum stuff.

    I quickly realized that a lot of the problems were largely outside the team’s control. It was shit like “The CEO doesn’t believe in designers or UX, so he won’t hire one, so we spend a lot of time doing that work badly ourselves.” Or, “management is making us spend all this time in ‘planning meetings’ so we don’t get anything done”

    Stuff that has easy solutions, but we can’t do because some idiot or powerful cry-baby is in the way.






  • Sounds about right.

    I’m using GitHub actions at work because this place is extremely dysfunctional, and I can just add GitHub actions without it being a whole “research spike planning meeting impact analysis” six week journey.

    I took it from “there are absolutely no checks and Bob broke the environment because he pushed up a change that’s just invalid syntax” to… well, I couldn’t make it block the build on failures but at least now when Bob breaks it again I can point to the big red X and ask why he merged with an error.



  • jtrek@startrek.websitetoProgrammer Humor@programming.devI'm in.
    link
    fedilink
    arrow-up
    38
    arrow-down
    1
    ·
    13 days ago

    I was on some website the other day and I opened the browser console for unrelated reasons. They had a giant message there that was like “STOP. If someone asked you to paste something here, you are probably going to be hacked. Do not do anything here unless you know what you’re doing.”

    Which, admittedly, is probably good advice.




  • All code going to the main branch must have a corresponding pull request reviewed and approved by someone with knowledge of the codebase. You really shouldn’t have the front end guy approving backend code.

    Ai doesn’t count as a code review.

    At my previous job, the policy also said you were supposed to actually check out the code and run it locally. Found a lot of bugs and issues that way.

    At my current job, it’s often a rubber stamp. I’ve seen things like “that’s too many parenthesis. This won’t run” sail through. This is bad.

    There should also be automated tests and checks.

    A long time ago a director told me “software engineers are the most sensitive people on the planet” and I think he was right. Some people just can’t take feedback. They take something like “please sort your imports. We agreed to use isort last week” as a personal attack.