tag:blogger.com,1999:blog-11788780.post6910758399923875179..comments2023-12-29T13:22:33.104-08:00Comments on JJinuxLand: Software Engineering: Reuse Has Finally Arrivedjjinuxhttp://www.blogger.com/profile/03270879497119114175noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11788780.post-35274708389028187702008-09-18T01:18:00.000-07:002008-09-18T01:18:00.000-07:00Bob, since I've worked on that same piece of comme...Bob, since I've worked on that same piece of commercial software, I absolutely agree with you. We definitely haven't come to some nirvana of component reuse, as was hoped. You're right, it's hardest at the micro level. However, we have come to a point where large open source projects are reused and languages themselves come with large, useful libraries.jjinuxhttps://www.blogger.com/profile/03270879497119114175noreply@blogger.comtag:blogger.com,1999:blog-11788780.post-18419685561720757292008-09-16T22:04:00.000-07:002008-09-16T22:04:00.000-07:00At a macro level you're obviously correct. However...At a macro level you're obviously correct. However, the closer we get to any given piece of software we find that code reuse is far from a reality. Within the commercial product that I work on there is plenty of copy and paste action. Within open source applications we find the same thing in the common case.<BR/><BR/>In a less explicit way we see engineers reinventing the wheel with code that looks and smells like code in a different module. So now you can talk about a different set of problems like communication amongst engineers and how do you structure a codebase so that it can be properly divided amongst teams so that they're less likely to duplicate effort.<BR/><BR/>So I absolutely agree with what you're seeing and writing, however, I think the problem of today is at a more micro level and very widespread.Bob Van Zanthttps://www.blogger.com/profile/04357848795026149057noreply@blogger.com