Forwarded from Foolish TraceWind (fourstring | 当时只道是寻常)
Forwarded from RSS bot
人类或许可用肛门-直肠呼吸
http://jandan.net/p/108965
http://jandan.net/p/108965
煎蛋网
人类或许可用肛门-直肠呼吸
医学人员推开了一扇全新的大门，用类似于灌肠的手段来为呼吸困难的病人提供支持
Forwarded from RSS bot
大气模型错了：闪电风暴竟然是最大的空气净化器
http://jandan.net/p/108912
http://jandan.net/p/108912
煎蛋网
大气模型错了：闪电风暴竟然是最大的空气净化器
研究人员一度怀疑是仪器坏了
Forwarded from Hacker News
Waymo AV Freaked Out by Traffic Cones, Blocks Traffic, Evades Support Vehicles (Score: 101+ in 5 hours)
Link: https://readhacker.news/s/4LHWM
Comments: https://readhacker.news/c/4LHWM
Link: https://readhacker.news/s/4LHWM
Comments: https://readhacker.news/c/4LHWM
Jalopnik
Watch A Waymo AV Get Freaked Out By Traffic Cones, Block Traffic, And Evade Support Vehicles
Making cars drive themselves is very, very hard. Sure, we’ve come an awful long way since that Stanford-modified Volkswagen Touareg won the first DARPA Grand Challenge back in 2005, but we’ve still got a long way to go before full Level 5 autonomy. No matter…
Forwarded from The Sky Was Pink
UML comes from an era where Object Oriented (Obsessed?) Design was the whole world, and everything that wasn’t OOD was being forced to not exist. In this era, Architects would draw UML diagrams and cheap Indian code monkeys would do the coding, because we thought that code monkeys would be cheap and replaceable. This was perfect for the MBAs because programmers started to be annoying by not delivering on the expected deadlines, and claiming about the algorithms, the damned algorithms. We wanted to replace them with cheaper and less-whiny ones.
Turns out that the details of the system are in the code, not in the diagrams, and only the trivial parts of the system would be expressed in diagrams, and the devil is in the details. But this makes programmers non replaceable and fungible, because the better ones can express algorithms that the worse programmers will never understand. And many times, you need these better algorithms.
All this makes UML not anymore the silver bullet for bodyshops. The broken idea of hiring 1 architect and 100 code monkeys from the consultancy just doesn’t work, because the architect is not expected to dig in the details, and the 100 code monkeys will just make a mess of the details.
UML was dead on arrival when it ignored most of the details of Software Development. Doesn’t mean though that some parts of UML can be salvaged, such as sequence diagrams, state diagrams, or entity-relation diagrams. But trying to model in UML an arbitrary problem and solution is likely to become wrestling with the language to express anything minimally complex or different.
https://lobste.rs/s/aoolwb/has_uml_died_without_anyone_noticing#c_0vcc9e
Turns out that the details of the system are in the code, not in the diagrams, and only the trivial parts of the system would be expressed in diagrams, and the devil is in the details. But this makes programmers non replaceable and fungible, because the better ones can express algorithms that the worse programmers will never understand. And many times, you need these better algorithms.
All this makes UML not anymore the silver bullet for bodyshops. The broken idea of hiring 1 architect and 100 code monkeys from the consultancy just doesn’t work, because the architect is not expected to dig in the details, and the 100 code monkeys will just make a mess of the details.
UML was dead on arrival when it ignored most of the details of Software Development. Doesn’t mean though that some parts of UML can be salvaged, such as sequence diagrams, state diagrams, or entity-relation diagrams. But trying to model in UML an arbitrary problem and solution is likely to become wrestling with the language to express anything minimally complex or different.
https://lobste.rs/s/aoolwb/has_uml_died_without_anyone_noticing#c_0vcc9e
lobste.rs
Has UML died without anyone noticing?
43 comments
Forwarded from 心惊报
This media is not supported in your browser
VIEW IN TELEGRAM