back

by dmitrygr·10y ago·view on hn ↗
The author claiming he'll never need to do a BFS, and thus does not need to know it is kind of funny to read. You should never be proud of your ignorance.

Oh, you think you're a front-end dev and will never need to do anything else? What happened to striving for growth (personal and professional)? Why not learn how to write a BFS instead of writing a rant about your pride in not knowing it? Are you really just proud of doing your one thing, doing it well, and have no interest in ever branching out? If so, it is not surprise nobody will hire you (who needs a single-use tool?). If not, then also no surprise as you've shown a complete lack of desire to learn (who needs an inflexible employee?).

I am further sorry to tell you that your github history is irrelevant. I've seen _my_ code on github under 10 names. None of them mine. I'd never trust anyone's github profile - no reason to believe they wrote the code, they did it themselves, and how many attemtps of guess-and-check they needed (or not). You know what I do trust? Your ability to prove your "skills", in person, under realistic pressure, on demand, and on a schedule. You know, by solving a problem perhaps a bit out of your comfort zone. Maybe a simple maze?

1 comments
A jack of all trades isn't inherently better at all trades. There's great value to be found in a specialist.

And if you're hiring a front-end pay him as such. If you want him to know more than front-end beforehand, pay him extra.

specialist != only know one thing

specialist = know one thing well, many things a little

only know one thing = useless one-time-use-tool whom i will contract for exactly my one-time-problem and then move on from