Jens Oliver Meiert

“2019”

2019

Another year, another retrospective. Factoids and data on life and work.

#31 ¡

An HTML Optimizer’s Config for html-minifier

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.

#30 ¡ ¡ , , ,

On Codes of Conduct

On the idea, the wish, the vision of us treating each other well.

#29 ¡ ¡ ,

When to Open Links in a New Tab

Always open links in the same tab unless doing so could 1) disrupt a process, 2) risk data loss, or 3) confuse users.

#28 ¡ ¡ , ,

On Leadership

Leadership is important, and it can be learned.

#27 ¡

CSS: When to Use Logical Properties

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…

#26 ¡ ¡ ,

Website Optimization Measures, Part IX

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.

#25 ¡ ¡ ,

Cover: Upgrade Your HTML.

Upgrade Your HTML (the Booklet)

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.

#24 ¡ ¡ , , , ,

On Writing Better Markup

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.

#23 ¡ ¡ , ,

The Developer’s Fallacy of Close Collaboration With Designers

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.

#22 ¡ ¡ ,

Definition of Web Developer

Web developer, n.: A person who—

#21 ¡

“Must Work Without JavaScript”

That websites should work without JavaScript has a long professional tradition, and for apps much the same has been asked for. Yet with the success and ubiquity of scripting, how relevant is it to make sure sites and apps “work without JavaScript”?

#20 ¡ ¡ ,

Optional HTML: Everything You Need to Know

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.

#19 ¡ ¡ , ,

Sources 2019

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.

#18 ¡

When to Use “img,” “img@srcset,” and “picture” and “source”

I’ve disliked 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.

#17 ¡ ¡ ,

13 Leadership Mistakes and How to Avoid Them

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.

#16 ¡

Image Compression: How to Super-Easily Set Up Automated Base Optimization

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.

#15 ¡ ¡ , ,

The Problem With Web Development Checklists, or: The Frontend Checklist, Revised

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).

#14 ¡ ¡ , , ,

3 Reasons Against Ad Blockers

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 existence.

#13 ¡

Understanding Image Compression: Tooling and Context

Image compression plays an important role in 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.

#12 ¡ ¡ , ,

A Crime Called Favicon

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.

#11 ¡

How Can We Make Website Maintenance Work More Visible?

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.

#10 ¡ ¡ ,

Counter the Happiness Assumption

It may be rather clear that life is not all about being happy.

#9 ¡

Cover: 199 Love Haiku.

199 Love Haiku (the Book)

In 2016, I wrote 1,000 short poems, haiku-style. I wrote those poems to challenge myself as a writer. I launched a website for the haiku and I shared the story. Today, I’ve published the 199 haiku that a few friends and I liked the most as a book.

#8 ¡ ¡ , ,

Print Styling, the 3 Basics

Many sites are not prepared for print, and yet our users print, and they save through print. Therefore: Have a print style sheet, and be it a negative one. Hide what’s not usable or useful. Always test, and tweak when you want better.

#7 ¡ ¡ , ,

Optional “@lang”

The lang attribute is one of HTML’s global attributes. If one doesn’t simply take it for granted, it begs a number of questions—and these suggest to drop W3C requirements around it, and to demand software to do the job.

#6 ¡ ¡ , ,

Highlights From “Free Thought and Official Propaganda” (Bertrand Russell)

“Our system of education turns young people out of the schools able to read, but for the most part unable to weigh evidence or to form an independent opinion.”

#5 ¡

What Happened on Google+, the Web Development Archives

Following a few philosophy posts to be archived, here are past entries related to web development. Nothing more, nothing less.

#4 ¡ ¡ , , ,

What Happened on Google+, the Philosophy Archives

Google+ is shutting down, pulling everything with it. I’ve used Google+. And although I’ve changed and would put a few things differently now, I decided to archive a few of the somewhat philosophical Google+ posts.

#3 ¡ ¡ ,

HTML and Performance: Leave Out Optional Tags and Quotes

As experts we should know what code is optional and leave it out, and our production systems should do a better job assisting us with that. After all the years of neglecting basic HTML optimization, let’s think about taking the next step and not ship optional HTML markup.

#2 ¡ ¡ , , ,

Google Lighthouse and PWA

A review of Lighthouse’s PWA audits and the PWA category as a whole. Just in time to see it be superseded by Lighthouse 4, the major update that solves some (unfortunately not all) of those issues.

#1 ¡