missing-semester VS javascript

> The realization came a few weeks ago when someone shared The Missing Semester of Comp Sci on HN. It’s full of basic things you’d expect any programmer to somehow magically know … but they don’t learn this anymore. https://missing.csail.mit.edu/

I do feel somewhat jealous though that these resources are now available for students to learn in a structured, borderline spoon-fed way when this stuff took me a number of years and hacking around to build up and gain muscle memory over. Still, I think the knowledge you struggle to learn yourself sticks around a lot longer than knowledge that was fed to you from school. :shrug: I could see it either way.

> "Why does it have to be so complicated? I just want to install a program"

> "Why would you do that in the command line? It's way easier using $Program"

A concerning observation that’s slowly dawning on me is that more and more programmers don’t know how computers work. They can write code, build software, and do lots of useful things. But they have no idea how computers work. They’re more akin to lusers as we used to call them than they are to hackers of old.

Fantastic at their specialty and the tools they use. But move a button to an unfamiliar place or throw them into a new (but fundamentally same) environment and they’re lost.

The realization came a few weeks ago when someone shared The Missing Semester of Comp Sci on HN. It’s full of basic things you’d expect any programmer to somehow magically know … but they don’t learn this anymore. https://missing.csail.mit.edu/

Seeing that link shared connected the dots in my mind. I’ve been wondering for months ”Why does everyone at work have so many random local environment issues all the time?” … it’s been working fine for me for years. Same code and hardware. ¯\_(ツ)_/¯

This is a webpage I refer people often to: https://missing.csail.mit.edu/

This from MIT is called "The missing semester of your CS education" and provides some practical hands on skills like Git https://missing.csail.mit.edu/

The Missing Semester: Made to address shortcomings in software engineers and teacher Vim.

In comparison, JavaScript doesn't have a strict coding standard, although it does have widely accepted code style guides like the Airbnb JavaScript Style Guide and the JavaScript Standard Style. These guides provide recommendations for code formatting and naming conventions, but they are not as strictly enforced as the Java coding standard.

😎 We use this language, but if you are asking how to write in the most correct way, a great repo and Style Guide -> airbnb/javascript -> clean-code-javascript

Airbnb JS Style Guide : A mostly reasonable approach to JavaScript

I think there's still a case for default exports for a file like toggle.js where the module itself is composed of a single function, but again it's down to your own workflow and personal preference. There's some great discussion in https://github.com/airbnb/javascript/issues/1365 about the pros and cons. Tooling support is definitely a big component of both sides.

On a related note, there's some excellent discussion in https://github.com/airbnb/javascript/issues/1365 about the pros/cons of default exports if you're interested.

Airbnb JavaScript Style Guide GitHub Repo

A linter is a tool to statically analyze code and finds problems with them, potentially preventing bugs/runtime errors and at the same time, enforcing a coding style. Time is saved during pull request reviews when reviewers do not have to leave nitpicky comments on coding style. ESLint is a tool for linting JavaScript code that is highly extensible and customizable. Teams can write their own lint rules to enforce their custom styles. At Grab, we use Airbnb's eslint-config-airbnb preset, that has already been configured with the common good coding style in the Airbnb JavaScript style guide.

Link with anchor to recent discussion:

https://github.com/airbnb/javascript/pull/255#issuecomment-1...