Six months ago, when we started a new project, everyone in my group and I received an email from our architect: Every time I started a new project, I was very excited. Even after 20 years of software development, I still feel like a little bunny pounding in my heart. This will be our common journey. I am confident that we are drawing a fun, challenging and informative roadmap. I want to make this journey a memorable one for you in the future, and I hope you will all experience this experience completely.
It's a bit idealistic, but I'll try to align the company's agenda, technical strategy and your progress. That way, if you do a good job, everyone will benefit. I have a deep respect for your technical engineers and the code you developed.
1. The program is everything. The document is immediately followed by something. So, writing your code itself is a document, and it's good to use.
2. Test test test.
3. Unit testing should be rigorous. Bugs found in any unit test bear the double cost of developer costs. You know, I would rather give you more money than to find another QA company to test and let you fix bugs. But if your program is poorly written, then I have to divide the money by these people, and you can only get a small piece of cake.
4. Write good code to be able to read to the human, to the CPU use. Never bow to bad code.
5. Read more knowledge, not limited to the current work needs. If you only have the knowledge you need today and you don't know what you need tomorrow, you won't have any progress.
6. Go home and cook every time. Yes, it's really dinner. This will let you know the difference between cooking a recipe and creating a meal yourself. The former knows what is needed before cooking, and the latter is done according to what you have now ... That's a little bit different.
This is the biggest experience of my business. It's hard to come.
7. New ideas and good ideas (technology or products) can be generated anytime, anywhere. Please share with us.
8. Know that you all hate business people. I understand why. They want to sell things you can't make, they promise but they don't, they don't pay but they want something more. But a company runs without them and needs them to position the product. It's a hard job. But please tell me what you think, and I will play a buffer. If you want to be a good company, all the discipline can not be less.
9. Love the profession of your technician. You can spend a lifetime in the technology/development role and earn a lot of money, respect and happiness.
English Address: Http://blog.kapilkaisare.info/from-an-architect-to-a-programmer
What is the architect of the other family?