LDD

Full-stack · Desktop · AI/ML · 2nd yr CSE

LENNY DANYDEREK D.

I don't write the code, I ship the code.

View Work

8+ shipped products
1,331+ commits · solo

01 / ABOUT

Second-year CSE (AI & ML) at SRM IST. I build production systems end-to-end — backend, frontend, infra, release pipeline — alone.

Native Windows overlays in Rust/Tauri. HRMS platforms on Flutter with biometric attendance. Registration systems holding 1,800+ live users. Three internships, one freelance venture (Ascendry, Udyam-registered), and a habit tracker selling on Gumroad. The pattern is the same every time: pick the hard part, ship it, keep it running.

0+
PRODUCTS SHIPPED
0+
LIVE REGISTRATIONS
0
GITHUB COMMITS
0
CGPA / 10

02 / SELECTED WORK

Things that are
running right now.

01v0.6.x · WINDOWS

Crest

The dynamic notch, built for Windows. A Mica-glass panel pinned to the top of any screen — media, files, notes, system load.

50+ installer downloads, organic. Tag-triggered NSIS releases via GitHub Actions. Microsoft Store submission next.

  • Tauri 2
  • Rust
  • TypeScript
  • React
02SAAS · IN BUILD

Bloom

A Django + Next.js SaaS — typed API, multi-tenant data model, billing wired through Razorpay.

Placeholder copy — swap in the real one-liner and metrics.

  • Django
  • DRF
  • Next.js
  • Postgres
In build
03MOBILE · DESKTOP · WEB

NukePC HRMS

A 3-in-1 HR platform built solo: recruitment ATS, GPS-geofenced attendance, leave management.

ZKTeco F22 biometrics over TCP/pyzk. API-level RBAC, 5 roles × 8 resources. S3 storage, Brevo SMTP.

  • Flutter
  • FastAPI
  • AWS S3
  • pyzk
Internal build
04KIOSK · HOSPITAL

SIMS SmartAssist

A walk-in kiosk that lets patients register, book appointments and look up records without staff.

Wired into a hospital SOAP API. Designed for non-technical users: error-tolerant flows over feature density.

  • React
  • Django
  • SOAP API
0513 EVENTS · LIVE

NIC Platform

Registration platform for every event of SRM IST's Nextgen Intelligence Club fest. 1,800+ live registrations.

Redis rate limiting, client-side image compression, S3 storage, automated confirmations. Architected and maintained as Joint Head of Technical.

  • Next.js
  • Supabase
  • Upstash Redis
  • AWS S3
01 / 05Swipe →

03 / STACK

Whatever the
problem needs.

BACKEND / CLOUD
Django · DRF · FastAPI · Celery · PostgreSQL · AWS S3 · Upstash Redis
FRONTEND / MOBILE
React · Next.js · React Native · Flutter · Tauri
AI / ML
LangChain · Ollama · Whisper · RAG · ChromaDB
DEVOPS
Git · GitHub Actions · CI/CD · Docker · Vercel · Postman
INTEGRATIONS
Razorpay · Cashfree · Brevo · ElevenLabs · ZKTeco
LANGUAGES
Python · JavaScript / TypeScript · Dart · Rust · C / C++

04 / PROCESS

The same four moves, every time.

  1. 01

    Pick the hard part

    The interesting problem is usually the one nobody wants to own — biometrics over TCP, a native Windows overlay, rate limiting under real load. Start there, not at the scaffolding.

  2. 02

    Build it end to end

    Backend, frontend, infra, release pipeline. One person holding every layer means no handoffs, no waiting, and no part of the system nobody understands.

  3. 03

    Ship it

    Tagged releases, real installers, real users. A branch that never merges is not work — it is a hobby with extra steps.

  4. 04

    Keep it running

    Shipping starts the maintenance, it does not end the project. Eight products still up is the number that actually matters.