Wednesday, October 7, 2026ArchiveSearchAsk the paper

The Computomatix Times

All the posts fit to save — curated from @computomatix's bookmarks & likes on X

Edition of Friday, May 8, 2026

3 stories

Thariq Makes the Case for HTML Over Markdown in Claude Code

Using Claude Code: The Unreasonable Effectiveness of HTML

Thariq of the Claude Code team argues HTML is a richer output format than markdown for agent-generated specs, plans and reviews, supporting tables, SVG, CSS and interactivity. He links to a gallery of examples and notes the Claude Code team increasingly uses the format.

Original post · 12 min read
X ArticleUsing Claude Code: The Unreasonable Effectiveness of HTML
This is now also on the Claude Blog.

Markdown has become the dominant file format used by agents to communicate with us. It’s simple, portable, has some rich text capability and is easy for you to edit. Claude has even gotten surprisingly good at using ASCII to make diagrams inside of markdown files.
But as agents have become more and more powerful, I have felt that markdown has become a restricting format. I find it difficult to read a markdown file of more than a hundred lines. I want richer visualizations, color and diagrams and I want to be able to share them easily.
I'm also increasingly not editing these files myself, but using them as specs, reference files, brainstorming outputs, etc. When I do make edits, I’m usually prompting Claude to edit them, which removes one of markdown’s largest benefits.
I’ve started preferring HTML as an output format instead of Markdown and increasingly see this being used by others on the Claude Code team, this is why.
(if you want to start with some examples, you can see a bunch here: thariqs.github.io/html-effectiveness, just be sure to come back and read more about why)
Why HTML?
Information Density

HTML can convey much richer information compared to markdown. It can of course do simple document structure like headers and formatting, but it can also represent all sorts of other information such as:
Tabular data using tables
Design data with CSS
Illustrations with SVG
Code snippets with script tags
Interactions using HTML elements with javascript + CSS
Workflows using SVG and HTML
Spatial data using absolute positions and canvases
Images using image tags
I would go so far as to say that there is almost no set of information that Claude can read that you cannot fairly efficiently represent with HTML. This makes it a highly efficient way for the model to communicate in-depth information to you and for you to review it.
I’ve found that in the absence of being able to do this, the model may do more inefficient things in markdown like ASCII diagrams or, my favorite, estimating colors with unicode characters like in this screenshot from Claude Code.

Visual Clarity & Ease of Reading

As Claude is able to do more complex work, it is also writing larger and larger specs and plans. In practice, I've found I tend to not actually read more than a 100-line markdown file, and I certainly am not able to get anyone else in my organization to read it.
But HTML documents are much easier to read, Claude can organize the structure visually to be ideal to navigate with tabs, illustrations, links, etc. It can even be mobile responsive so you can read it differently based on your form factor.
Ease of Sharing
Markdown files are fairly hard to share since most browsers do not render them natively well. You often have to add them as attachments to emails or messages.
With HTML, as long as you upload the file (for example to S3), you can share the link easily. Your colleagues can open it wherever they wish and easily reference it.
The chance of someone actually reading your spec, report or PR writeup is much much higher if it’s in HTML.
Two-way Interaction

HTML can allow you to interact with the document, for example you might want to ask it to add sliders or knobs to adjust a design or allow you to tweak different options in the algorithm to see what happens. You can also ask it to let you copy these changes into a prompt to paste back into Claude Code.

Read more about my playgrounds post to see examples of this two way interaction: x.com/trq212/status/2017024445244924382
Data Ingestion
Why use Claude Code to make HTML files instead of ClaudeAI or Claude Design for example? One of the biggest reasons is all the context Claude Code can ingest.

For example, when writing this article, I asked Claude Code to read through my code folder and find all the HTML files I’ve generated, group and categorize them and then make an HTML file with all diagrams representing each type. The diagrams you see in this article are a direct result of that.
Besides the file system, Claude Code can find additional context using your MCPs (like Slack, Linear, etc.), your web browser (with Claude in Chrome), your git history, etc.
It’s Joyful
Making HTML documents with Claude is just more fun and makes me feel more involved and invested in the creation, and that by itself is enough.
How to Get Started
I’m a little bit afraid that people will read this article and turn it into a /html skill or something. While there might be some value in that, I want to emphasize that you don’t need to do much to get Claude to do this. You can just ask it to “make a HTML file” or “make a HTML artifact”.
The trick is knowing what you want the artifact to do and how you might use it. You may over time make a skill, but for now I’d suggest just prompting from scratch to get a hang of how to use it in different cases.
Use Cases
To make this more concrete, I’ve made many different HTML files for different use cases… continue on X ↗
♥ 17.8K · ⟲ 2.3K · 👁 14.8MView on X ↗

Jaya Gupta Argues Company Institutions Will Be AI's Next Moat

Jaya Gupta argues that as AI products and technical advantages become easy to copy, the enduring moat is the organization itself, including how a company attracts talent, distributes authority and builds compounding systems. She cites OpenAI and Palantir as examples of organizational invention.

Original post · 12 min read
X ArticleThe next biggest moat in AI
It's pretty obvious to everyone that everything in AI is converging. Companies I couldn't have imagined competing with each other are today. The application layer is collapsing into infrastructure, infrastructure companies are moving up into workflows, and almost every startup is rebranding itself as some version of a transformation company. The words change every few months: context graph, system of action, organizational world model. A new category gets named, every website absorbs it, and within weeks the market is filled with companies claiming to be the inevitable platform for how work will change.
When models improve quickly, interfaces converge, and product velocity becomes cheap, the visible parts of company-building get easier to imitate. The harder thing to copy is the institution underneath: the way a company attracts exceptional people, organizes their ambition, concentrates judgment, distributes authority, and turns work into a compounding system no other company can reproduce.
The best companies have always known that people are not an input to the company, but rather are the company. But in AI, that truth becomes sharper because everything else is moving so fast. If products can be copied, categories can be renamed, and technical advantages can collapse in months, then the enduring question is what kind of organization you build around the people capable of building it.
The shape of the company itself is becoming the moat.
Great companies are organizational inventions
The most important companies are actually organizational inventions. They create a new kind of institution around a new kind of work, and in doing so, they make a new kind of person possible.
OpenAI did not look like academia, a corporate research lab, or a traditional software company. At its center was frontier model training as the organizing activity. Safety, policy, product, infrastructure, and deployment all orbited that gravitational center. The structure changed what kind of researcher could exist there: someone who wanted to operate at the edge of science, product, geopolitics, and civilizational risk at the same time.
Palantir invented a new kind of operating institution for broken systems. Forward deployment was not just a go-to-market motion. It was a status hierarchy, a talent model, and a worldview. The company took work that would have been low-status elsewhere, sitting with customers, absorbing institutional mess, translating politics into product and made it central. It created a protagonist who did not fit cleanly into software engineering, consulting, or policy, but could operate across all three.
None of these companies fit the boxes that existed before them. None of the people who built them did either. Great companies are not just places where talented people go. They are structures that let a certain kind of talent finally express themselves.
Shape determines who can exist there
The best companies in the world do not only compete on category, market, or compensation. They compete on identity. Ambitious people tend to value a few things intensely: feeling special, being close to power, becoming undeniable, staying full of optionality, belonging to a mission, being in the room where history bends but they often do not know which of these they are actually optimizing for yet. That is why the strongest institutions find people early and are recruiting at the most top tier universities when they are freshman. They reach them before their self-concept has hardened, before they know what they want to be famous for or what their values are, before they can distinguish between the work they are good at and the person they are trying to become.
A great company gives them a language for their own ambition. It says: the thing you have been circling around but have not known how to name can happen here. You can become the person who moved the Mars timeline, the person who was in the room when the frontier shifted, the person who could operate inside broken institutions, the person whose work became undeniable.
This is why great institutions are wrappers around a kind of person.
Many compete on cash, which is the least interesting form of talent competition for legendary companies (maybe Jane Street or Citadel though). Cash can close people, but it rarely converts them (ask some of the neolabs or Alex Wang). The best people are most loyal when the company can offer something more specific than money: a path to becoming the version of themselves they already wanted to be, or did not yet know they wanted to be.
Each emotional promise is also a structural promise. If the company says customer proximity matters but customer-facing work is low status, the promise is fake. If it says ownership matters but decision rights are centralized, the promise is fake. If it says mission matters but the mission offends no one, selects for no one, and costs nothing, the promise is fake.
So what do people want to feel?
People want to… continue on X ↗
♥ 5.7K · ⟲ 721 · 👁 4.5MView on X ↗

Michelle Maxwell Says Being a Grandma Beats Being a Mom

Michelle Maxwell Says Being a Grandma Beats Being a Mom▶

Michelle Maxwell shares a personal reflection that her mother was right that being a grandmother is better than being a mother, and asks followers whether they agree. The post is a short video with an emotional personal anecdote.

Original post · 1 min read
When my daughters were born I remember my Mom telling me how much better being a Grandma is than being a Mom. I remember feeling hurt. Now that I am a Grandma I understand how right she was and I wish I could tell her 💔 He nailed exactly why we feel this way!! Do you agree?
♥ 4.2K · ⟲ 571 · 👁 447.1KView on X ↗