3 ms·
Notice that nowhere in the article is there any mention of what a good architectural choice is, nor any mention of the perception of debt in relation to the siz
by PopeOfNope 11y ago
Notice that nowhere in the article is there any mention of what a good architectural choice is, nor any mention of the perception of debt in relation to the size of the system[0]. My personal experience with architectural choices is that all of them are great early on when the code base is small. As that code base grows, they all suffer under the weight.
[0]: 100k-1M is a very large range. Kudos to them for filtering out small code bases, but a graph of these perceptions measured against code size would have been helpful.
- nernst 11y ago(author here) We cross-tabbed system age vs perception of amount of TD. There was a moderate association between older systems (> 6 yrs) and more perceived debt. I did not explicitly look at size as this was not one of the original research questions, but a good point. I suspect older systems will tend to be larger (in the domains we studied, anyway). And your point about arch choices being great "early on" can, I think, be captured in the "system age" variable. I guess I'm trying to think of a system that might be young and yet quite large in LOC.. would be an interesting outlier to look at.
- PopeOfNope 11y agoI guess I'm trying to think of a system that might be young and yet quite large in LOC.. would be an interesting outlier to look at. Take a look at video game companies. They tend to build up a large infrastructure early in the development of a game. Keep up the great work! I love to see scientific research being done on software development. :)