Bilal Ben Aouad
HomeProjectsArticlesAboutContact
Execute.hire()

// FEATURED_DISPATCH

react

Why Your React Project Will Never Score 100 on Lighthouse If You Ignore Setup

Why React performance problems often start before feature work begins: bloated entry points, global layouts, bad routing, heavy dependencies, and project structure decisions that quietly damage Lighthouse scores.

BB
Bilal Ben AouadSoftware Engineer
Execute.read_more()→
Why Your React Project Will Never Score 100 on Lighthouse If You Ignore Setup
System.Runtime.status: active

FILTER_BY_TAG

>All Dispatches#algorithms#c#c++#concurrency#engineering#frontend#gamedev#graphics#internals#io-multiplexing#javascript#lighthouse#math#mutexes#networking#performance#processes#react#sockets#systems#threads#unix#web-performance
commitLatest Commit

docs: update Why Your React Project Will Never S...

commit: whyyour

2025-09-24

Recent Dispatches

TOTAL // 01 DISPATCHES

Threads, Mutexes, and the Anatomy of a Deadlock
7 min read#c

Threads, Mutexes, and the Anatomy of a Deadlock

2025-04-01

The Dining Philosophers problem is 60 years old and still the clearest demonstration of deadlock. Implementing it in C with POSIX threads forces you to understand data races, mutex internals, the four Coffman conditions, and why asymmetry breaks circular wait.

#c
#concurrency
#threads
#mutexes
#systems
Written by Bilal Ben Aouad

STDOUT >>

THE_RUNTIME_LOGS

Stay in sync with Bilal.

I regularly share technical insights, architectural deep-dives, and thoughts on the craft of software engineering.
connect on socials to keep the conversation going.

01_GITHUB
02_LINKEDIN
03_MEDIUM

System.Runtime.status: active

© 2026 Bilal Ben Aouad. Engineered for performance and long-term maintainability.

GitHubLinkedInMediumEmail

npm run build && npm run start