All of this is just opinion, only the code is known to be correct.

Like when liquid is turning to gas. There’s a state in-between that you know it’s going to be in, but not necessarily when. You have to guess and test your assumptions, and then re-calibrate.

Example of three “other” phases:

  • Boiling point — evaporate (ee-vap-or-it)
  • Freezing point — crystalline
  • Plasma

Active Learning Always:

You have to change and adapt your code intuitively. Instead of guessing why things work, try to break them and make them work in other ways. The more options for trial and error, the better. A lot of times data can be pulled out from other actions taking place, whether user generated, or system.

The more errors you see at first, the better.

--

--