BLS also projects "Software Developer" jobs to increase by 25% by 2032 [0]. Without more detail on how these roles are categorized, hard to say if this is a valuable source of data.
This feels like a reply in bad faith. The point that the parent comment is making is that the title of the article isn't convincing, it's just making a provocative statement with no backing.
Citing a settlement date range with language like "may be a class member if you connected a financial account to an app" doesn't really refute my point.
As an interviewer I find it easy to catch candidates who are regurgitating a memorized answer, but catching people who know the answer in-and-out is really hard. I've had the exact same experiences on the interviewing side of the table as well.
I think interviewers tend to overestimate their ability to catch people who have seen the question before and miss on tons of candidates who are good at answering seen questions.
The problem with induction stovetops in my experience is that they really don't play nicely with Asian (particularly Chinese) cooking. Trying to stir-fry on one is maddening.
Usually any discussion about induction stoves seems to wholly revolve around European-centric cuisines, which is why I'm surprised to see this article quote a positive experience from a self-described "Kind of Chinese" restaurant. I genuinely wonder how they manage it and what I'm missing.
> By license I mean the current Leetcode interview process except you do it once and are good for at least five years
Some companies do seem to be offering something similar to this, see CodeSignal's general coding assessment or back when TripleByte was big a few years ago. I think the problem is that even within the specialized topic of LC style interviews, many companies don't agree on a similar strategy when it comes to types of questions and difficulty. There isn't one standard that every company agrees on, so most have their own flavor of it.
> Letting all causes be elevated via unrelated venues would be untenable
I'm not sure it would be untenable. People generally intuit the social cost/risk that comes with making a statement in an unrelated venue. That is a natural force acting against people randomly bringing up strongly held opinions on unrelated platforms. Explicitly drawing and enforcing a line just doesn't seem necessary.
> I suppose it's not totally unreasonable to draw that line by saying, "all content must be related to the topic at hand"
I think this would have the effect of either completely sterilizing platform discussion or being impossible to enforce reasonably. For instance, what would happen if a competitor just mentioned something totally innocuous that would incense nobody but was off-topic? Should that be punished?
Conversely, if someone makes their sandbox publicly available, they accept some risk that someone else in it may behave in a way that they don't like.
You can argue that Blizzard was well within their rights in punishing Blitzchung, but then Blizzard's audience is well within their rights to be upset with said punishment.
> Generally I'll avoid the subreddits for anything I'm interested in, as they're frequented by "experts" who feel the need to ruin everyone's fun.
Mind giving an example? I'm just curious because to me the high point of reddit is learning way more about interests I already love. For example I don't think I would've gotten nearly as into mechanical keyboards without /r/mechanicalkeyboards around.
In my experience the information getting across is just a pulse check of how others feel about the content. Tells you something about what to expect from the video.
I went through the "beta" version of this back when Dan and Maggie were developing it and it was great. I'm no JS expert but I've been working with it for many years and the mental models they teach have helped me intuit the language a lot better.
I'd pay for it in a heartbeat, just wish that they released even more episodes in this format.
[0] https://www.bls.gov/ooh/computer-and-information-technology/...