Work
ProjectsCase studies, shipped work, and prototypes.Open SourceGitHub, npm, PyPI, and public packages.Hackathons & CompetitionsHackathons, contests, and rapid-build work.Depth
JourneyCareer timeline, roles, and education.AchievementsScholarships, rankings, and milestones.Courses & CertificationsStructured learning, courses, and credentials.SkillsTechnical capability map.This website · 02
Browse this website posts across architecture, delivery, product systems, and the public writing footprint connected to this site.
Zero-downtime deploys on a cheap VPS
Field notes
485 published articles. Essays written here open in place; older tutorials take you back to the site where they first appeared.
Google's AI Overviews don't use special ranking factors. They pull from pages Google already ranks—and there's no hidden optimization beyond solid fundamentals.
CareerThis is not an argument that craft doesn't matter. It's an argument that craft is an input, and that engineers routinely present inputs as though they were outcomes — then conclude the business doesn't value quality when it declines to fund one.
ArticleGSO and GEO are often used interchangeably, but they mark different strategic priorities. One targets search engines; the other targets all generative systems.
ArticleGoogle's AI Overviews don't use special ranking factors. They pull from pages Google already ranks—and there's no hidden optimization beyond solid fundamentals.
ArticleSearch rankings alone don't drive results. SXO combines SEO with UX signals—Core Web Vitals, engagement, task completion—to build experiences search engines and users actually reward.
ArticleThree leading AI engines use fundamentally different retrieval pipelines to decide which sources earn a citation. Here's how each one actually works.
Tutorialllms.txt won't boost your SEO or make AI search engines cite you more. But it's genuinely useful for coding agents. Here's the honest breakdown.
TutorialSchema markup isn't a citation driver—but it's still essential hygiene. Here's what structured data actually does for AI search.
TutorialHow to structure paragraphs, avoid pronoun chains, and use answer-first framing so your content remains coherent when LLMs extract isolated passages.
TutorialGPTBot, ClaudeBot, PerplexityBot, and a dozen others are already crawling your site. Here's what each one wants, and exactly how to allow, block, or rate-limit them in robots.txt.
ArticleSEO still drives 60% of organic traffic, but GEO is growing fast. Here's how to split your content budget between traditional search and generative engines in 2026.
ArticleNo tool can tell you exactly when Claude or ChatGPT cites your content. Here's what you can actually measure, what's vendor speculation, and why ground truth doesn't exist yet.
ArticleAI search visibility is real, but most vendors are selling you the wrong solution. Cut through the hype with evidence-based skepticism.
ArticleFAQ schema improves traditional search visibility. But do answer blocks and editorial briefs actually drive AI citations? What the data shows—and what remains unproven.
ArticleA practical guide to the technical SEO fundamentals that drive visibility in 2026—from Core Web Vitals to crawlability, backed by what Google actually rewards.
TutorialCore Web Vitals still matter for SEO, but INP replaced FID and Google's ranking weight shifted. What actually changed, what stayed the same, and what you should optimize for now.
TutorialInternal linking is the one SEO lever you fully control, and most sites still waste it. A practical framework for topic clusters, link-weight hierarchy, and anchor text that scales as content grows.
TutorialA practical 3-hour technical SEO audit framework using free tools. Identify crawl errors, Core Web Vitals issues, and indexability problems—no paid software required.
ArticleProgrammatic SEO can be worth millions or worthless spam. See what separates Zapier's 10M+ indexed pages from Google's spam crackdowns.
TutorialNot all schema markup triggers rich results. Learn which structured data types Google actually renders, eligibility requirements, and how to implement them correctly.
ArticleAs autonomous agents handle business workflows, who's liable when things go wrong? An engineering framework for thinking through accountability without the law degree.
Web DevSpeed directly impacts SEO rankings. Learn how Next.js Server Components, streaming, image optimization, and partial prerendering reduce Core Web Vitals and improve search visibility.
ArticleWhy do old blog posts fade from search results? Content decay isn't just theory—it's how Google signals freshness. Learn what triggers it and how to fix it.
Web DevAfter five years on a hybrid stack, I rebuilt farasat.me with Next.js 16 and Payload CMS 3. Here's why the modern approach to full-stack typesafety and content management actually matters.
CareerA 2004 trust-repair study found that apologizing works better than denying blame for one kind of violation, and worse for another. Most engineers explaining a delay pick the wrong one without realizing there was a choice.
CareerMost 'no' conversations fail for one of two reasons: the engineer says yes to avoid the conversation, or says no with nothing behind it. Neither is a negotiation. A framework from Harvard's Program on Negotiation, and 52% of projects that report scope creep, explain why.
Web DevNext.js App Router defaults to server components. Learn when to stay server-side, when to cross the "use client" boundary, and how to architect high-performance apps.
Web DevThree dominant headless CMSs offer fundamentally different models. Payload emphasizes total control, Strapi balances flexibility with ease, Sanity prioritizes real-time collaboration. Here's how to choose.
Cloud / DevOpsTurning on the orange cloud doesn't hide anything by itself. It hides your origin only if you also make the origin refuse to talk to anyone who isn't Cloudflare — and there are at least four ordinary ways your real IP gets out anyway if you skip that part.
CareerThe most-cited scoping statistic in software — a 16% project success rate — comes from a 1994 survey whose own authors' later critics called the definitions misleading. The number is shaky. The reason scoping fails anyway is not.
Web DevMost design systems collapse the first time they encounter a real product. Here's how to build one resilient enough to scale without calcifying.
A working notebook
“Some ideas belong here because they connect directly to projects and services.
Older tutorials still live on Medium, where people first found them. This page keeps the trail intact without pretending everything was published in one place.
How I choose a topic
I would rather publish one useful explanation from lived work than five summaries of things everyone already knows.
Step 01
A topic usually starts as the second or third time the same engineering, product, hiring, or research question lands on my desk.
Step 02
I look for a shipped system, a measured result, a failed approach, or a public artifact that keeps the argument honest.
Step 03
Most technical choices touch something else. The useful links are the ones that help a reader follow that chain without opening fifteen tabs.
Step 04
Some pieces belong on this site; others already have a life elsewhere. I keep the original destination and publishing history intact.
Topics covered
The recurring technical and strategic themes represented across this archive.
A quick orientation
The practical details behind this mixed archive.
Those pieces were published there first. I would rather send you to the original article—with its date, responses, and history—than create a duplicate here.
Thirty-five posts are enough to become noisy. The filters separate original essays from outside tutorials, and permanent page links make it easier to pick up where you left off.
Usually. The essays here tend to connect a technical decision to the project, service, or research context behind it. External posts are often narrower, practical guides.
Please do. Real questions are where the best pieces start. Send the context, what you have already tried, and the part that still feels unclear.
Next step
You do not need a polished brief. A bottleneck, an uncertain architecture decision, or a product idea that refuses to become concrete is enough to start.