What is the technical content of interface development and underlying development?

Today is the first day of Department change, from the previous format conversion department to the image processing department. I have just been involved in image processing, and I do not understand many basic concepts, so I have done some basic image processing exercises. Let's get started. Let's talk about how we feel over the past few days and how we talk about Microsoft and software development.

I remember that when I graduated from college, I used the command line interface. During the reply, the following dialogue emerged:

Teacher: Did you write in C ++,

Me: Yes.

INSTRUCTOR: Why is it not a graphical interface. (The Black Box is my name for the command line interface)

Me: ##￥ ￥ @@**&&&

At that time, I was messy. Well, if the layman thinks that C ++ = VC ++ = GUI is the same, I don't even know what the professional teacher thinks.

In fact, when I graduated from college, I wanted to engage in underlying development and felt that there was a technical level at the underlying level. Later I started my work, because I had little experience, so I started to work on the format conversion part, mainly to save the OCR data as word, ppt and excel. In the past, I spoke to Microsoft. Now I can see that the Office format can finally be well spoken. There are only 6000 pages in the document, so there are still some questions that I have not made clearly. The complexity of the format is definitely not what you can imagine. In this way, I have persisted for six months. Now, I still admire myself.

I remember asking me to create a PDF Editor interface when I was just two months old. Well, I have been engaged in an interface for half a month. I know that I am not good at interface development. The key is that it took us a week to discuss the interface. This is what I think is the most nonsense. Can I do a good job of functions first? Can I do it on the interface. Later, I thought it was really not. This is just like a girl's blind date. I always had to dress myself beautifully. It indicates that I am not an idol. I am not good at this. I told my supervisor that I was transferred to my office.

I used to think that my true love for life and getting away from Microsoft is a joke. After going through the office format, I really realized that this is not a joke. I used to feel that everyone has been talking about Microsoft, and I think Microsoft is not so pitfall. Now I find Microsoft is really pitfall. In fact, msdn is quite comprehensive compared with the Linux documentation. There is only one problem behind this comprehensiveness, with many details and no architecture. This is like when you go somewhere without a map. Although a tour guide will take you to the place you want to go, you have to rely on the tour guide every time. We cannot rely on remembering answers to complete the task. What we need is the methods and ideas to complete the answer. Microsoft's Thoughts on its architecture are rarely mentioned. I think that's why everyone is talking about Microsoft. That is why Microsoft is so tired of pursuing technology.

I also want to talk about interface development, because I want to change departments and talk a lot with the department supervisor later. He told me that interface development and underlying development are not good or bad. In fact, I haven't figured it out yet. However, my complaints about the interface are actually due to interface imitation, and the interface is easy to provide comments. Button size, position, font size, and position. It is easy to find a place where you can give comments. You can change it after you have mentioned it. After the change, you may find it difficult and then change it back. Fortunately, we are not doing a website, and it is estimated that it is more difficult to do a website.

So I switched to the background processing without the interface, so that the boss can only view the effect, and the rest will not work. Haha.