Hi, I’m Dawid Kowalczyk
for better understanding the people I design for, and because the boundary between design and engineering is disappearing anyway.
Due to strict NDAs and the proprietary nature of these enterprise back-office platforms, all user interfaces have been intentionally abstracted.
Learning goals: {
"understand the developer world" :
"I design for developers —
I need to think like one",
"bridge design and code" :
"no more handoff friction —
what I design, I can build",
"own the visual layer" :
"small UI fixes and adjustments
without pulling a dev in",
"prototype real apps" :
"not just Figma mockups —
something you can actually use",
}| html/css/js | running |
| tailwind | running |
| react | running |
| Typescript | running |

UXE Educaton
A website explaining what UX Engineering is — built for designers curious about crossing into code.The content is mine. So is the code.
I'm learning React, Tailwind by writing it myself. The site is the lesson.
Users who know their domain deeply and don't forgive bad design. Every domain I've worked in demanded deep learning before the first sketch.
From the first research question to the final interface — and now, further into the code. These are the tools I use to get there.