Every job will have some sort of crunch time. Even just staying in a programming position, the definition of “crunch time” will vary wildly. I’m lucky enough that “crunch time” just means that I set aside all my other tasks until I fix whatever is on fire, but I still get to go home on time unless I really want the overtime pay.
I don’t envy positions with forced 80-hour workweek crunch times. That’s a sign of bad management.
In the video game industry, crunch (or crunch culture) is compulsory overtime during the development of a game. Crunch is common in the industry and can lead to work weeks of 65–80 hours for extended periods of time, often uncompensated beyond the normal working hours.
This is the crunch time I’m talking about. Not a few hours overtime or being oncall.
“crunch time” just means that I set aside all my other tasks until I fix whatever is on fire, but I still get to go home on time unless I really want the overtime pay
I get the feeling that this is what the industry is moving toward. Most crunches are due to poor planning, so it’s stupid to pin them on devs.
Are you able to fall back to normal git commands if you don’t know the shortcuts? This sounds awesome until I can’t remember the syntax to do something I don’t do everyday.
I’d use Desktop if it worked, unfortunately recently it decided that I don’t have read/write access to a repo I’m working on. Works fine in git CLI so idk what the problem there is.
No matter the GUI you use, you’re leaving a lot of useful functionality on the table. By their nature, you only get a small fraction of git’s features. There are many useful commands I use regularly that are impossible to replicate using GUIs.
A good UI (for you personally) should do all the things you regularly do. Git is a complex and messy enough beast that when I have to use the CLI I’m going off the golden path and copy+pasting something arcane.
You have rust, you decide to rewrite the C plan but the only library that supports it uses unsafe code so you go back and rewrite it. Wait what were you working on?
I started coding with TurboBasic. My favorite thing about TB was that you could have variable names of any length but the compiler only used the first two letters - and case insensitive at that. So “Douchebag” and “doorknocker” looked like different variables but were actually the same thing.
I read that recently as well, it is a great read. I can relate to a lot of the things. While it is meant as a humor piece, there is some solid advice in there.
I didn’t exactly have it in mind when I wrote my comment, but maybe subconsciously 😅
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.