Beginner JavaScript Notes - Wes Bos
A very handy collection of organised notes on all things JavaScript.
Link tags: language
248
Data isn’t oil, so what is it? - How To Measure Ghosts
The discussions around data policy still feel like they are framing data as oil - as a vast, passive resource that either needs to be exploited or protected. But this data isn’t dead fish from millions of years ago - it’s the thoughts, emotions and behaviours of over a third of the world’s population, the largest record of human thought and activity ever collected. It’s not oil, it’s history. It’s people. It’s us.
Words To Avoid in Educational Writing | CSS-Tricks
This old article from Chris is evergreen. There’s been some recent discussion of calling these words “downplayers”, which I kind of like. Whatever they are, try not to use them in documentation.
esoteric.codes
Languages, platforms, and systems that break from the norms of computing.
This Word Does Not Exist
This is easily my favourite use of a machine learning algorithm.
Front-of-the-front-end and back-of-the-front-end web development | Brad Frost
These definitions work for me:
A front-of-the-front-end developer is a web developer who specializes in writing HTML, CSS, and presentational JavaScript code.
A back-of-the-front-end developer is a web developer who specializes in writing JavaScript code necessary to make a web application function properly.
Historical Dictionary of Science Fiction
A fascinating crowdsourced project. You can read the backstory in this article in Wired magazine.
Talking out loud to yourself is a technology for thinking | Psyche Ideas
This explains rubber ducking.
Speaking out loud is not only a medium of communication, but a technology of thinking: it encourages the formation and processing of thoughts.
What Makes CSS Hard To Master - Tim Severien
If we, as a community, start to appreciate the complexity of writing CSS, perhaps we can ask for help instead of blaming the language when we’re confused or stuck. We might also stop looking down on CSS specialists.
Parties and browsers
Tess calls for more precise language—like “site” and “origin”—when talking about browsers and resources:
When talking about web features with security or privacy impact, folks often talk about “first parties” and “third parties”. Everyone sort of knows what we mean when we use these terms, but it turns out that we often mean different things, and what we each think these terms mean usually doesn’t map cleanly onto the technical mechanisms browsers actually use to distinguish different actors for security or privacy purposes.
Personally, rather than say “third-party JavaScript”, I prefer the more squirm-inducing and brutually honest phrase “other people’s JavaScript”.
Russell Davies: Writing for snobs
They came for the writers of car brochures, but I wasn’t a writer of car brochures, so I said nothing.
CSS Vocabulary
This is a nifty visual interactive explainer for the language of CSS—could be very handy for Codebar students.
Easily rename your Git default branch from master to main - Scott Hanselman
Nice and straightforward. Locally:
git branch -m master main
git push -u origin main
Then on the server:
git branch -m master main
git branch -u origin/main
On github.com, go into the repo’s settings and update the default branch.
Thanks for this, Scott!
P.S. Don’t read the comments.
Is it time for a Web Performance rebrand? – Simon Hearne
I think Simon is onto something here. While the word “performance” means something amongst devs, it’s too vague to be useful when communicating with other disciplines. I like the idea of using the more descriptive “page speed” or “site speed” in those situations.
Web Performance and Web Performance Optimization are still valid and descriptive terms for our industry, but we might benefit from a change to our language when working with others. The language we use could be critical to the success of making the web a faster and more accessible place.
The 3 Laws of Serverless - Burke Holland
“Serverless”, is a buzzword. We can’t seem to agree on what it actaully means, so it ends up meaning nothing at all. Much like “cloud” or “dynamic” or “synergy”. You just wait for the right time in a meeting to drop it, walk to the board and draw a Venn Diagram, and then just sit back and wait for your well-deserved promotion.
That’s very true, and I do not like the term “serverless” for the rather obvious reason that it’s all about servers (someone else’s servers, that is). But these three principles are handy for figuring out if you’re building with in a serverlessy kind of way:
- You have no knowledge of the underlying system where your code runs.
- Scaling is an intrinsic attribute of the technology; so much so that it just happens automatically.
- You only pay for what you use.
Abstraction; scale; consumption.
Selectors Explained
I can see this coming in very handy at Codebar—pop any CSS selector in here and get a plain English explanation of what it’s doing.
Calling for a More-Than-Human Politics - Anab Jain - Medium
It may be the end of the world as we know it, but other worlds are possible.
“Let us Calculate!”: Leibniz, Llull, and the Computational Imagination – The Public Domain Review
The characteristica universalis and the calculus racionator of Leibniz.
Standards for Writing Accessibly – A List Apart
- Write Chronologically, Not Spatially
- Write Left to Right, Top to Bottom
- Don’t Use Colors and Icons Alone
- Describe the Action, Not the Behavior