React
FrontendI use React to turn product ideas into reusable, state-driven interfaces. It taught me to think in components, keep data flow predictable, and design UI that is easy to evolve.
Loading content...
A focused stack built for product velocity and durable UX. Each category is curated for clarity, reliability, and speed in production.
Balanced coverage across UI systems, API delivery, and data architecture with modern tooling.
I use React to turn product ideas into reusable, state-driven interfaces. It taught me to think in components, keep data flow predictable, and design UI that is easy to evolve.
I build full-stack, production-ready experiences with Next.js, from routed pages to server-rendered data. It taught me how rendering choices, caching, and structure shape performance.
JavaScript is the foundation of the interactive products I create. Working with it has sharpened my understanding of asynchronous code, browser behavior, and dependable application logic.
I use TypeScript to make growing codebases safer and easier to understand. It taught me to model data clearly, catch mistakes early, and create better contracts between components.
I use Tailwind CSS to build responsive interfaces quickly while keeping visual rules consistent. It strengthened my eye for spacing, layout systems, and maintainable design tokens.
I use shadcn/ui as an accessible, flexible base for polished product interfaces. It taught me how to adapt component primitives without losing control of behavior or design.
I use Expo to develop, test, and ship React Native applications with a productive cross-platform workflow. It taught me how config plugins, EAS builds, and native capabilities fit together.
I build mobile interfaces with React Native while sharing familiar React patterns across Android and iOS. It taught me mobile-first interaction, native constraints, and platform-aware UI design.
I develop and test Android application flows, permissions, builds, and device-specific behavior. It taught me to account for lifecycle changes, hardware differences, and native delivery requirements.
I use Node.js to build server-side features and connect frontend experiences to real data. It taught me event-driven thinking, asynchronous workflows, and practical service architecture.
I build focused web services and middleware pipelines with Express. The framework taught me to structure routes cleanly, validate requests, and handle errors consistently.
I design and consume REST APIs that keep client-server communication clear and reliable. This work taught me thoughtful resource modeling, useful status codes, and stable contracts.
I use Laravel to deliver structured backend applications with authentication, validation, and database workflows. It deepened my understanding of MVC and convention-led development.
I have used PHP to create dynamic server-rendered features and application logic. It gave me strong fundamentals in request lifecycles, sessions, and dependable backend development.
I use PostgreSQL for relational data that needs consistency and expressive querying. It taught me deliberate schema design, indexing, joins, and the value of data integrity.
I have built application data layers with MySQL and written queries for everyday product needs. It strengthened my understanding of normalization, relationships, and query performance.
I use Prisma for type-safe database access and clear, reviewable schema changes. It taught me to keep application models and persisted data closely aligned.
I use Supabase to move quickly with hosted Postgres, authentication, storage, and real-time features. It taught me to prototype fast while still respecting permissions and data design.
I use Git every day to work iteratively, collaborate safely, and keep changes traceable. It taught me disciplined commits, confident branching, and thoughtful code review habits.
I use Postman to explore, test, and document APIs before they reach the UI. It taught me to verify edge cases early and make backend behavior easier to share and debug.