I'm a Frontend Engineer who believes in understanding systems deeply, not just using them.
I build production-grade UI components with zero dependencies — not because it's trendy, but because constraints force better architecture. When you can't reach for a library, you learn how things actually work.
I created Black & White UI to share this approach: open-source components built from first principles, with courses that teach the why behind every decision. My goal is to help mid-level developers think like senior engineers — understanding trade-offs, designing for extensibility, and writing code that scales.
Currently: Building the BW-UI component ecosystem and creating educational content on YouTube.
|
Full-featured date picker with plugin architecture, theming, and WCAG 2.1 AA accessibility.
|
Undo/Redo, Excel copy-paste, Command palette, AI filtering, URL state sync.
|
Command palette with fuzzy search, keyboard navigation, and nested menus.
|
|
Great code isn't about clever tricks — it's about clear separation of concerns. I design systems with distinct layers: EventBus for communication, StateManager for data flow, and PluginManager for extensibility. Each piece has one job and does it well. |
Every component I build uses battle-tested patterns: Observer for reactive updates, Strategy for swappable behaviors, Factory for plugin instantiation, and Command for undo/redo. These aren't academic exercises — they're what makes code maintainable at scale. |
|
Instead of rigid class hierarchies, I favor composable plugin architecture. Need theming? Add the theming plugin. Need mobile support? Add the mobile plugin. You ship only what you use, and extending functionality never means touching core code. |
Zero dependencies isn't a limitation — it's a forcing function for better decisions. When you can't import a solution, you learn to build one. This approach produces smaller bundles, fewer breaking changes, and engineers who understand their tools. |
|
A11y isn't a checkbox — it's a design constraint that makes components better for everyone. Keyboard navigation, focus management, ARIA semantics, and screen reader support are built into the foundation, not bolted on after. |
Most tutorials teach you how to use a library. I teach how to build one. Understanding the internals — the state machines, the event loops, the rendering strategies — is what separates senior engineers from those who just consume APIs. |
UI Engineering