I started working on a new project (web+andriod) in November last year. It was intermittent and stumbling. At most, there were 4 developers, and at least there was only one. From the very beginning to now, I have been in a development position, and there have been many problems in the middle: business (mobile health) comes first, team building comes second, and technology comes last.
Business-related, especially in industries such as medical, are centered on handling complex business. Mobile healthcare itself is divided into two directions: inside and outside the hospital. The core point is still inside the hospital. How to introduce the limited resources in the hospital to the outside of the hospital is the key. This will be described in a related article later.
Team building, how to build a stable team and build a good atmosphere for learning and growth. I have always had a goal of building small teams with a learning atmosphere, consistent goals, and passion. There are team-related content in agile methods. This series of articles will talk about some of the content of agile development.
Technology, technology is driven by business, and the business itself in the hospital does not involve high concurrency and multi-threading scenarios, but necessary optimizations are still required. I have been exploring technology, hoping that I can become an excellent architect first (although I don’t know exactly what an architect is), I can only keep encouraging myself, learning, and learning.
I saw an article before that mentioned the methodology for dealing with some problems in the project:
starting point:
1. Personal brain power is limited
2. The problem is constantly developing
Based on the problem, how to solve it:
1. Break the big problem into small problems:
difficult, It is because the problem is not subdivided to the extent that it can be solved;
easy, because the solution to the small problem is found.
2. Nothing is more than two things
3. Use existing tools and technologies to
change thinking:
1. Top-down, and gradually refine
2. Hierarchical model
3. Modular processing
4. Documentation
5. Agile
6. Design pattern The
ultimate goal:
not to solve the problem itself, but to find the know-how to deal with this series of problems.