Jens Oliver Meiert

Web Development × Engineering Management × Philosophy (12)

Articles and books on the craft of web development (with a focus on HTML/CSS optimization and maintainability), engineering management, and philosophy.

HTML/CSS Frameworks: Useful, Universal, Usable, Unobtrusive

A high quality HTML/CSS framework needs to have four attributes: useful, universal, usable, and unobtrusive. The four U’s.

#125 · · , , , ,

The 3 Ground Rules for Writing HTML

The fundamentals every web developer should know: on respecting syntax and semantics, avoiding presentational and behavioral markup, and leaving out everything that is not absolutely necessary.

#124 · · , , ,

Product of the Environment

Philosophy, live from Zurich airport.

#123 · ·

HTML, CSS, and Web Development Practices: Past, Present, and Future

Articles with a title consisting of more than 15,000 characters don’t need an introduction.

#122 · · , , ,

Website Optimization Measures, Part VII

In this episode: Unquoted attribute value syntax, q elements, Google Friend Connect, feed styling, work/life balance. Served in no time.

#121 · · ,

“HTML 5” or “HTML5”?

It’s “HTML5,” not “HTML 5,” declares the most recent post on the WHATWG blog. A seemingly trivial matter, yet it’s inconsistent.

#120 · · ,

The True Advantage of CSS

Despite CSS being around for a long, long time, there are still some myths around it. Reading Mike’s post on CSS evangelism again I couldn’t only relate to Mike’s concerns, I also felt reminded of…

#119 · · , ,

My Top 15 Android Apps

This is a serious post, not one of those “the 1,000 best blah” ones. I think. I’m an Android user for a bit longer than December 2008, and I love my HTC Magic as much as the HTC Dream (aka G1)…

#118 · ·

Diagnostic Styling Reloaded

Eric cultivated the concept of “diagnostic styling,” meaning using CSS to track down problems within HTML documents. I’ve been working with diagnostic style sheets for general quality assurance…

#117 · · , ,

WDR #3: Optional Tags, Unquoted Attribute Value Syntax

The Web Dev Report, issue #3.

#116 · · ,

Microformats, Key Flaws

I like the idea behind microformats, but I’m not convinced of the way that idea is brought to life. I see three major flaws that appear to make microformats stand in their own way.

#115 · · , ,

XHTML, RIP

Let’s end this week of morbid posts: The XHTML 2 Working Group is expected to stop their work end of 2009. “Today the Director announces that when the XHTML 2 Working Group charter expires as scheduled at the end of 2009…”

#114 · · ,

“handheld” Media Type, RIP?

Website authors don’t use handheld as it’s barely supported; mobile device manufacturers don’t support handheld because it’s barely used. This is kind of the situation I think we’re facing, and it’s a problem.

#113 · · ,

Let’s Make The Web Faster

Two weeks after my last outcry regarding slowness on the Web there’s a more proactive response: Google launched code.google.com/speed, subtitled “let’s make the Web faster.”

#112 · · , , ,

Maintainability Guide

Maintainability is important in order to deal with change. Good maintainability means making change easier and more affordable, and avoiding change that is not necessary…

#111 · · , , ,

Punctuation Cheat Sheet

Developing and working with international sites is an interesting challenge, not just because of right-to-left contents. Typographically, there are differences between many locales. To improve punctuation in Google translations I’m using a localization aid…

#110 · · ,

CSS: The Maintenance Issue #1 and How You Can Avoid It

The biggest—as most unnecessary—maintenance issue in web development is, as my recent research shows, style sheet naming and integration. Web developers use inadvisable style sheet names and inadvisable ways to integrate style sheets that force them…

#109 · · , , ,

The Result of Maturity Is Simplicity

“Finally, it doesn’t lack some irony considering that web design gets often enough protected by the credo ‘the end justifies the means’ and pragmatism’s paid homage to. The question is whether you’re talking about unhealthy, sanctimonious pragmatism or—”

#108 · ·

Notes on XML, Elements, and Attributes

Knowledge of the design of markup languages is something I consider beneficial for my job as a web professional. A few notes on XML design, inspired by internal and external documentation.

#107 · ·

Why CSS Needs No Variables

CSS variables and constants are one of the top features web developers are asking for in web development fora, magazines, blogs, and on W3C’s www-style. Following a concept written by Daniel Glazman and Apple’s Dave Hyatt, the WebKit rendering engine…

#106 · · ,

The Stupidest Style Sheet Name Ever

The last name you want to pick for your style sheet is “style.css”. Why is “style.css” such a poor CSS file name? The main reason is maintenance…

#105 · · ,

CSS: Style the Non-Obvious

One of the qualities you have to acquire as a web developer is to see the non-obvious, and to use that skill to your code’s advantage. Let me explain by two simple examples.

#104 · · ,

Presenting… the Google Shoe

They finally arrived, long longed for Google shoes, in this case the “Google j9t” model based on the Adidas ZX700. They’re not for sale but I might share the configuration I used to design them. The “Google j9t” may only be worn for dynamite fishing and important launches.

#103 · ·

Performance of CSS Selectors Is Irrelevant

…if you like to have a strict read of Steve Souders’ recent research. We’ve still got few but now a few more numbers backing up what we always suspected, that merely optimizing selectors is micro-optimization.

#102 · · , ,

Website Optimization Measures, Part VI

In this episode: On the utilization of Google Friend Connect, maintenance of Google Analytics, sanity checks, type attributes, charset rules, cite elements, and ICRA labels. Fresh and sexy.

#101 · · ,

When to Split Style Sheets

Three factors influence whether it makes sense to split style sheets: probability, meaning (aka semantics), and granularity.

#100 · · ,

Another Survey (Including Website Usability Scale Template)

I’m doing it again: Do you have another 15 seconds to answer a couple of questions? The survey is based on the System Usability Scale (SUS) John Brooke presented in the 80s. Which means nothing less than that there’s another experiment taking place with me testing SUS.

#99 · · ,

Performance and RFC 2396

RFC 2396 specifies that relative URIs like //foo get resolved as http://foo. This means, if you link a resource like https://example.com/, @ href may as well just point to //example.com/.

#98 · · ,

Arial, Helvetica

An extension of my post on Arial and Helvetica: For those who want or have to use Arial as their standard font, there is no point in mentioning Helvetica anywhere in the code, as in arial, helvetica, sans-serif.

#97 · · ,

The Two Great Things About Validation (and Conformance)

There are two great things about validation: Validating helps technical understanding and thus contributes to awareness of respective specifications, and writing valid code is a sign of professionalism.

#96 · · ,

Browser Support: The Two Metrics That Count

There are two things that matter to determine what user agents—browsers—to support on a given site: First, what popularity (percentage of market) makes a browser important to support? Second, what browsers pass that threshold?

#95 · ·

5 Cool Ways to Support the W3C

I recently got a mail by someone interested in supporting the World Wide Web Consortium (W3C) similar to how I do it. While replying I noticed that the information I was about to share might not be obvious to everyone, but still important…

#94 · ·

My Year in Cities, 2008

Following Anne; I couldn’t resist.

#93 · ·

HTML vs. XHTML: Why HTML Wins

Document types are cool, and there are plenty of them. There are plenty, countless discussions about the “right” document type, too. Alas, these discussions may deal with irrelevant details or miss the point.

#92 · · ,

5 Tips To Deal With Right-to-Left Projects

Know what goes into your markup and what goes into your style sheets. It’s actually simple: When available, you should always use dedicated bidi markup to describe your content. CSS may not be available, and the specs actually say that…

#91 · · ,

The Greatest Secret in Web Design

Alright I cheated, this isn’t a secret. Or an open secret. Or whatever. It’s that web design is a process. Good web design is an ongoing endeavor.

#90 · · , ,

WDR #2: Web Developers Needed for a Website

The Web Dev Report, issue #2, this time featuring a classic situation.

#89 · ·

How to Uncover Pseudo-Standardistas

There’s a growing group of developers that doesn’t help our attempts for faster, more accessible, more maintainable, and generally quality-oriented web development: pseudo-standardistas.

#88 · ·

WDR #1: Versioned Style Sheets

Ladies and gents, all I present’s… the Web Dev Report, issue #1.

#87 · · ,

5 CSS Tips Every Web Developer Should Know About

Of all the tips this site shares, the following ones may be special. Let’s quickly run through what might be essential for every web developer to know about CSS. Main focus: maintainability, though differently.

#86 · · , ,

Website Optimization Measures, Part V

Almost half a year since the last article it’s about time to present version 5 of random website optimization measures, hopefully of use for your site as well. Short and crispy, to use a random German expression.

#85 · · ,

Thoughts on Disclaimers

Disclaimers are popular in Germany, both for websites and emails. Recently I came across the German Wikipedia article on disclaimers which talks about the topic in detail, and I could not but go for another “thoughts” post…

#84 · ·

An Exercise for Emerging CSS Experts: Avoid IDs and Classes

To gain more expertise with CSS, there’s a great bonus level: Try to avoid IDs and classes altogether. That’s right: Write your markup without any IDs and classes.

#83 · · , ,

The Most Annoying Yet Most Important Task in Website Management

…is link checking. There are tools out there, en masse, but we still have to run after professionals who neglect online fundamentals or don’t set up redirects—and with that waste other people’s time.

#82 · ·

meiert.com Survey Results

It’s one and a half months since I asked for your feedback about meiert.com, and I’ve finally decided to publish some of the results.

#81 · ·

Code Responsibly

Exactly.

#80 · ·

Accessibility Heuristics

You can bolster your accessibility knowledge by internalizing heuristics and ground rules. Review the guidelines and rules provided by the W3C and IBM.

#79 · · ,

Web Standards at Google

As an exception, I’m writing as a Googler here: At Google, we care about web standards. Officially, that’s no news, but given repeated criticism for the code of our pages, maybe it is.

#78 · · ,

The Most Important Thing Is to Get the HTML Right

Why? Because it’s the markup that makes for most of the code of a site and is hence key to cost efficiency and maintainability; because it carries meaning and is important for accessibility; because it often has an impact on performance; and because it is the prerequisite for online success.

#77 · · , , , , ,

When Guidelines Should Be Descriptive or Prescriptive

Every time I’m putting up guidelines or conventions one of the decisions I need to make is whether the guidelines, or which parts of them, should be descriptive or prescriptive. For coding guidelines this could mean the difference between, say, “the markup should be valid” and “the markup must be valid”…

#76 · · , , ,