ipconfOct 6, 2025

Well well well.

https://lemmy.ml/post/37183049

Show threadQuizzaciousOtterOct 7, 2025
  • Use git for any code you write. Yes, even a simple script.
  • Commit and push often. More often than you think is reasonable. You can always rebase / fixup / squash / edit but you can’t recover what you didn’t commit.
  • ???
  • Profit.

    • Seriously, once you commited something to the repo it’s hard to lose it. Unless you delete .git. But a this point frequent pushing has your back.

    I know git can be hard to grasp in the beginning. It was hard for me to. I highly encourage everyone to put in the effort to understand it. But if you don’t want to do that right now just use it. Just commit and push. It will pay off.

    Show threadRooster326Oct 7, 2025
  • Get qlannoyed by constantly increasing Code Coverage Requirements on untestable code. Never down!
  • Change step 2 to "Commit and push ONLY when absolutely necessary. Because adding comments often requires a rewrite of untestable code."
  • Go back to Step 2 and wait for a major bug.
    • Show threadfibojoly
    Our company “architects” decided we needed 80% coverage minimum. On a mostly .Net 4.8 codebase. Hundreds of program used in prod, with barely any tests in sight.
    It’s a fucking nightmare.
    Oct 7, 2025 at 7:01pmWeb
    Show threadMetjuOct 8

    Ah, the classical “just introduce tests in a legacy codebase”, what can go wrong?

    My condolences, it’s always a BITCH to handle

    Show threadfibojolyOct 11
    Fixing that bug you just found in prod : half a day. Adding enough tests so the app is now at 80% coverage : a whole fucking week. My student colleague was not impressed. I was like “yup, that’s what jobs are like”.