3 ms·
I'm not sure which is worse. Being that awk/sed guy or being that Git guy.
by zaphar 8y ago
I'm not sure which is worse. Being that awk/sed guy or being that Git guy.
- dmos62 8y agoWho uses "guys" anymore? Didn't stackoverflow replace that?
- Klathmon 8y agoSO often can take hours to weeks for a good answer, and that's assuming it doesn't just get closed as a dupe when the other one doesn't answer the question. A good "guy" (or girl!) is a phone call away and can often solve the problem in minutes.
- zachberger 8y agoTotally agree, that network of SMEs is a huge productivity multiplier
- Insanity 8y agoI find that a surprising amount of people actually don't use SO where I work for anything beyond simple things. It's usually faster (and safer) to ask a 'local expert' first. Does depend on the situation, I work in a large-ish team where people have specialized in different technologies. So if I encounter something I'm unfamiliar with, asking someone locally is better than spending time finding a solution on Stackoverflow that might not be what I want.
- imhoguy 8y agoYou would be surprised how much some technical people are lacking in Google, SO skills. When I am lazy I sometimes just shout them what they should put in google to get an answer. Thankfuly it is minority in my gigs.
- colanderman 8y agoNah being the Git guy is easy. Step 1: Look in .git/logs/HEAD and roll them back to whatever state they were in before the mess they're in now. Step 2: Forward them the e-mail you keep handy that lists the only 3–5 commands they should ever use, verbatim, without deviation.