WebTech1223411 logo WebTech1223411Web tech, read closely

About

About WebTech1223411

What WebTech1223411 is for, who writes it, how claims are checked, and where to write when we get something wrong.

Start here

This is a blog and nothing more complicated than that. Nothing is deleted once it is up, so the archive is the full record, written to the standard of the line under the logo, Web tech, read closely.

WebTech1223411 started as a private notebook. Somebody kept a record of what was worth the money and what was noise, and after a few years that notebook was more useful than most of what was published online.

How an article gets made

We write from notes taken while doing the thing, not from a summary of other summaries. Where we are unsure, the page says so in plain words.

Nobody has editorial input except the people whose names are on the articles. That includes anyone who has ever sent us money.

The full process, including corrections and commercial links, is set out on the editorial policy page.

What we cover

  • Front-End. CSS, layout and JavaScript on the user's side of the screen, written for people who ship it.
  • Back-End. APIs, servers and data, and the decisions that decide whether a service holds up under load.
  • Browsers. How pages are fetched, parsed and painted, and why that order matters to everything you build.
  • Dev Tools. Debuggers, profilers and the small workflow habits that save developers whole afternoons.
  • Accessibility. Building for keyboards, screen readers and tired eyes, because that is everyone eventually.
  • Games. Online games and the web technology underneath them, from browser rendering to servers and netcode.

Nothing gets filed under three headings at once. If a piece does not have an obvious home, that usually means it has not been thought through yet. The busiest sections are front-end, back-end and browsers.

Why this name

People ask about the name. There is rarely a good story behind a domain, and there is not one here either. WebTech1223411 was available, it was short enough to say out loud, and it has been the name long enough now that changing it would be more confusing than keeping it.

Who writes here

Every article carries the name of the person who wrote it, and every name links to a page listing everything else they have written.

Lorenzo Vidal, Front-end lead. Lorenzo started as a visual designer and moved into CSS after watching too many of his layouts fall apart on phones. He writes about front-end craft, interfaces and accessibility, and still tests everything with the keyboard first.

Kofi Oosterhuis, Back-end and infrastructure writer. Kofi spent years keeping APIs and game servers alive through traffic spikes and the occasional bad deploy. He covers back-end design, scaling and networking, with a preference for boring systems that do not page anyone at night.

Maren Castellanos, Browsers and tooling editor. Maren worked in cross-browser QA before editing, and knows the DevTools Network tab better than most people know their inbox. She writes about how browsers load and render pages and about the tools that show what is really happening.

How this is paid for

The site pays for itself through a small number of outbound links. It has never been enough to change what gets written, and the day it is, we will say so here.

The limits of this site

What we do not do is predict outcomes. Nothing about front-end, back-end, browsers, dev tools and accessibility works that way, and pages that pretend otherwise are selling something.

Telling us we are wrong

Point at the sentence. Write to [email protected] or use the contact page. Factual errors are fixed quickly, and when a correction changes the conclusion of a piece we say so at the foot of the page rather than editing quietly.