Go schema-first and skeleton loading stops being a problem
The skeleton loading problem is a contract problem in disguise; explicit content schemas dissolve it.
I ship systems that deliver impact. I understand technology and human organizational dynamics equally — and how to make them work together. Twenty years with UN agencies, international science, and media have sharpened that.
The skeleton loading problem is a contract problem in disguise; explicit content schemas dissolve it.

AI has general knowledge of the universe, not yours. The engineers who get results were always doing context work.
Software engineering is splitting into tiers, and in every tier the remaining human work is holding context.
AI-generated code is outpacing human understanding — and teams need to self-govern before someone else does.

The technology works, the design looks good, but content can't get to the reader — because nobody agreed on what a card is.
The static site generator I've backed for years just got its future sorted.
Benj Edwards burned through 50 projects in two months with AI coding agents and I know the feeling.

Every post needs a hero image. Sometimes you don't need the perfect one — you just need something that doesn't clash.

Vector embeddings at build time, cosine similarity in the browser. The same 23 MB model runs both sides.

No API keys, no external service — just a build step and one HTML attribute.
Open to strategic opportunities — let’s connect.
Printed direct from AllAboutKen.com