tag:blogger.com,1999:blog-5135517.post115928570235431601..comments2023-11-05T03:54:44.710-08:00Comments on Making it stick.: Less BignessPatrick Loganhttp://www.blogger.com/profile/02088461489050417591noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5135517.post-1159549484437976932006-09-29T10:04:00.000-07:002006-09-29T10:04:00.000-07:00Hi Patrick,Something I've wondered about before is...Hi Patrick,<BR/><BR/>Something I've wondered about before is that bigness is a vicious cycle. If you're a programmer working on (say) a ten million line system, then of course you don't know how the whole thing works, because the time to learn it all is utterly infeasible.<BR/><BR/>So when you run into a problem, you don't know whether someone else has solved it before or not, and often you end up re-implementing a solution. So the app has multiple incompatible implementations of the same thing, which feeds the problem of the system being too big to understand.<BR/><BR/>The question of how we communicate the design solutions we've built to the other programmers is a really deep and interesting one. That's because it's a semantic question: we need to ask the system, and have it tell us, whether (say) a message bus has been implemented already. And what's more, often we really want to take something that exists already and generalize it, so the query engine has to look for specializations of the semantics, too.Neel Krishnaswamihttps://www.blogger.com/profile/06853898957395028131noreply@blogger.comtag:blogger.com,1999:blog-5135517.post-1159545070525990762006-09-29T08:51:00.000-07:002006-09-29T08:51:00.000-07:00Oh and of course, excuse my bad english ;)Dan.Oh and of course, excuse my bad english ;)<BR/><BR/>Dan.PetrolHeadhttps://www.blogger.com/profile/06404572533828179184noreply@blogger.com