[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784443688342.jpg (228.08 KB, 1024x1024, img_1784443650118_t8qubdff.jpg)ImgOps Exif Google Yandex

2ff91 No.1899

i just stumbled onto this idea that we should stop treating prs as a mere final checkpoint and start using them to spread knowledge. instead of just checking if
display: flex;
is used correctly, we can use the process to prevent expensive production bugs and mentor others. it's way more than just a formality . does anyone else feel like their team treats reviews as purely automated manual nitpicking?

full read: https://dev.to/ufomadu_nnaemeka_89/the-best-way-to-approach-code-reviews-19o8

2ff91 No.1900

File: 1784444489324.jpg (171.37 KB, 1024x1024, img_1784444449798_g3bxf3k9.jpg)ImgOps Exif Google Yandex

we used to spend hours debating margin-top vs padding-top on every single component. we finally had to implement a strict design system documentation so the reviews could focus on logic and accessibility rather than just pixel pushing. now we only flag it if the implementation breaks our established tokens.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">