Hi Kevin - thanks for sharing! Good stuff - in particular, I think your argument for why modularization is necessary as a codebase grows was very well made. In terms of constructive criticism - the last set of recommendations (for medium-sized codebases) seems a bit abstract / difficult to connect to moving the ball forward on modularization to me…
Hey, thanks for the feedback! This is just the kind of thing I’m looking for. I will take another look at that section. Luckily dev.to is not Twitter so, I can edit
Hmmm - so at this stage it appears that you’re not recommending starting to add internal modularity yet? If not, are there steps they should be taking at this stage to prep for that work (mapping out future contexts, detangling AR models, etc.)?
Yes, I see. Maybe a “laying the groundwork” phase is the right approach, given that it may be too early to go all in with something like the Solidus gems approach, but it’s not too early to start preparing either.