Why you should hire a frontend developer - Technology in government
This is a really good description of the role of a front-end developer.
That’s front end, not full stack.
I like this distinction between coders and developers.
The Coder is characterized by his proficiency in a narrow range of chosen skills.
By contrast the Developer’s single greatest skill is in being an applied learner.
I’m definitely not a coder. Alas, by this criterion, I’m also not a developer (because I do not pick things up fast):
Quite simply the Developer has a knack for grokking new [languages|frameworks|platforms] and becoming proficient very quickly.
I prefer Charlie’s framing. It’s not about speed, it’s about priorities:
I’m not a “developer” in that I’m obsessed with code and frameworks. I’m a “developer” as in I develop the users experience for the better.
This is a really good description of the role of a front-end developer.
That’s front end, not full stack.
Chris broke both his arms just to avoid speaking at the JAMstack conference in London. Seems a bit extreme to me.
Anyway, to make up for not being there, he made a website of his talk. It’s good stuff, tackling the split.
It’s cool to see the tech around our job evolve to the point that we can reach our arms around the whole thing. It’s worthy of some concern when we feel like complication of web technology feels like it’s raising the barrier to entry
On the surface this is about the pros and cons of minting a new HTML search
element to replace div role="search"
but there’s a deeper point which is that, while ARIA exists to the plug the gaps in HTML, the long-term goal is to have no gaps.
ARIA is not meant to replace HTML. If anything, the need to use ARIA as ‘polyfill’ for HTML semantics could be considered as a sign and a constant reminder of the fact that HTML falls short on some semantics that benefit users of assistive technologies.
This is a very handy table of elements from Steve of where aria-label
can be applied.
Like, for example, not on a div
element.
A very handy community project that documents support for ARIA and native HTML accessibility features in screen readers and browsers.
If you like the sound of being a design engineer, come and join us at Clearleft.
We’re hiring a design engineer. You should apply.
Do websites need to sound the same in every screen reader?
A presentation at An Event Apart Seattle 2019.
It’s snappier than front-of-the-front-end developer.