You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(this came up when I gave my Sculpt talk in Chicago. can't remember who suggested it)
it would be really nice if when you aggregate at the class level or the package level, the output had some measure of the "thickness" of a dependency. probably just a count of how many individual entries were aggregated into the single entry.
this would help identify dependencies that would be especially easy to cut.
The text was updated successfully, but these errors were encountered:
informally, I used to do this all the time using Classycle, as follows.
if there was a package-level dependency I suggested of being thin, I'd disallow it in the config, run Classycle, and then eyeball how long the output is. if the output was only a few lines, the dependency was probably easy to cut.
(this came up when I gave my Sculpt talk in Chicago. can't remember who suggested it)
it would be really nice if when you aggregate at the class level or the package level, the output had some measure of the "thickness" of a dependency. probably just a count of how many individual entries were aggregated into the single entry.
this would help identify dependencies that would be especially easy to cut.
The text was updated successfully, but these errors were encountered: