Had

Portfolio · 2026

Live
IST--:--:--
@Haddharanesh3 repos1 followers

Dharaneshwaran B

Had/Full Stack · Discord · FiveM

I don’t just code — I build complete systems.

View workSource · GitHub
Had — Photo collage with acoustic guitar: Sound & Silence, Had 01
Sound & code · same eye for systems

01 — Identity

Facts, not fluff.

Legal name
Dharaneshwaran B
Goes by
Had
Role
Full Stack · Discord · FiveM
Based in
India
Time
IST · comfortable across EU / US async windows
Availability
Open to selective collaborations & retainers
GitHub
github.com/Haddharanesh

Narrative

I lead with full stack engineering — React / Next.js UIs, Node backends, APIs, databases, and delivery discipline. On top of that I build production Discord systems: bots, automation, moderation, ticketing, and community tooling with Discord.js and Discord.py (queues, persistence, gateway limits). I also ship FiveM work where it fits — ESX, QBCore, and QBOX Lua systems, tuning, and architecture.

Engagements

    Full stack apps & APIsDiscord bots & server automationStaff dashboards & internal toolsFiveM frameworks & optimization

02 — Work

Dossier-style case notes.

Representative builds — each row links to the public repository.
  1. 01

    Atlas admin console

    Next.js operations surface for staff — roles, queues, audit trails, and APIs with predictable failure modes.

    Next.jsReactTailwindNode.js
    Repository
  2. 02

    Nexus Discord mesh

    Event-driven bot architecture: shards, workers, embed builders, and permission models that stay sane as your guild grows.

    Discord.jsTypeScriptPostgreSQLRedis
    Repository
  3. 03

    Relay ticket & intake system

    Discord-native support flows: selective menus, transcript retention, SLA hooks, and bridge patterns to external tools.

    Discord.pyPythonFastAPISQLite
    Repository
  4. 04

    QBOX commerce layer

    FiveM-side economy flows when your community spans web, Discord, and the game — validation, caching, operator visibility.

    LuaQBOXMySQLRedis
    Repository

More on github.com/Haddharanesh

03 — Craft

How the work gets disciplined.

01

Traceability

Every change should answer “why” in logs, git, and runbooks — not tribal knowledge.

02

Bounded complexity

Clear boundaries for web modules, Discord commands and workers, and — when needed — game-server resources so nothing turns into spaghetti.

03

API-grade reliability

HTTP APIs, Discord REST constraints, and FiveM tick/DB paths all get the same discipline: limits, retries, and measurable outcomes.

Full stack

  • React / Next.js
  • Tailwind CSS & shadcn/ui
  • Node.js & APIs
  • PostgreSQL / MySQL / Redis

Discord

  • Discord.js / discord.py
  • Bot architecture & sharding
  • Embeds, components, permissions
  • Automation & community tooling

FiveM & assets

  • ESX / QBCore / QBOX
  • Lua systems
  • Server tuning
  • Blender / ZModeler3

04 — Lab

Interaction primitives

A compact bench for buttons, fields, and overlays — same tokens as the rest of the site, packaged for reuse.

Actions

Primary / outline / spectral CTA

Fields

Labels, focus, validation-ready inputs

Overlay

Modal shell for confirmations & wizards

05 — Contact

Send the messy details.

Repos, player counts, deadlines, budgets — specificity gets a useful reply faster than a vague “hey.”

Direct

Haddharanesh

Email can be shared here when you're ready to publish it.

Open to selective collaborations & retainers