Two Paradigms of Web Development
On a sunny Tuesday in Düsseldorf a few weeks back, at Beyond Tellerrand, I had a pleasant recorded conversation (in German) with the team of Working Draft. In our discussion we briefly touched on the idea of web development paradigms—I vaguely borrowed from Thomas Kuhn—when it comes to the ideas behind the maintenance and optimization of frontend code, particularly HTML.
I suggested that we were dealing with two paradigms, and two models of web development.
The first model, which can be called the traditional or conservative model, follows the idea that HTML should only be touched on structural changes, and that the vision are CSS-only refreshs and redesigns. In this model, separation of concerns is critical, and the quality of the markup the highest priority. (You usually find me squarely in this camp.)
The second model, which may be called the ubiquitous model (other names? please leave suggestions), reflects the idea that all changes are so easy—including HTML changes that have ceased to mean edits to huge collections of static files—that there are no fixed boundaries anymore around what to place particular emphasis or importance on: If anything we’ve become so efficiency-oriented that most now appears to be a matter of process and automation.
As I added on the Working Draft podcast, “paradigm” is somewhat of a misnomer in a sense that one is not currently superseding the other (Kuhn again), but they’ll likely stay with us to represent two different development realities. I personally believe in strict separation of concerns and to put most emphasis on quality HTML code (first model), yet the technological landscape has changed and one can find more taste not making such distinctions (second model).
The most important piece, however, is that we recognize and learn to work well with these paradigms, just as we’ve long been benefiting from differentiating between sites and apps, and research and production code. Like in other parts of life, answers in web development often start with “it depends,” too.
I’m Jens, and I’m an engineering lead and author. I’ve worked as a technical lead for Google, I’m close to W3C and WHATWG, and I write and review books for O’Reilly. I love trying things, sometimes including philosophy, art, and adventure. Here on meiert.com I share some of my views and experiences.
If you have a question or suggestion about what I write, please leave a comment (if available) or a message. Thank you!
Maybe this is interesting to you, too:
- Next: Highlights from Dewey’s “How We Think”
- Previous: The Great Web Maintainability Survey Results
- More under Web Development, or from 2017
- Most popular posts
Looking for a way to comment? Comments have been disabled, unfortunately.
Get a good look at web development? Try The Web Development Glossary (2020). With explanations and definitions for literally thousands of terms from Web Development and related fields, building on Wikipedia as well as the MDN Web Docs. Available at Apple Books, Kobo, Google Play Books, and Leanpub.