Shayan Jamil | Building MVPs, SaaS & Apps

I build MVPs, SaaS, Mobile Apps & AI Integrations for founders. I write about shipping AI software that survives production. Top Rated Upwork · Level 2 Fiverr

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

https://t.co/Y2hbcRlz1s

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

Beyond the Demo #7

A user hits Checkout. To show shipping options, your backend calls a courier's rate API. It usually answers in 300ms. Today it takes 30 seconds.

Now checkout hangs for 30 seconds, and every checkout is holding a worker open waiting. The whole site slows down behind one slow dependency you don't even control.

A longer timeout feels like the fix. It's backwards. The longer you wait, the more requests pile up behind the slow call.

Three things fix it: a tight timeout so a slow call fails fast and frees the worker, a fallback like a flat shipping estimate so checkout still loads, and a circuit breaker (see image) that stops calling a dead service for a minute and serves the fallback instantly.

The shift for anything over the network: every external call can hang, not just fail. Design for slow, not only for down. Slow is what quietly takes the rest of your system with it.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@thdxr We spent years learning how to write perfect prompts... then discovered rambling works too.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@DanielGlejzner Sometimes GraphQL is architecture. Sometimes it’s just a prettier front door to the same mess.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@DThompsonDev In the next decade, “can you build it?” matters less than “should we build it?”

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@rauchg “You’re right, I was cargo-culting” is exactly why code review isn’t optional yet.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@patilvishi Authorization doesn’t mean “never cache.” It means “don’t assume this response is safe to share.”

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@forgebitz Turns out a little chaos was exactly what programming was missing 🥹

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@Akintola_steve Backend gets interesting when the database says one thing, the gateway says another, and the customer says a third.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@theo /goal build GitHub, constraint: it should work

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@DThompsonDev Skills get listed on resumes, solved problems create stories recruiters remember.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@mattpocockuk At this point /wait-what isn’t a skill... it’s a verbosity firewall.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@sflorimm VPN says “I’m in Germany.” Your timezone and browser say “bro, you’re not.”

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@peegzy1 Some people didn’t grow up fast... they just had no choice.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@Prathkum Once you get used to agentic coding, plain VS Code starts feeling weirdly manual.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@thdxr What happens when two generated sessions need to modify the same part of the codebase?

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@Simon_Ingari Taking your earned leave, the company will survive.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@Dearme2_ You can recover from failure... but not from never trying.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@mattpocockuk Basically a “catch me up before I break something” command.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

@forgebitz Your repository is part of the prompt, whether you realize it or not.

[Shayan Jamil | Building MVPs, SaaS & Apps @ShayanJ81846859]

Infinite feed bug:

User is reading page 2.

New posts arrive at the top.

They tap load more.

Now they see duplicate posts…
and miss one post completely.
Why?

Because offset pagination says:

“give me posts 20–40”

But the list moved.

New posts shifted everything.

The fix:

Use cursor pagination.

Instead of asking for a position, ask:

“give me posts after this exact post.”

Cursor should be stable, ordered, and unique.

created_at alone is not enough.

Use something like:

created_at + id

That’s how you avoid duplicate/missing posts in feeds.