Following the spirit of my last post on Postgres, this is a guide to asking questions that I wish I had the opportunity to read earlier in my career. I’m mostly going to be noting the habits of those to whom I’ve looked up to in my time as a software engineer who are great at asking questions.| ChallahScript
In this article I go over three things that, in my mind, would make JavaScript better. None are new ideas. This post is an expansion of a tweet I had when I saw someone asking about improvements for JS. (though probably are impossible for various reasons). I’m going to be primarily speaking about browsers and the web, though much of this might apply to Node.js (though I’m not as familiar with that area so I can’t speak on it confidently).| ChallahScript
“Where should this information live?” is a common question I encounter daily as a software engineer. I (alone or in consultation with others) will make a decision and that information needs to persist…somewhere. The goal of course is to prevent some future engineer (often myself) from encountering some code and asking “why?” or, even worse, “what?”.| ChallahScript
Core philosophy| ChallahScript
I’ve been working professionally for the better part of a decade on web apps and, in that time, I’ve had to learn how to use a lot of different systems and tools. During that education, I found that the official documentation typically proved to be the most helpful.| ChallahScript