倒点儿工作黑泥
强迫加班的结果就比谁能糊弄,反正公司压榨员工,员工能多把活当回事。
糊弄的结果就是需求文档也糊弄(式样记载大量错误,错误怎么了?反正客户会变需求的),开发也糊弄(bug多到修不过来因为一直走人一直来新人换了三批人不止,根本不需要为自己的代码负责。)测试更糊弄(我为什么要给你精细测?偶现性我报了,你打回来我要对策测100次,那我不报又能怎么样?)
国产的一些量产玩意为什么用不住,用着用着这坏那坏这反应慢那吭哧瘪肚,因为这产品的制造者把它弄出来的时候基本就是本着反正你压榨我那我糊弄得了的心情。 干好没好处,干坏不负责,那就这样,爱咋咋地。
日本人搞流程有一套精细的责任分配,你写的东西不对,下一轮的人给你揪出来了是要被指摘的。测试也是多方交叉进行,像性能压力这样的要详细日志的,所以成品质量稳定。单一功能压力测试500次能不偷工减料做完一条的测试有几个呢?外包出去的测试身上如果压着一天200条的任务呢?
假如我买车我是绝对不买把智能系统外包给我司的品牌的,糊弄出来的东西什么质量一清二楚,所有人都在那“差不多得了”,反正对付开车的时候系统崩溃出事创死的车主的也不是供应商。
煮的应该不浪费 优雅怎么算
I thought chain letter is something serial not parallel/concurrent and with something meaningful that need a chain of people/letters to reach a certain target you cannot directly reach.
What you described is more supposed to be named like pyramid letter, tree letter, fission letter, or multicast letter in my mind.
I didn't expect the toxic one. I thought it could be peacefully or something that can let people understand the initiators' concern.
Thanks for showing and explaining it for me in April 1st.
I have no idea about it. Do you know is there a museum/archive for a chain letter?
Can chain letters be used in political usages? Any examples?
"Safety is not a commodity that can be tabulated. It is rather a chronic value ‘under our feet’ that infuses all aspects of practice. "