<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mitch O&#39;Neill on Medium]]></title>
        <description><![CDATA[Stories by Mitch O&#39;Neill on Medium]]></description>
        <link>https://medium.com/@mitchoneill?source=rss-2186ff08b72a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*3UEXpWG0cOrKbN90dMXOiw.jpeg</url>
            <title>Stories by Mitch O&amp;#39;Neill on Medium</title>
            <link>https://medium.com/@mitchoneill?source=rss-2186ff08b72a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:24:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mitchoneill/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tools of the Trade]]></title>
            <link>https://medium.com/@mitchoneill/tools-of-the-trade-dbe52aa91928?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbe52aa91928</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[devices]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Sun, 23 Jun 2019 07:40:29 GMT</pubDate>
            <atom:updated>2019-06-23T08:52:04.892Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why I have a morning phone and like limited capability devices</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*O1MxMHgw0k0z4Btu.jpg" /></figure><p>Just as trade-based professionals devote time over their careers to acquire the right tools for the right jobs, I too think that knowledge workers should place a high priority on finding the hardware, applications, and processes that work best for them. When you’re spending 40+ hours on a pursuit, small improvements to both your quality of life and output can have outsized impacts over time.</p><p>Throughout the day I use many different devices. Often on my desk you’ll see a laptop, tablet, phone, and kindle. And for each of these devices I try to use them for as little overlapping functionality as possible, meaning for any function I need to perform there is ideally only one specific device that can carry this out. By limiting what each device can do allows me to easily compartmentalise and focus on individual tasks.</p><p>For instance, when I was a technical lead this involved me writing code as an individual contributor, managing a team, and communicating often with other parts of the company. Initially I did all of these roles purely on a laptop, but found that because this device can do all functions, I’d get distracted and mindlessly switch between roles. I’d be in the midst of writing code and a slack alert would come up, or I’d find myself opening a browser and typing in “gmai…”. It was too easy to context switch. Now, yes, of course you can do things to improve your focus and mindfulness, effectively minimising the problem through awareness and discipline, but that sounds hard. So instead, I decided to increase the effort needed to context switch by limiting the capability of each device. I purchased an iPad, this was the communication machine. It had email and slack and hangouts, and when I was using this device I was in communication mode. This allowed me to uninstall and sign out of all these services on my laptop, and focus on using the laptop purely for programming. Often times too I’d use them in different locations. Am I sitting at my desk on my computer? Great, that means I’m programming. Would I like to do some email? Sure, that means I have to get my iPad and move to the couch. Nice, simple, the constraints work.</p><p>I’ve extended this to my personal life as well. In the mornings using my phone is tempting; checking email, reddit, hackernews, watching youtube, it’s oh so tempting. But there are some things I like using on my phone in the early morning ; checking the weather, meditation apps, playing some music. So how do I use my phone in a way that I only use the good apps and not the bad ones? With self discipline and a strong will? Pfft, difficult. Instead, I have a seperate phone for my mornings. It’s an old iPhone SE, loaded up with only the good apps. My normal phone I keep in a box until I’m ready to leave the house. Once again this might seem like overkill, why have two phones (and one much less functional) when a single phone can do all of the things you need? But I’ve found that physically separating contexts, and having temptations further away than just a tap, allows me to more easily keep on track.</p><p>In this connected world, where all of your different devices can be connected and synchronised, there is the urge to maximise the functionality of each device by loading them up with as much capability as possible. But I’ve found that in many cases limiting the functionality of a device works well for me. I’m writing this on my iPad, a device which is largely set up for creating. If I wanted to check twitter or talk to friends on messenger, I can’t do that on this device, I’d have to go to the other side of the room and get my phone to do that, and often that is enough of a barrier for me to stop and think about what I’m doing, rather than getting in these automatic loops of jumping between functions. And this is why I love my kindle. It serves a single function. To read ebooks. No other distractions or capabilities. That’s what I strive for when thinking about how I use my devices.</p><p>I do this for the apps I choose to use as well. If I have email on a device, I make sure to use different apps for my personal and work emails. I even had two slack apps to separate my work based slack channels from personal ones. I have three note-taking apps ( <a href="https://agenda.com/">Agenda</a>, <a href="https://bear.app/">Bear</a>, <a href="https://www.gingerlabs.com/">Notability</a>) for different note-taking functions (Project based meetings, Text Notes, Visual or Handwritten notes) and two todo list apps; <a href="https://www.omnigroup.com/omnifocus">Omnifocus</a> for project based todos, <a href="https://www.dueapp.com/">Due</a> for routine based todos. This means that when I have a specific function I need to perform I go to the specific app the fulfils that and only that function.</p><p>This may sound complex, but in reality it just takes some reflection every once in a while to think through how you do things and what tools are suitable to achieve these things. I find that by getting these systems right it simplifies things as it’s always very clear which function you’re performing right now as well as forcing you to be more considerate when you need to context switch.</p><p><a href="https://mitchoneill.com/blog">Back to posts</a></p><p><em>Originally published at </em><a href="https://mitchoneill.com/blog/tools-of-the-trade/"><em>https://mitchoneill.com</em></a><em> on June 23, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbe52aa91928" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges to overcome in Voice UIs]]></title>
            <link>https://medium.com/@mitchoneill/challenges-to-overcome-in-voice-uis-f2bfc8c5d9fc?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2bfc8c5d9fc</guid>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Thu, 23 Nov 2017 20:49:50 GMT</pubDate>
            <atom:updated>2017-11-23T23:20:04.752Z</atom:updated>
            <content:encoded><![CDATA[<h4>Voice as a consumer interface is still in its infancy, with some issues to iron out before it truly hits prime-time</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xOIH0p9XPYZJkORii226Hw.jpeg" /></figure><p>With Black Friday upon us and Christmas around the corner, purchases of home voice assistants such as Google Home and Alexa are expected to be more popular than ever. While voice has been used as a complementary tool in other interfaces (e.g voice google search on a mobile phone), it really hasn’t existed purely on it’s own two feet in many consumer devices – meaning no screen to complement it.</p><p>During my short time developing Voice UIs for these home assistants I’ve realised that the design patters in Voice UIs feel very underdeveloped and lead to some issues in usability and retention. I don’t think this is terminal, I see this in a similar vein to when mobile apps first become popular – a lot of messing around and experimentation, eventually settling on some general principles common to most apps.</p><p>Below I’ve listed a few of the main problems I’ve experienced in developing for voice which aren’t really problems when creating visual UIs. Whether these are problems that can be solved, or just constraints that we have to live with and work around, I’m not sure.</p><h3>Feature Discoverability</h3><p>Give me a mobile app, tell me nothing about it, and I’ll figure it out through prompts and experimentation. Put a Google Home in front of me and it’s hard to figure out what to do. Google have currently dealt with this by having a “Discover” tab in their Google Home mobile app (visual), but users don’t want to have to read an instruction book.</p><p>A potential solution could be the app trying to teach you over time based on what kind of things you currently use it for (“Timer is set, did you know you can also ask X”), it will be tricky though to not make this intrusive and spammy. Another could be some kind of on-boarding, similar to how many visual apps do it now, although with the lower bandwidth of audio it may take minutes to explain, and users may not want to sit through or even remember the lesson a few days later.</p><h3>Flat Attention Hierarchy</h3><p>With visual apps you can scan and then focus on different things. Scroll, scroll, scroll, then tap into the thing that catches you eye. Components can be different sizes to convey importance. In voice, everything is given the same “attention priority”, meaning it’s all conveyed to you in a sequential, ordered fashion that you can’t tend to skip over as you’re not entirely sure the full extent of what you’re skipping over or skipping to.</p><p>One consequence to think about, this has huge ramifications for online shopping. Visually you can scan items very quickly, looking at 10s of options in a 30 second period and getting a pretty good idea of what’s on offer. This currently isn’t the case in voice interfaces, it takes a painful amount of time to get through each item and you can’t really know if you should skip or not until you’ve heard most of the speal. Further exploration of this is in the video below, starting at about 15 minutes in:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3MOwRTTq1bY%3Fstart%3D908%26feature%3Doembed%26start%3D908&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3MOwRTTq1bY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3MOwRTTq1bY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2176b0ac6a1503114ac6d6d615a5f61a/href">https://medium.com/media/2176b0ac6a1503114ac6d6d615a5f61a/href</a></iframe><h3>Side note: Listening speeds vs Reading speeds</h3><p>According to wikipedia:</p><blockquote>The average adult reads text at 250 to 300 words per minute. 150 to 160 words per minute is the recommended talking speed that allows for comprehension and understanding.</blockquote><p>On the surface this doesn’t seem like a huge divide, ~2x word speed. The one advantage though that text has is you can skim read it, not picking up 100% of the details but getting a pretty good idea of the content. Skim reading can be done significantly faster:</p><blockquote>Skimming is usually seen more in adults than in children. It is conducted at a higher rate (700 words per minute and above)</blockquote><p>Now we’re looking at an almost 5x increase in information transmission speed, albeit at a lower comprehensibility.</p><h3>Requires Active Intent</h3><p>Voice UIs currently require conscious and active intent outside of a few common tools that can be ingrained into habits (such as setting timers whilst cooking). Mobile apps on the flipside can be picked up and browsed in a more relaxed, less directed fashion. I’m not going to trounce into whether this is a good feature of mobile UIs or not, but the fact is that it leads to mobile being much stickier than voice in day to day usage. Like I said at the start this may not be a challenge to overcome but merely a constraint – that Voice UIs are more suited towards active tools than passive consumption.</p><h3>Retention</h3><p>All of the above leads to common situations where the Google Home or Alexa product is used for a week or two after purchase, but then is relegated to an ornamental role outside of a few key uses that people ingrain into a habit (I currently use my Google Home to make white noise and tell me the weather).</p><p>As <a href="http://fortune.com/2017/01/23/amazon-echo-google-home-voice-app/">VoiceLabs reported earlier this year</a> “When customers use a voice app on Alexa or on Google Assistant, there is only a 3% chance that they will become an active user in the second week, according to the report.”</p><h3>Bring it all together</h3><p>Voice UIs currently haven’t solved how to become a common interface that users naturally engage with on a common basis, nor encouraged users to learn more and expand their use of these interfaces over time (at the moment it seems to be the opposite). On the other hand voice as a tool, usually a convenient input method, integrated into other UIs seems to be taking off. An increasing proportion of google searches are now done by voice (coming from the phone).</p><p>Whether voice can stand on it’s own two feet or remains a tool integrated into visual interfaces, only time will tell.</p><p>Let me know your thought in the comments (<a href="https://twitter.com/mitch_oneill">or get in touch with me on twitter</a>). These are just my initial underbaked thoughts used as a prompt for more thought and discussion throughout the community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2bfc8c5d9fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Interesting Product At The Apple Event]]></title>
            <link>https://medium.com/@mitchoneill/the-most-interesting-product-at-the-apple-event-ecd1e873dcd?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecd1e873dcd</guid>
            <category><![CDATA[siri]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[airpods]]></category>
            <category><![CDATA[apple-watch]]></category>
            <category><![CDATA[iphone]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Mon, 18 Sep 2017 09:05:13 GMT</pubDate>
            <atom:updated>2017-09-18T09:36:18.616Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDN-pbpmsJYaIZP1IKjaQQ.png" /></figure><p>It redefines how we interact with technology. Moving us ahead in capability. The software still has some catching up to do and use cases still left to be discovered.</p><p>But it’s here.</p><p>An Apple Watch with a cellular connection.</p><p>Honestly what were you expecting, iPhoneX? Ohhh what a lovely OLED you have, and the phone body is a bit smaller. I don’t care how great you are iPhone, because I’m walking out of the house without you. I’m leaving you stuffed in my bag until I’m unable to do some mobile task without a screen, and even then I’ll probably use the totally amazing, multi-tasking ready, full work station in a slim and easy to use design aka iPad Pro.</p><p>Back to the watch…</p><p>And you know what, this isn’t even about the watch. It’s about AirPods and Siri and how much of a weirdo you’re going to be when you start talking to yourself all day.</p><p>Now that the phone has been made non-essential, how will our behaviours change? When will it be acceptable to talk to someone with your headphones on? <em>“It’s ok, I can hear you, this has audio passthrough!”</em>. Hell, some earbuds now have features that help you <a href="https://hereplus.me/">hear conversations better</a>. When will you be able to address Siri or Alexa in a conversation as seamlessly as you address others in the group? Or will it be some other yet unknown interaction method?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XV8Kf1ACFl0ODfYop3wnwg.jpeg" /><figcaption>I hope you liked this scene, because you’re going to be seeing it a lot more from now on.</figcaption></figure><p>Ambient computing, the next frontier. Or maybe it’s ubiquitous computing. Or… pervasive computing? How is this next wave of tech going to break existing societal conventions? Just like 20 years ago having a group of friends spending their time together, heads down, staring at black rectangles would have been unthinkable, what today do we consider ill-mannered or unseemly that will become the norm before our eyes?</p><p>To me the significance of the cellular Apple Watch is that it’s a step towards the relegation of the phone, and therefore towards a new way we’ll have to interact with technology.</p><p><strong>Career tip of the week</strong>: If you’re up for it I think having the ability to solve these new problems will be quite valuable.</p><p>Don’t forget to clap if you liked this story. Loud enough so your ambient device can hear it and translate it into a Medium Like and Hi-Five or whatever they’re doing these days. Also can someone help me use my Google Home? I don’t want to be left behind in this technological epoch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecd1e873dcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native for Web]]></title>
            <link>https://medium.com/@mitchoneill/react-native-for-web-16c5c96f7165?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/16c5c96f7165</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Sun, 09 Jul 2017 04:35:06 GMT</pubDate>
            <atom:updated>2017-07-09T05:52:32.212Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using React and React Native in a single, shared codebase</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*KM40lo-izQCPWcHFobcLuA.jpeg" /><figcaption>Sometimes there’s lots to share between web and mobile apps</figcaption></figure><p>If you’re building a react app that is intending to have mobile and web versions, <a href="https://github.com/necolas/react-native-web">react-native-web</a> may be for you. Even if you’re not intending on using the <a href="http://necolas.github.io/react-native-web/storybook/?selectedKind=Components&amp;selectedStory=ActivityIndicator&amp;full=0&amp;down=0&amp;left=1&amp;panelRight=0">shared components</a> or styles, being able to share functionality (state management, fetch, etc) is a huge win for productivity and maintainability.</p><p>The <a href="https://github.com/necolas/react-native-web">github repo</a> has a good overview on what react-native-web is, so I’ll leave that to the experts, but what I will give you are a few things I’ve learnt along the way that have helped me out.</p><h4>Setup</h4><p>I haven’t completely worked out the best way to get a project going. There are <a href="https://github.com/grabcode/react-native-web-starter">starter kits</a> which, although I haven’t tried, look like the best way to get started.</p><p>With that said (and before knowing the above) I love create-react-app so I ended up initialising a standard react repo with that, created another repo with react-native init and then carefully merged them together with <a href="http://meldmerge.org/">meld merge</a>. It went fine and works, but took an hour or two to figure out, plus I later ejected to get access to the webpack config which lessens the advantages of using create-react-app. In conclusion, I recommend going with a starter kit, although I suspect create-react-app will full integrate into this at some stage (it’s latest release supports .web.js files).</p><h4>Shared API Libraries</h4><p>react-native-web provides a lot of <a href="http://necolas.github.io/react-native-web/storybook/">shared components and apis</a>, but there are a few that it doesn’t cover which other libraries do.</p><p><strong>1. Storage: </strong><a href="https://github.com/sunnylqm/react-native-storage">react-native-storage</a></p><p>Cross-platform storage is a bit tricky. The browser’s <a href="https://developer.mozilla.org/en/docs/Web/API/Window/localStorage">localStorage</a> is synchronous but the mobile version of it, <a href="https://facebook.github.io/react-native/docs/asyncstorage.html">AsyncStorage</a>, is as the name suggests… asynchronous. This means you can’t simply create a wrapper to use localStorage for web and AsyncStorage for the rest, because one returns the actual stored object and the other returns a promise. <a href="https://github.com/sunnylqm/react-native-storage">react-native-storage</a> is great solution to this, it turns both into promises so you can call storage from anywhere and get a promise back. If you’re using redux and react-native-storage, then learn something like <a href="https://github.com/gaearon/redux-thunk">thunk</a> as redux by default will yell at you if you try to do async actions with it.</p><p><strong>2. Navigation: </strong><a href="https://reactnavigation.org/">ReactNavigation</a></p><p><a href="https://reactnavigation.org/">ReactNavigation</a> is great for navigation on mobile, and also works on <a href="https://reactnavigation.org/docs/guides/web">web</a>. I couldn’t actually get it working on web, and only being able to use the routers and not the navigators is a bit of a drawback, so I’m waiting for some more documentation about it.</p><p>My interim solution was to use ReactNavigation for the mobile navigation and <a href="https://github.com/ReactTraining/react-router">react-router</a> for the web. This just means wrapping each app in its’ specific navigation library and writing a navigation utility that would use navigator(screenName) on mobile and browserHistory.push(screenName) on web. Works well, is simple and easy to setup, and is nicely abstracted away from the rest of the app.</p><h4>Productivity</h4><p><strong>1. Hotloading</strong></p><p>One thing I noticed about ReactNative in general is that even if you have both the iOS and Android simulators up, only one will hot reload. I’m not sure if this is getting fixed but there’s a straightforward work around at the moment, which is running the react-native dev server on two ports (and pointing iOS at the second port you set up), <a href="https://github.com/ethercreative/react-native-tips/wiki/React-IOS-&amp;-Android-simultaneous-device-development">here are the instructions</a>. I originally thought having all three platforms hot reloading would be awesome for development, but I’ve found myself mostly only having one platform up at a time, or web + one mobile at best.</p><p>There is a use I have found for hot reloading all three platforms though, and that’s when you want to demo this system’s capability. You can talk about how productive this workflow is until you’re blue in the face, but simply changing a line of code and showing all three apps changing simultaneously gets your point across more succinctly.</p><p><strong>2. Loading your dev environment</strong></p><p>There can be a lot to set up each time you want to develop. Start up two servers, start up the iOS and android emulators, wait a minute for the android emulator to load then run react-native run-android. I recommend scripting the process. I used <a href="https://www.alfredapp.com/">Alfred App</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fm-sPfJFE7fE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dm-sPfJFE7fE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fm-sPfJFE7fE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/38be9487c181be528675e0b93c1cea8d/href">https://medium.com/media/38be9487c181be528675e0b93c1cea8d/href</a></iframe><p>So that’s my initial roundup. With this being a reasonably new and low documented library I was a little worried about spending a lot of time struggling against it to get things working. Whilst you need some experience in the react stack (including an understanding of webpack and babel), and will have to solve some problems without having a top quality walkthrough to reference, overall I’ve found this structure to be a pleasure to work with and unparalleled in output.</p><p>This is a new space and best practices and processes are still being figured out. Discussion and disagreement will be essential to pave the way to having strong resources in place that we can point to. If there’s any knowledge you want to share or parts you disagree with, I encourage you to get involved, and we can all figure this out together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16c5c96f7165" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NSW paid over $337 million for 2.5 hours of energy today.]]></title>
            <link>https://medium.com/@mitchoneill/nsw-paid-over-337-million-for-2-5-hours-of-energy-today-551dfce9802d?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/551dfce9802d</guid>
            <category><![CDATA[australia]]></category>
            <category><![CDATA[electricity]]></category>
            <category><![CDATA[energy]]></category>
            <category><![CDATA[climate-change]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Fri, 10 Feb 2017 10:28:07 GMT</pubDate>
            <atom:updated>2017-02-11T04:12:36.720Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhgFDVTFORo2WmvKg87ORg.png" /><figcaption>Source: aemo.com.au</figcaption></figure><p>High temperatures today in NSW caused energy demand to spiral towards record highs, testing the grid and the generation capacity of the region. According to the market operator <a href="http://nem.mwheeler.org/notice/NEMITWEB1_MKTNOTICE_20170210.R57396">there was load shedding</a> for 75 minutes with a max load of 310MW shed. More may have been needed if it wasn’t for <a href="https://twitter.com/Ausgrid/status/829932076719693825">widespread outages</a> naturally reducing demand as well as facilities being instructed to fall back to backup power generation:</p><figure><a href="https://twitter.com/CanberraAirport/status/829929966011719680"><img alt="" src="https://cdn-images-1.medium.com/max/483/1*8C5cYUFpeDEgnHbDNT8dVQ.png" /></a></figure><p>Officials pleaded with consumers to use less energy during the peak period, expecting their customers to do this out of the goodness of their heart and to help out their mates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*mab2DsRfOYfrnxbLVvRyAA.jpeg" /></figure><p>The national electricity market is broken. High prices in QLD last month bankrupted an <a href="http://reneweconomy.com.au/solar-focused-retailer-urth-energy-goes-into-administration-19753/">energy retailer</a>, SA and NSW have failed under peak demand and VIC is forecast to join the generation shortfall when <a href="http://www.businessinsider.com.au/hazelwood-victorias-biggest-coal-fired-power-station-is-closing-in-4-months-2016-11">Hazelwood is decommissioned</a>. Retail prices will continue to rise (someone has to cover this $337 million) and the level of service will drop — like asking your customers to turn their air-conditioners off in 40° heat yet having no demand response system to actually incentivise this behaviour.</p><p>There is light at the end of the tunnel though. A next generation grid is within our grasp, where intelligence, automation and flexibility are key. Where consumers are allowed to participate on both sides and get a fair price for the services they provide. The main blocker to this transition has been the will to execute on it, but as these system failure events happen at a growing frequency the environment will emerge for these new structures to come into play.</p><p>Stay tuned.</p><p>Edit: I’ve now put up an early stage tool up that exposes the true cost of energy generation in realtime. Would love your feedback. It’s at <a href="http://isenergyexpensive.today/">isenergyexpensive.today</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=551dfce9802d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BOM’s storm achieve is a national treasure]]></title>
            <link>https://medium.com/@mitchoneill/boms-storm-achieve-is-a-national-treasure-ad90d2c37ab7?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad90d2c37ab7</guid>
            <category><![CDATA[history]]></category>
            <category><![CDATA[weather]]></category>
            <category><![CDATA[science]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 13:42:45 GMT</pubDate>
            <atom:updated>2017-02-09T13:49:22.086Z</atom:updated>
            <content:encoded><![CDATA[<p>BUNBURY, 1961–07–26, Observation: “Gust in the arvo, freaky in nature.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7XKNvwTAotFLTVOZYNsSjA.jpeg" /></figure><p>Australia’s Bureau of Meteorology has a little database tucked away in the corner of their website, the <a href="http://www.bom.gov.au/australia/stormarchive/">Severe Storm Achieve</a>.</p><blockquote>“ The Severe Storms Archive contains data relating to recorded Severe Thunderstorm and related events dating back to the 18th Century. ”</blockquote><p>And it really does has observations going back to the 1700s. It also includes the type of event, geolocation, and one extra amazing field: comments from the public.</p><blockquote>“ Due to the relative scarcity of robust observation systems across the country, …it is necessary to utilise information that can be gleaned from all possible sources. This often requires the use of subjective information gathered from the public impacted by the event (e.g.<em> the hail was the size of cricket balls!</em>)”</blockquote><p>These observations vary wildly from undecipherable half sentences to absurd stories of death and chaos. Some of my favourites listed below.</p><blockquote>Chetwynd, 1861–07–01<br>Tornado</blockquote><blockquote>Large trees torn out of ground, hut destroyed. 2 women &amp; 6 men &amp; baby lifted into the air; one man carried 70 yards, died later. Tools from hut found 2.5 miles away. Loud roar/rumbling heard, ”terrific” lightning and “sheets of water”.</blockquote><blockquote>Beverly, 1962–01–08<br>Wind</blockquote><blockquote>“ROOF OFF”</blockquote><blockquote>Collie, 1960–04–05<br>Tornado</blockquote><blockquote>“Tornado through Jarrah forest near Lyall’s Mill, 240m wide for 30km. The estimated volume of timber useful for milling would be about 10000 loads of mill logs, 3000 poles and 18000 lengths of mine timber, enough for a year’s work at the local mill.”</blockquote><blockquote>Adelaide, 1851–11–08<br>Lightning</blockquote><blockquote>“A bull valued at 100 pounds was killed by lightning.”</blockquote><blockquote>Brisbane, 1860–12–03<br>Hail</blockquote><blockquote>“Severe hailstorm during the afternoon in Brisbane; pieces of ice fell with great violence from the northwest quarter and did much damage.”</blockquote><blockquote>Jimna, 1869–01–22<br>Tornado</blockquote><blockquote>“Fiercest storm ever experienced occurred in the evening; Every tree in a track 7 or 8 miles long and 400 yard wide was blown down. Loud lightning and vivid thunder.”</blockquote><p>More here: <a href="http://www.bom.gov.au/australia/stormarchive/">Severe Storm Achieve</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad90d2c37ab7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Micropayments, Bitcoin and High Risk Demos: My PyconAU 2016]]></title>
            <link>https://medium.com/@mitchoneill/micropayments-bitcoin-and-high-risk-demos-my-pyconau-2016-c796ebf0714?source=rss-2186ff08b72a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c796ebf0714</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Mitch O'Neill]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 06:33:22 GMT</pubDate>
            <atom:updated>2016-12-04T06:33:22.799Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><strong>tldr; Pycon was fun, I did some talks tangentially related to python:</strong><br>* 402: Payment Required | <a href="https://youtu.be/OvJpWt5gapQ">Youtube</a> | <a href="https://speakerdeck.com/mitchoneill/402-payment-required-micropayment-and-iot">Slides</a><br>* High Risk Demos Ep1 …| <a href="https://youtu.be/xJ1-QdatS9Q?t=50m29s">Youtube</a> | <a href="https://speakerdeck.com/mitchoneill/high-risk-demos-ep1">Slides</a></p><p>Last year’s PyconAU was my first python conference (and conference in general) and I was excited to come back this year to see what’s new in the python community and contribute a bit back.</p><p>The Reposit dev team travelled down to Melbourne and got to spend some time hanging out and brushing shoulders with teams from slightly bigger organisations.</p><h3>Lachlan Blackhall on Twitter</h3><p>The @RepositPower power engineering team teaching the @facebook engineering team how its done at #pyconau.</p><p>The main talk I did was in the IoT Miniconference where I focused on micropayments and open protocols that could allow for transfer of payments as easily as HTTP does for transfer of data. Although a solid implementation of this is very far away, rather than just talk abstractly about the ideas I showed some working demos using the bitcoin blockchain and layers ontop of it (one of the examples is <a href="http://storage.mitch.fyi/">storage.mitch.fyi</a>). <a href="https://youtu.be/OvJpWt5gapQ">Youtube</a> | <a href="https://speakerdeck.com/mitchoneill/402-payment-required-micropayment-and-iot">Slides</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOvJpWt5gapQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOvJpWt5gapQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOvJpWt5gapQ%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d7b68fcd37803779f32f909e5e42a75/href">https://medium.com/media/6d7b68fcd37803779f32f909e5e42a75/href</a></iframe><p>One of the demos in the talk was to make small payments to many devices through an aggregator and in return they would ping my site and report their results. Turns out an owner of one of the devices saw the talk, checked their logs and noticed their device was one of the participants in the demo.</p><h3>Justin Camarena on Twitter</h3><p>@mitch_oneill @balajis @21 the awesome thing about this is you actually pinged mine. Pretty cool...</p><p>Over the past few weeks I’ve been experimenting with transferring small amounts of data between devices with sound. A quick implementation of this is to use <a href="https://github.com/jleb/pyaudiohttps://github.com/jleb/pyaudio">PyAudio</a> and <a href="https://github.com/Katee/quietnet">Quietnet</a>. Even for a basic implementation it works surprisingly well, to the extent that you can transmit from devices as low powered as earbuds. So I got up on stage for the lightning talks and did exactly that, transmitting data between my earbuds and microphone then decoding the string onto the screen. Everyone was a bit dubious as to the likelihood of it working (and I may have helped reenforce that position) but I was actually pretty certain it was going to work in that environment, and if it failed audiences at lightning talks are very forgiving. <a href="https://youtu.be/xJ1-QdatS9Q?t=50m29s">Youtube</a> | <a href="https://speakerdeck.com/mitchoneill/high-risk-demos-ep1">Slides</a></p><h3>Sam 北島-Kimbrel on Twitter</h3><p>Oh nooo (oh yesss) #PyConAU</p><h3>Katie McLaughlin ✨ on Twitter</h3><p>TLDR slide, because I can&#39;t tweet a live demo. #pyconau AND IT WORKED! THE DEMO WORKED!</p><p>All in all was a fun weekend, some of my favourite talks I saw are below.</p><h3>Next Day Video on Twitter</h3><p>pyconau Working with real-time data streams in Python - Lachlan Blackhall https://t.co/aKOPn9SBwK</p><h3>Katie McLaughlin ✨ on Twitter</h3><p>Hey, it&#39;s @freakboy3742 and his @PyBeeWare related keynote! https://t.co/YPzlVKYNJe #pyconau</p><h3>Next Day Video on Twitter</h3><p>pyconau Hitting the Wall and How to Get Up Again - Tackling Burnout and Strategies for Self Care https://t.co/rO36xLsp24</p><h3>Katie McLaughlin ✨ on Twitter</h3><p>It me! #pyconau https://t.co/yDzMmWCYsN</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c796ebf0714" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>