I am a vb.net developer in a small IT department and I have difficulty in jumping for particular programming with the object Is happening
I understand the principles of OOP, design patterns, unit testing etc., but when my applications come to the development, my object design is poor or I leave the building completely with the object. I can not know how to test the unit, but I do not believe in people I have created.
I create data-driven data entry / reporting type apps almost exclusively. In most cases, most business logic is stored in the database in stored procedures and UDF. I ask developers about ASP.Net and Winform applications for internal and external customers.
I have asked from here on the stack that I can think of good design and testing, but mostly reduced. I have read a bunch of books on the design.
What are some good steps to go away from my old 'VB6' mode?
Thank you!
I have heard that man also lives in my own world. In a world where business people demand a report, a complex report report that is easily made with complex stored procedures, it is easy to think that the database is king and runs this application. From that line of consideration, the complex database leads to TSQL code, views, functions, and stored procedures.
Of course, if this is actually a report that you need, then a complex SQL statement may be answered. However, you want to know how to get out of the data-driven world and enter an object-oriented world.
I think the specific OO Design Tutorial will not do justice to you. Who cares that a dog is an animal type and a German Shepherd is a type of dog does not tell you how you do business on your own business. Apart from this, it is an example of O.O. inheritance, other Ooty patterns like structure and dependency injection are most useful for most of the time.
The way I think you should go to your next project or task, forget about the database temporarily. It is an excuse that you live in a magical world where you have to get data from the database and not even writing the data back in the database. You live in a world where your objects always come with the right data. Show your objects first in that abstract world. After doing so, then (and after) worry about getting the databases yourself and the details of the messy implementation of writing. The database is only for your data to continue. Your data is live because you have already prepared it in accordance with the rules of your domain.
Understanding UML will help a lot for this type of modeling. Use UML Design for the model of your domain then code those designs. Then work them to fit within the constraints of your database.
Eric Evans "Domain Inspired Design" is a good book that keeps it and many other related points at home. They make this issue that domain modeling is an important element for modeling successfully. He suggests that object-oriented design is better for domain modeling compared to other types of programming paradigm.
Good luck. Once you embrace completely typed objects, completely modeled, you will not want to re-pars another dataset again.
Comments
Post a Comment