Links by Friday 015 - Devaluing Frontend
We have a frontend focus in this issue, so it makes sense to point out that the 4th edition of Eloquent JavaScript is live. It's free to read online, but if you want to support the exceptional author, you can purchase it from the website.
Devaluing Frontend
I almost didn't link to this because well I'm not sure how I feel about it, but it's worth sharing.
I think of HTML and CSS as tools you need to build the thing you want to build. It doesn't make sense for everyone working in frontend to be experts in them.
The quiet, pervasive devaluation of frontend - Josh Collinsworth blog
I keep noticing those of us in the frontend field being treated much the same as nurses, paralegals, and executive assistants. Our work is seen as important, certainly, but just not the same as, or as important as, the “real” work.
Why it's good for users that HTML, CSS and JS are separate languages
the separation between structure, style and interactivity goes all the way back to the web’s first proposal. At the start, there was only structure. The platform was for scientists to exchange documents. After the initial idea, a bunch of smart minds worked years on making the platform to what it is and what it is used for today.
Why it's good for users that HTML, CSS and JS are separate languages | hidde.blog
A response to an idea to merge HTML, CSS and JavaScript into one language.
CSS Cascade - A (Re)Introduction
This is the first time I'm sharing a video in an issue. It's a little over 30mins and very useful if you work on the web.
Manuel goes into detail on how the Cascade works in CSS. Even if you're an expert you may learn something new.
Don't be the glue
This is me right now at my current job.
Being Glue — No Idea Blog
Slides and notes for the Being Glue talk.
Go is enough
Let the scalability be a consequence of the success, not something that holds you back.
You don’t need a database, a queue, a distributed system: Go is enough. | Simone Dutto
This article is a reminder to me and you all that you probably don’t need to make things harder for yourself. Reading all these articles about software architectures and scalability has influenced me to think that before shipping an idea we need to have it all figured out. The Scalability Tale We need to choose a database: so, let’s start with that. We need to choose a db with a generous free tier, set it up, secure it, check the client API, and debug obscure network thingy (VPC, security group,...
That's it, see you next time.