The recent commute has been reading out of the software workshop. The business-centric thinking in the book makes me feel rather deep. Although the author has been focused on the enterprise management software industry, the book of many concrete case method is also in this industry, but in terms of software development, or even amplification to do things, the truth is the same. My deepest impression of a paragraph is to tell the author of a novice, in the development of extreme pursuit of Oo and design patterns, make the code is very troublesome, see his own code pleasing, others see his code foggy, and the author's code is simple and clear, it is easy to see the business process. The novice asked the author how to do it, the author said:
"My mind is only business, business and code, and I think just the difference between English and Chinese, expressing the same idea. And in your mind, the business is Doc text, code is your technical performance, you old need to put business and code mapping together, I do not need. The business process, how my code flow is. ”
I used to go to research and work with my brother when the design style is really like the novice. Now I am more and more inclined to flat design, and even "no design", which is in the actual production development environment, in the business is forced out. But even so, the nature of his perfectionism is quite deep-rooted, there will be a lot of tangled when coding, especially when writing a new thing. This was also mentioned in last year's annual summary.
One important reason is that I have been comparing drilling technology to drill the bottom, write the business is still relatively small, in particular, have not started to write a complete business process and business system from scratch-for game development, that is, like Guild, store, backpack this game logic system. Although I have also handled some business, and in the old club also handled like the drop of goods and pick up this critical business system, but it is maintenance or two development. In recent conversations with the main course, Lord Chengye said I lacked this exercise and needed to find a chance to write the big system myself.
In fact, although I have always been fond of studying the technical principles and academic aspects, but not exclusive to the business, and I now more and more feel that business is more important-when you stand in the perspective of planning, bosses and users to look at this problem, you will understand this more. The so-called business-centric, in fact, is the goal-driven attitude of doing things. In addition, I think it is necessary to take some time to write business even if it is the engine and tool programmer that is going to develop on the technical level, because only then can you provide the tools and the interface to be close to the project, really good, and not become a castle in the castles, narcissistic. Many of the technological advances in history come from actual business needs.
I am still very excited about writing business.
It's time to write more business.