Frontend engineer
Hovi Digital Lab
Intro
Who I am
Mohamad Abbar — Frontend Engineer
I spend most of my days turning complicated things into interfaces that feel simple.
Five years of frontend have taught me that making things work is only half the job. The other half is making them feel right, from how information is laid out to the tiny details people notice without realizing.
- Beirut, Lebanon
- GMT+3
- React · TypeScript
Note to self
Make it make sense to someone who wasn't there.
Projects
01 Test
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
- Lorem · 2025
- Duis aute irure
- Excepteur sint occaecat
The decision
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam eaque ipsa quae ab illo inventore veritatis.
+ what I'd change now− hide what I'd change
What I'd change now: Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore.
Experience
Where I've worked
BSc computer science
Lebanese International University
2017 → 2021
2021
Full-stack bootcamp
SE Factory
2021 → 2024
2023 → 2024
Frontend engineer
PortalysPART-TIME
Frontend engineer
Grower AI
2024 → now
Skills
My stack
TypeScript
A little more ceremony. A lot less guessing.
JavaScript
Still the language underneath. Know what's actually happening.
CSS
Most layout bugs are a missing constraint, not a missing property.
React
Boring, and that's the point.
Next.js
A lot of power. A lot of places to accidentally use it wrong.
Tailwind
Ugly in the file, fast in the browser. I will take it.
Zustand
Most state is local. What is left rarely needs more than this.
TanStack Query
It ended the argument about where server state lives.
Zod
One schema for the form and the type. The duplication was the bug.
Recharts
Fine until the design gets specific. Then you're drawing SVG.
Design systems
The components are the easy part. Agreement is the real system.
Playwright
If breaking it costs money, it gets a test.
- Languages
- Frontend
- State & data
- Craft
Changed my mind
Things I used to believe · and what changed them
6 merged0 open
I used to think a design system was a component library.#01It's an agreement. The components are just where it gets written down.
I used to abstract things because they looked similar.#02Now I wait until they actually behave the same.
I used to think complexity was something you could remove.#03Now I think good UX is often about hiding the right amount of it.
I used to think building AI features was mostly a model problem.#04It's an interface problem too. The hard part is deciding what people should be able to control.
I used to build the happy path first.#05Now I think about the weird states while I'm building the normal one.
I used to ask, “Does this work?”#06Now I also ask, “What happens when someone has to change it?”
Contact
All checks passed · open to new work
Ready to merge into your team.