~/ domain/francisfuzz.com.mdTHE AGENT-READABLE WEB

francisfuzz.com valid

Francis Batac

Senior Software Engineer at GitHub on the New User Experience team. I work on onboarding, engagement, and retention for millions of developers. I write about engineering craft, code review culture, psychological safety, and lessons from the field.

Visit publisher ↗
Authority
45 reach 0 · trust 5 · quality 25 · freshness 15
Tier
listed
llms.txt
https://francisfuzz.com/llms.txt
llms-full.txt
https://francisfuzz.com/llms-full.txt
Sections
3
Links
16
Size
3275 bytes
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-25T23:28:38.063Z
Last checked
2026-10-25T23:28:38.849Z
Badge
Agent Web Map badge for francisfuzz.com

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T23:28:38.067Z. Cached copy · Source on francisfuzz.com

# Francis Batac

> Senior Software Engineer at GitHub on the New User Experience team. I work on onboarding, engagement, and retention for millions of developers. I write about engineering craft, code review culture, psychological safety, and lessons from the field.

## About

- [About](https://francisfuzz.com/): Who I am, my role at GitHub, and my professional background
- [Résumé](https://francisfuzz.com/resume/): Full work history from GitHub (2015–present), partner engineering, program management, and earlier software roles. B.S. Mathematics, Pepperdine University.
- [Gear](https://francisfuzz.com/gear/): Software, audio/video, and desk setup I rely on daily

## Posts


- [Write, execute, read](https://francisfuzz.com/posts/2026/05/04/write-execute-read/): A mental shift: write and execute immediately after reading, then let the output become a portable, reusable artifact for future work.

- [Five learnings from Claude Code San Diego](https://francisfuzz.com/posts/2026/04/14/10-learnings-from-claude-code-san-diego/): Five takeaways from Claude Code San Diego: domain expertise, collapsing the gap between understanding and building, and keeping your agentic setup lean.

- [Building a second brain](https://francisfuzz.com/posts/2026/04/06/building-a-second-brain/): Extending my contexts using Git + agents — and what the log reveals that I never intended to show

- [Building tariff-everywhere: One Dataset, Many Interfaces](https://francisfuzz.com/posts/2026/03/26/tariff-everywhere/): How I turned a public API into a CLI, MCP server, and searchable web interface—iteratively, with Claude as a thinking partner

- [10 Lessons from a Decade at GitHub](https://francisfuzz.com/posts/2025/12/27/a-decade-at-github/): Ten years across support engineering, program management, partner engineering, and product engineering—lessons on asking great questions, mentorship, technical spikes, and building with AI agents

- [Relearning Rust Through Play by building emoji_gen with Claude Code](https://francisfuzz.com/posts/2025/12/27/relearning-rust-through-play-weekend-building-with-claude-code/): What happens when you combine Rust, Claude Code, and free weekend hours? I built Emojigen and rediscovered the joy of coding without deadlines while learning about AI-assisted workflows.

- [How @francisfuzz approaches code review](https://francisfuzz.com/posts/2025/06/02/how-i-approach-code-review/): Supercharging shipping confidence

- [Web Summit Lisbon 2023](https://francisfuzz.com/posts/2023/11/21/web-summit-lisbon-2023/): Pro pitching tips, the microbiome's role in evolution, and what it takes to be a tech leader

- [Building Psychological Safety In Code Reviews](https://francisfuzz.com/posts/2023/07/21/building-psychological-safety-in-code-reviews/): What would code reviews look like if teams prioritized this?

- [Shipping small](https://francisfuzz.com/posts/2023/04/06/shipping-small-potent-pull-requests/): Potent Pull Requests

- [Seeking Clarity Without Being A Je
…

Machine-readable: GET /v1/resolve?q=francisfuzz.com · GET /v1/domain/francisfuzz.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 francisfuzz.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.

Verify your website—free

Preview the owner dashboard · All verification benefits

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 francisfuzz.com:
1. POST https://agentwebmap.com/v1/sites/francisfuzz.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://francisfuzz.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/francisfuzz.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/francisfuzz.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact