3 ms·

A friend and I were joking today that we could probably create a career out of helping people/companies fix their git issues. I've been to several employers no

A friend and I were joking today that we could probably create a career out of helping people/companies fix their git issues. I've been to several employers now where most of the developers have an anxiety attack when they get merge conflicts. Being good at this is really great, though I'm not sure how to capture that on a resume, because basically everyone lists git these days.

gen220 6y ago
heh I've noticed this, too. There are a group of us at work that are known as "git surgeons", maybe that's the modifying noun you're looking for! In general, claiming status as a <technology> <noun> will get you positive attention, as long as it doesn't come off too arrogant (e.g. expert, master, w/e) e.g. git guru, nix nerd. It reminds me of this excellent article [0] that I like to share with all the engineers I work with, every year or so. In that case, you'd be a "taco bell programmer". But it's maybe too self-effacing depending on your opinion of taco bell :) [0]: http://widgetsandshit.com/teddziuba/2010/10/taco-bell-programming.html http://widgetsandshit.com/teddziuba/2010/10/taco-bell-progra...
the_af 6y ago
> because basically everyone lists git these days True! And apparently you cannot skip listing it. I recently changed jobs and was told one red flag in my CV was that I didn't list git as a tool I was familiar with. This wasn't a recruiter on a buzzword hunt, but the actual technical screener. I had explicitly removed all filler because I thought interviewers wanted to focus on the important bits... (got the job anyway, thankfully).