Software Development Method -- practical

On the blog Software Engineering homepage, I saw Deng Yongqing's article Joel vs Bob, agile is actually boring. After reading this article, I am similar to my current understanding, and practical is the most important thing.

I have been learning agile development recently. I bought Agile Software Development C # edition, and I only read less than 1/5. We also downloaded the Development Mode Tutorial on webcast, and only saw less than five courses. The first reading of the things mentioned here is basically Yun, and the second reading, if enlightened. For the third time, it is still enlightened. I understand what I am talking about, and I have basically understood the original principle. But I have no idea how to use it. However, I think these methods must be abstracted from the problems frequently encountered in software development. After understanding these methods, they may be applied to them unconsciously in actual programming, maybe after the application, I will think of it. Isn't that a certain mode? Or when you see a problem, you will think, Well, what mode does this work!

I just started learning C # And learning Oo, so an example of an interface application in my actual work may have little to do with agile development, however, I think the theory should be combined with practice in this way.

Some time ago, when I learned C #, I had never had a deep understanding of the interface, and I basically understood everything in the book. But I always thought it was too abstract and should not be used in my work, I also learned from my colleagues that this interface is very useful! The result didn't take long and I encountered a problem: I need to perform a data conversion between multiple data sources, for example, you can import data from a DBF table to SQL, and export data from SQL to DBF and excel.

After thinking for several days and trying one or two methods, I suddenly thought, isn't it just possible to implement it using interfaces? Define an interface for data conversion and implement it in the classes corresponding to MSSQL, DBF, and Excel. Isn't this the case suitable? Therefore, we were prepared to define this interface, and the result was written but we could not find an accurate interface.

So I leave the interface alone and write a DBF conversion class first. So I wrote such a class,

There are methods for creating tables, obtaining data tables, obtaining table structures, saving tables, and other attributes, and then directly selecting "extract interface" in the code, OK, after a few simple hooks, I will extract the public part into an interface. Then, MSSQL and Excel classes are implemented one by one based on this interface. Everything is so natural. This interface is used:

 

 

Therefore, I think that learning is a must, but never be difficult. You can use it only when you think that you just need it. Otherwise, it is better to use it!