Hot take: Get good if you need 70 hours
If you need 70 hours to do what others are doing in 40-50 hours, you need to git good. If you feel your employees should work 70 hours to produce meaningful impact as a team (maybe because your team is lagging behind competition), you might have failed as a founder and built a weak team. You need to git good. Change my mind.
Tell me you're a programmer without telling me you're a programmer.
OP: Whenever I write 'get', it is auto-corrected to 'git'.
RightPatch
Stealth
a year ago
When build time takes more than 2+ hour to build, you didn't do git (ops) good.
When your dont have testcases in your SDLC and production fails, you didn't do git good.
When you send a PR with a large number of file changes, you didn't do git good.
Software engineering is full of such meaningless pain and misery. Time to revolt.
