1. Consistent Understanding In a large organization, we can think of a small team as a microservice. As early as 1967, Conway proposed the concept of the microservice. Conway argued that any organization designing a system will deliver a design whose structure is consistent with that organization’s communication structure. When developing complex systems, we usually split the system into modules.

The team I work with is building a ToB product that has considerable influence in its vertical. This article is a review of key events for the team, and also contains some personal reflections. 1. Be the Best in a Familiar Setting On the internet there is far too much shoddy content, and products that win broad attention and influence are few and far between.

1. How to Do Code Review Better Requirement Items Requirements for the committer Small granularity Atomicity With comments Tool checks Requirements for the reviewer First conventions Second logic & performance Third design Requirements for the team Reviewing the old to learn the new 2. Define a Code Review Checklist Requirement Items Naming Variable names

Collaboration is a journey. 1. Obstacles to Cross-Departmental Collaboration Resistance to collaborating on new business Gray areas in responsibilities Employees’ ability to collaborate Information asymmetry The management mechanisms for cross-departmental collaboration Misaligned goals and interests Limited resources 2. The Core Philosophy of Collaboration Win-win thinking An open mindset The three aspects at the heart of collaboration

In recent years, with the rise of single-page web applications, all kinds of frameworks have kept emerging. The front end has begun to enter a stage of engineering and componentization. Single-page web technology has expanded the boundaries of the front end, which can now also route and render pages without depending on the back end.