RunPee Weekly Newsletter 21st edition (August 5th, 2020)

A top movie that’s topping out box offices at the Drive-Ins. Leave your fussy adulthood behind and catch the magic of being a Goonie again.

F Movies – What films FAIL at RunPee
The F scores range from Offensively Bad, work up to Entirely Disappointing, and peak at being a Non-Achievement. Someone was executed, or at least sacked. Here are the movies we threw to the lions.
Read more.

RIP Sir Ian Holm – Farewell to Bilbo, Ash, Father Cornelius, King Lear and more
What man has been both Frodo and Bilbo, a trickster and a king, a space priest and a deadly android? He also played a dignified scientist graciously toasting a last glass of whiskey in the face of death. Not a bad way to be remembered.
Read more.

Top Twenty Games on Star Trek – Including Poker, Dabo, 3-D Chess, Fizzbin, and Tongo
Why it’s impossible to get bored on a starship. People worked out the rules to the best games so you can play too!
Read more.

Classic Movie Review – Gremlins
A Christmas in Summer horror-lite classic to remind you what microwave ovens are REALLY for. Don’t feed your Mogwai after midnight!
Read more.

Weekly progress diary on RunPee:NX
We are rebuilding the RunPee app from scratch using Google Flutter. Here’s a brief report on our weekly progress:

User registration is the last major feature I need to implement before beta testing can begin. It isn’t sexy, but this is obviously a crucial feature in the app, and one that may surprise you in it’s complexity.

For all the non-programmers out there: writing code to do what is expected in an app is relatively straightforward; writing code to handle all the way things can go wrong is the hard part.

For instance, with user registration the user could type in the wrong email address, so that has to be accounted for. Or they get the right email address but they don’t have a data connection and so they can’t connect to the server, or perhaps the server is currently overloaded and doesn’t respond, or… You get the point.

Trying to account for every possible outcomes and then code a solution for each, without turning the code into a plate of spaghetti, is a hair pulling experience.