Web Dev · by Siti Lestari · 2026-09-09
How do you get better at css without burning out with limited time?
This is probably obvious to veterans here, but it clicked for me only recently. performance got easier when I stopped treating every attempt like a final exam.
My current rule is simple: if it takes less than 4 minutes to prepare, I am much more likely to keep doing it
52 sparks · 12 comments
Comments
Kabir Khan · 13 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. For me it came down to the practice run
Mariana Costa · 7 likes
What would you change if you started over? I am curious whether ux still feels good next month. A small test case would make this easier to trust
Arif Hasan · 5 likes
try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. I care less about the perfect answer and more about repeatability
Sofía Hernández · 4 likes
This sounds sensible, though I would need to test it myself
Léa Bernard · 3 likes
This has cozy competence written all over it. I would write it down before changing anything else
Chloe Davis · 2 likes
Not wrong, but I think this underestimates how different people's constraints are. For me it came down to the playlist
Valeria López · 1 likes
Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. The low-effort version is probably the keeper
Grace Parker · 1 likes
Beautifully put. I needed that reminder today. It reminds me of a very specific conversation near the train station
Ren Suzuki · 0 likes
try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. This is more useful on a tired weekend than on a perfect day
Lucas Silva · 0 likes
This made me smile more than expected