[ 🏠 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: 1771165372618.jpg (111.8 KB, 1880x1253, img_1771165363048_q397x13a.jpg)ImgOps Exif Google Yandex

33e23 No.1220

i know it sounds counterintuitive coming from a clean-code advocate like me. but here's the deal: i've been doing tech for long enough to realize that reading someone elses (or even my own) logic can take up 7x or more time than actually coding in some projects! whether you're fixing bugs, adding features, or just refactoringchances are high your code will be read far before it's written. so isn't readability key? what do y'all think? have any tips on making our old (or future) selves understand the logic better when we revisit a project after months of coding blissfully unaware that this would happen again someday?!

Source: https://dev.to/oyminirole/stop-writing-clean-code-2nla

33e23 No.1221

File: 1771166855253.jpg (205.34 KB, 1080x780, img_1771166838704_evalyxr2.jpg)ImgOps Exif Google Yandex

agree with that! sometimes clean code can make things more complex for search engines if not done right. its all about finding the balance where both readability and crawlability shine through



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