/*

TODO: Greg and Mark ask themselves if it's right to put comments in code, discuss the the office light switches, and dig up age-old flame wars

*/

In which Greg and Mark have a ramblechat. Greg has a cathartic moan about avoiding a 'pile on' when trying to prioritise, and Mark reminisces about the good old days when 32K was enough for anyone. In between, Mastodon, Twitter, Slack and Teams come under fire - we reveal how the mild-mannered Mark was transformed into the superhero @revbingo, and why Greg is upset with a Twitter user who hasn't posted for nearly 10 years.

We are on Mastodon! - https://mastodon.technology/@withgregandmark

A beginners guide to Mastodon - https://lifehacker.com/a-beginner-s-guide-to-mastodon-1828503235

We're also on Twitter! - https://twitter.com/withgregandmark

Picade - https://shop.pimoroni.com/products/picade

Mark's poorly constructed Intel8080 emulator - https://github.com/revbingo/kotlin8080

The Universal Machine - http://www.boundvariable.org/task.shtml

Come along to Redevelop 2018 on October 12th, and be in with a chance of getting yourself on YDIW! - https://redevelop.io

Following the minor success of the first episode, Greg and Mark run a small retro to consider what they can do better and then turn to retrospective practices generally. What are they good for, how do you run them, and most importantly - can Indiana Jones help get the best out of the team?

And, as promised, we Google'd some retro formats for you and this came top! http://www.funretrospectives.com

Join the conversation - get in touch on Twitter: https://twitter.com/withgregandmark

In their first episode, Greg and Mark discuss the impact of ‘good enough’ - when the thing you’re doing is not entirely finished, but might be considered good enough to serve its purpose. Should you ship or should you carry on until it is complete?