PROJECT01.Web Development & Vibe Coding: UdyomX ORG - Dynamic Content Platform
- Content Management: Publish and organize blogs, projects, galleries, and custom pages from one unified system.
- Flexible Page Creation: Deploy different page types instantly without rewriting the core application or rebuilding from scratch.
- Discovery & Visibility: Engineered with SEO, AEO, structured data, FAQs, and recommendation engines to help users find the right content.
- Centralized Administration: Manage content, media, and platform access securely through a dedicated admin dashboard.
How fast can a new campaign or event page be deployed?
Because the system isn't hardcoded, new landing pages can be generated instantly. The custom engine allows the creation of standalone pages with their own layouts, media galleries, and dynamic FAQs directly from the dashboard—built explicitly for rapid, on-demand deployment.
Why build a custom platform instead of using a standard CMS?
I wanted tighter control over the architecture, page structure, and publishing workflow. A custom system gave me that flexibility while keeping the platform entirely focused on the features I actually needed, without the overhead of unnecessary third-party plugins.
How did you manage such a wide feature set without making it difficult to maintain?
I focused on building reusable systems instead of creating every page separately. Content, media, navigation, FAQs, and page structures were designed as modular components. This allows new content and pages to be added without repeatedly changing the core application.
PROJECT02.Web Development & Vibe Coding: Digital Identity & Portfolio
- Information Architecture: Structured projects, skills, and background so visitors can understand the complete profile at a glance without reading a dense resume.
- Responsive UI Design: Engineered a fluid, multi-device layout that maintains clean typography and visual hierarchy across mobile, tablet, and desktop screens.
- Reusable Showcase Cards: Modular card components built to highlight diverse projects with immediate clarity, scannability, and individual deep-dive links.
- Search & Discoverability: Implemented structured metadata and SEO/AEO-friendly architecture to make the portfolio discoverable by both search engines and AI agents.
How did you organize diverse information without it feeling like a plain CV?
I grouped content hierarchically based on what a visitor looks for first: core identity, technical capabilities, proof of work, and practical experience. By using modular cards and clear spacing, deep details remain accessible without cluttering the initial viewport.
What was the engineering approach behind the showcase cards?
I treated each card as a visual entry point rather than a static list item. Each component surfaces the title, domain tags, and core impact at a glance, allowing readers to scan, compare, and explore different types of work instantly.
How was the system built for future expansion and maintenance?
The platform relies on dynamic components and Supabase rather than static hardcoded blocks. New accomplishments, events, and projects can be introduced seamlessly through a dedicated backend without altering the fundamental design system.
PROJECT03.Web Development & Vibe Coding: NEXUS - Personal Productivity Infrastructure
- Unified Workspace: All important notes, files, and resources are organized securely in one central hub.
- Cross-Device Flow: Move data seamlessly between mobile and desktop without breaking the workflow.
- Secure Access: A private Google Login ensures my personal data is locked away from public view.
- Activity Tracking: Turns daily habits and work sessions into simple visual charts to help me understand my workflow.
Right now, NEXUS is built just for my personal use. But the core architecture is highly scalable. By adding role-based access, this exact model can become a team system. For example, an executive team could access planning documents, while an event team accesses media assets—all from the same secure platform, without mixing everyone's data together.
Could this system support different users and permissions?
Yes. While I use it alone right now, the database is designed so roles can be added easily. This means a system like this could give a content team access to certain files, while keeping financial or management documents locked safely for executives.
Why build one big system instead of using several existing apps?
Using many different apps makes data messy and hard to find. Building my own central system gives me full control over my files. I decide how my data is organized, and I can add new features immediately whenever my daily workflow changes.
SHOWCASE04: AI Visual Framework - Automated Brand Design
Note: The images below are conceptual mockups designed specifically to demonstrate how this framework handles organizational branding.
SHOWCASE05. Computational Photography - LMC Engine
Achieving this level of quality usually requires expensive camera gear.
Hardware is only half the equation. My phone's physical sensor is actually quite weak. Instead of buying expensive gear, I rely on computational photography. I use the LMC camera port and apply specific XML configuration files. My method is simply bypassing hardware limits by knowing exactly which software profile to use.
If the software does the processing, the camera is basically doing all the work.
The software only processes what you feed it. The real skill is visual sense—framing the shot, reading the light, and knowing which specific configuration file will handle that exact environment. A night-mode config will ruin a bright daylight shot. My core job is observing the environment and making the perfect match.
With results like these, the post-editing process must take a lot of time.
Actually, almost all the processing happens the moment I take the picture. Because the chosen LMC config handles the shadows, colors, and noise reduction instantly, the photo comes out ready to use. There is no huge backlog of photos waiting to be edited for days before an organization can publish them.
This kind of photography depends entirely on your personal intuition, which cannot be shared.
The visual framing relies on my sense, but the technical quality is completely documented. I use a fixed set of config files mapped to specific situations (like "indoor warm light" or "cloudy day"). Because the technical part is file-based, the process of getting clear, professional shots is repeatable, not just a one-time lucky shot.
SHOWCASE06.Basic Photo Editing & Color Restoration
[ Drag the slider left and right to compare ]
Editing hundreds of event photos usually takes days and delays media teams.
That happens when editors process every single photo manually. I solve this by using automated batch-processing workflows. Once I perfectly color-correct one anchor photo for a specific room or lighting setup, I sync that exact adjustment across hundreds of similar images instantly. This turns a multi-day editing backlog into a task that takes just a few hours.
Applying automated edits to an entire batch makes photos look generic.
Automation does not mean slapping a cheap filter on everything. It is about doing the heavy lifting fast. The system automatically fixes the base exposure, removes digital noise, and balances colors for the whole batch based on my manual settings. This gets the photos 90% ready instantly, leaving me with plenty of time to carefully hand-retouch only the few standout shots.
WORK PROJECT07. July 2026 - Flood Assessment
What exactly is SERC, and what is your role in this organization?
SERC stands for the Space and Environment Research Center. I contribute to this organization entirely on a voluntary basis, working remotely to handle tech-driven activities. Currently, I hold the position of Program Executive, where my main responsibility is executing and managing data-backed environmental programs, just like this flood assessment project.
If an AI assistant is writing the spatial scripts, the tool is essentially doing the analysis for you.
AI is an incredibly fast typist, but a terrible strategist. It does not understand physical geography or know which specific radar filter makes sense for extracting floodwater data. My job is to architect the spatial logic and make all the analytical decisions. I only use AI to instantly generate the syntax required to execute that logic. The thinking and strategy are entirely mine; only the typing is automated.



































