jpd-

I was accepted into the program.

The wording definitely implies that both free and paid content will be deleted.

Unfortunately if this is true -- and the organization is then up for grabs from a paid customer -- then I'm afraid it will open end users up to supply chain attacks

I'm in the same boat. I applied for their Open Source program (https://www.docker.com/community/open-source/application/) and am hoping this will allow me to retain my organization.

This really sucks for end users.

Perhaps, if the speaker incited a crowd to remove their masks at a protest in a municipality in which not wearing a mask was illegal.

Simply advocating that people violate mask orders doesn't pass the imminence test.

> By what specific evidence do you suggest that one person is "better" than another, or the "best [person] for the job"?

Experience and/or accomplishments for the vast majority of jobs.

Under what circumstances do you believe it is not possible to select among candidates based on merit?

For the same reason other groups complain when sweeping generalizations are made about them.

Criticism of the Chinese government is not racism. They have a history of controlling the flow of information both in and out of the country; any suggestion they are controlling the flow of information about this virus is rooted in established historical facts.

The entire hiring process is an act of discrimination. What's the alternative? Hire everybody that applies?

I feel like a lot of people that push back on this premise do so believing that "coding outside of work" means doing more of your day job. When you look at it from that perspective, yeah, doing 60 hours of the same thing per week instead of 40 is not going to do much for you.

In reality, most people that code outside of work do so to learn new things; new stacks or languages, or take on projects that are orthogonal to their day job.

I think the argument should probably be framed around "learning outside of work" rather than "coding outside of work".

The underlying assumption is that when you code outside of work, you're working on things that are different from what you do at work.

There's a difference between filtering incoming information and preventing someone from sending it in the first place.

Companies like you describe are the primary focus of Rackspace these days.

Context means everything. Is the author working on a startup with weekly sprints and a small dev team, or an enterprise app with 400 devs and a legacy codebase in a waterfall environment?

The author strikes me as someone who has a very narrow breadth of experience.

"A developer who can code the front-end, back-end, API, and database isn't as absurd as it once was (excluding visual design, interaction design, and CSS). Still mythical in my opinion, but not as uncommon as it once was."

I see this attitude expressed a lot among people who identify as "front end" developers and it seems like psychological projection to me. I would count myself and a number of close friends and associates as these mythical "full stack" developers so (in my circle) I don't think it is uncommon at all.

One thing I have noticed (again, in my circle) is that "front end" developers tend to start learning with front end development and are commonly self taught, while "back end" guys are more likely to have a degree and start with something enterprisey like .NET or Java. From what I've seen, back end guys have a much easier time moving to front end than vice versa.