<?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 Ed O’Reilly on Medium]]></title>
        <description><![CDATA[Stories by Ed O’Reilly on Medium]]></description>
        <link>https://medium.com/@edwardtoreilly?source=rss-d068db47c1b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N87UUSxd_4ADIeV4ed4KVw.png</url>
            <title>Stories by Ed O’Reilly on Medium</title>
            <link>https://medium.com/@edwardtoreilly?source=rss-d068db47c1b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:51:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edwardtoreilly/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[What’s the Story Point anyway?]]></title>
            <link>https://medium.com/nona-web/whats-the-story-point-anyway-529f701f172e?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/529f701f172e</guid>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 08:51:00 GMT</pubDate>
            <atom:updated>2021-02-23T11:40:42.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xwZOltIx_u5cYvOR.jpg" /></figure><p>I had a great chat with a developer recently about story points and whether they have any value. We spoke about how they’ve been used at his companies, past and present, and how we use them at Nona.</p><p>I realised in that conversation that there may be some useful nuggets I can share from our many years of trying to apply agile effectively and how we get value from using Story Points.</p><h3>What are story points?</h3><p>Surprisingly (or maybe not) there isn’t an agreed upon universal definition of the story point and giving that phrase a ‘google’ will turn up a variety of results which differ in important ways.</p><p><strong>I like the </strong><a href="https://www.scrum.org/resources/blog/why-do-we-use-story-points-estimating"><strong>story point definition</strong></a><strong> here by Derek Davidson:</strong></p><p><em>“A Story Point is a relative unit of measure, decided upon and used by individual Scrum teams, to provide relative estimates of effort for completing requirements”</em></p><p>The key part of that is <strong>“a relative unit of measure”</strong>.</p><p>That’s essentially what it comes down to. Ignore everything else and focus on the fact that we’re trying to measure something and we’ve elected to do so relatively.</p><p>We’ll get into why below.</p><h3>What do we need to measure and why?</h3><p>Simply put, stakeholders at the least, and likely ourselves as well, are interested in <strong>how long particular pieces of work and entire projects full of work will take</strong> to complete.</p><p>However inconvenient this truth may be, one can understand how that is a useful piece of information to have regarding a project that needs to be delivered at some point.</p><p><strong>Problem 1:</strong></p><p>We can be as agile as we want to but someone, somewhere needs to have at least <strong>a good approximation of when this will be completed</strong> and some hope that the process used to arrive at this estimate is <strong>reasonably accurate and fit for purpose</strong>.</p><h3>Why Story Points? Just estimate time in days?</h3><p><strong>Problem 2:</strong></p><p>Great question… why do we use a relative measure? Surely if the objective is to have some kind of idea how long something will take, then the best measure is just “how long will this take in hours/days/weeks”?</p><p>We <strong>humans</strong>, however much we protest this fact, <strong>are</strong> <strong>terrible at estimating how long things will take</strong> to do.</p><p><strong>Problem 3:</strong></p><p>Particularly difficult things that we <strong>haven’t done before</strong>. Which is usually what software development involves.</p><p><strong>Estimation takes long</strong>. It’s an arduous process, it is very time consuming, it can be highly stressful and at the end of the day <strong>doomed to be wrong anyway</strong>?</p><p>It feels like there may be a better way to spend this time.</p><p><strong>For example:</strong></p><p><strong>Situations change.</strong> Teams change. Environments change. Coding styles change. These changes affect how long it will take to complete a task in various scenarios rendering previously mildly inaccurate estimates, wildly inaccurate.</p><h3>So how does measuring relatively help?</h3><p>The big idea here is that while humans are terrible at estimation, we’re not too bad at relative estimation. Given two tasks or objects, we’re pretty good at comparing them to one another.</p><p>“Will it take longer to add the login form or the signup form? How much longer? Roughly twice as long? Or only half as long?”</p><p>“Will it take longer to build the search feature or the list posts feature?”</p><p><strong>Personally, I’d be happy to stop there:</strong> <strong>Or maybe just a little further than that:</strong></p><p>These comparisons we can do reasonably quickly and more accurately than we can actually estimate their individual times. So we can begin by setting a baseline.</p><p>This is a very small thing: “adding a button”.</p><p>In relation to this very small thing: This is a very big thing: “filtering search results”.</p><p><strong>Take for example:</strong></p><p>We can do these estimates quickly! We don’t find this difficult to do! Over time <strong>we’re actually pretty accurate with these comparative or relative measures.</strong></p><h3>So what’s the point of the story point?</h3><p>Story points allow us to accumulate measures of relative size into number sets that can be handled more effectively. While one cannot sum a “big” and a “small” together to arrive at a final number if we assigned a ‘Point System’ to each value then we’d be able to do so more easily.</p><p>Now if we had sized the stories in a sprint with our team and these had the following size: 2 very small tasks, 3 small ones, 5 medium ones, 2 big ones and 1 very big one.</p><p><strong>We’d be able to say:</strong></p><p>(2 x 1) + (3 x 2) + (5×3) + (2 x 5) + 8 = 41</p><p>And that would be our estimated “velocity” in Story Points for that team!</p><p><strong>There are a number of common mistakes I’ve seen teams make that are listed below:</strong></p><ol><li>Spending too long estimating.</li><li>Not understanding / sharing / explaining that these are relative measures.</li><li>Not updating estimates when people are sick or when teams change.</li><li>Putting too much pressure on the team to reach a certain number of points such that they begin inflating points to meet targets without actually delivering more work.</li></ol><p>We could track how many points we actually end up completing each ‘sprint’ or iteration and eventually, for the same team, work out how many points we complete on average.</p><p><strong>For example at Nona we’ve dealt with the above mistakes as follows:</strong></p><ol><li>Too long</li></ol><ul><li>Emphasise that these are instinctual and not to be deliberated for too long.</li><li>Be sufficiently prepared for ticket estimations through doing enough refinement.</li><li><a href="https://www.planitpoker.com/">Use a tool like planitpoker</a> to speed things up.</li></ul><p>2. Lack of understanding</p><ul><li>Ensure that the full team has a solid education in Agile.</li><li>We recommend the book <a href="https://www.goodreads.com/en/book/show/45280021-clean-agile">Clean Agile</a> by <a href="https://twitter.com/unclebobmartin">Robert C Martin</a> and nearly everyone at Nona has read it.</li><li>Speak about <strong>why </strong>you are doing each agile meeting often.</li><li>Share responsibility for running meetings with every member of the team to ensure buy in and proficiency with the process.</li></ul><p>3. Updating estimates.</p><ul><li>We communicate often and honestly with our clients and within our teams, constantly refining our estimates and letting our stakeholders know how changing situations have impacted these.</li><li>We take a proper look at our sprint half way through and ask ourselves if we’re still on track, if anything needs to change, etc.</li></ul><p>4. Too much pressure on the team</p><ul><li>We communicate regularly that points are not the key measure. Real delivered value over time is.</li><li>We have fostered a culture of trust and accountability such that development team members aren’t incentivised to lie about progress or inflate points for any reason.</li></ul><p>I usually give it about 3 iterations before a team starts developing a roughly accurate measure of their story point capacity. After that time one can start being reasonably sure of the average.</p><p><strong>Great question… Ed…</strong></p><h3>How do teams often get this wrong?</h3><p>Each one of these is imminently solvable and have nothing to do with whether story points are a valuable tool or not.</p><h3>What about the longer term — project length estimates?</h3><p>Once one has written down all of the requirements for a project one can apply some very loose estimates to ALL the remaining tasks in a project. These are normally not very finely broken down — so the estimates will be in the HUGE or VERY HUGE category.</p><p>E.g. Complete payment functionality = 40 points.</p><p>Summing everything that remains and dividing by the average points completed in a sprint and then adding a sprint or two for unknowns, changes, cleanup will arrive at what is generally quite an accurate measure of the time remaining in a project to arrive either at the end or at a predefined milestone.</p><p>It is worth noting that this estimation becomes more and more accurate over time. As the bigger chunks of work are broken up into smaller pieces, and the team’s velocity becomes more certain, the accuracy of the estimate improves.</p><p>This makes it a very useful measure over time for when the project will actually be completed and also serves to clearly illustrate the effect on the timeline of adding or removing features from the roadmap which can make it a great discussion point with your stakeholders about priority and timeline.</p><p><strong><em>Nona helps funded founders accelerate their software projects. If you’d like to soundboard your tech or your team, </em></strong><a href="https://calendly.com/carl-nona/30-min-catch-up"><strong><em>book a </em></strong></a><a href="https://calendly.com/ed-nona/30min-meeting"><strong><em>consultation</em></strong></a><strong><em> with me and we can chat through it!</em></strong></p><h3>So what do you think?</h3><p>I’d love to hear your opinions on Story Points, how you love or hate them, how you’ve used or abused them? Please get in touch!</p><p>If you enjoyed this article I’ve recently written posts on <a href="https://blog.nona.digital/why-we-ditched-user-stories-for-given-when-then/">Given When Then</a> and <a href="https://blog.nona.digital/remote-stand-ups-agile-scrum/">how our stand ups have changed</a> now that we’re fully remote.</p><p><em>Originally published at </em><a href="https://blog.nona.digital/whats-the-story-point-anyway/"><em>https://blog.nona.digital</em></a><em> on September 28, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=529f701f172e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nona-web/whats-the-story-point-anyway-529f701f172e">What’s the Story Point anyway?</a> was originally published in <a href="https://medium.com/nona-web">Nona Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Australian Wool Handlers (AWH) — Case Study.]]></title>
            <link>https://medium.com/nona-web/australian-wool-handlers-awh-case-study-f448235d6e43?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f448235d6e43</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[logistics]]></category>
            <category><![CDATA[australia]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Wed, 03 Jul 2019 14:52:07 GMT</pubDate>
            <atom:updated>2019-09-13T13:15:55.586Z</atom:updated>
            <content:encoded><![CDATA[<h3>Australian Wool Handlers (AWH) — Case Study.</h3><p>How we rebuilt business-critical auctioning software for AWH— the world’s largest wool and independent cotton handler whose software applications process hundreds of millions of dollars each year.</p><p>We worked with AWH to replace a 15 year old entrenched, and critical, piece of third party software with no downtime or business interruption</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mX30cO7M5PewbCZxioPtog.jpeg" /></figure><h3>Why did AWH approach NONA?</h3><p>AWH were looking for a software development partner to help them with a core application. They needed to modernise their operating software to create future readiness and reduce reliance on 3rd party software vendors.</p><blockquote>“Due to the complexity of our problem, the disjointed legacy systems and the urgency to get a new system in place, it was obvious we needed a world class software organisation. NONA was a clear standout.</blockquote><p><strong><em>Michael Jones, former CEO, AWH</em></strong></p><blockquote><strong>“We were looking to partner with a team that we could rely on to:</strong></blockquote><blockquote>Modernise our existing auction software.</blockquote><blockquote>Eliminate our reliance on external software vendors.</blockquote><blockquote>Completely replace our external facing API’s without our existing partners even being aware of any changes or having to make any modifications to their own systems.</blockquote><blockquote>Do the above without any downtime or interruption to our daily business.”</blockquote><blockquote><strong>Darryl Drake, CTO, AWH</strong></blockquote><h3>Key requirements of this project</h3><ul><li>All external facing API’s would need to be replaced <strong>without existing partners even being aware of any changes</strong> or having to make any modifications to their own systems.</li><li>Catalogues needed to be imported from a 3rd party over which we had no control.</li><li>The system needed to be <strong>resilient to losses of internet connectivity</strong>.</li><li>All data captured during an auction would need to be <strong>recoverable in the event of a crash</strong> mid-auction.</li><li>Results would need to be <strong>displayed in real time</strong> with or without internet connectivity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8xX1PGGo6N7CG60SquYeXQ.jpeg" /><figcaption>The old AWH auction system</figcaption></figure><h3>We needed to fully understand the AWH business, their unique situation, culture and their operations to ensure that we achieved success for them.</h3><p><a href="https://medium.com/nona-web/should-you-be-scared-of-outsourcing-your-software-development-9ebee8ce2ab2">Outsourcing software projects that are key to your business can be a fear-filled, financially wasteful and stressful process.</a> Kicking the project off in the right way is essential to lowering the risk of failure and increasing the transparency and flow of information.</p><p>Three of our directors flew down to spend quality time with the AWH leadership team in Melbourne; working out of the AWH offices for a few weeks, touring their warehouses, visiting their auctions, to get to know the team the culture of the organisation.</p><p><strong>We ran in-depth workshops with many stakeholders to unpack the detailed specifications that would be required:</strong></p><ul><li>Dave, the man behind the Wool Industry’s statistics educated us on the numbers, what they mean and why they matter.</li><li>Adrian, who would actually be operating the software after launch, explained how the auctions ran, what the risks and constraints were.</li><li>Darryl, AWH’s CTO and our direct contact worked through what he needed from us to be successful, what mattered and what outcomes were required.</li><li>Sean, Nick and Nigel the developers behind AWH’s in-house systems detailed the intricacies of this particular industry’s operating model.</li></ul><p>Additionally, we got our hands on as much literature as we possibly could in order to get up to speed on existing <a href="https://en.wikipedia.org/wiki/Electronic_data_interchange">EDI</a> specifications within the industry.</p><blockquote>NONA understood our requirements, came to grips with the legacy systems as well as the difficulty and demands of our specifications and requirements, and understood it so well they were offering really excellent suggestions. What was really impressive was being able to meld all of that with a fantastic UI/UX and also keeping eye to future growth and development. I will definitely seek NONA out for all my future development requirements.”</blockquote><p><strong><em>Michael Jones, former CEO, AWH</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CSG_2UUt8QWYxIZIlice3w.jpeg" /><figcaption>Three of our Directors spending the necessary time on site with the AWH team.</figcaption></figure><h3>Once we were fully immersed in the AWH business and culture, we got to work.</h3><p>Now that we deeply understood AWH’s needs, we selected the tools, languages and frameworks to build the application with.</p><p><strong>The choice was made on the following criteria:</strong></p><ol><li>Must be <strong>easily updatable and maintainable</strong> by anyone with an understanding of modern web technologies.</li><li>Must be as familiar to AWH’s team as possible with a view to the future handover.</li><li>Must be <strong>secure, scalable</strong> and have a serverless backend being both <strong>cost effective and future proof</strong>.</li><li>Must result in <strong>real time secure data transfer.</strong></li></ol><h3>Working in different timezones… not a problem.</h3><p>We ran the project predominantly from our Cape Town office while our client remained in Melbourne. This is a dance we’ve done <a href="https://medium.com/nona-web/remote-working-leadership-and-teams-feb6794b99fd"><strong>many times before</strong></a> so we knew the intricacies around how to make it painless. Yes, there were some early mornings and late nights for us, but nothing we couldn’t handle.</p><p>We worked very closely with the AWH team — meeting at least weekly to show progress, ask questions, test features and ensure we remained constantly on the same page.</p><p>We performed multiple dry runs, demo’d and trained AWH staff on the use of the software and then, after 5 months of close collaboration Dave (NONA’s CTO) flew back to Melbourne to personally oversee the launch — <strong>the new Auction software was brought into the world!</strong></p><h3>The results.</h3><p>AWH put the new system into production in early May 2019.</p><p><strong>On its first morning of the operation, the application processed approximately 16 million AUD worth of sales and without a single glitch.</strong></p><p>Only one month after putting the new system into production, AWH<strong> felt confident enough in the new system to internally take over both the maintenance and development</strong>, a resounding indication of success for us.</p><p>We attribute this largely to a dedication to code quality, a near 100% test coverage, our strict standards and clear documentation which we applied to every facet of this project.</p><p>Thank‘s AWH for working with us to deliver this great project!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wrhPrf_O9yWpfuDz_DiDRw.jpeg" /><figcaption>Screen designs of the new software</figcaption></figure><blockquote>What struck me about the NONA team was their deep understanding of our business in such a short space of time. The combination of their business insight and obvious technical ability lead to a great experience throughout the build and ultimately to a very high quality application which we now own and maintain. I highly recommend NONA to anyone that wants to work with a world class software development partner.</blockquote><blockquote>- Darryl Drake, CTO, AWH</blockquote><h3>What’s next?</h3><p>We’re already speaking to AWH about the next project in their suite and hope to begin work on this next year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*df0P5NCzW2GNcYgDWSuo9w.jpeg" /><figcaption>The new software in use on launch day</figcaption></figure><h3>Get in touch and let’s build amazing software together!</h3><h3>hello@nona.digital<br>+27 021 200 5958</h3><h3>Specific Tech Details for those who are interested:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GTu0AZMZDBjnOP5FbVRvFA.jpeg" /></figure><p><a href="https://electronjs.org/"><strong>Electron</strong></a><strong><br></strong>Allowed quick development of cross-platform desktop software, easily updatable and maintainable by anyone with an understanding of modern web technologies.</p><p><a href="https://angularjs.org/"><strong>Angular 7</strong></a><strong><br></strong>AWH had an in house development capacity with experience with this framework, so this was chosen to ease their takeover of the project on completion.</p><p><a href="https://aws.amazon.com/"><strong>AWS</strong></a><strong><br></strong>RDS (Postgresql), Lambda, API Gateway, SQS, CloudFront, KMS, S3 and Param Store allowed the development of a secure, scalable, and serverless backend both cost effective and future proof.</p><p><a href="https://en.wikipedia.org/wiki/WebSocket"><strong>Web sockets</strong></a><strong><br></strong>Real-time updating of information and the need to allow an auction to proceed, even in the absence of internet connectivity, suggested this technology as a way to pipe information between the various in-room components of the system in a real-time, secure manner.</p><p>Our approach was largely microservice based with a hybrid of functional programming (ramda and rxjs) and TypeScript, depending on the situation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f448235d6e43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nona-web/australian-wool-handlers-awh-case-study-f448235d6e43">Australian Wool Handlers (AWH) — Case Study.</a> was originally published in <a href="https://medium.com/nona-web">Nona Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Books I read in 2018]]></title>
            <link>https://edwardtoreilly.medium.com/books-i-read-in-2018-f21ef0d10ed9?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f21ef0d10ed9</guid>
            <category><![CDATA[anon]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[52-week-challenge]]></category>
            <category><![CDATA[2018]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 11:41:46 GMT</pubDate>
            <atom:updated>2019-01-15T23:15:46.607Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*2K2aU5-WMRDeOkGBscTHlA.jpeg" /></figure><p>My Business Partner and CEO <a href="https://medium.com/@mikescott88">Mike Scott</a> wrote <a href="https://medium.com/@mikescott88/books-i-read-in-2018-ad57fca76566">this post about the books he’d read in 2018</a>.</p><p>We often chat about books and have read many of the same ones and I thought it was a good idea — both as a way to share and perhaps to connect with like-minded people who have read the same or similar books as well as a way to keep track over the years of all the books I’d read.</p><p><strong>Like Mike mentions in his post:</strong></p><blockquote>At <a href="http://www.nona.digital/">NONA</a> one of our core values is ‘continuous improvement as a way of life’. Without the constant pursuit of improvement and knowledge, we will fast become obsolete.</blockquote><p><strong>So, with that in mind, here follows a list of books I read in 2018 broken into some loose categories:<br></strong>I add a * if it was an audio book.</p><h3>Business / Leadership / Productivity</h3><ol><li>Zero to One — Peter Thiel</li><li>This is Marketing — Seth Godin *</li><li>Get Your Shit Together — Sarah Knight*</li><li>Remote — Jason Fried*</li><li>The One Thing — Gary Keller</li><li>Traction — Gino Wickman *</li><li>Rocket Fuel — Gino Wickman *</li><li>So Good They Can’t Ignore You — Cal Newport*</li><li>Deep Work — Cal Newport*</li><li>Extreme Ownership — Jocko Willink</li><li>Flow — Mihaly Csikszentmihaly*</li><li>How Google Works — Jonathan Rosenberg*</li><li>How to Win Friends and Influence People — Dale Carnegie*</li></ol><h3><strong>Blockchain / Coding / Agile</strong></h3><ol><li>The Business Blockchain — William Mougayar*</li><li>Blockchain Revolution — Don and Alex Tapscott*</li><li>The Art of Agile Development — James Shore</li><li>The internet of money — Andreas Antonopolous*</li></ol><h3><strong>Fiction / Out of Interest / For the vibe</strong></h3><ol><li>Thinking, Fast and Slow — Daniel Kahneman.</li><li>Spanish: Short Stories for Beginners — Olly Richards *</li><li>God Bless You, Mr Rosewater — Kurt Vonnegut</li><li>Cat’s Cradle — Kurt Vonnegut</li><li>How Will You Measure Your Life? — James Alworth *</li><li>The Art of War — Sun Tzu</li><li>12 Rules for Life — Jordan Peterson*</li><li>Cancer Ward — Aleksandr Solzhenitsyn</li><li>Fire &amp; Blood — George RR Martin</li><li>Liar’s Poker — Michael Lewis</li><li>Down and Out in London and Paris — George Orwell</li><li>Antifragile — Nassim Nicholas Taleb*</li><li>Skin in the Game — Nassim Nicholas Taleb</li><li>Principles — Ray Dalio*</li></ol><p>That totals 31 across genre and category.</p><p>I had hoped to make 52 books this year… but never managed to get that done by quite some margin it turns out— it’s a little harder to do when reading paperbacks than it is with audio books of course but I’m sure I can do better in 2019.</p><p><strong>I’m currently reading the following:<br></strong>For the first time in my life really I’m experimenting with more than one book at a time — let’s see how that goes.</p><ol><li>Profit First — Mike Michalowicz*</li><li>Stealing Fire — Jamie Wheal*</li><li>The Gulag Archipelago — Aleksandr Solzhenitsyn</li><li>Maps of Meaning — Jordan Peterson*</li><li>Think and Grow Rich — Napoleon Hill</li><li>The Dichotomy of Leadership — Jocko Willink*</li></ol><p>Have you read any of the above books? Any other recommendations?</p><p>Let me know if the comments below.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2IVAl0TbsfES9cFGYr40g.png" /></a></figure><p><strong>This story is published in Noteworthy, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><strong>Follow our publication to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_text"><strong>Journal</strong></a><strong> team.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f21ef0d10ed9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WordPress, Vue and Nuxt — an SEO love story]]></title>
            <link>https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7593d0827730</guid>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[rest-api]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 09:14:15 GMT</pubDate>
            <atom:updated>2020-03-02T14:20:15.194Z</atom:updated>
            <content:encoded><![CDATA[<h3>WordPress, Vue and Nuxt — an SEO love story</h3><h3>WordPress and VueJS — SEO tutorial</h3><p>I wrote a <strong><em>surprisingly</em></strong> popular article a few months back titled: “<a href="https://medium.com/nona-web/vue-js-the-wordpress-rest-api-on-a-large-content-site-210124e39bd1">Vue.js &amp; the WordPress REST API on a large content site</a>” — I received a number of comments on that article asking for further information on how we got the SEO working.</p><p>So here goes :)</p><p>This tutorial demonstrates, very simply, how one would make use of the <a href="https://yoast.com/wordpress/plugins/seo/">WordPress SEO Plugin by Yoast</a> to provide SEO Title and Metadata to a <a href="https://vuejs.org/">Vue.js</a> front end over the <a href="https://developer.wordpress.org/rest-api/">WordPress REST API</a>.</p><p>There are a few pieces to this puzzle so I’ll try to be as clear as possible, without wasting anyone’s time and go through each piece in sufficient, but not laborious, detail.</p><p>I’ve created the simplest possible example to demonstrate what’s involved but you’ll need quite a lot more to get it all working smoothly in a production environment which I’ll touch on briefly at the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-ynI__W5DVvsDY2r_4uew.jpeg" /><figcaption>What is love?</figcaption></figure><h3>We’ll go through the following steps:</h3><ul><li>Setup a <a href="https://vuejs.org/">Vue.js</a> (<a href="https://nuxtjs.org/guide/installation/">Nuxt</a>) frontend which can display single posts.</li><li>Setup a WordPress API that serves post data over a restful endpoint.</li><li>Add Yoast SEO Plugin data to that endpoint.</li><li>Connect the Vue JS frontend to the API to pull the post and SEO meta data.</li></ul><p><strong>This tutorial assumes the following:</strong></p><ul><li>An intermediate knowledge of WordPress (PHP) development.</li><li>An understanding of Javascript development and some of what goes with that: NPM etc</li><li>Light familiarity with Yoast’s SEO Plugin for WordPress.</li><li>An interest in using Vue.js.</li></ul><h3>Setup a <a href="https://vuejs.org/">Vue.js</a> (<a href="https://nuxtjs.org/guide/installation/">Nuxt</a>) frontend which can display single posts.</h3><p>Choose a directory on your machine and create a new nuxt project like so:</p><pre>npx create-nuxt-app &lt;project-name&gt;</pre><p>Follow the steps and configure it however you’d like — I went with NPM over Yarn, no linting and no tests for the purposes of this lil demo.</p><p>Run the following to see your site on: <a href="http://localhost:3000/">http://localhost:3000</a></p><pre>npm run dev</pre><p>And voila — You’ll see your vue-tiful new project running!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJNQJxsmFdjyeaXp9ar6SQ.png" /><figcaption>The default index page after installing nuxt.</figcaption></figure><p>After that you’ll want to navigate to the “pages” directory and create a new folder called “post”. Inside that folder create two files: index.vue and _id.vue.</p><p>The index file will be used to disaply the listing page for posts which we won’t be covering in this tutorial and the _id.vue file will be used to display the individual posts.</p><p>In the ‘_id.vue’ file add the following code for now:</p><pre>&lt;template&gt;<br>  &lt;section class=&quot;container&quot;&gt;<br>    &lt;div&gt;<br>      &lt;logo/&gt;<br>      &lt;h1 class=&quot;title&quot;&gt;<br>        Static Post Title<br>      &lt;/h1&gt;<br>      &lt;span class=&quot;content&quot;&gt;<br>        Static Post Content<br>      &lt;/span&gt;<br>    &lt;/div&gt;<br>  &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>&lt;script&gt;</pre><pre>export default {</pre><pre>}<br>&lt;/script&gt;</pre><pre>&lt;style&gt;</pre><pre>.container {<br>  min-height: 100vh;<br>  display: flex;<br>  justify-content: center;<br>  align-items: center;<br>  text-align: center;<br>}</pre><pre>.title {<br>  font-family: &#39;Quicksand&#39;, &#39;Source Sans Pro&#39;, -apple-system, BlinkMacSystemFont,<br>    &#39;Segoe UI&#39;, Roboto, &#39;Helvetica Neue&#39;, Arial, sans-serif;<br>  display: block;<br>  font-weight: 300;<br>  font-size: 100px;<br>  color: #35495e;<br>  letter-spacing: 1px;<br>}</pre><pre>&lt;/style&gt;</pre><p>Then visit this here: <a href="http://localhost:3000/post/1">http://localhost:3000/post/1</a></p><p>There we go, a lovely little posts template showing the same static data over and over again no matter what ID is entered into the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1SsxGIUL88_8Y2e0_J7fhg.png" /><figcaption>Our starting static post page.</figcaption></figure><h3>Next we will setup a WordPress API that serves post data.</h3><p>I <a href="https://github.com/10up/wp-local-docker">install WP locally via Docker</a> but it’s totally your call how you wanna do the installation bit. Once you’ve got a site setup we work with the WordPress Rest API to serve the post data — with some additional SEO metadata using <a href="https://yoast.com/wordpress/plugins/seo/">Yoast’s SEO Plugin</a>.</p><p>WordPress, by default, provides an API endpoint for posts.</p><p><strong>You can visit this here:</strong> <a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/52852">http://your-local-wp-site-url/wp-json/wp/v2/posts/P</a>OST_ID</p><p>My exact one was: <a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/52852">http://devapi.seotest.com:20080/wp-json/wp/v2/posts/</a>1</p><p>This will produce a response which looks something like the following:</p><pre>{  <br>   <strong>&quot;id&quot;</strong>:1,<br>   <strong>&quot;date&quot;</strong>:&quot;2019-01-03T09:54:21&quot;,<br>   <strong>&quot;date_gmt&quot;</strong>:&quot;2019-01-03T09:54:21&quot;,<br>   <strong>&quot;guid&quot;</strong>:{  <br>      <strong>&quot;rendered&quot;</strong>:&quot;http://<a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/52852">devapi.seotest.com</a>:20080/?p=1&quot;<br>   },<br>   <strong>&quot;modified&quot;</strong>:&quot;2019-01-03T09:54:21&quot;,<br>   <strong>&quot;modified_gmt&quot;</strong>:&quot;2019-01-03T09:54:21&quot;,<br>   <strong>&quot;slug&quot;</strong>:&quot;test-post-seo&quot;,<br>   <strong>&quot;status&quot;</strong>:&quot;publish&quot;,<br>   <strong>&quot;type&quot;</strong>:&quot;post&quot;,<br>   <strong>&quot;link&quot;</strong>:&quot;http://<a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/52852">devapi.seotest.com</a>:20080/test-post-seo/&quot;,<br>   <strong>&quot;title&quot;</strong>:{  <br>      <strong>&quot;rendered&quot;</strong>:&quot;My test Post for SEO&quot;<br>   },<br>   <strong>&quot;content&quot;</strong>:{  <br>      <strong>&quot;rendered&quot;</strong>:&quot;&lt;p&gt;My test post main body content &amp;#8211; ain&amp;#8217;t that nice!&lt;/p&gt;\n&quot;,<br>      <strong>&quot;protected&quot;</strong>:false<br>   }</pre><pre>........</pre><p>There you go! You have an API endpoint setup which returns post data and you didn’t even have to write any code!</p><h3>Add Yoast SEO data to those posts.</h3><p>The next part is also pretty straight forward. We need to add Yoast’s SEO Meta data to this response.</p><p>First things first — visit your plugins page and install the <a href="https://yoast.com/wordpress/plugins/seo/">Yoast SEO plugin</a>.</p><p>I’m only going to focus on the Title and Meta Description to keep this post from getting too long but the rest of the fields follow a very similar pattern.</p><p><strong>Add the following code to your functions.php:</strong></p><pre>&lt;?php</pre><pre>add_action( &#39;rest_api_init&#39;, &#39;slug_register_yoast_seo_meta&#39; );</pre><pre>function slug_register_yoast_seo_meta() {<br>    register_rest_field( &#39;post&#39;,<br>        &#39;_yoast_wpseo_title&#39;,<br>        array(<br>            &#39;get_callback&#39;    =&gt; &#39;get_seo_meta_field&#39;,<br>            &#39;update_callback&#39; =&gt; null,<br>            &#39;schema&#39;          =&gt; null,<br>        )<br>    );<br>    register_rest_field( &#39;post&#39;,<br>        &#39;_yoast_wpseo_metadesc&#39;,<br>        array(<br>            &#39;get_callback&#39;    =&gt; &#39;get_seo_meta_field&#39;,<br>            &#39;update_callback&#39; =&gt; null,<br>            &#39;schema&#39;          =&gt; null,<br>        )<br>    );<br>}</pre><pre>function get_seo_meta_field( $object, $field_name, $request ) {<br>    return get_post_meta( $object[ &#39;id&#39; ], $field_name, true );<br>}</pre><p><strong>What this does is the following:</strong></p><p>Hooks into the ‘rest_api_init’ function to register two custom fields. Using ‘rest_api_init’ instead of ‘init’ so that this code only runs on API requests and not regular post requests.</p><p>Specifies the callback function for fetching the two fields as ‘get_seo_meta_field’ which simply takes the object ID (the post in this case) and the field name (either ‘_yoast_wpseo_title’ or ‘_yoast_wpseo_metadesc’) and returns the value of that post meta field.</p><p>Wonderful! Now we have a posts API endpoint that returns Yoast SEO Meta data! Woop Woop!</p><p>You can find the full description for how to add additional meta fields to endpoints here: <a href="https://v2.wp-api.org/extending/modifying/">https://v2.wp-api.org/extending/modifying</a></p><h3>Connect the Vue JS app to pull post data</h3><p>This is the final step — we need to tell the Vue Frontend to fetch the Post Data for each post from the WordPress API. We do this as follows:</p><p>We’re going to use Axios for this so in your _id.vue file add the following in the &lt;script&gt; tags.</p><pre>&lt;script&gt;<br>import axios from &#39;axios&#39;</pre><pre>export default {<br>  <br>  asyncData ({ params }) {<br>    return axios.get(`http://<a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/52852">devapi.seotest.com</a>:20080/test-post-seo<a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/$%7Bparams.id%7D%60">/wp-json/wp/v2/posts/${params.id}`</a>)<br>      .then(response =&gt; {<br>        return { post: response.data }<br>      })<br>      .catch((error) =&gt; {<br>        return { error: error }<br>      })<br>  },<br>  data () {<br>    return {<br>      post: {},<br>      error: []<br>    }<br>  }<br>}<br>&lt;/script&gt;</pre><p><strong>What’s going on here?</strong></p><ul><li>We’re importing <a href="https://www.axios.com/">Axios</a> into the file.</li><li>We’re using Nuxt’s ‘<a href="https://nuxtjs.org/guide/async-data/">asyncData</a>’ method to perform our Axios request.</li><li>We’re using a dynamic ID parameter so that we can pull different posts by visiting different URLs.</li><li>We’re adding the returned post data into a ‘post’ object that we’ve created.</li></ul><p><strong>We can now display a dynamic title and dynamic content for our post like so:</strong></p><pre>&lt;template&gt;<br>  &lt;section class=&quot;container&quot;&gt;<br>    &lt;div&gt;<br>      &lt;h1 class=&quot;title&quot;&gt;<br>        {{post.title.rendered}}<br>      &lt;/h1&gt;<br>      &lt;span v-html=&quot;post.content.rendered&quot;&gt;&lt;/span&gt;<br>    &lt;/div&gt;<br>  &lt;/section&gt;<br>&lt;/template&gt;</pre><p><strong>Please note the:</strong></p><pre>v-html=”post.content.rendered”</pre><p>This formats the HTML markup returned nicely and we should see something like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JO5A0NjyVJ18GDby9bcv-Q.png" /><figcaption>Woop! We’re getting there!</figcaption></figure><p>Of course the content itself will depend on what you put in the post you created on the WordPress side and the ID in the URL bar will depend on the ID of that post.</p><p><strong>Next we’ll want to include the SEO data as follows:</strong></p><pre>&lt;script&gt;<br>import axios from &#39;axios&#39;</pre><pre>export default {<br>  head () {<br>    return {<br>      title: this.post._yoast_wpseo_title,<br>      meta: [<br>        { hid: &#39;description&#39;, id: &#39;description&#39;, name: &#39;description&#39;, content: this.post._yoast_wpseo_metadesc }<br>      ]<br>    }<br>  },<br>  asyncData ({ params }) {</pre><p><strong>Full code for the file below:</strong></p><pre>&lt;template&gt;<br>  &lt;section class=&quot;container&quot;&gt;<br>    &lt;div&gt;<br>      &lt;h1 class=&quot;title&quot;&gt;<br>        {{post.title.rendered}}<br>      &lt;/h1&gt;<br>      &lt;span v-html=&quot;post.content.rendered&quot;&gt;&lt;/span&gt;<br>    &lt;/div&gt;<br>  &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>&lt;script&gt;<br>import axios from &#39;axios&#39;</pre><pre>export default {<br>  head () {<br>    return {<br>      title: this.post._yoast_wpseo_title,<br>      meta: [<br>        { hid: &#39;description&#39;, id: &#39;description&#39;, name: &#39;description&#39;, content: this.post._yoast_wpseo_metadesc }<br>      ]<br>    }<br>  },<br>  asyncData ({ params }) {<br>    return axios.get(`<a href="http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/$%7Bparams.id%7D%60">http://devapi.go2africa.com:20080/wp-json/wp/v2/posts/${params.id}`</a>)<br>      .then(response =&gt; {<br>        return { post: response.data }<br>      })<br>      .catch((error) =&gt; {<br>        return { error: error }<br>      })<br>  },<br>  data () {<br>    return {<br>      post: {},<br>      error: []<br>    }<br>  }<br>}<br>&lt;/script&gt;</pre><pre>&lt;style&gt;</pre><pre>.container {<br>  min-height: 100vh;<br>  display: flex;<br>  justify-content: center;<br>  align-items: center;<br>  text-align: center;<br>}</pre><pre>.title {<br>  font-family: &#39;Quicksand&#39;, &#39;Source Sans Pro&#39;, -apple-system, BlinkMacSystemFont,<br>    &#39;Segoe UI&#39;, Roboto, &#39;Helvetica Neue&#39;, Arial, sans-serif;<br>  display: block;<br>  font-weight: 300;<br>  font-size: 100px;<br>  color: #35495e;<br>  letter-spacing: 1px;<br>}</pre><pre>.subtitle {<br>  font-weight: 300;<br>  font-size: 42px;<br>  color: #526488;<br>  word-spacing: 5px;<br>  padding-bottom: 15px;<br>}</pre><pre>.links {<br>  padding-top: 15px;<br>}<br>&lt;/style&gt;</pre><p>This has been done the simplest possible way — just to illustrate the point of how to tie it all together. I mention below how we’ve actually done quite a bit more to get this working in production.</p><h3>Wrapping up</h3><p>There you go, now you have a Vue.js frontend with SEO provided by Yoast’s SEO plugin from a WordPress backend!</p><p><strong>Here’s a screenshot of our example:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gtGBoNoe9968Dgx0fzdFtQ.png" /><figcaption>You can see the SEO Title and Meta Description pulling through in the TAB and the Console!</figcaption></figure><h3>Please note</h3><p>In the project referenced in the <a href="https://medium.com/nona-web/vue-js-the-wordpress-rest-api-on-a-large-content-site-210124e39bd1">previous post</a> we went quite a lot further and added Metadata for all <a href="https://codex.wordpress.org/Taxonomies">taxonomies</a> and <a href="https://schema.org/">schema.org</a> metadata for images and videos etc.</p><p>We also used <a href="https://vuejs.org/v2/guide/mixins.html">Mixins</a> to be DRY and avoid repeating code on every different content type.</p><p>The above is actually quite important if it’s a production site but it’s tough to get all of that into one post concisely so I thought I’d explain the main mechanisms here and can cover doing this with Mixins and schema.org etc in a follow up post if there’s sufficient interest.</p><h3>What next?</h3><p>Feel free to reach out if you have any trouble getting this to run — I might have missed a step.</p><p>Let me know in the comments below if you’d be interested in a follow up post or more details on this setup.</p><p>Follow me or leave a comment if you’d be keen on hearing more!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7593d0827730" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730">WordPress, Vue and Nuxt — an SEO love story</a> was originally published in <a href="https://medium.com/nona-web">Nona Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vue.js & the WordPress REST API on a large content site]]></title>
            <link>https://medium.com/nona-web/vue-js-the-wordpress-rest-api-on-a-large-content-site-210124e39bd1?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/210124e39bd1</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[rest-api]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 07:25:18 GMT</pubDate>
            <atom:updated>2019-01-10T09:32:34.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CO9JSzxLJ3ZQ_UdHigWp-Q.png" /></figure><p>When we set out to build our first large scale Vue.js website last year, there was hardly any information online to help us gauge whether or not this would work well.</p><p>Since then, I’ve seen a few articles and some tutorials on using Vue.js with WordPress and the WordPress REST API, including a few on theme and plugin development. However, what I have not yet seen is an article describing a project of significant size and the underlying architecture supporting it. This is where this piece comes in. It’s not a tutorial, or a guide, it is simply an overview of our experience of actually building something reasonably large on this stack.</p><p><strong>UPDATE: I wrote a follow up post on how the Yoast SEO bit works over here:</strong><br><a href="https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730">https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730</a></p><h3>So, how big is this project?</h3><ul><li>+-3000 unique posts/pages</li><li>10 post types</li><li>5 taxonomies</li><li>Thousands of visitors daily</li></ul><h3>What tech stack did we use?</h3><ul><li>WordPress (hosted on <a href="https://pagely.com/">Pagely</a>)</li><li>Vue.js (contact me for a full list of supporting NPM packages)</li><li>Nuxt</li><li>AWS (S3, EC2, Elastic Load Balancer, Cloudfront CDN)</li><li>Elasticsearch</li><li>MailChimp (newsletters)</li><li>A custom enquiry API</li></ul><h3>How do these parts fit together?</h3><p>We host a WordPress site with <a href="https://pagely.com/">Pagely</a> (who, incidentally, host on AWS themselves anyway). The client uses the WordPress CMS to load and edit their content, and media content is offloaded to Amazon’s S3, using the <a href="https://deliciousbrains.com/wp-offload-s3/">Amazon offload S3 plugin</a> by <a href="https://deliciousbrains.com/">Delicious Brains</a>. When records are added or edited, the ones which are searchable are also hooked into an Elasticsearch index — more on this later.</p><p>The content is exposed using the WordPress REST API, and Vue consumes the REST API, using Nuxt to handle the routing. A Node server is hosted on AWS, on two EC2 instances balanced by ELB sitting behind Cloudfront.</p><h3>What happens when a user browses the site?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARyVF8PuxfGdSUesynOZNQ.png" /></figure><p><strong>When a user first requests a page by typing a url into a browser (the pink block in the image below)</strong></p><p>The request is originally handled by Cloudfront CDN. Cloudfront checks if it has a cached version of the requested URL, and if it does, the cached version is returned to the user. This contains a number of CSS, JS, and other media URLs (these are hosted on S3 behind Cloudfront) which will then be served to the user’s browser.</p><p>If Cloudfront does not have a cached version of the page, it requests one from ELB, and ELB in turn requests one from either of the two EC2 instances. The EC2 instances both run identical Node servers (which serve our Vue.js app), and make requests to the WordPress REST API for the content needed for the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYqVEYnOH1DhjZXgIh_VCQ.png" /><figcaption>A visualisation of the full setup and the relationships between them.</figcaption></figure><p><strong>When a user clicks on an internal link</strong></p><p>After the initial load, the website is actually now only JavaScript running in the user’s browser. When an internal link is clicked, the browser requests updated content from the WordPress REST API directly, and Vue.js updates the page and associated metadata (SEO, state variables etc).</p><p><strong>When a user submits an enquiry or newsletter registration</strong></p><p>The browser sends a request to our “middleware” application — running on a Node server on another EC2 instance. This middleware application sends the request on to the client’s enquiry API, or to MailChimp.</p><p>This was a tricky, but necessary step, since MailChimp and the enquiry API would not accept requests directly from a browser (security), and therefore required a connection from a server.</p><h3>Why did we choose Vue?</h3><p>The choice came down to either Vue or React. Another team at Nona Creative was keen on React, so we decided to use Vue instead so as to compare the two — it was the up-and-comer and we wanted to know what all the fuss was about.</p><p><a href="https://risingstars.js.org/2017/en/">It appears to have been a reasonable choice.</a></p><p>We’ll be trying React for our next project in order to get a feel for both, and learn which one we prefer through experience, rather than hype.</p><h3>Which parts of this were difficult to get right?</h3><p><strong>SEO</strong></p><ul><li>In the past, we’ve relied quite heavily on <a href="https://yoast.com/wordpress/plugins/seo/">Yoast’s WordPress SEO plugin</a>, which automatically adds most of what you need for SEO to your website both backend and frontend.</li><li>Doing without that automation was very tricky in the beginning, as we had to pass all the relevant SEO data through to the front-end ourselves, over the API.</li><li>We still use Yoast so that the client can more easily tweak their own SEO data, but we needed to create our own PHP class to handle gathering and sending that data through to the browser.</li><li>Nuxt handles server side rendering so that Google can crawl full html pages without any downside to building the site as a single page application from an SEO perspective.</li></ul><p><strong>WordPress as an API for the first time for the whole site</strong></p><ul><li>While this was quite pleasant to work with, it was the first time we’d used it for an entire website, and it took far longer than we’d anticipated to get everything up and running .</li><li>We also tried writing most of the database queries ourselves using SQL, which, in retrospect, probably wasn’t worth the time since the endpoints are cached anyway and the WP queries would have been more familiar.</li></ul><p><strong>Deployments and AWS</strong></p><ul><li>This was a whole new world for us — configs stored on S3, and Circle CI deployments to Elastic Load Balancer, test servers etc.</li><li>Circle made our lives a lot easier, and while it feels reasonably simple and familiar now, there was a lot of wiring up to do and the learning curve was steep.</li><li>We also needed to learn a fair amount about caching and uncaching, and made use of Cloudfront’s API and a curl request to the <a href="https://pagely.com/">Pagely</a> server to achieve this from the WordPress back-end. This allows for the uncaching of individual pages conveniently through the admin.</li></ul><p><strong>Using NUXT for routing</strong></p><ul><li>There was nothing online about using Nuxt, so, for once, we couldn’t rely on Google to answer all of our questions.</li><li>Overall it was pretty simple to use, but the build process takes an unfortunately long time before the version 1.1.1 update.</li></ul><h3>How did it all workout in the end?</h3><p>Pretty great!</p><ul><li>We learnt one hell of a lot.</li><li>The website is incredibly speedy, particularly switching between pages.</li><li>Reactivity is awesome! Change a single variable to update areas all over the site — think maps, currencies, prices, telephone numbers, etc.</li><li>Building a site in an API / Client manner is more extensible. The same back-end can be used to provide data to other apps, or sites in future. We’re about to make use of this feature, which is exciting!</li><li>The client is happy, and so are we.</li></ul><h3>Would I recommend doing this?</h3><p>Hell yeah! It was a lot of fun and has many benefits, as listed above.</p><p>Have you tried building something similar with WordPress and or React/Vue? Tell us about it in the comments below!</p><p><strong>UPDATE: I wrote a follow up post on how the Yoast SEO bit works over here:</strong><br><a href="https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730">https://medium.com/nona-web/wordpress-vue-and-nuxt-an-seo-love-story-7593d0827730</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210124e39bd1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nona-web/vue-js-the-wordpress-rest-api-on-a-large-content-site-210124e39bd1">Vue.js &amp; the WordPress REST API on a large content site</a> was originally published in <a href="https://medium.com/nona-web">Nona Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The man of many masks]]></title>
            <link>https://edwardtoreilly.medium.com/the-man-of-many-masks-2748a79ff9eb?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2748a79ff9eb</guid>
            <category><![CDATA[masks]]></category>
            <category><![CDATA[fiction]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Tue, 08 Aug 2017 22:36:15 GMT</pubDate>
            <atom:updated>2017-08-08T22:36:15.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5WhfOMcAdXkxczjprGi_Q.png" /><figcaption>Credit: <a href="http://www.stockvault.net/user/profile/161904">Pixabay</a></figcaption></figure><p>A very long time ago, in a kingdom that humanity has all but forgotten, there lived a very unusual man.</p><p>In those days, mystical and magical things such as dragons, sorcerers, unicorns and the like, were far more commonplace than they are today. Thus this man’s peculiar predicament was not entirely out of the ordinary. He had no face of his own.</p><p>He did, however, have a staggeringly large collection of masks, depicting all the many guises and expressions that another’s face would. In his lifetime he had become remarkably adept at very quickly, in fact almost instantly, swapping between his masks when the situation called for it. He would flick from furious to flirtatious, transform from tranquil to tyrannical, with the greatest ease and most immaculate timing.</p><p>His range of emotional expressions varied significantly more in fact than the average man’s as he paid far more attention to the physical interpretation of his internal emotional balance than perhaps you or I would. This being necessary for one in his situation.</p><p>He never projected an unintentional desire or accidentally revealed a deep seeded hatred, for the man of many masks was perpetually in complete control of his facial appearance.</p><p>For special occasions: the banquets thrown by the king, his own celebrations and festivities etc, our fellow would wear a warm embracing smile or an extravagant, royal and welcoming laugh. At home he would carry the peaceful face of the content master of his own land. Never in his life before had he encountered a person, place or situation for which he couldn’t choose the fitting display of his feelings toward.</p><p>Then one day when he was walking through town happily projecting his inner feeling of satisfaction and intrigue, passing the various shops in the town’s quaint little market, he tripped over a stray stone and came crashing down hard on his hands, knees, and chest.</p><p>Faster than the eye could see, his mask had been swapped into one depicting the internal feeling of pain and mild embarrassment that he now experienced. As he lay, gripping his knee and writhing in pain, a young lady who worked at the small herb shop, nearest to where he had fallen, came upon him to provide assistance.</p><p>She was the single most beautiful thing he had ever seen, or imagined to be real. Not only for her outward beauty but, in fact more so for the immense compassion, slightness and sweetness, that shone like the dazzle of a newly cut diamond from her glimmering eyes. As she held his hand and gently soothed him whilst dabbing his grazed knees with a damp cloth, he could feel the welling up of intense emotional turmoil inside of him.</p><p>His masks swapped at lightning speed from, grateful to awestruck to shy to ecstatic to embarrassed, quickly dancing through over 1000 different expressions but none could completely capture this feeling that grew ever more powerful from the depths of his very soul.</p><p>Then all of a sudden, the masks he was wearing cracked and splintered into hundreds of tiny pieces. Beneath where they had been, for the very first tine, was the man’s own true face.</p><p>As he stared into the eyes of the one he now knew he loved, he felt completely qualified, defined, safe, and more alive than ever before.</p><p>He no longer had to consider how to express what he felt inside because he knew that it would never be possible to externalise this feeling. It was so much greater than any mask, than any person, than anything else in this world.</p><ul><li>A short story I wrote in 2009 for a friend. I thought of it the other day and looked it up. In the spirit of publishing writing regularly till I get better at it (regardless of subject matter for the moment) I’ve edited the story a little bit and put it online. Olay!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2748a79ff9eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 tricks to learn a new language - without spending ANY time]]></title>
            <link>https://edwardtoreilly.medium.com/3-tricks-to-learn-a-new-language-without-spending-any-time-c73d4b6ff8d7?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c73d4b6ff8d7</guid>
            <category><![CDATA[language-learning]]></category>
            <category><![CDATA[life-hacking]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Thu, 03 Aug 2017 19:14:22 GMT</pubDate>
            <atom:updated>2017-08-04T08:55:42.197Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oLSU9vI438aYfMTH3KfENg.jpeg" /></figure><p>Many people want to learn a second language but believe it’s too difficult for them to achieve. It isn’t.</p><p>Learning another language is perfectly within your reach. It may take some work. It may take some repetition — but these three tricks will speed that process up like you won’t believe.</p><p>The best part? They won’t take <em>any</em> time at all.</p><h3>1. Switch your phone to the language you’re trying to learn right now</h3><p>It may seem scary — but it works better than most things I’ve tried. The problem with a lot of language courses and books (and sometimes teachers) is that they often fail to teach you current and relevant language. You’ll be able to say things like: “The dog eats the potato.” and not be able to ask someone “Which app should I download for this?”.</p><p>I’m not going to lie to you, it’s a little unsettling at first but pretty soon you’ll learn words like: application, download, install, update. You’ll learn about weather, events and activities. You’ll learn about messages, sending and receiving.</p><p>You’ll learn current and relevant things daily.</p><p>You’ll learn them without spending even one minute of time.</p><p>It will become second nature <em>without you even having to try</em>.</p><h3><strong>2. Listen to the language you’re trying to learn daily</strong></h3><p>Here’s the trick: this doesn’t have to take any time at all.</p><p>All you have to do is find something that you already love listening to and switch to doing it in the language you’re learning.</p><p>There’s something called “The Slow News”. Available in many languages.</p><p>I love reading the news or watching it.</p><p>I want to improve my Spanish.</p><p>I now listen to or watch the news in Spanish.</p><p>Without spending any time, I am learning very relevant Spanish.</p><p>Sure, you’ll take a bit of an understanding knock initially. Much like trying to use your phone in the beginning this may be a bit frustrating — but necessity (and an interest in the subject matter) will make you adapt to your new language more quickly.</p><p>Perhaps the news isn’t your thing? No worries. For learning German I turn to rap music. I can highly recommend: Alligatoah or DeichKind.</p><h3>3. Duolingo on the loo</h3><p>We all need to use the loo.</p><p>We all like something to do while we’re on the loo.</p><p>Use a language learning app (I use Duolingo) to get your 10 minutes of daily practice in… while you’re on the loo.</p><p>Zero additional time invested.</p><p>An automatic, natural trigger to remind you to practice.</p><p>The perfect time hack.</p><p>Personally I use coffee and smoke breaks as well as these serve as triggers for me. They won’t work for everyone though but none of us can avoid nature’s call for a day.</p><h3>*Bonus: Learning two languages at once.</h3><p>Something amazing I discovered recently that won’t work for everyone is that you can learn two languages at once but you’ll need to be conversational in one of them first.</p><p>Once I got good enough at Spanish, I switched Duolingo from English to Spanish and continued my German lessons as if I was Spanish. This means that every 5mins I spend learning German, reinforces my Spanish as well.</p><p>It has been an absolute game changer for productivity and I highly recommend it to anyone who is keen on becoming a polyglot like me.</p><h3>Call to Action</h3><p>If any of this sounds like it could work for you or a friend then please give it a green heart.</p><p>Got any great tricks yourself? Please share them in the comments section.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c73d4b6ff8d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 great books in 2 short weeks]]></title>
            <link>https://edwardtoreilly.medium.com/5-books-in-2-weeks-e0389d746458?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0389d746458</guid>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Wed, 02 Aug 2017 07:39:17 GMT</pubDate>
            <atom:updated>2017-08-02T07:42:08.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0oqcDoeSMABErRRv2zWzw.jpeg" /><figcaption>Credit: <a href="https://stocksnap.io/author/56793">Shopify</a></figcaption></figure><p>I recently received a suggested list of books from someone I admire. I absolutely devoured them. I was travelling a lot and working daily, yet they still flew into my mind.</p><p>They were so great that I feel compelled to share them with the world.</p><p>Please enjoy.</p><h3><a href="http://amzn.to/2uY8IUz">1. The Goal — Eliyahu M. Goldratt</a></h3><p>Do you know what the Goal is? Why are you working? Why are you writing? A surprising number of us are completely unaware of this critical answer.</p><p>Even more of us believe we know — but we don’t.</p><p>This book takes you on a journey of intellectual discovery for a factory manager in 80’s America. It gets the message across in a story format, rather than a lecture. Fantastically written, incredibly interesting. Highly recommended.</p><p><strong>My take away:</strong> “Not only 10% or 20% improvements are hidden all around us. 2X or 10X improvements are waiting to be discovered.”</p><h3>2. <a href="http://amzn.to/2uXZZBW">Great by Choice - Jim Collins</a></h3><p>As we all probably know by now, considering the incredible amount of times he is referenced on Medium — Jim Collins is an amazing author and meticulous researcher. I’ve read both <a href="http://amzn.to/2vrTpqb">Built to Last</a> and <a href="http://amzn.to/2uVadVf">Good to Great</a> before — but this one was certainly my favourite of the three.</p><p><strong>My take away:</strong> “Luck exists but is far less of defining factor for success than one may think. Being prepared to get a return, on both good and bad luck, is far more important.”</p><h3>3. <a href="http://amzn.to/2uUI8NV">Bringing out the best in People - Aubrey C. Daniels</a></h3><p>I’m a partner in a company of 29 employees. I’ve never read something better on people management before.</p><p>We missed the mark on so many of these but if any books have ever changed my approach to work it is this and <a href="http://amzn.to/2uUHEHj">Scaling Up by Verne Harnish</a>.</p><p>Two absolute must-reads for any entrepreneur.</p><p><strong>My take away:</strong> “Positive, immediate and certain rewards and recognition do far more for daily motivation than rewards which are further away. If you want the best out of people, you need to positively reinforce good behaviours daily. You simply <em>cannot</em> wait for a quarterly review.”</p><h3>4. <a href="http://amzn.to/2uUkYXF">The ten faces of Innovation - Jonathan Littman</a></h3><p>So often we hear someone say: “I’m just playing Devil’s advocate” as if that gives them license to shoot down ideas. Why aren’t we playing other roles? Why not play “The Director” or “The Anthropologist”.</p><p>In this insightful book from one of the greatest companies in the world we discover the power of playing other roles to unlock innovation.</p><p><strong>My take away: </strong>“I will never tolerate the Devil’s advocate again. We can do so much better than that.”</p><h3>5. <a href="http://amzn.to/2vrOllN">The Starfish and the Spider - Rod Beckstrom</a></h3><p>When you cut a spider’s head off it dies — but what about the starfish? A fascinating look at leaderless and loosely structured organisations. From Apache’s to E-Mule. How they impacted the world. Why they’re hard to kill, and how some still killed them.</p><p><strong>My take away:</strong> “We can all benefit from the principals adopted by leaderless organisations without losing all leadership. A compromise is possible and promises strength and opportunity.”</p><h3>6. <a href="http://amzn.to/2uixXiA">Hidden Champions of the 21st Century - Hermann Simon</a></h3><p>Currently reading this one and it’s amazing so far. Will update with another post next week.</p><h3>Call to Action</h3><p>Have you been reading ferociously lately? Anything brilliant? Please share in the comment section below. I can’t get enough at the moment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0389d746458" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Steps to publish a medium post in under 90 minutes]]></title>
            <link>https://edwardtoreilly.medium.com/publish-your-first-medium-post-in-the-next-90-minutes-with-these-7-steps-eb2d24c3eac?source=rss-d068db47c1b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb2d24c3eac</guid>
            <category><![CDATA[starting]]></category>
            <category><![CDATA[lists]]></category>
            <category><![CDATA[commitment]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Ed O’Reilly]]></dc:creator>
            <pubDate>Sun, 30 Jul 2017 11:50:26 GMT</pubDate>
            <atom:updated>2017-08-01T22:03:32.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sdUxBJrWur4_QDLIV7Ed6w.jpeg" /><figcaption>Credit: <a href="https://stocksnap.io/author/48136">Stanley Dai</a></figcaption></figure><p>Overcoming inertia and getting the stone rolling is often the hardest thing for people to do. It may seem oversimplified to say that the best way to get started is to just start but it really is. In case you doubt that advice or indeed the title of this article, this is my first medium post — it’s published and I started it 87 minutes ago. Now, let’s get cracking…</p><h3>1. Create an account on Medium - like, right now</h3><p>It’s possible that you already have one and if so, that’s great — you’ve already got one of seven steps out the way! Go you! But in the event that you haven’t, go on and sign up right now. Done? Good.</p><p>Now you’ve started, you may not have taken the biggest step just yet but you’ve taken a step — and that’s what <em>really</em> matters. as Lao Tzu wrote thousands of years ago in the Tao Te Ching, <em>“A Journey of a thousand miles begins with a single step”</em>.</p><p>Now, let’s take 6 more.</p><h3>2. Commit 100% to completing your post within the next 90 minutes</h3><p>Perhaps you’re reading this at work or just before you have to head somewhere important, and you don’t have the next 90 minutes available. If that’s the case, stop. Stop right now, bookmark this link and come back to it later. It’s vitally important that you commit yourself entirely if you want to publish your post now.</p><p>Once you’ve truly committed yourself to a task, completing it is no longer a challenge, it becomes second nature. I could, and probably will at some point, write a post dedicated to the benefits of committing wholeheartedly to whatever it is you want to achieve, but for now I’ll just leave you with a single quote:</p><blockquote>“99% is a bitch, 100% is a breeze” — Jack Canfield</blockquote><p>I committed myself to completing this article and if you’re reading this, it worked for me and will work for you.</p><h3>3. Be prepared to be amateur - Done now is better than perfect never</h3><p>Great, now that you’ve committed yourself 100% to completing this article let’s deal with the last emotional hurdle before getting into the creating.</p><p>Is this the best article you’ve ever read? I sure as hell hope not. Seriously, there are a lot of good writers out there - go and find them. It is published though. It made it out of my mind, through the keyboard and onto the screen in front of your eyes. It’s not perfect, and it’s my first attempt, but I’ve done what I set out to do.</p><p>I don’t have a blog I commit to posting on - but I really want to and if I’m not willing to publish this article or the next 100 after it (which probably won’t be very good either), I’ll never become great at writing and that’s what I want to do. I imagine that since you’re reading this post you have similar ambitions. So let’s be vulnerable, put our egos aside and get our thoughts out there.</p><h3>4. Write your conclusion</h3><p>Great, let’s do a quick recap of where we are:</p><ul><li>You’ve created a Medium account</li><li>You’ve committed to completing this article</li><li>You’ve prepared yourself mentally and emotionally for publishing it while knowing it’s not necessarily going to be the greatest piece of writing ever</li></ul><p>So now you need to decide on the point of the post, the message you’re trying to get out there. You need to start where you want to finish - and work backwards from there.</p><blockquote>I started with the conclusion that:</blockquote><blockquote>“It is completely possible to publish an article on Medium, having never done so before, if you just sit down and commit yourself to the cause, and allow yourself only 90 minutes to get there.“ — Ed O’Reilly</blockquote><p>Remember again that this conclusion doesn’t have to be revolutionary, it doesn’t have to change the world or make you seem clever. You’ve got something to say, we <em>all</em> do. You’ve said many things before in conversation, in arguments. Say one of them here, make a point, be wrong, be right — decide on where you’re going to end and write that down.</p><p>It doesn’t have to be well written, or succinct. It doesn’t even have to be original but it does have to be written down before you go any further.</p><p>Remember, you can do this!</p><blockquote>“The urge, starting out, is to copy. And that’s not a bad thing. Most of us only find our own voices after we’ve sounded like a lot of other people. But the one thing that you have that nobody else has is you. Your voice, your mind, your story, your vision. So write and draw and build and play and dance and live as only you can.” — Neil Gaiman</blockquote><h3>5. Write your introduction</h3><p>Introduce your topic. Don’t waffle on, state, as simply as you possibly can, what this article is about and why you’re writing it. If you want to get all fancy, try and lure the reader in with some sort of hint at the value contained inside, but really that’s not the most important thing.</p><p>Remember our goal here is to publish our first Medium article <strong>in the next 90 minutes</strong>, to overcome our anxieties and life inertia and to actually get this done, without compromise. If someday when you’re famous you don’t want this poorly written article tarnishing your name, which it probably wouldn’t anyway, you can always just remove it.</p><p>So start working on the introduction, tell us what the post is about. Have the first attempt written before you carry on.</p><h3>6. Write your body</h3><p>This part is largely up to you but having decided on your conclusion and having written your introduction, really what you’re doing now is just bridging the gap between the two.</p><p>Explore your style, write down your thoughts. Maybe they’re wrong? Who cares, let’s get them down now and worry about that later. Remember, you haven’t hit publish just yet. You probably still have 60 (or more) minutes to refine this — that’s plenty of time. Write them down now, refine them all later.</p><p>I found it easier to divide this section of the work into 7 steps. I write these down first and then filled out the content supporting each claim. Not all topics are well suited to list-style writing but many can be, and if it helps you get this one done then go for it! Is there a set of steps that logically leads you from your introduction to your conclusion?</p><h3>7. Publish and share</h3><p>Here goes. The big moment. Hit publish. Just do it. Overcome the final step and put yourself out there. I’m about to do it and I hope it feels as good as I believe it will.</p><p>I’m going to share it too. I know, scary right? Really I think it’s the only way it will get enough exposure for me to learn from this experience and improve. So here goes.</p><h3>What next?</h3><p>I don’t know… We’re in the same boat now you and I. Personally I’m going to read absolutely everything I can about writing and reach out to those around me who do it well.</p><p>I’m also going to commit myself to writing another post in the next week. On what? I have no idea yet — but I’m excited.</p><h3>Call to action</h3><p>If this resonated with you, then please share it. Help me get out there. If you’re able to help me get better at writing, then I’d love to hear from you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb2d24c3eac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>