johnjwang.com valid
John Wang
Personal website of John Wang — co-founder / CTO of Assembled, previously an early engineer at Stripe. Writing about AI, engineering, and startups. Also co-created 143.dev, open-source coding-agent infrastructure.
- Authority
- 46 reach 5 · trust 5 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://johnjwang.com/llms.txt
- Sections
- 3
- Links
- 14
- Size
- 2844 bytes
- Popularity rank
- #794865
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T17:59:36.541Z
- Last checked
- 2026-10-26T02:26:11.517Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T02:26:05.919Z. Cached copy · Source on johnjwang.com
# John Wang
> Personal website of John Wang — co-founder / CTO of Assembled, previously an early engineer at Stripe. Writing about AI, engineering, and startups. Also co-created 143.dev, open-source coding-agent infrastructure.
John Wang is the co-founder and CTO of [Assembled](https://www.assembled.com), where he builds software that transforms customer support. He was an early engineer at Stripe (~employee 100), a co-founder and Chief Engineer at Zinc, and an active Ruby on Rails contributor (mostly ActiveRecord). He studied Computer Science at MIT. His writing focuses on AI systems, engineering craft and leadership, and practical lessons from scaling startups — aimed at engineers and technical executives.
## Blog
- [How Claude's watermarking (probably) works](https://johnjwang.com/post/2026/08/12/how-claude-watermarking-probably-works/): reverse-engineering Anthropic's Claude watermark from first principles — later confirmed correct by Anthropic's announcement that it uses SynthID-Text.
- [Cheap software won't make engineering cheap](https://johnjwang.com/post/2026/05/31/cheap-software-wont-make-engineering-cheap/): why engineers who know how to build quality systems become more valuable as AI writes more of the code.
- [Why we built 143](https://johnjwang.com/post/2026/06/30/why-we-built-143/): why Assembled built open-source coding-agent infrastructure so non-engineers can fix real product issues.
- [Number of tokens shouldn't be the only metric](https://johnjwang.com/post/2026/05/06/tokens-shouldnt-be-the-only-metric/): rethinking how we measure LLM output beyond token counts.
- [Why are executives enamored with AI but ICs aren't?](https://johnjwang.com/post/2026/03/27/why-are-executives-enabled-with-ai-but-ics-arent/): on the incentive and visibility gap between executives and ICs around AI adoption.
- [Time](https://johnjwang.com/post/2026/05/29/time/): reflections on time, compounding, and long-term building.
- [Mamba-3](https://johnjwang.com/post/2026/03/21/mamba-3/): an engineer's walkthrough of the Mamba-3 architecture.
- [Five opinions on building things well](https://johnjwang.com/post/2023/10/23/five-opinions-on-building-things-well/): what mortise-and-tenon joinery taught the author about building lasting software.
## Pages
- [Home](https://johnjwang.com/): bio, current work, and selected writing.
- [Blog archive](https://johnjwang.com/blog/): all posts, including external writing.
- [Work](https://johnjwang.com/work/): open source projects (143.dev, quickselect, Wallace), economics research, and Rails contributions.
## For machines
- Full-text RSS: [https://johnjwang.com/index.xml](https://johnjwang.com/index.xml)
- Every page is also available as markdown by appending `index.md` to its URL (e.g. [https://johnjwang.com/index.md](https://johnjwang.com/index.md)).
Machine-readable: GET /v1/resolve?q=johnjwang.com · GET /v1/domain/johnjwang.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage johnjwang.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for johnjwang.com:
1. POST https://agentwebmap.com/v1/sites/johnjwang.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://johnjwang.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/johnjwang.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/johnjwang.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.