Back to articles
Front-End & Struggles

Front-End & Struggles

via Dev.toyep

I didn’t have much frontend experience. This post covers the struggles I ran into. Starting Point: React + TypeScript + Plain CSS React with TypeScript felt like the obvious choice — popular, good ecosystem, type safety. I started writing plain CSS modules for styling. Full control, right? The problem wasn't the code. It was that I had no design vision. I'd write a component, look at it, and know it looked bad but not know how to fix it. What colors? How much padding? How should this align? I couldn't answer these questions. The feedback loop was: write code → look bad → feel stuck → repeat. This went on for weeks. Tailwind CSS Didn't Solve the Real Problem I switched to Tailwind CSS thinking it would help. It sped things up — utility classes are fast to write, no context switching between files. But Tailwind is a tool for people who already know what they want to build. It doesn't give you design vision, it just makes it faster to execute one. I still didn't know what I wanted. I trie

Continue reading on Dev.to

Opens in a new tab

Read Full Article
0 views

Related Articles