isochronous

I mean, it's not going to win any philosophical debates, but these kinds of results are WORLDS better than they would have been just a couple of years ago. I have to wonder what would it take to impress you.

The very first thing I thought when I saw this wasn't "ooh, cool tech for voice chat", it was "man, the special effects industry will KILL for this - no more manually going through every frame of an effects shot and painstakingly removing background elements!"

So basically, I think the main assumption on which you built the rest of your advice is flawed.

I'd argue that this is less true for the specific field in question (computer science). Most companies looking to hire a developer aren't looking for a jack-of-all-trades hacker, they're looking for someone with a specific skillset, and in my experience it's not very hard for one good developer to recognize another good developer, especially with the way most CS interviews are conducted: problem solving, whiteboarding code, mock design sessions, etc. If you're a developer and you can't satisfy yourself that another developer being interviewed has the skills you need, you need to work on your interview questions.

That being said, it's almost certainly easier to land an interview in the first place with a good degree. I'm in Atlanta, and every company I've worked for here has almost automatically granted an interview to anyone with a degree from Georgia Tech.

I don't either, but if it's going to happen, I'd MUCH rather those messages be sent directly to me via DM rather than being just @channel or @general blasts. At least with DMs it's obvious that I've been sent a message that I need to read.

I don't understand the point you're trying to make. That's just how much disk space those tools and their dependencies take. You might as well ask why iron is as dense as it is.

Because modern web development is a friggin' minefield of browser support matrices, front-end development languages with experimental features, and aging specifications that require the use of preprocessors for simple things like variables and functions. Almost everything in that 106 MB is a preprocessor of some type that's designed to either make developer's lives easier, normalize code to a widely-supported standard, and/or optimize said code to deliver the smallest possible bundle to end users.

It's also 99% server-side preprocessors. Only a single package in that list (lodash) is something that could be actually loaded via browser, and even that would only be a small percentage of the full package size. It's also not required for a new rails project, it's simply a convenience workflow that integrates many of the tools used in modern best practices.

Then all you have to do is specify the specific version you want in your package.json, rather than a semver range, and you'll never get a version you haven't explicitly approved.

He starts off by saying that he has a library of e-books, then goes on to tell a story about how he actually purchased his first e-book recently.

How else would one build up a library of e-books without purchasing them?

Uh, no. Not legally, at least.

The answer to "your basic service doesn't work well" should not be "well have you tried our additional services?"

You could ask the same question about many government contractors. I would dispute calling what they've done "nothing," though. Building a facility of that size and complexity is obviously a non-trivial task, especially when they're having to solve multiple large-scale problems that have never been solved before.

So, uh... anyone else notice that a Supermutant apparently fell into one of the single-shell underground storage tanks? I needed that laugh!