The problem is when even Jr. positions require 2-3 years of experience.

Should designers read?

I don't understand the negativity. There are 40 points and people seem to be pretty butthurt about a couple of them. Most of them, however, are spot-on. For example, it's hard for me to see the text as I'm typing this comment because such the text is such a light grey.

I really like the article as well. The author seems to put emphasis on design accomplishing specific goals, not trying to be trendy or cool. They can both happen, but not all the time.

Sounds like 7 is talking about making it pretty / artsy / trendy, while the other is more about it properly accomplishing a specific task. Don't worry about your pixels being pretty, worry about your pixels being performant.

I also disagree with the sentiment that good design cannot be art, but I think the author is trying to point out when a designer opts for the latter in the cost of the former. Design should solve real problems with practical solutions. Art is beautiful and expressive. Can it be both? Absolutely, but not necessarily all the time, and not usually if you are inexperienced. Solving the problem is essential, making it sexy is secondary (unless it's like, a website for a lingerie company? I don't know).

My company's webapp has thousands of active users, and we're doing fine so far. No performance issues, no terrible mess of code. We don't use entirely just jQuery, there's a good chunk of Vanilla JS and a little bit of Twine, but mostly we try to avoid using Javascript when we can.

I don't get why people don't just still use jQuery. It works fine. It is incredibly easy to use, and is able to accomplish so much.

Solarized Dark forever.

Also, using the Pigments plugin is super cool. It highlights the CSS color code in the actual color. Works with Sass variables too.

If nobody reads, then why does my content matter?

If nobody reads, then why did you write an article?

If nobody reads, why is most communication today text-based?

People read. People read documentation. People read help articles. I worked in customer support for over a year before becoming a developer. When we wrote more help articles and more in-app instructional text, support emails went down significantly. I don't think it was a coincidence.