There’s a quote that says, &quot;An idiot admires complexity, a genius admires simplicity.&quot; If that’s the case, I am leaning fully into the “idiot” category. I’ve spent the last 4 months grinding on an ERP, and I’ve reached the point where TypeScript feels too easy and C++ feels like home. I’ve already moved my backend modules to C++ using <code>httplib</code> and <code>nlohmann/json</code>.
But yesterday, after a 20-hour shift and only 4 hours of sleep, I woke up and decided it wasn’t enough. I’m adding Assembly to the stack.
<h3>The Goal</h3>
I’m picking a core piece of logic or a heavy calculation and writing it in pure Assembly.
<ul>
<li>No WASM. _ No abstractions. _ Just registers and raw instructions.</li>
</ul>
<h3>The Motivation</h3>
<ol>
<li>The Challenge: I’m bored of predictable dev cycles. I want to break things.</li>
<li>The Aesthetic: Let’s be honest—seeing “Assembly” show up next to C++ and Vue on the GitHub language statistics bar is a massive flex.</li>
</ol>
It’s unnecessary, over-engineered, and probably stupid. But I’d rather be the “idiot” mastering the machine than the “genius” getting bored of the surface level.

Nour Eldeen Sayed Hamdy

A developer working on an ERP system shares their decision to add Assembly language to a backend stack already using C++, httplib, and nlohmann/json. Motivated by boredom with predictable development cycles and a desire for low-level mastery, they plan to rewrite core logic or heavy calculations in pure Assembly with no WASM or abstractions. The post is candid about the decision being unnecessary and over-engineered, framed as a personal challenge rather than a practical recommendation.

Adding Assembly to my Backend — Because I’m that "Idiot"