3 ms·
>How about just a "solid, hard-working senior developer"? When you say "brilliant", most good, competent developers think of a truly 1 in 1000 brilliant develop
by mlevental 8y ago
>How about just a "solid, hard-working senior developer"? When you say "brilliant", most good, competent developers think of a truly 1 in 1000 brilliant developer we know, and think of how short we fall from that.
no one thinks that because it's pr speak. i've never met anyone deterred by "brilliant" or "ninja" or "10x" or etc.
- jnbiche 8y ago> i've never met anyone deterred by "brilliant" or "ninja" or "10x" or etc. I'm deterred from such job ads. But in fact you're right, it's not because of what I wrote above. Instead, it's because I've found a high correlation between those job ad keywords and dev work doing nothing but CRUD apps under the micromanaging eye of dysfunctional management. But I tried to explain that in a more rational, diplomatic way, rather than just assume his company sucks.
- lovelearning 8y agoNo one? Never met? Well then, nice to meet you! Yes, such terms in a job description - or in my case, in initial contract meetings - are red flags for me. Red enough to either never apply or show myself out with some excuse. Because my definition of "brilliant" may not match their definition of "brilliant" in terms of capability or efficiency, and I don't want to find out how high the expectations are after the agreement's signed.
- icebraining 8y agoThe point of the interview is to sync up those expectations. If you're wondering what's their definition of brilliant, that's the perfect time to ask.