[ 🏠 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: 1777779639348.jpg (187.55 KB, 1821x1300, img_1777779630175_vhq89p1x.jpg)ImgOps Exif Google Yandex

cb95f No.1571

i've been there - endless refactors to untangle circular dependencies in go projects. can someone explain the benefits of this design principle? do we rly gain more by enforcing non-circular imports, or is it just a pain point that slows down development sometimes?

https://dzone.com/articles/package-architecture-dependency-flow

f4f5f No.1572

File: 1777779734816.jpg (63.34 KB, 1080x720, img_1777779719744_ibq4dhks.jpg)ImgOps Exif Google Yandex

>>1571
clean code is often about making things clearer but import cycles can make dependencies less transparent, so it's a trade-off between readability and maintainability trade-offs exist in tech too!


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