Blame Debate: Product, Development, or Operations, who should take the blame?

【51CTO.com original article】

The word "argument" is the most important. The eloquence and sophistry are based on emotion. The best argument is the workmanship.

Discuss the world, talk about the devil, the fallacy, the relativity, and don't talk about the winner and the loser;

During the period of the Three Kingdoms, Cao Wei, Shu Han, and Eastern Wu divided the world into three parts. Zhuge Liang used his eloquence to establish the three-part world.

From IT to DT, products, development, and operation and maintenance are the three pillars, and programmers are constantly expressing their ideal future with witty words.

When the system has problems after the project goes online, who should be blamed?

It could be that the product was not well thought out, the developers were lazy, or the operation and maintenance staff did not set up a good environment...

Debate entry points:

1. Who should take the blame for performance optimization ?

Who is to blame for the slow loading and crash of the product/website? Is it the code that needs to be optimized? Or the architecture level optimization? Or the cache design optimization? Who should consider this issue?

2. Who should be blamed for the product experience ?

Who is to blame for the unreasonable product buttons and missing page guides? Is it a product design problem? Or is it the developer's laziness? Or is it that the operation and maintenance team missed a function?

3. Who should be blamed for monitoring deployment ?

Who is to blame for server downtime and web attacks? Is it because the organizational structure and permissions are too large? Or is it because the early warning system fails? Or is it because of omissions in the development code?

4. There is always someone to blame, it depends on who is to take the blame, the core staff or the grassroots staff?

Development has evolved from the previous "waterfall process" to the current "iterative" agile development. What should be blamed? Should it be blamed?

Did taking the blame attract the attention of your leader, did it solve his troubles, and did it give you an opportunity to grow?

[[204797]]

Come to the right place. 51CTO has tailored a great debate for you. Let us speak out your opinions and express our unyielding determination to pass on the blame!

Debate topic : When the system has problems after the project goes online, who should take the blame?

Development + Operations perspective : It may be that the product is not well considered;

        Product + Operations perspective : It may be due to laziness in development;

        Product + Development point of view : Maybe the operation and maintenance did not configure the environment properly;

Time : 2017.9.26 10:00-17:00

Debate location : Q group 627843829

Debate format : free debate.

Jury : Backend - Wings of Memories, Cloud Computing - Enwei, Full Stack Craftsman - Mr. Cao

Selection criteria : The arguments for the topic are clear and logical.

Awards : (There are prizes for participating in the debate)

At the end of the debate, one best team and 10 best debaters will be selected.

Best team: Sunflower Boot Stick

Best debate partner: technical books

Participation Award: 200 yuan Big Cloud product bonus.

Scan the QR code to join the team

[51CTO original article, please indicate the original author and source as 51CTO.com when reprinting on partner sites]