Use SVGs instead of icon fonts for the reasons explained in the articles.

Source of markup ghosts:

1. proprietary markup introduced by browser vendors
2. specs which didn*t see uptake like HTML3
3. use case specific markup on devices like WebTV or early smartphones

Some old tags:

• <audioscope> to display the sound over time. A demo https://www.youtube.com/watch?v=tM7YVhar2Dg
• <au> for authors
• <blackface> for double-weight boldface... in HTML 🤡
• <center> oh shit
• <font> and color attributes
• dingbat attribute to embed emojis, extended unicode entities, icon fonts and custom things. Now it is used as < for example and does not rely on the attribute anymore.
• <multicols> ....
• <person> in HTML 3, but it opens the door for so many other tags. Now instead we can rely on <a rel="author"> or with me

and more

How to ramp up quickly?

The first step is to find someone on the team and ask for 30 minutes with them. In that meeting you have a simple agenda:

• For the first 25 minutes: ask them to tell you everything they think you should know. Take copious notes. Only stop them to ask about things you don’t understand. Always stop them to ask about things you don’t understand.
• For the next 3 minutes: ask about the biggest challenges the team has right now.
• In the final 2 minutes: ask who else you should talk to. Write down every name they give you.

Repeat the above process for every name you're given. Don’t stop until there are no new names.

system-ui is a good typography because it falls back on the system font (that is readable). It means 0 bandwidth cost.

They're nice and useful tools :)

They can be extended to browser extensions if they need to.

It can be a meme: instead of talking about semantics, UX is trendy and can be used as trendy shit word instead.
UX HTML is more accessible, less error-prone, more maintainable because it uses the right tags and attributes. Yes it is semantic at the end.
So UX of HTML matters.

With the latest changes in MacOS, we can now build Progressive Web Apps for all devices.

The web of things is built on the web of documents, which is built on the web of computers controlled by Domain Name owners, which itself is build on a set of interconnected cables. This is an architecture which provides a social backing to the names for things. It allows people to find out the social aspects of the things they are dealing with, such as provenance, trust, persistence, licensing and appropriate use as well as the raw data. It allows people to figure out what has gone wrong when things don't work, by making the responsibility clear.

The value of this architecture is that each layer leverages the social components of the lower layer's architecture

• Universality
• Open Standards
• Open Web Platform (OWP)
• Open Government through Open Data
• Openness with personal data on the Social Net
• Open Platform
• Open Source
• Open Access
• Open Internet and Net Neutrality

Too many websites could generate nice reports as documents, but had no way to access the data behind it to check and build on the results.

Hypertext systems should take about 1/4 second to move from one place to another. If the delay is longer, people may be distracted; if the delay is much longer, people will stop using the system. If the delay is much shorter, people may not realize that the display has changed.

It is funny how thoughts about speed and user experience were already there before the 2000's.

Issue: Links on the web are often quite slow

One solution is to abandon hypertext links. [...] Have a one-page view.

Another strategy is to exchange one large delay for many small ones. We can sometimes arrange a Web site to to bundle large parts of the data in a package that is pre-loaded at the entrance. Within the site, link response is quick because time-consuming sound, graphic, video, and applets have been pre-loaded onto the user's computer.

A better solution, for sophisticated hypertexts that must provide crisp performance, may be to use the Web as a way to provide access to, and information about, hypertexts that can be downloaded (or purchased) as a unit and then performed on the user's machine.

Exactly.

Law 1: Utility Classes Consume the Design System, They Don’t Create It
Law 2: Utility Classes Cover Only the Low-Hanging Fruit
Law 3: Utility Classes Complement, not Supplant, Semantic CSS

Let's take a look at how to spin up a simple Node server and use custom elements as templates in three popular formats

As always it depends of the need.

Signal has open-sourced a SQLite extension that provides better support for non-latin languages (Chinese, Japanese, etc) in the Full-Text Search (FTS) virtual table.

We pile up things to read later that we

Here's the funny thing: In trying to learn everything, we learn very little. We stuff ourselves with information but don't digest it. It's a sign of our times – we want to know more but feel empty.

But at the same time, each saved item is a reminder of our finite nature in contrast to the infinity of knowledge available.

It is a planning fallacy: we overestimate our future time and resources. A way to solve lies is by aligning our aspirations with our actions. [...] "we need to cultivate a habit of selective engagement, where we consciously choose what to consume based on its relevance and value to our personal and professional growth, creating space for thoughtful engagement with content that truly matters rather than mindlessly accumulating information."

Principles:

1. Know what motivates you
2. Not everybody needs to (or wants to) progress
3. The way up (or sideways. Or backward.): all roles are relative

The levels of experience in a company, range from Engineer I to III, then Senior engineers (and there are a variety of it).

Other potential sideways steps: Developer relations, Sales engineering, or specialist consultancy roles.

Two types of anxiety: the one that fills you with terror and the other one that tends to rush you.

A solution is framing: how to look at the situation.
A framework proposes to frame a presentation or an oral intervention with the following scale:

• Practicing / Perfection
• Enthusiasm / Audience
• Prepared / Flawless
• One of many / The big one
• Sharing Enthusiasm / Giving a presentation

The right side of this scale is what people normally imagine when they hear public speaking. It is however the wrong framing.

The positive frame would move to the left side of the spectrum. It is just practice, being enthusiastic, only preparation is needed, this is one of many public speaking so get ready for the next one too.

The trick is to switch the focus from yourself and the audience to the ideas in the talk.

The reason it doesn’t matter is because the audience is not the point. And you aren’t the point either. It’s the content. It’s the idea.