Re:Signaling in tech is some fucked up shit (2016)
by GijsjanB on Sunday July 29, 2018 @07:37PM
(#17641011)
I have 0 years hiring people, my experience is this. The language(s) you write code in don't mean a thing. It's the ecosystem. I'm a JS programmer, but that is not why you should hire me, it's my experience with the DOM, HTTP, indexeddb, File API, documentFragment, Fetch API, TreeWalker, NPM, WebGL, interactive SVG, the pros and cons of React, when to use Redux, Basic login, NGINX, Docker, etc, etc, etc. My point is this: knowledge of Closure(Script) is a great tool in any programmers tool belt, but it is definitely not the most important one for a solid frontend engineer.
[ Parent
| on HN ]
Re:Signaling in tech is some fucked up shit (2016)
by louthy on Sunday July 29, 2018 @08:23PM
(#17641228)
Knowledge of APIs is not a good indicator of ability in my experience (I have many years of hiring people). So, the 'ecosystem' isn't particularly interesting and neither are the devs that just put endless lists of acronyms on their CVs. It's much more useful to listen to a dev tell you how they solved various problems, dig into their CS knowledge, see what they like working on in their spare time (code or not code related).
Re:Signaling in tech is some fucked up shit (2016)
by denkmoon on Sunday July 29, 2018 @09:30PM
(#17641454)
When I see an interviewee list out a bunch of things they have "experience" with like that, I assume they actually mean "I used this once".
Re:Signaling in tech is some fucked up shit (2016)
by Hydraulix989 on Sunday July 29, 2018 @10:37PM
(#17641665)
It's hard to avoid touching the DOM, HTTP, NPM, React, NGINX, Docker, etc. on a daily basis if you're doing any kind of serious work; it's not just some disjoint list of obscure buzzwords.
Re:Signaling in tech is some fucked up shit (2016)
by braythwayt on Monday July 30, 2018 @11:20AM
(#17645015)
Yes, compare and contrast the above to my own partial list of technologies from 1977 to 1997...
“Nova 1220 BASIC, Acius 4th Dimension, Hypercard, MetroWerks CodeWarrior, Lightspeed C, Turbo Pascal, MP/M, DigiTalk Smalltalk/V, J2EE, ...”
What does any of that have to do with each other.
Re:Signaling in tech is some fucked up shit (2016)
by scroot on Monday July 30, 2018 @01:05PM
(#17646004)
There's one thing: Hypercard and DigiTalk represent directions personal computing should have gone, but didn't (although that's not relevant to the thread topic)
Re:Signaling in tech is some fucked up shit (2016)
by denkmoon on Monday July 30, 2018 @11:22PM
(#17650307)
It's not so much that someone has touched <acronym soup> rather the kind of people that think just listing all that out is useful, are typically not the developers I want.
Re:Signaling in tech is some fucked up shit (2016)
by msds on Sunday July 29, 2018 @09:08PM
(#17641388)
You just named a lot of things. Why should I hire you?
Re:Signaling in tech is some fucked up shit (2016)
by GijsjanB on Monday July 30, 2018 @01:56AM
(#17642362)
Ok, the list is distracting. I mean, experience with web dev's ecosystem is more important than the languages you can write code in. Of course a list on it's own is useless, it should be supported with actual projects (hopefully some in production).