In general in the past till now I have written Utility classes and methods when doing my programs. I usually instantiate these classes or have shared methods in them and use them in other classes as needed. I went to a Microsoft seminar recently and the presenter, an ALM expert and developer, was mentioning some old techniques in programming that should not be used any more. One of the things he mentioned was the use of Utility classes. He said that in the new way people define methods they would use in the utility classes, right in the class they are using them in.
This didn't make sense to me. Wouldn't this lead to duplicated methods all over the place? What do you guys think about this? Is there some other better way? I am always looking for best practices as I usually see so much bad programming all day that needs to be fixed and old ways to do things that can be written much better with newer language constructs.
This didn't make sense to me. Wouldn't this lead to duplicated methods all over the place? What do you guys think about this? Is there some other better way? I am always looking for best practices as I usually see so much bad programming all day that needs to be fixed and old ways to do things that can be written much better with newer language constructs.