FRONTEND CORE
Standard Library
State Management
Prod Framework
SPA Framework
No Virtual DOM
Redux, but chill
Utility CSS
JS with rules


Whenever I spin up a new project, I usually use the same set of tools. Here's a quick look at the core stack I use daily to get stuff done.
Standard Library
State Management
Prod Framework
SPA Framework
No Virtual DOM
Redux, but chill
Utility CSS
JS with rules
Open-source OS
JS on servers
Relational DB
Cache everything
2-way Binding
Safety First
Fast APIs
Scripting
Human Readable
Hjkl?
Panes For Terminal
Version Control

I've been building production web apps for over 6 years. My main focus is on the frontend, making sure the UI feels right and I have enough backend knowledge to build the whole thing myself.
I worked with PO team to launch 10+ features and new pages. I suggested a unified UI kit and worked with my teammates to build it out, it made the whole platform look way more consistent and easier to scale. I also wanted to improve our daily processes, so I wrote up a Git guide for team, and spending time mentoring junior devs.

I built the UI/UX for a massive Production Planning System completely from scratch. I also took over some old legacy projects and spent time cleaning up the interfaces to make them easier to maintain and follow my rules.

I worked on HR digital platform, working with the PM team to launch new feature, making sure it follow team's coding convensions and UI matched design and responsive. I also took time researching automation testing tools to update workflow and replace old flaky test.

I did a bunch of R&D for a Fraud Detection System, figuring out how to use machine learning to spot phishing attacks. I did build a working prototype that hit over 99% accuracy.

in Computer Science
It's the perfect time to get started!