There are some interesting algorithms in simulation from Physics, Chemistry, and Engineering especially regarding Monte Carlo simulation: Heat Bath algorithm, Metro-Police algorithm, Markov Chain Monte Carlo, etc.

A negative effect could potentially kill a unit. We need to check if the unit is still alive after executing the effects and return early if the unit died. Example: a "poisoned" effect (it doesn't exist, at least yet) that damages the unit turn by turn.

Right now it's just a collection of links (the basic format of each entry is 'name - author'). It might be helpful to make room for 1-2 sentence explanations of the link, particularly as the list grows.

(PS this project is linked prominently from the website now)

The typeof operator, as used in type queries rather than Javascript, isn't documented, other than as used in documentation of other things, like type guards. Because it is overloaded from the Javascript operator, there can be lots of novice puzzlement.

If your reaction is "that can't possibly be", please look for yourself!

I'd provide a PR, but the wording should be much more precise and co

I think you could rename the project's file to follow the guidelines with lowercase and undescore. Just an improvement :)

`
Some file systems are not case-sensitive, so many projects require filenames to be all lowercase. Using a separating character allows names to still be readable in that form. Using underscores as the separator ensur

Long running issue:

• Link mf.com web to GH mindforger-repository.
• Links directly to sections in documentation.
• Add documentation section to mf.com, and link GH from there.
• Have discussions, ...
• Written with MindForger
• I don't have to sustain it mf.com
• beginner users will be scared by seeing all files
• make links to point to beginning of doc ~ section anchor
• review web

Simon Sinek, one of the great communicators of 21^st Century,
has a new book out called "The Infinite Game"
https://www.amazon.com/The-Infinite-Game/dp/B07DKHFTB7

Sinek borrowed the basic premise from James Carse's book "Finite and Infinite Games":

Some games are bounded and have a , like football or basketball or chess.
You see the **short-term immediat

Some descriptions for certain resources are very long, it'd be great if someone could go through all of these and shorten them. There shouldn't be too much of them.

Some examples:

• PHP: (The only proper) PDO tutorial
• Fullstack: freeCodeCamp curriculum

@lostdesign Maybe we should put some restriction on the amount of words that can be used for a resource?

With the recent release of Phoenix 1.5 🎉 https://elixirforum.com/t/phoenix-v1-5-0-released/30693
Now is a great time to go through this example/tutorial with a fresh pair of eyes and completely update it (including) links to code snapshots. We can also extend it to include auth_plug #25 🔐 and presence #32 🚀.

• Checkout master
• Create new branch e.g: `update-t

While fixing #444 in a recent commit to development, I realized that the explanation comes 2 files after the file that introduces the where and let keywords. It should come immediately afterwards, so this must be fixed in a major breaking change.