There is something inside of me trying to process the parade of resumes I'm seeing that say someone is a "JavaScript Engineer"
-
Show this thread
-
AFAICT this means one of two things: 1.) a career spent (thus far) in a single, preferred backend language 2.) a career spent on the frontend with an increasingly backend-relevant set of skills (hopefully)
2 replies 0 retweets 4 likesShow this thread -
In none of the cases I've encountered thus far does this seem to describe a cross-cutting set of backend or frontend relevant skills. that is, JavaScript seems to be the commonality in something I'm struggling to express kindly. Perhaps this was once PHP's role?
3 replies 0 retweets 4 likesShow this thread -
It could all be branding!!!! That said, nobody who professes to be a "JavaScript engineer" seems down with either real-world frontend device constraints or the complex tradeoffs in service design that arise from the CAP theorem.
1 reply 1 retweet 10 likesShow this thread -
The folks who have facility with these problems seems to call themselves "web developer" or "frontend engineer" (on the client) or something other-language-aligned on the server (even if they spend all day in JS/TypeScript).
5 replies 0 retweets 12 likesShow this thread -
Replying to @slightlylate
To clarify: your qualms are not about the term "JavaScript Engineer", but about the pattern you see emerging across those applicants who call themselves that?
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.