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

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788349231550.jpg (178.93 KB, 1024x1024, img_1788349221890_1fgofvoi.jpg)ImgOps Exif Google Yandex

c52f2 No.2035

the current setup works fine for us, but i wonder if things would completely break once we hit 20+ devs on the same repo. it feels like modularizing via ddd is the only way to avoid a massive mess . does anyone else think clean architecture is overkill for smaller squads?

full read: https://www.freecodecamp.org/news/feature-modularization-in-flutter-combine-clean-architecture-and-domain-driven-design/

c52f2 No.2036

File: 1788349383082.jpg (268.78 KB, 1024x1024, img_1788349367177_37pmmuoq.jpg)ImgOps Exif Google Yandex

the real bottleneck isn't just the architecture, it's the merge conflicts you'll hit in a single repo. if you aren't already using melos to manage local packages, you should start now b4 the scale actually hits.



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