Abdul Salam

Engineering systems that scale — beautifully.

I design and build reliable software, elegant interfaces, and business-ready platforms. From architecture to execution, with taste and discipline.

Scalable SystemsReliable ArchitectureElegant InterfacesBusiness-Ready Platforms
Scroll ↓
ABOUT

I think in systems, not features.

Most problems aren’t technical — they’re structural. I design software by understanding how decisions, constraints, and people interact over time.

Backend ArchitectureSystem DesignCloud & InfraDeveloper ExperienceProduct Thinking
Primary instinct
Understand the problem first
Default approach
Design before code
Quality bar
Production-grade only
Engineering Judgment

Knowing when to optimize, when to simplify, and when to leave things alone.

Execution Discipline

Shipping clean, observable, and maintainable systems — not half-solutions.

Long-Term Thinking

I build software that survives growth, change, and real-world usage.

Design-minded engineering. Product-first thinking.
SKILLS

Skill Constellation

A path, not a grid. Hover a star to see the signal.

GolangJavaScript / TypeScriptJavaPHPSQL / NoSQLRustPythonC / C++RubyKotlinElixirC#Solidity
Hover / tap a star
SELECTED STAR
Golang
Expert
Golang is my default for backend services.

I mainly use Go when building APIs and internal services that must stay fast, predictable, and easy to reason about under load. Goroutines and explicit concurrency help me control latency instead of guessing it.

  • Consistent response times under traffic
  • Simpler services → easier maintenance
  • Lower operational overhead in production
MicroservicesLatencyConcurrency
Source: Abdul Salam's “EXPERTISE”.
PORTFOLIO

Artifacts from my universe

Not a grid — a flight path. Systems I’ve shipped, scaled, and made cheaper to run.

FLIGHT PATH
STAR SYSTEM

MMS — Procurement & Accounting Platform

Event-driven PR → PO → GR → Invoice → payment terms, built for real operations.

IMPACT
  • Designed idempotent events + sync patterns to keep procurement flows consistent under retries
  • Modular boundaries (validation/service/controller/routes) to keep velocity high without spaghetti
  • Instrumentation-first (latency + traces + logs) so performance work is measurable
STACK
TypeScriptBunHonoPrismaPostgreSQLRabbitMQNetdata
CONTACT

Open a wormhole to my inbox

If you’ve read this far, we’re basically friends. Drop a message—I'll respond faster than a build pipeline that *actually* caches.

SIGNAL CONSOLE
ONLINE
TRANSMISSION TEMPLATE
“Hi Abdul, I'm building ___. I need help with ___. Timeline: ___. Budget: ___.”
Bonus points if you include a link to specs. My brain loves specs.
Mode
Serious 👔 / Chaos 🪐
Response time
Fast (unless I’m in a merge conflict)
Preferred topic
Systems, Product, Performance
PS: If you send “hello”, I will reply with a meme and a roadmap.