I’m a Software Engineering student and self-taught developer focused on building practical software — from Django and FastAPI backends to React interfaces, real-time systems, and AI-powered workflows.

I enjoy taking an idea from a rough concept, turning it into a structured system, and then working through the details that make it actually usable: authentication, APIs, database design, real-time communication, state management, responsive interfaces, and deployment.

Currently, I'm going deeper into AI agents, LLM integrations, MCP, and production-oriented backend architecture while continuing to build full-stack applications.

I’m most interested in software where the frontend, backend, data, and real-time behavior have to work together.

Building complete applications with:

• REST APIs and authentication
• Custom user systems and role-based access
• PostgreSQL / MySQL / SQLite data models
• React and Vite interfaces
• JWT-based authentication
• API integration and client-side state
• Responsive and mobile-first UI

I have worked with real-time application patterns using WebSockets and Socket.IO, including:

• Live classroom sessions
• Student/teacher communication
• Join requests
• Live questions and answers
• Participant presence
• Real-time notifications
• Session state synchronization

I'm expanding my backend experience into AI systems involving:

• LLM APIs
• AI service layers
• Structured model output
• Agent workflows
• LangGraph
• MCP-based tool integration
• Document/audio/video processing
• Automated business workflows

The goal isn't simply to add an AI API to an application. I’m interested in building the surrounding system that makes AI useful, controlled, testable, and connected to real application data.

A full-stack classroom and live-session platform designed around interaction between teachers and students.

Frontend

React · Vite · Tailwind CSS

Backend

Node.js · Express · Socket.IO

• Teacher live-session management
• Student participation
• Join-request workflows
• Live questions and answers
• Real-time participant updates
• Announcements
• Question bank
• Session analytics
• PDF presentation / slide viewing
• Client-side PDF caching
• Authentication and protected application routes

One of the more interesting parts of this project was working with the boundary between normal HTTP APIs and real-time application state. Instead of treating the interface as a collection of pages, the application has to react to events as the session changes.

A question-and-answer platform built with a Django backend and React frontend.

• Django REST Framework
• Custom user authentication
• JWT authentication
• Questions and answers
• User interactions
• Protected routes
• API-driven React interfaces
• Database relationships
• Serializer validation

This project gave me practical experience designing an application where the backend API and frontend state have to remain consistent as users create, update, and interact with content.

A complete e-commerce application combining a Django/DRF backend with a JavaScript-based frontend.

• Django
• Django REST Framework
• Custom user model
• JWT authentication
• Product and category APIs
• Serializers and validation
• Cart-related application logic

• JavaScript
• HTML
• CSS
• Fetch/AJAX
• Local storage
• Responsive product interfaces

The project helped me understand the full request lifecycle — from a user interaction in the browser through API validation and database operations and back to the UI.

A presentation system built around live classroom sessions.

The system explores how teachers can present PDF material while students participate in the same live session.

• pdfjs-dist
• PDF rendering
• Canvas-based slide presentation
• Slide thumbnails
• IndexedDB
• Local PDF caching
• Real-time session events
• Teacher/student synchronization

Using IndexedDB for local PDF storage was particularly useful for reducing unnecessary repeated downloads while keeping the presentation experience responsive.

A restaurant ordering application focused on making the ordering experience simple while keeping the underlying application architecture structured.

• Restaurant / branch discovery
• Food catalog
• Food detail pages
• Search and filtering
• Cart management
• Food categories
• Order flow
• Responsive mobile interface
• Restaurant availability
• Nutrition information

The interface is being designed around a simple principle:

A customer should be able to find something they want, understand it quickly, and add it to their order without fighting the interface.

I'm currently moving deeper into AI engineering from the foundation I built through full-stack development.

Agent orchestration

LangGraph

Designing workflows where different stages of an AI task can maintain state, validate results, recover from failures, and continue execution.

Model integrations

OpenAI · Gemini · Claude

Working with model APIs as application services rather than isolated chatbot features.

MCP

Exploring Model Context Protocol systems that allow models and agents to interact with application tools and structured data through controlled interfaces.

AI pipelines

Building toward systems that can take unstructured input such as:

Audio → Transcription → Analysis → Structured Data → Application Workflow

rather than stopping at text generation.

I also work with:

React Router · Hooks · Context API · Fetch · Axios · Responsive CSS

Experience includes:

Django REST Framework · REST APIs · JWT · WebSockets · Socket.IO · Service-layer architecture

LangGraph · LLM APIs · MCP · Pandas · scikit-learn

I don't want a project to work only in the happy path.

When building an application, I usually think about:

Problem
   ↓
Data Model
   ↓
Backend / API
   ↓
Validation & Business Logic
   ↓
Authentication
   ↓
Frontend State
   ↓
User Interface
   ↓
Real-Time Behaviour
   ↓
Testing & Edge Cases
   ↓
Deployment

That mindset has become especially important as my projects have grown from simple CRUD applications into systems involving authentication, real-time communication, file processing, and AI services.

• Designing cleaner backend service layers
• Advanced Django REST Framework patterns
• FastAPI architecture
• React application architecture
• Real-time systems with WebSockets
• PostgreSQL database design
• AI agent workflows
• LangGraph
• MCP
• LLM application architecture
• System design
• Data structures and algorithms
• Production deployment and DevOps

I'm interested in the parts of software engineering that become visible only when a project gets bigger:

• Why one architecture scales and another becomes difficult to maintain
• How frontend and backend contracts should evolve
• How real-time state should be synchronized
• How databases affect application design
• How AI systems can safely interact with real application data
• How to turn prototypes into maintainable software

I'm still learning, but I prefer learning by building systems where the problems are real enough to force better engineering decisions.

I'm interested in collaborating on:

Full-stack products Web applications with serious backend and frontend architecture.

AI-powered applications LLM integrations, agent workflows, automation, and intelligent application features.

Real-time platforms Classrooms, collaboration tools, dashboards, communication systems, and event-driven applications.

Developer tools Tools that make repetitive technical work simpler or more reliable.

If you're building something interesting, feel free to reach out.

_{Building, breaking, learning, and rebuilding better.}