Product | technology drops

The author | composed of



Introduction: This article comes from the topic sharing published by Teacher Tao Wen in the internal, which has triggered a hot discussion among technical oranges. Sister Orange is here to share this topic with you. We look forward to reading Teacher Tao’s interpretation and sharing our views on the depth of technology at the end of the article.

Students are often challenged to work without technical depth. Many daily writing business students immediately nervous up. Start looking for evidence in your head that something you’ve done is “hard.”

In fact, if you prepare this question, you will not panic. In my opinion, technical depth can be derived from the following diagram:



The main task of technical students is to build a workable solution to solve a problem of users. With this theme, there are two things to do:

  • Operate and maintain the solution, and continue to solve the problem.

  • Insight into the change in the problem itself, or a better solution. Then, the existing solution is transferred to a new solution to better solve the problem.

The technical depth is in doing these two things “better,” which is an optimization problem:

For operations and maintenance work

  • Reducing labor costs in operations: for example, replacing labor with automation.

  • Reduce other costs of operation: for example, less machinery input, such as stability and safety construction reduces risk.

For research and development

  • Insight into new problems or solutions: data analysis, market research, new technology follow-up, etc. Enhance the attractiveness of solution to users. New experience – Old experience – Migration costs.

  • Short-term agility: The ability to rush out a version quickly because of familiarity with the API. Because of the familiarity with the environment, the ability to quickly locate bugs, etc.

  • Long term agility: architectural design, complexity management, etc.

  • The ability to provide unique solutions: autonomous driving, for example. The process of going from zero to one maximizes the appeal to users because few people offer competitive solutions.

Each optimization work, can do very deep

  • For example, you can spend a lot of time learning database principles and optimizing the efficiency of index searches, thereby reducing other operating costs.

  • You can also build traffic recording and playback technology to provide confidence in refactoring efforts. This improves long-term agility.

  • You can also hone your product insight. Proficient in data analysis, listening to users, and providing insight into the future evolution of the product.

  • You can also practice your ability to quickly debug, using various tools to quickly find performance bottlenecks after a crash. This is an ability for short term agility. It mainly tests whether to be familiar with the environment and ecology. So-called experience live.

When the judges ask you about technical depth, they are not asking you about the depth of your stack (for example, whether you know everything from pixel rendering to silicon purification), they are really asking you about your competitiveness.

There are two things you need to think about

  • Why at this point, the work I’ve done has proven to be stronger than other colleagues.

  • Why this capability is what companies need right now, which is called revenue. You can build guIs by hand in assembly, but the company doesn’t need the “technical depth” that is useless.

Hopefully, the next time you’re asked a technical depth question, you’ll take it easy.

END



               

Tao drops | chief engineer

In Didi, I have participated in infrastructure, reconstruction of core travel platform, construction of business center and other work. Currently, I am engaged in platform governance and customer service system, and am committed to reducing the unhappiness encountered in travel. Before joining Didi, he worked in agile consulting, test development, operation and maintenance platform and other fields for more than 10 years.