The following is a (slightly modified) chapter from Upgrade Your HTML, which is “all about picking examples of HTML in the wild, and explaining how to make that code better.”
The typical reason for why professionals don’t have their own websites is that they don’t want to make the commitment, and yet that misses how the disadvantages people see are actually advantages. Renewed thoughts on how running your own website is an asset.
Another year, another retrospective. Factoids and data on life and work.
Jad (Joubran) asked me about my configuration for html-minifier the other week, and in a hurry I pointed him to the config I had worked out for sum.cumo. In my own projects, however, I work with a different, more ambitious setup.
On the idea, the wish, the vision of us treating each other well.
Always open links in the same tab unless doing so 1) could disrupt a process, 2) could risk data loss, or 3) could confuse the user.
Leadership is important, and it can be learned.
Logical properties are great and long overdue. They are great because they solve an ugly problem of international, multi-directional web development in that directionality does not need to affect your writing and managing of CSS anymore…
Random improvements and notes around compression and caching, content security and feature policies, IndieWeb markup, protocols in links, entity references, image formats, and ISBNs in URL paths.
I’ve written a very short book on improving HTML code: Upgrade Your HTML. Upgrade Your HTML is about one thing: Picking examples of HTML in the wild, and explaining how to make that code better. Kindly. Constructively. Thoroughly, as finding a balance between detail and brevity permits.
As HTML is so important and yet also so easy, everyone writes HTML, and everyone says they can write HTML. And with that they don’t just mean they are able to write HTML, but that they write good HTML, where “good” means “high quality.” That would be great news.
Working closely with designers makes sense and is awesome, notably for mutual understanding and efficiency. And yet there are also good reasons not to work closely with designers. For developers it’s important, for otherwise foolish, to be aware.
Web developer, n.: A person who—
Optional HTML can be left out to improve performance, to guide code comprehension, and to hone the craft. An overview over all optional tags, rules around quotes for attribute values, and omissible attribute value defaults, as well as notes on pitfalls and tools.
In 2014, for idealistic transparency and enthusiastic link love, I’ve shared the feed sources I was following at the time. I’m still a huge believer in and user of feeds. As I also still like to be transparent I thought to share an update.
srcset and the whole family of ideas around it from the start because doing the same thing for the same purpose several times has usually looked like too much DX cost for too little UX gain to me. Two angles at what to use when.
We’ve all seen approaches to team management and leadership that work, and others that don’t. A brief and scrappy list of the mistakes I’ve witnessed (or committed), together with thoughts on how not to make them.
Setting up image compression tooling is easy—and for those who want to err on the safe side automatically employing lossless compression, it’s even easier with a solution from sum.cumo: Merlin.
Checklists are a great way to make sure nothing gets forgotten, yet they are problematic when they contain items that aren’t important. A few general thoughts and a very specific review of The Frontend Checklist—of which 33 guidelines appear useful, and 41 not (yet).
Ad blockers are popular. Yet, they’re also a problem. They’re a problem that can be broken into three sub-problems, sub-problems that speak not only against the use of ad blockers but argue against their very existence.
Image compression plays an important role for performance optimization. It seems straightforward but is a little deceptive, however, because it consists not of one but two parts—and it’s usually lack of understanding of one part that causes problems.
16×16, 30×30, 32×32, 48×48, 57×57, 60×60, 64×64, 70×70, 72×72, 76×76, 90×90, 96×96, 114×114, 120×120, 128×128, 144×144, 150×150, 152×152, 160×160, 167×167, 180×180, 192×192, 195×195, 196×196, 228×228, 256×256, 270×270, 310×310, 558×558.
The maintenance and maintainability of websites is a much neglected topic. This is problematic because: We cannot not maintain. Yet primarily we may deal with a visibility problem that we could explore more options for.
It may be rather clear that life is not all about being happy.
- Barker, Michelle
- Becker, Kraig
- bij de Weg, Henk
- Fung, Kaiser
- Heilmann, Christian
- Kadlec, Tim
- Keith, Jeremy
- Krugman, Paul
- Martin, Robert C.
- Meyer, Eric A.
- Ockerman, Stephanie
- Osmani, Addy
- Roselli, Adrian
- Schneier, Bruce
- Sterling, Bruce
- Verou, Lea
Perhaps my most interesting book: 100 Things I Learned as an Everyday Adventurer (2013). During my time in the States I started trying everything. Everything. Then I noticed that wasn’t only fun, it was also useful. Available at Amazon, Apple Books, Kobo, Google Play Books, and Leanpub.