31–40 of 130 posts
Just use some automated coding test like Codility: https://codility.com/ Even an easy JavaScript programming tasks can filter a lot of applications so you can concentrate on best candidates.
I've used `nav` or `section` for a long time, never found of the difference from `div`. Screen readers? Maybe for `nav`, what about `section` and other 1000 tags with subtle different semantics?
At 80 people it might start being the time to question whether its really everyone else thats unskilled or your approach to evaluation is wrong. Asking a pop quiz of arbitrary tools / techniques that you happen to have remember really isn't a good way to evaluate if someone is a good developer. I am a good developer and I only just remember what clearfix is, I most certainly couldnt explain how it works.
At 80 people it might start being the time to question whether its really everyone else thats unskilled or your approach to evaluation is wrong. Asking a pop quiz of arbitrary tools / techniques that you happen to have remember really isn't a good way to evaluate if someone is a good developer. I am a good developer and I only just remember what clearfix is, I most certainly couldnt explain how it works.
Agreed. I understand missing accessibility (either you have ARIA or you don't), but what does "solid markup skills" mean? The differences between many tags is just user agent stylesheet defaults. If I wanted to be extra crazy, I could build a website using alone. Or maybe I am just a bad developer.
If this post were phrased as "web developers don't know accessibility" it would be obviously true and uncontroversial. Unfortunately.
Although I only had the chance to review their personal websites or github profiles
Many are not able to choose the right HTML elements, to explain why and how a clearfix works, or what ARIA roles are for, but they can use React and Angular.
You want to talk about incompetence, and your "application review" consists of browsing the web.
And almost no backend developers can write assembler either! It's almost like we've spent decades layering abstractions on this stuff so we don't have to wrangle it ourselves, isn't it.
There are no useful abstractions that will let you fail to understand how HTML and CSS work.
WebGL, WebAssembly, emscripten
What the heck is "A11y"? I've never heard of that.
Kinda like i18n for "internationalization."
The contrarian argument is that this signifies an important truth, that HTML never worked the way it was suppose to. In the same way that we might argue that a misunderstood product is the fault of the designer, not the user, we could argue that developers moving away from HTML is the fault of HTML, not the developers. This has been discussed many times, both here on Hacker News as well as elsewhere. To recap that ar…