I’m a problem-driven software engineer who loves designing robust systems, scalable architectures, and real-world solutions — from web platforms to robotics middleware.

I care deeply about:

• Correctness
• Architecture
• Failure handling
• Long-term maintainability

I don’t just write code that works. I make sure they keep working under pressure. I design systems that survive, scale, and fail gracefully.

• 🏗️ System Architecture — designing fault-tolerant, modular, production-ready systems
• 🤖 Robotics & Middleware — assistive robots, intent engines, recovery systems
• 🔐 Security & Reliability — authentication, fault detection, secure logging
• 🌐 Full-Stack Engineering — from APIs to UI with clean separation of concerns
• 🧪 Research-Oriented Development — building with novelty, not copy-paste

• 🧠 A.L.T.R.U.S — Adaptive Life-support & Therapeutic Robotic Unit System

  A Baymax-inspired assistive robot with:

  • Intent-driven middleware
  • Fault detection & auto-recovery
  • Blockchain-backed immutable event logging
  • Developer CLI & monitoring tools

• 🧩 Middleware Engineering

  • Intent arbitration engines
  • Modular plugin systems
  • Event-driven architectures

• 🛡️ Cybersecurity Mastery Path

  • Deep CS fundamentals
  • Secure system design
  • Offensive & defensive security (long-term goal: GOAT level 🐐)

• JavaScript / TypeScript
• Python
• Java
• Bash / Shell
• Go
• Rust
• C++
• C#

• React
• Next.js
• Zustand
• TanStack
• Tailwind CSS

• Node.js
• REST APIs
• Django
• Fast API
• Nest.js
• Middleware-based architectures
• Authentication & session handling

• Linux (Ubuntu)
• Docker (working knowledge)
• CI/CD concepts
• CLI tool development

• ROS (learning & integration)
• LiDAR-based navigation concepts
• Modular robotic software design
• Fault-tolerant systems

• Software Engineering roles (Backend / Full-Stack / Systems)
• Research-driven engineering teams
• Startups solving hard technical problems
• Teams that value engineering depth over hype

I strongly believe in:

• Root-cause understanding over quick fixes
• Design first, code second
• Readable systems > clever hacks
• Documentation is part of engineering
• Failure handling is not optional

If a system fails silently — it’s broken.

Check my pinned repositories to see:

• Production-style frontend architecture
• Research-backed middleware systems
• CLI tools & developer utilities
• Clean codebases with real structure (not tutorial junk)

• 💼 1.5+ years professional experience

• 🧑‍💻 2.5+ years freelance & independent development

• 🛠️ Worked on:

  • Web platforms
  • Mobile apps
  • System tools
  • Robotics research projects
  • Open-source utilities

• 💼 Open to:

  • Software Engineering roles
  • Research collaborations
  • Startup & system design discussions

If you care about quality engineering, real systems, and thinking deeply — we’ll get along.

I’m on a long-term mission to become:

A world-class engineer with deep computer science + system-level thinking

No shortcuts. No hype. Just mastery.

Drop a star ⭐ on a repo — it genuinely helps and is appreciated.