DEV Community: Saad Salman

The domino effect: a short FAQ

Saad Salman — Thu, 01 Oct 2026 16:05:10 +0000

Every time I write about focus, it comes back to one image: a domino. Here's the whole idea as a set of questions, because that's how people actually ask about it.

What's the domino effect?

You knock over one domino and it knocks over the next, which knocks over the one after that. The push you spend is tiny. The distance the chain travels is not. Small cause, large result.

A domino can only knock over one its own size, though.

No, and this is the part that surprised me. In 1983 a physicist named Lorne Whitehead showed that a domino can topple another about one and a half times its size. So if you line up a row where each piece is 50% bigger than the last, every small domino still hands off to a bigger one.

So how big does it get?

Big, fast. Start at two inches and grow each domino by half. By Keller's telling in the book, the 18th domino is as tall as the Leaning Tower of Pisa. The 31st is taller than Everest. The 57th nearly reaches the moon. All of it set off by a push you could manage with one finger.

What does a physics demo have to do with my to-do list?

I used to treat progress like it needed a proportional shove: big result, big effort, so spread yourself across fifteen tasks and give each one a tap. Dominoes don't fall that way. They fall because someone lined them up and knocked over the first. The work is in the lining up and the first hit, not the shoving.

I have twenty priorities, not one.

You have twenty things you'd like done. One of them, done first, makes several of the others easier or pointless. That's your first domino. The other nineteen aren't equal; they just look equal sitting on a list.

Fine. I did my one thing today. Now what?

This is the part I missed for years. The domino effect doesn't only run inside a single chain, it runs across days. Today's one thing is domino #1. Because you did it, tomorrow's one thing is a little bigger and a little easier to reach. Do that, and the day after has a bigger domino still. One right thing, then the next, then the next: the same geometric math as the row above, played out on a calendar instead of a tabletop.

A single good day looks small. Thirty of them, each one setting up the next, is the 18th domino. You never feel the Tower of Pisa on a given morning. You feel one task that's slightly bigger than yesterday's. The size compounds while your attention stays on the next push.

Is this real, or just a tidy metaphor?

It's useful because it changes what you measure. Instead of "how much did I get through today," the question becomes "did I knock over the one that sets up tomorrow." Some days that takes twenty minutes. The compounding does the rest of the work.

Where do I start?

Tomorrow morning, before the list, ask one question: what's the one thing I can do today such that everything else becomes easier or unnecessary? Do that first, then do it again the next day. I wrote more about that question here.

Pick tomorrow's first domino tonight. Then keep knocking them over in order.

Winning your own name is an entity problem

Saad Salman — Tue, 01 Sep 2026 19:32:38 +0000

When I rebuilt this site, Google could already find me. The hard part was standing out from every other Saad Salman: a fabrics business, a film director, hundreds of namesakes. Winning your own name is an entity problem — ambiguity and authority, not discovery.

So I wrote down everything that worked: the on-site setup (titles, a JSON-LD entity graph, canonicals, sitemap), the off-site profile links that matter, and a free Google Search Console script that tracks your rank daily. Then I open-sourced it.

It's a Claude skill, MIT-licensed, works for people and companies, and drops straight into Claude Code: github.com/saadsalmankhan/entity-seo-skill.

Install it in one line

It's a Claude skill, so there's nothing to clone or configure. Open Claude Code and paste this into the chat:

Install this skill globally https://github.com/saadsalmankhan/entity-seo-skill

It'll pull down the playbook and the Search Console rank script, and walk you through the on-site and off-site steps for your own name or brand.

No black-hat tricks and no promises of position one. Just the legitimate playbook, and honest expectations about how long it takes.

Take it, fork it, open an issue: github.com/saadsalmankhan/entity-seo-skill.

I built a free API for Pakistani mutual fund NAVs (because MUFAP's own one doesn't work)

Saad Salman — Sun, 30 Aug 2026 11:02:52 +0000

Originally published on saadsalman.org in July 2026. Updated August 2026 with NAV history, fund metadata and a free public dataset.

Why MUFAP's own API doesn't work

I needed daily NAV data for Pakistani mutual funds for Gramafin, a personal finance app I'm building. MUFAP, the Mutual Funds Association of Pakistan, does have a JSON API. It just doesn't work for anyone who isn't a browser. I replicated Chrome's exact headers and parameters and still got 500 errors on every server-side request. My best guess is the frontend JavaScript establishes some session or anti-forgery state that isn't practical to replicate outside a real browser.

Their public Fund Directory page is a different story. It's a plain server-rendered HTML table with over 500 funds, current NAVs and prices sitting right in the markup. No auth, no pagination, no JavaScript required. So instead of fighting the broken API, I scrape the page that works.

To be fair, there is a paid option

CapitalStake sells a serious Pakistani mutual funds data product with AUMs, sector allocations, holdings history and uptime guarantees, delivered over REST, WebSocket, CSV and Excel. It's a commercial product with a "request a consultation" button, and if you're an organization that needs deep historical data and strict SLAs, that's probably where you should go.

But most developers just need today's NAVs as JSON without a sales call or a subscription. That's the gap this fills.

Turning it into its own thing

The scraper started as a piece of Gramafin's backend and grew into a standalone MIT-licensed project: pakistan-mutual-funds-api. If you're building anything fintech-adjacent in Pakistan, you've probably hit this exact wall, so I pulled it out into something you can clone and run in two minutes. No database to set up, no cloud account to configure, no framework to learn.

What it actually does

Three things:

Scrapes MUFAP's Fund Directory with cheerio, pulling each fund's name, AMC, NAV, offer price and category
Stores the result as plain JSON on disk, no Postgres or Redis required
Serves it from a small Express API at GET /api/funds, CORS wide open so you can call it straight from frontend code

By default it re-scrapes once a day and skips weekends, since MUFAP only publishes new NAVs on business days. Both are configurable through environment variables.

Try it

git clone https://github.com/saadsalmankhan/pakistan-mutual-funds-api.git
cd pakistan-mutual-funds-api
npm install
cp .env.example .env
npm run dev

The API is up at localhost:4000/api/funds, and the README covers every configuration option.

Update (August 2026): it's a dataset now, not just an API

Since publishing this, the project grew the pieces people kept asking for.

NAV history. Every scrape now appends each fund's NAV to a per-fund NDJSON file, so any instance builds its own time series from the day it starts running. New endpoint: GET /api/funds/:id/history?from=&to=.

Lookups and filters. GET /api/funds/:id for a single fund, plus ?category=, ?amc=, ?q= and ?shariah=true on the list endpoint, and /api/categories and /api/amcs for building dropdowns.

Shariah flags, benchmarks and expense ratios. Every fund now carries a shariah boolean (295 of 549 funds are Shariah-compliant, derived from MUFAP's own category names) and a benchmark mapping: KSE-100 for conventional equity categories, KMI-30 for Shariah equity, null where no single index honestly applies. A separate npm run enrich pulls each fund's total expense ratio, management fee and inception date from MUFAP's expense ratios table and merges them into the snapshot.

A public dataset that updates itself. If you don't want to run anything at all: pakistan-mutual-funds-data is a repo where a GitHub Action scrapes MUFAP every business day and commits the snapshot, the growing NAV history and the fund metadata. You can curl the raw files and be done, and the commit log doubles as an audit trail of every data change.

Why this matters: a team building an AI mutual funds advisor wrote about their AWS hackathon project that no clean, structured, public dataset existed for Pakistani mutual funds, and they had to assemble 301,749 NAV rows by hand before they could build anything. That dataset now exists, it updates itself daily and it's free.

If you build something with it, I'd genuinely like to hear about it. I'm at saadsalman.org.

How I Built This Website With Claude Code

Saad Salman — Tue, 04 Aug 2026 09:14:04 +0000

This entire website — the pages you're clicking through, the illustrations, the CMS this post was published from, even the favicon in your browser tab — was built through a conversation with Claude Code, Anthropic's AI coding agent. I didn't write the code. I described what I wanted, reviewed what came back, and steered. Here's how it went.

Start with a vibe, not a spec

My first message was one line: "keep a clean white look, take inspiration from Apple and how Claude designs." No wireframes, no tickets. Claude scaffolded a Next.js and Tailwind project, pulled my details from my resume PDF, and had a working site — hero, experience, resume download, analytics hooks — running in a live browser preview within minutes.

Borrow taste, then make it yours

I shared a portfolio site I liked and said "go creative." Claude drew an entire illustration language from scratch — hand-written SVGs of payment cards, tap-to-pay phones, currency coins, and funnels, each with flat color blocks offset behind ink outlines. That language now runs through everything: the hero, the section tiles, the case-study artwork, the S-coin favicon in the browser tab, and even my LinkedIn banner.

Restructure without fear

The first draft was one long page, and honestly, it was boring. So we split it: a minimal home, then About, Experience, Blog, and Case Studies as their own pages. Copy got trimmed, gradients came in, my photo got a cleaner background and an animated frame. Big refactors are cheap when your pair programmer holds the whole codebase in its head — and checks every change in a real browser, on desktop and mobile widths, before calling it done.

Give the site a brain

For publishing, Claude created a Sanity project on my account through its management API, defined schemas for blog posts and case studies, and embedded the editing studio directly into the site. Content goes live within a minute of hitting Publish — no redeploys, no code changes.

Ship it like you mean it

Every change was committed to GitHub and auto-deployed by Vercel. When I pointed my domain at the project, Claude attached it, told me exactly which DNS records to add, watched the records propagate, and set up the www redirect and SSL. Analytics counts visits, project clicks, and resume downloads; speed monitoring watches how fast the site feels for real visitors.

What I'd tell you if you're trying this

Talk in outcomes, not implementations. "How do we track clicks and downloads," plus a reference link, beats any detailed spec I could have written.
Ask for proof. Every change was verified in a live browser preview — screenshots at desktop and mobile widths — before I ever looked at it.
Iterate out loud. "The intro is too long and boring" and "we need to support rapid publishing of articles and case studies" are both perfectly good code reviews.
Keep one design language. When the site, favicon, banner, and blog art share a visual system, everything reads as intentional.

Total build: a few conversations spread across two days. Lines of code I wrote myself: zero. If you've been putting off building your personal site, the excuse pool just got a lot shallower.