the roadmap is not a lie, and it shows at a minimum just how much is being requested to be carried around in one’s head for a good paying job. I didn’t see anyt

the roadmap is not a lie, and it shows at a minimum just how much is being requested to be carried around in one’s head for a good paying job. I didn’t see anything regarding cloud computing (knowing AWS basics, forget about the ever growing list of capabilities there) and the accompanying tools such as terraform/Ansible/Packer. Or how about the automation of style like including gofmt for golang or something like pre-commit and black/pylint. This list eventually will need to include security training. Also what’s worse is when a backend job actually wants you know “a little” front end. That’s a lie to avoid full stack pay because then the number of boxes duplicates (css, flex box, component based design, some flavor of React/Angular/Vue/Svelte, promises, maybe sagas if you’re in react, Babel/transpiling, Webpack/minification-alternatives, npm/yarn/grunt, tree-shaking, can-I-use-this and other community tools for dealing with the variability between what’s possible today vs what browsers you wish/must support, some modern UI comment tooling like material UI, the testing framework of the day from a front end perspective jest/mocha/eslint, accessibility considerations of design and components, automation tools to ensure easier collaboration with team members prettier/husky. I dunno I feel like I’m going to sound like a madman when I’m 60-70 rambling on and on about the weird side rabbit holes that most likely won’t even be remembered by my progeny. Me: “Code smells…DRY…YAGNI…YAGI…KISS…leblancs law…Murphy’s law… conways law … PR…MR…non-deterministism, stateless, ramble mumble mumble” Grandkid: “Somebody take granpops out for a walk again” I already sound crazy.