Preface: "more than Code" is Ali's first technical experience Collection, Daniel covers many technical views on career development, writing is simple and elegant, easy to understand, just look at the first two chapters I was fascinated, is this recommended books, suitable for the fragmented time to read. Only a hundred page books, but not recommended devoured, it is best to read each chapter to have their own thinking perception, then read on.
- Do more: do more, do more than your supervisor to arrange your task more, trying to stand out in a team.
- Do better: know that there is no perfect thing in this world, you are responsible for system and business, there is always unreasonable and areas for improvement, these "unreasonable" and "improvement" of the place, trying to put forward their own solutions to the leadership, and pay practices.
tips: more than two points on the job how to do it? 1. a sense of belonging to the company / project! As is their great cause. 2. in the hands of their good work ethic.
- I hear and I forget. I see and I remember. I do and I understand. 实践出真知。
- Methodology of learning: learning (principle underlying knowledge reading books, frames, components, read the documentation), trying (write Demo practice based on knowledge of the book, practice makes perfect), teaching (knowledge summarized into a document)
- If you encounter a problem, coworkers solved, but I can not solve. So I went to think how to solve the problem he was, he saw the logic and thinking after the question is how? What knowledge to guide him so logical reasoning, knowledge is what I know, but I did not think to use such reasoning; this knowledge and what I do not know.
- + Basic knowledge of logic is equal to your ability. Knowledge let you know that thing; logic makes you put things and problems linked to the problem here can be understood as programs, architecture and design.
- Value of the software system is based on the ability to solve business problems, the ability to support business growth, as measured, not by the software system how fast hardware technology. So, architecture goal is to support business growth, enhance the service capabilities of the software system, must recognize the business value behind the system, rather than the pursuit of an idealized technology.
- Not because it is not a developer to focus on software operation and maintenance, not because testing is not just concerned about software development, because the more you focus on the more you can see the overall value of the target. If you focus only on third of an acre, it is doomed in this life can only be holed up in the third of the acres, becoming the yard lines on a farm anxiety to death. Try to change the thinking, consider the value of the issue from the perspective of the architect, to see whether the technology through to business, to the user, go to the final value.
- Interestingly, the Internet connects us to the vast world, but also our unique enclosed in their own little world.
tips: once we graduated just how vibrant blooming, full of ideas, not because of science and technology, thus dying in their own world.
- Team has on hiring a comparative benchmark, is that you recruit people who are not in the same class team better than 50% of the students, if you do not think they are good, that do not tangle, the candidates do not, the team must not stop adding more students to become more outstanding.
- Do not try to prove in an interview others as their own.
- Architecture is evolving, wait until we really need such a high-availability system reconstructed again, remember: Do not premature optimization, premature optimization is the root of all evil - "UNIX Programming philosophy"
- Efficient division of labor is the main driving force of social collaboration since the industrial revolution, after a long period of time should also maintain this form.
- Software field and the biggest difference is the field of software hardware field is no absolute industry standard, we both have fun, like how to play how to play.
- You are the owner of your career. You are responsible for your career development.
- We need to do is to never repeat work, when you think it's working, more comfortable, more risk of missing time, it should arouse vigilance.
- Scratch the schema; from front to back is abstraction; from coarse to fine design.
- Microsoft architects have a Category:
- Enterprise Architect EA (Enterprise Architect)
- Infrastructure Architect IA (Infrastructure Architect)
- Specific technical architecture TSA (Technology-Specific Architect)
- Solutions Architect SA (Solution Architect)
- "Part-time architect": small teams or projects undertaken in non-explicit architect responsibilities; to do the project or product key design and implementation; responsible for product infrastructure; the introduction of new concepts, framework; solve complex problems in the team. But only a fraction of the time assumed the role of the architect, most of the time doing the development work of the PM. And do most of the things that are their own controllable, make their own infrastructure, their own implementation, implementation or in small teams. (SA biased in favor of the type of architect)
- "Full-time architect": not responsible for the specific business systems, but is responsible for all systems, rarely directly responsible for the project, but must be in advance to control the project, in the face of a bigger team, bigger problem domain . (Biased in favor of IA, TSA type of architect)
- Do a good job overall technology plan
- Unified approach, norms, mechanisms
- Complete basic components to build
- Architecture landing implementation
- Customer architects are faced with every member of the team must always keep in mind the customer first. The purpose of existence is the architect R & D team every student achievement, we provide the necessary platform for services and space, then the achievements of each other.