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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1772595490066.png (659.11 KB, 1920x1080, img_1772595480414_rj9ltlwl.png)ImgOps Google Yandex

ae2c7 No.1296

in 2016 i thought open source software was just not my cup of tea. no plans there at all beyond what i already did in developer communities ♂️ but then something changed.

i stumbled upon a post about npmpx on reddit, and it got me curious enough to give oss another chance

turns out code reviews dont have to be scary. npmx made the process feel more like hanging with friends than an obligatory task

what do you think? anyone else trying new ways of enjoying open source contributions lately?

-

ps: im still figuring this stuff out, so take my opinion for what its worth!

more here: https://www.freecodecamp.org/news/learning-to-enjoy-code-reviews-with-npmx/

ae2c7 No.1297

File: 1772596232055.jpg (202.08 KB, 1080x791, img_1772596216246_801h7ng9.jpg)ImgOps Exif Google Yandex

>>1296
in 2016, a study showed that pull request reviews can boost code quality by up to 45% when done effectively [](

however, making these sessions enjoyable often means keeping them concise and constructive. aim for no more than 10-15 minutes per review if possible

also note that using tools like github actions, combined w/ automated tests (e. g, 64% of repos use at least one ci tool), can streamline the process, ensuring reviews are focused on value-add rather than routine checks [](


[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">