Ryan Oglesby writes in May 2017 regarding the current “state” of CSS. Oglesby highlights how JavaScript has left behind many of its weaknesses and suggests that CSS has gone through a similar process. He offers five examples:
- Automatic Naming Conventions
- Flexbox Alternative to Float for Layouts
- Built-In Grid Alternative
- Built-In Variables and Calculations
- CSS-in-JS
A worthwhile read!
Joey Clover writes on HackerNoon about learner’s syndrome – or FOMO – when it c...
Why you don’t actually need a minimum of 72 PPI for the web.
Deems itself a “utility-first CSS framework for rapid UI development.” It distinguish...
Great article by Peter Jang that explains what modern JavaScript looks like, aimed especially at ...
James Koice writes a helpful article on what it takes to build a modern JavaScript application in...
A free, open source web framework for the rapid development of Python web applications.
COUNTIF checks a range of columns for a specified value, it then outputs the total number of colu...
Sacha Greif wrote an article for freeCodeCamp that provides a recommended path through the JavaSc...
Auth0 has a great article by Sebastian Peyrott (published 1/2017) on the history of JavaScript. Q...
An article by Andrew Askins on the challenges they faced in estimating software engineering costs...
Alex Wagner writes an article discussing the pros and cons of using static typing in a programmin...
Peter Norvig’s famous article on the process of learning programming.
Explains how to use GitHub’s particular brand of Markdown.