about · lately · live · notes · talks · writing · contact · thanks · support ·


live

🙌 I’m Geoff, an open source software engineer. I’m currently in Sydney, Australia. I’m observing the AEST timezone. Instead of writing and maintaining software on my own I’m inviting you to pair-program with me in my office. Let’s build software together. Be interactive, I love live suggestions, but please be kind and constructive. Live streaming can be scary. 💖

I currently work through a consultancy, but the opinions expressed publicly are my own and do not necessarily represent those of my clients unless otherwise stated. Do not quote me as “$company person Geoffrey Huntley said” – if I speak for a company, I will publish on its channels. This is my personal slice of the internet. Everything here is me and is my opinion.

schedule

The stream schedule is maintained in an online calendar you can subscribe to. Past stream recordings are on my YouTube channel. When I’m not broadcasting you’ll find me in the discord chat. Please drop in and say howdy.

code of conduct

Please read the Code of Conduct. As a project specifically setup to encourage folks to get involved further with open-source, I do not tolerate harassment of any kind directed towards myself, family or community members.

equipment

contributing

There’s a contributing guide that outlines how you can get involved. Let’s build software together. Be interactive, I love live suggestions, but please be kind and constructive. Live streaming can be scary. 💖

support me

Please follow me on Twitch and Twitter. Tell your friends, as by doing so you’ll help prove that there is demand for live coding on twitch and this activity worth doing. Twitch subs and bits are also greatly appreciated.

If you truly appreciate the work do on-air or in open source, please buy me a cup coffee. Things that take mental energy just work better with coffee! I (almost always) brew my own coffee unless I’m in the city in which case you’ll usually find me hanging out at Espressory.

Anyway, thanks for any support you can offer if you decide to.

operational safety

The 20th of December will go down as an iconic day in history. Robert E. Kelly, a political science professor at Pusan National University in South Korea, was explaining the ramifications of the impeachment of South Korea President Park Geun-hye live on the BBC in March when his two young children made their on-air debut. The clip quickly went viral and Kelly and his wife Kim Jung-A were soon the focus of media around the world.

Kelly told the Guardian that he wasn’t prepared for the spotlight the viral clip cast on his family. He said his daughter’s elementary school had to hire a guard to ensure no “weirdos” showed up, and he felt uncomfortable with many peoples’ assumption that his wife was his nanny.

“People were reading stuff into our relationship and, oh my God, I didn’t want to get near any of that crap, so we didn’t say anything”, he told the Guardian. “It was a comedy of errors, a family blooper. There was nothing to say.”

Whilst I live a somewhat public life, to ensure this doesn’t happen I’ve implemented safeguards to minimise the risks of broadcasting on the internet.

The line of defense is a strip of lights attached to my door frame that act as a traffic light to let folks know if a broadcast or video call/meeting is in progress. This simple system is extremely handy for communicating availability.

If you work remotely from your house as I do you should totally steal this idea - I did. When I jump on a call or I am broadcasting the light automatically changes to red and my children understand what it means as I’ve had the system in place for a couple years now.

“Hot” microphones are a recipe for disaster so none of my microphones are on unless I physically activate them

I use a dedicated control panel so that I can switch inputs via dedicated buttons and can fade to black instantly if the need arises. It is so important to have a big fat eject button, bumbling through systrays and application focus to terminate a stream is another recipe for disaster.

inadvertent disclosure

I have multiple systems in place (multiple-monitors, broadcasting under an isolated operating system account, automated privacy screen switcher software, a physical production controlpad) to reduce the likely hood of accidentally disclosing secrets whilst on the air. That doesn’t mean it cannot happen.

If you believe there has been inadvertent disclosure please get in contact with me immediately. I don’t have the resources of Google, Facebook or Mozilla but at minimum if you so desire, I’ll put your name in the end of show hall of fame credits and send you some swag in the mail. Thank-you.