Snail_Commando

https://en.wikipedia.org/wiki/MIM-104_Patriot#Failure_at_Dha...

Whether or not this can be attributed to technical debt, I don't know. But it is an instance of a software failure that resulted in death.

More cynically, I've noticed that it's a relatively benign form of hoarding. i.e. I get the quick dopamine rush of "oh this is interesting, now I have it" without, say, crowding up my living space with trinkets. With an abundance of storage that is essentially invisible to me when I don't want to think about it, I can keep what I want, when I want; often while fully aware that I'll never look at most items individually again. I think of it as a kludgey form of external memory / internet butterfly collecting. The only downsides I've thought of are: time frittered revisiting archives, the (small) transaction cost of tagging and placing items into the archive, and the externalized costs of maintaining the hardware.

Basically, trying to give an example of the grandparent's point. (i.e. fewer nucleotides to be flipped -> more likely that an important one will be). I agree that it was a poorly executed analogy. The metaphor I was trying to make is that on the 'vast field' a random single point mutation is probably going to land on an individually unimportant nucleotide, and in the 'narrow beach' (the smaller strand/higher geninfo density) an individually important nucleotide is more likely to be hit. I'm still probably not articulating my point well, sorry.

But I think your analogy is better for a subtly different point; describing how DNA replication works in a system, where stands can be selected out, errors corrected, and genetic information can be preserved at a systemic level.

The artillery that lands on the plain may strike an advancing unit, or it may fall (possibly harmlessly) between a set of advancing units. The artillery that lands on the narrow beachhead is more likely to hit a unit.

This analogy is far from perfect: sometimes mutations are good, which is one primary driver of evolution. Non-coding regions and/or "baggage to be refactored" (paraphrased great-great-gp comment) in DNA (the regions of the plain/beach not occupied by an advancing unit) can absorb "errors". Also, there are other types of mutations (insertions, deletions, ...), aside from the single point mutations that this analogy was attempting to help convey.

The point is: it's like bunching up a lot of important things over a few points of failure. If you increase "the genetic surface area", you lower the chance of the important thing getting hit.

On evolutionary scales, viable DNA has been selected with a lot of non-coding (and sometimes useful) regions, we know that if we reduce that down, we are more likely to be susceptible to fatal mutations on coding regions (e.g. a region that codes for a vital protein).

If you accept this, no matter how great We make this simulation (of objective physical phenomena and our best theorized non-human perceptions of these phenomena), this game is always false.

(For what it's worth, I'm not sure yet if I hold any firm viewpoints on this. The essay (at least partially) is an argument against reductionism, but I'm no philosopher; to be honest I'm still wrapping my head around the entire argument. I just think it's interesting to think about.)

Here is the essay if anyone is interested:

http://organizations.utep.edu/portals/1475/nagel_bat.pdf

In the set of nation state funded research facilities (e.g. funded by US Dept. of Energy, European Research Council, etc.) I'm willing to bet that most of the facilities are more often relatively near cities (greater than 150K pop). Many (high energy / high capital cost) facilities, employ on the orders of 1-10K staff alone.

[] (... and that Basic Science, High Energy Physics, Computational Science, Basic Tech, Corporate Research, and/or Public Policy/Economic/GeoPol research are the hard problem spaces you are alluding to...)

I was responding to the 'I'll trade this time now, for more time later' line of reasoning (which I believe is a false transaction). Not only should one recognize that each epoch is unique (in a child's life, in a relationship, in a career, etc.) and therefore not interchangeable with later epochs; but one should also recognize that "selfish" (OP's word choice) actions now are usually not offset by generous actions later.

I suppose one can recognize those tradeoffs and traverse "borrowing time" reasoning with a bit more self awareness, though not many do. Especially those that subscribe to the 'compress your 40 year career into a 4-10 year startup' meme without reading the fine print.

Epochs are not fungible, especially when raising children. Missing a toddler play at the beach for the first time cannot be reclaimed by sharing their first scuba lesson.

He covers his background, early computer games, the origins of Sim City, the Sims, as well as more abstract/high-level discussion of game design and simulation.

Some high level themes of the talk: using the computer as a modeling tool, simulation design, Will Wright's game design principles and philosophy, programming for two dynamic processes "the software" and "the player's model of the system", and traversal of possibility spaces in game design and simulation.

https://www.youtube.com/watch?v=CdgQyq3hEPo

It's excellent otherwise. Especially in that it doesn't romanticize "the lifestyle"; which is a rubbish cliché, endemic in many criminal enterprise films. Other films that I think are successful in this sense are: "City of God" (Portuguese title: "Cidade de Deus") and "Maria Full of Grace" (Spanish title: "María llena eres de gracia").

Protip: If your business model relies on "fear factor" you may have failed to satisfy the "completely legit business" specification.

http://arxiv.org/abs/1405.5563

Edited to steal more screenspace/add context:

Authors:

https://web.archive.org/web/20120402224250/http://193.189.74...

http://edge.org/memberbio/chiara_marletto

You may also be interested in this paper:

http://www.cs.berkeley.edu/~christos/classics/Deutsch_quantu...

Also, http://edge.org/conversation/constructor-theory