r41nbowcrash

never tried it myself, but you can take a look at the accompanying code "Your Code as a Crime Scene"

https://github.com/adamtornhill/code-maat

>My teammates have tons of experience

i think it's too early to judge these guys either positively or negatively. it might be that the friction you're experiencing at this point is a result of things like working with rotten code, them withholding the specific domain knowledge, etc. and what you take for your own incompetency in reality is someone else's mess dropped on your head.

Can be flickering between two equilibriums, that happens when we're close to a phase transition:

http://www.uvm.edu/~pdodds/files/papers/others/2009/scheffer...

>The greatest way to piss of managers and colleagues is to have a poor grasp on what they have told you or asked you.

That is if they have communication skills (which most people lack), share the same domain knowledge (usually the guy already knows the problem, and you'll be figuring it out in the next days, so there's no way you can even ask informed questions). Plus recall bias, plus confirmation bias, not to mention pure bullshitting, especially when things go wrong.

Dependence on memory is a system error. It means there's something wrong with the process, or the workplace lacks proper communication.

My default response to "I told you to...", is in every circumstances "no, you didn't". Until they know better.

>Can we at least conclude that our probabilities outperform bookmakers?

More like outperform the market?

Not sure if more precise probabilities outweigh the risk of ruin, if there's unbalanced amount of money backing each option.

>inventory management

That would be Lands of Lore. A single inventory for all the party members.

I remember liking the AI - all these different objects, complex, emergent behaviours, expressed usually in less than 40 lines of code. Clean, effective, with great bang to buck ratio.

If modding was high on their list of priorities, I'm pretty sure they would get it right.

Reminds me a bit from The Inner Product that basically said that context is the biggest hammer in the programmer's toolbox, and each layer of abstraction just adds more constraints.

It isn't the most common way of looking at it.

[1] http://twvideo01.ubm-us.net/o1/vault/GD_Mag_Archives/GDM_Jun...

It's worth to mention that being 1-2 years ahead of the programme gives you early successes, something to fall back when things go little rough later on.

No school, and no teacher in the world can make you feel "bad at math", if your mother taught you elementary arithmetic at the age of 5. Thanks mom.

That's not about Star Trek.

Weka: http://www.cs.waikato.ac.nz/ml/weka/

Lets you test dozens of different algorithms on a given dataset, to see what works and what not, in like one evening.

Also success stories from Kaggle competition: http://blog.kaggle.com/category/dojo/

>When the number of incoming stimuli is reduced, the mind gradually perceives finer details in the ones that remain. This is famously true of blind people, but you can consciously narrow your attention to the same effect.

Or starts hallucinating stuff (ganzfeld effect, Charles Bonnet syndrome)

"Open systems communicate and live. Closed systems do not communicate, become non-discerning, uninteresting and die." - Col. John Boyd