<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Abdelhalim Yahya</title>
    <description>The latest articles on DEV Community by Abdelhalim Yahya (@abdelhalim9).</description>
    <link>https://dev.to/abdelhalim9</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4040885%2F5204a7f6-228d-4964-8d73-470bdee0576c.png</url>
      <title>DEV Community: Abdelhalim Yahya</title>
      <link>https://dev.to/abdelhalim9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abdelhalim9"/>
    <language>en</language>
    <item>
      <title>I built the performance engineering resource I wished existed - full stack, real code, 6 levels, no fluff</title>
      <dc:creator>Abdelhalim Yahya</dc:creator>
      <pubDate>Wed, 22 Jul 2026 00:37:00 +0000</pubDate>
      <link>https://dev.to/abdelhalim9/i-built-the-performance-engineering-resource-i-wished-existed-full-stack-real-code-6-levels-no-2nhh</link>
      <guid>https://dev.to/abdelhalim9/i-built-the-performance-engineering-resource-i-wished-existed-full-stack-real-code-6-levels-no-2nhh</guid>
      <description>&lt;p&gt;alright let me be real with you for a second&lt;/p&gt;

&lt;p&gt;i've been building production systems for a few years now, mostly backend with node and nestjs, react and next on top, and the one thing that always drove me absolutely crazy was how performance content online just doesn't respect your time&lt;/p&gt;

&lt;p&gt;you google "how to optimize react rendering" and you get a medium article with 47 claps that shows you useMemo on a counter app&lt;/p&gt;

&lt;p&gt;you google "how to optimize node performance" and you get a 2019 blog post that tells you to use async await&lt;/p&gt;

&lt;p&gt;neither of them has real numbers, neither of them shows you how to actually FIND the problem before you start fixing things, and absolutely none of them connect the frontend and backend story together&lt;/p&gt;

&lt;p&gt;so i spent the last few months building it myself&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;what i built&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;it's called frontend-backend-performance-mastery and it's structured across 6 levels, each level has a frontend folder (react, next.js, typescript) and a backend folder (node, express, nestjs), and every single folder follows the exact same 3-file structure&lt;/p&gt;

&lt;p&gt;detect.md — how to find the problem, what to look for, what tools to use, before you even open devtools&lt;/p&gt;

&lt;p&gt;fix.md — the actual fix, with a before and after, when to apply it, and just as important when NOT to apply it&lt;/p&gt;

&lt;p&gt;project/ — a fully runnable code example, npm install and npm run dev and you're looking at real numbers on your screen, not a screenshot from someone's laptop from 2021&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;the 6 levels&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;level 01 — fundamentals: web vitals, profiling, baselines, benchmarking with clinic.js and autocannon&lt;br&gt;
level 02 — rendering: ssr vs csr vs ssg, react fiber internals, hydration, response streaming, fast-json-stringify&lt;br&gt;
level 03 — caching: react query, swr, service workers, redis, cache-aside pattern, cdn and http headers&lt;br&gt;
level 04 — database and api: n+1 queries, cursor pagination that stays fast at 10 million rows, dataloader, query optimization, indexes&lt;br&gt;
level 05 — advanced: wasm in next.js, worker threads, piscina, bull queue, grpc, node streams, code splitting that actually reduces bundle size&lt;br&gt;
level 06 — production: opentelemetry, prometheus, grafana dashboards, lighthouse ci in github actions, real user monitoring, distributed tracing&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;the philosophy behind it&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;one rule i followed building every single example:&lt;/p&gt;

&lt;p&gt;never fix what you haven't measured, never measure what you can't reproduce&lt;/p&gt;

&lt;p&gt;every fix in this repo comes with actual benchmark output, actual lighthouse scores, actual bundle sizes before and after — not "trust me bro this is faster"&lt;/p&gt;

&lt;p&gt;no pseudo code anywhere, if i wrote a typescript snippet it compiles, if i wrote a bash command it works, if i wrote a sql query it executes&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;who this is for&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;if you're a junior dev this might be a stretch, it's not a beginner resource and i'm not gonna pretend it is&lt;/p&gt;

&lt;p&gt;if you're mid level and you want to actually understand what's happening under the hood instead of just copy pasting stack overflow fixes, this is for you&lt;/p&gt;

&lt;p&gt;if you're senior and you want a structured reference or something to point your team at, this is also for you&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;the stack&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;react 18, next.js 14 app router, typescript 5, node 20, nestjs 10, postgresql, redis, opentelemetry, prometheus, grafana, clinic.js, autocannon, piscina, dataloader, bull, workbox — all the real stuff&lt;/p&gt;

&lt;p&gt;it's fully open source and free, no newsletter signup no course upsell no "buy the premium version", just the repo&lt;/p&gt;

&lt;p&gt;if you've been grinding to level up your perf engineering skills i genuinely hope this helps&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/AbdelhalimYahya/FulllStack-Performance-Mastery" rel="noopener noreferrer"&gt;https://github.com/AbdelhalimYahya/FulllStack-Performance-Mastery&lt;/a&gt;&lt;/p&gt;

</description>
      <category>node</category>
      <category>programming</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
