But they're at least into the idea, according to a new survey. | "Game Boy development was interesting in that you were always coding with battery in mind." https://news.ycombinator.com/item?id=18873662
412,861 users with 67,008,585 bottles; world's most complete database of 2,084,420 wines; 5,317,790 free wine reviews;
autom. integration with 601,019+ professional reviews from 25 publications
Why our intuition about sea-level rise is wrong. Harvard geophysicist Jerry Mitrovica explains that climate change is not just about a global average sea rise.
Human gaming tactics draw analogies from the physical world to hide the underlying complexity (chunking), and enable the players to think at a higher level. AlphaGo isnt limited(?) by physical world analogies.
Common mistake in arch: Using functionality to id services ("Buying Stocks", "Selling Stocks", ...). Functional decomposition maximizes impact of change, is coupled to it. Better encapsulate change to insulate. Do not resonate with change. |
The conclusion is that you should never design against the requirements (or the features, or the use cases, or the user stories). What you must do instead is identify the smallest set of building blocks, call them microservices if you like, that you can put together to satisfy ANY requirement: present and future, known and unknown. There is a strong process angle of how you go about doing just that.
Identify areas of volatilities, and those you encapsulate in (micro)services. Then you implement the required behavior as the interaction between those services. A new requirement would simply mean a different services interaction, not a different decomposition, so now when the requirements change, your design does not.
https://www.infoq.com/news/2016/07/lowy-every-class-service?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
The limitations of backpropagation learning can now be overcome by using multilayer neural networks that contain top-down connections and training them to /generate/ sensory data rather than to classify it. (...) much better than previous approaches
zu einfach m Ethikcode=Konflikte m Gutverhalten eindämmen, Gründe egal; Blick für Missbrauchsmglk. (Risiko-Id für Negativ-Stakeholder), v.a. bei Tools für Minderheiten mit pol. Gegnern (Irreführung v Flüchtlingen, Adressen v Helfern, Ortsbestimmung v Schwulen, ...)
bspw. ANT Censuses of the Internet Address Space: https://ant.isi.edu/address/ | Almost optimal way to take a 1-dimensional array of bytes, and arrange them in 2 dimensions, such that bytes that are close together in a single dimension are also close in two dimensions
Computer scientists at MIT have developed a program called Helium that can automatically revamp and fine-tune old code, without needing the original source, in a matter of hours or even minutes.