You must log in or # to comment.
What does “all tech debt is legal” mean?
That accumulation of a hundred years of tech debt during that 12h window is acceptable
Good opportunity to introduce a Cobol subsystem.
So the equivalente to not wanting to make part of it and staying at home is setting repositories private a few hours before and only reopening the day after?
Sweet ninjesus, i’m having a heart attack just imagining it
This summer - GIT OUT
Oh God damn you. Have your upvote and… you know the rest…
(ノಠ益ಠ)ノ彡┻━┻
I expected ‘git gud’
┬──┬◡ﾉ(° -°ﾉ)
Unironically I think this is my only shot at getting past our code debt.
Wdym you don’t like waiting 3 weeks for a code owner to approve a 1 line change?
“Just an FYI, you can multiple people to code owners”
- Me, every week to that one guy
It didn’t say anything about wiping previous debt
I thought this was programmer humor, not programmer horror
Another movie pitch:
Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.
Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?
Here’s one for a TV show.
In 2022, a crack quality assurance team was made redundant by a CTO for a botched product launch they didn’t commit.
These men promptly escaped from a maximally unstable job market to the LinkedIn underground.
Today, still wanted by recruiters, they survive as soldiers of fortune.
If you have a broken codebase, if no one else can help, and if you can find them, maybe you can hire the QA-team.
You are amazing, you beautiful lemmy stranger, you.
DO DODO DO DOO DOO. DO DODO DO DO
I am ramping a vehicle onto its roof in celebration
Merging all the feature branches in time is easy.
Having the project compile afterwards is hard.
Very easy: merge everything, fix after the feature freeze. It’s a feature freeze, not a bugfix freeze.
Edit: wait you said code freeze, my bad. Still, merge everything. If stuff doesn’t work after the freeze, management will unfreeze for fixes. Or they freeze a non-working product. Do stupid management, get stupid results. Not on me to make idiotic processes work.
Merge/test/fix on a separate branch and then merge this into main when the freeze lifts?
Is there a robust test suite?
Merge, test, merge, test, patch, merge, test
If by test you mean wait for customers to yell at us, it’s super robust
Only some of the new code does. Unfortunately, most of the code base is 10 years old written in the good ol’ Anarchy Driven Programming paradigm.
The test suite takes 24 hours to run fully.
I’m not understand , what it’s mean
It’s a meme referencing the movie “the purge” which legalizes all crimes during one specific night.
Thanks
rm -rf * git add -A git commit -m "oops." rm -rf .git git init git add . git commit -m "bye." git push origin main --forcerm-ing.gitisn’t gonna work cuz you’ll have to re-add the remotes.Oh good point 🤦
So maybe instead, we can clear all local + remote branches and tags, create a blank branch, delete main, rename the blank branch to main, then delete .git
Although the OP says that we can merge anything, and we might not have access to mess with branches
Or just
git push origin --force blank:main
I’m not sure about the git history wipe, I can’t test it myself right now
Just test it on production, you could do it right now
Goodbye
fedecan.ca
My question would be for what time zone? That seems like an important detail
Well my pull request simplified all time zones to just UTC +8:45 so we never have to worry about it again
