Discuz! Board

 找回密碼
 立即註冊
搜索
熱搜: 活動 交友 discuz
查看: 2|回復: 0

Secondly, the entire business code contains

[複製鏈接]

1

主題

1

帖子

5

積分

新手上路

Rank: 1

積分
5
發表於 14:30:33 | 顯示全部樓層 |閱讀模式
If it is manufacturer , it should follow the data format of manufacturer Display, if it is Manufacturer , display it according to the data format of Manufacturer After that, the company introduced new manufacturers, and then the development students were exploded - it was like artificially creating a code shit mountain! When a new manufacturer is introduced, firstly, the entire development chain from device data API docking to business logic processing to front-end page display needs to be modified accordingly;


Secondly, the entire business code contains a bunch of conditional judgments based FR Numbers on different manufacturers. , becoming more and more bloated and difficult to maintain. Development classmates are complaining, and their cooperation with product managers will naturally drop a lot. What’s the problem? When something goes wrong, you naturally have to figure out how to pass the blame. So is this a problem with product students or development students?







Personally, I think they all have problems, but the product is the source and the responsibility is greater. As a product manager, you should have business foresight. In this case, IoT devices are hardware devices.

回復

使用道具 舉報

您需要登錄後才可以回帖 登錄 | 立即註冊

本版積分規則

Archiver|手機版|自動贊助|z

GMT+8, 19:03 , Processed in 0.683875 second(s), 19 queries .

抗攻擊 by GameHost X3.4

Copyright © 2001-2021, Tencent Cloud.

快速回復 返回頂部 返回列表
一粒米 | 中興米 | 論壇美工 | 設計 抗ddos | 天堂私服 | ddos | ddos | 防ddos | 防禦ddos | 防ddos主機 | 天堂美工 | 設計 防ddos主機 | 抗ddos主機 | 抗ddos | 抗ddos主機 | 抗攻擊論壇 | 天堂自動贊助 | 免費論壇 | 天堂私服 | 天堂123 | 台南清潔 | 天堂 | 天堂私服 | 免費論壇申請 | 抗ddos | 虛擬主機 | 實體主機 | vps | 網域註冊 | 抗攻擊遊戲主機 | ddos |