No, inheritance is not the way to achieve code reuse!
posted by JamesEggers(1250) 3 years, 9 months ago 0
I have sat through a number of programming classes across different languages, schools, and instructors and they all fall into the bucket described by this post. The post's main focus is that "why" to use inheritance is missing in most cases. It can be a form of code reuse; however, in many companies, a number of developers will use inheritance for the sake of using it. I've actually worked for a company that said "our code uses OOP techniques, we inherit". Obviously something is a bit wrong in some people's definition as to why to use it. I think the final point that the post is trying to make is that the scope of code reuse should be defined. If you aren't looking at a number of different objects that will use the same methods, then an Interface is probably more beneficial than a base class. If you're looking for overall code reuse (i.e. a company's custom DAL code), then it should be in a framework or assembly and not as a set of base classes that a person can inherit from. It boils down to understanding the "why" of the design and purpose of the code.
Reply
Google Chrome is here
posted by JamesEggers(1250) 3 years, 8 months ago 0
I'll be curious to see how Google's Browser attacks Firefox's ability for extensions and themes. I agree Chrome is decent but it I see it as a competitor more to Opera currently than any other browser right now. We shall see how things go though since V8 is nice.
10 Reasons ASP.NET Webforms Suck
posted by JamesEggers(1250) 3 years, 4 months ago 0
This post feels like the author learned ASP.Net from the old MCAD books instead of looking at best practices on when to use server controls and when not to. While I agree to an extent with the items listed (especially the single form comment), there's a lot of ways to ease these pain points to make things work better.
Playing with JSON
Nice post and great examples that cover the various options.