I can see myself almost certainly needing to use this clever technique at some point so I’m going to squirrel it away now for future me.
If we were to follow Jiro’s and his apprentices’ journeys and imagine web development the same way then would we ask of our junior developers to spend the first year of their career only on HTML. No CSS. No JavaScript. No frameworks. Only HTML. Only once HTML has been mastered do we move onto CSS. And only once that has been mastered do we move onto JavaScript.
If you like the prospect of an old man ranting at clouds, this is for you.
Anselm isn’t talking about becoming a CSS wizard, but simply having an understanding of what CSS can do. I have had similar experiences to this:
In the past years I had various situations where TypeScript developers (they called themselves) approached me and asked whether I could help them out with CSS. I expected to solve a complex problem but for me — knowing CSS very well — it was always a simple, straightforward solution or code snippet.
Let’s face it, “full stack” usually means “JavaScript”—HTML and CSS aren’t considered worthy of consideration. Their loss.
Technology doesn’t have to be terrible. Here’s an absolutely wonderful use of an e-ink display:
I made as much use of vanilla HTML and CSS as possible. I used a small amount of JavaScript but no framework or other libraries.
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
You might want to use `display: contents` …maybe.
If you’re going to toggle the display of content with CSS, make sure the more complex selector does the hiding, not the showing.
Going back to school in Amsterdam.
Trying to understand a different mindset to mine.