<?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 Alice Cheung on Medium]]></title>
        <description><![CDATA[Stories by Alice Cheung on Medium]]></description>
        <link>https://medium.com/@alicespyglass?source=rss-d748beb3d4c9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*25-4Ls8ZDt-xRmMd4mnFzA.jpeg</url>
            <title>Stories by Alice Cheung on Medium</title>
            <link>https://medium.com/@alicespyglass?source=rss-d748beb3d4c9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:05:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alicespyglass/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[A glimpse into the life of a software engineer at Ravelin]]></title>
            <link>https://syslog.ravelin.com/a-glimpse-into-the-life-of-a-software-engineer-at-ravelin-dfe9488ff9ed?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfe9488ff9ed</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[careers-in-tech]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Thu, 15 Apr 2021 13:49:55 GMT</pubDate>
            <atom:updated>2021-04-15T13:50:50.656Z</atom:updated>
            <content:encoded><![CDATA[<p>What does a day in the life of a Ravelin Software Engineer look like? We chat with <a href="https://medium.com/u/d748beb3d4c9">Alice Cheung</a> to find out…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*x1SOG66_AaM795abDtvpOg.jpeg" /></figure><p>Our software engineers are at the heart of what we do. They work closely with fellow engineers, data scientists and product managers to make online transactions safer and help our clients feel confident serving their customers.</p><p>To find out more about the day-to-day role of our engineers, we had a chat with Alice Cheung, software engineer and engineering manager about her role.</p><p>Here’s what she had to say!</p><h3>Can you tell us a bit about your role at Ravelin?</h3><p>“Sure! I’m a software engineer and engineering manager and very hands on in my role. Currently I’m on the dashboard team, working on the interface our clients use to access our product. My role ensures our clients’ fraud teams have a great experience when accessing their data, ultimately allowing them to make efficient data-driven business decisions.</p><p>“The management side of my role includes managing engineers of all levels — championing them to achieve their career goals. At the moment I’m managing two software engineers, with more onboarding soon.”</p><h3>How did you come to join Ravelin?</h3><p>“I’ve been at Ravelin for two years now. I actually wasn’t looking for a job at the time, but a friend invited me to a hiring event in the form of speed dating. That really intrigued me, so I went along and met some of the Ravelin team. I asked around after the event and found that people only had good things to say about the team and its tech — so I went ahead with the process and the rest is history.</p><p>“In terms of experience, I had one previous role in the industry — at an insurance tech start up. But before that I spent 10 years working in finance. I had a feeling that wasn’t for me anymore. And after talking to some software engineer friends, I decided to take the plunge and learn to code. I hadn’t had that much fun in a long time! I fully immersed myself in coding and within a year I had a job as a software engineer.”</p><h3>What does a typical day look like for you?</h3><p>“Every day we begin with a short ‘stand up.’ This is time to share what we’re currently working on and anything we might need help with. It’s been especially useful throughout the pandemic with us all working from home.</p><p>“After this, I get to spend most of my day coding, which is great. The team knows what they’re doing, so we’re all free to get stuck into whatever project we’re working on. And there’s no worries if we need help, people at all levels are more than happy to lend a hand.</p><p>“I’m currently working on an exciting project producing analytics for ‘rules’ our clients have in place. It’s useful for fraud teams to see exactly how these rules are performing, instead of us just saying ‘trust us.’”</p><h3>How has your role changed since you started working at Ravelin?</h3><p>“I began my career at Ravelin as a software engineer, so a lot of the fundamentals are the same, but I’ve now started my progression down the management track. This allows me to broaden my experience as a leader and pick up new responsibilities. Within the business, there’s a technical track for those who just want to focus on coding, as well as a management track for those wanting to experience managing people.”</p><h3>How has the pandemic changed the way you work?</h3><p>“There’s been a major change with the way we work. But it’s not necessarily a bad thing. A lot of us software engineers have enjoyed being able to code from home. And as our culture is great, we’ve still had the opportunity to be creative in the way we socialise. This includes planned activities like virtual escape rooms and cook-along nights to fill in the social aspect of the job.</p><p>“Ravelin’s also been very supportive of our needs throughout the pandemic. We were initially provided transport to take our equipment home, as well as being given a budget to buy anything else we needed to make our new work lives easier.</p><p>“As well as equipment, we’ve got generous new health insurance which includes mental health support. People are always approachable and understanding when it comes to talking about any issues you may have.”</p><h3>Software engineering is a fairly male-dominated world. How have you found it?</h3><p>“I came from the world of finance, so the ratios have been pretty similar. But to be honest, the geeks are my people, so I’ve never felt the odd one out because I’m female. I’m part of a great team where gender doesn’t matter — just your passion for coding.</p><p>“It’s also nice to know that we are making a conscious effort to hire more women, so I’m sure we’ll see change going forward!”</p><h3>What’s the best thing about working at Ravelin?</h3><p>“The thing I love about working here is the culture. It’s very tech focused, which stems from the founders being engineers themselves. They’ve been in our shoes and share our passion for delivering quality software. Obviously, we try to turn projects around quickly for clients. But this won’t be done at the expense of the tech. We do it right.</p><p>“I also enjoy the open nature of the company. We have demo sessions every week and “ask me anything” sessions with the founders. (we really do ask anything) It’s also very transparent in terms of where the company is at and where it’s going. I find this really refreshing.</p><p>“And of course, the people are great!”</p><h3>What does the future hold for you at Ravelin?</h3><p>“I’ve thoroughly enjoyed my time so far. It’s a great place to work and I plan to continue progressing along the management track. My managers are very supportive of my career goals and I’m confident there’s a bright path for me to follow.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe9488ff9ed" width="1" height="1" alt=""><hr><p><a href="https://syslog.ravelin.com/a-glimpse-into-the-life-of-a-software-engineer-at-ravelin-dfe9488ff9ed">A glimpse into the life of a software engineer at Ravelin</a> was originally published in <a href="https://syslog.ravelin.com/">Ravelin Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting involved in your tech community as a newbie in a language]]></title>
            <link>https://medium.com/makers-academy/getting-involved-in-your-tech-community-as-a-newbie-in-a-language-a3163143b23e?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3163143b23e</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Thu, 25 Jul 2019 09:46:10 GMT</pubDate>
            <atom:updated>2019-07-26T09:39:35.530Z</atom:updated>
            <content:encoded><![CDATA[<p>So you’re learning a new language; maybe it’s for fun, maybe you’re up-skilling, or maybe it’s because you’re starting a new job.</p><p>I’m going to make a suggestion…</p><p>How about, getting involved with a local meet-up for that language?</p><p>There are plenty of meet-ups out there. If you’re not sure, maybe the voices sound something like these:</p><blockquote>Jane Doe — I have a full time job already, the idea of volunteering extra time to organising a meet-up sounds… ambitious.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F10950500&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fstay-alive-beyonce-9to5-working-gif-10950500&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fimages%2Fad41554f1040d4a0592bfaddab454fe7%2Ftenor.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/40f50bcc244870884520e4d54703e4f2/href">https://medium.com/media/40f50bcc244870884520e4d54703e4f2/href</a></iframe><blockquote>Jane Snow — I know nothing. It’s intimidating to ask for help, let alone assume I have anything to offer.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F3480018&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fgame-of-thrones-ygritte-jon-snow-you-know-nothing-gif-3480018&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fimages%2Fc315a5f99d25d5dfce5cc8a7f97c142c%2Fraw&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d4144e70d2240da0ec99a60bf6e6a11/href">https://medium.com/media/9d4144e70d2240da0ec99a60bf6e6a11/href</a></iframe><p>If so, I thought I’d share the story of how I got involved with Women Who Go as a complete newbie to the language, why I’m doing it and how it’s helped me on my coding journey.</p><h3><strong>How do I get started?</strong></h3><p>By way of introduction; I’ve been a software engineer for a couple of years and in February, decided to join an online fraud detection company who’s stack involved Golang.</p><p>A couple of weeks in, my colleague mentions Women Who Go and introduces me to the organisers via Slack. As it turns out, one of the lead organisers were going on maternity and would love some help organising future meet-ups. We had a FaceTime call together with another co-organiser and we hit it off.</p><p>My main ‘sell’ was that I had experience in marketing and organising events (from a previous career). Saying that, I’d not been to this meet-up before, so we agreed to use the next event as a tester for us all and, if we worked well together, we could take it from there.</p><p><strong>What if I don’t know anyone?</strong></p><p>The thing I’ve found with a lot of meet-ups and why I love working in tech is, people are so, so friendly. The key is finding a group you like. I got lucky with the introduction to Women Who Go (WWG). Alternatively, I have friends who simply attended other meet-ups, felt the vibe fitted them, and simply introduced themselves and volunteered to help.</p><p>After being more involved in WWG, I can safely say, we can always use help!</p><p>Besides the traditional call for speakers, ways to support and get involved with a meet-up may be:</p><ul><li><strong>Marketing</strong> — Are you good with social media? Do you have experience managing a mailing list?</li><li><strong>Commercial</strong> — Are you a relationship builder? Could you get sponsorship?</li><li><strong>Community manager</strong> — Could you make the place a safe environment and connect people?</li><li><strong>Web, Design</strong> — Is a bug annoying you, could you give a website a revamp?</li><li><strong>Operations </strong>— Are you organised? Could you make sure the right people are in the right place, at the right time and the right things are in the right folders?</li><li><strong>Body</strong> — Can you help set-up or point people the right way?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*xQ-cmx-wLBilc6B1VmKzhQ.jpeg" /></figure><h3><strong>Why get involved?</strong></h3><p>For me, it feels fab to give back after years of attending some great meet-ups.</p><p>I learn best by immersing myself and one way is by attending meet-ups to be surrounded and enthused by like-minded, supportive people. Organising one definitely made me more committed to attending.</p><p>From a selfish perspective, the time and effort spent has definitely paid off in learning experiences.</p><h3>How has it helped me on my coding journey?</h3><p>Alongside the warm glow of volunteering, in 4 months since my first Slack chat with the WWG founders, I have:</p><ul><li>Started to build a computer from scratch! We’re hosting a monthly bookclub based on <a href="https://www.nand2tetris.org/">an open sourced online course</a> by a couple of computer science professors. As a group, we’re starting at basic computer chips, we’ll learn how to develop a compiler and basic operating system, culminating in writing and playing our own game of Tetris. How cool is that?! By understanding computers better, it’s also helping me become a better engineer.</li><li><a href="https://www.meetup.com/Women-Who-Go-London/events/260170305/">Given a talk on encryption using Golang</a></li><li>Become a sponsor. Well, technically, my very supportive employer <a href="https://www.ravelin.com/about-ravelin">Ravelin </a>was the sponsor who gave us the help, meeting space and a generous budget for food and drink ❤️</li><li>Got Google on board as a sponsor for our next meet up (again, with help and introduction from Ravelin)</li><li>Co-organised a total of 3 meet-ups</li><li>Got involved with another group — <a href="https://github.com/gobridge/about-us/blob/master/README.md">Go Foundry</a> who are developing a standardised curriculum for teaching Golang</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*4n6nHqcwDEbiufFOtbGTug.png" /><figcaption>My cryptography assistant, Gopher Holmes. Courtesy of <a href="https://medium.com/u/650d8387983b">Rob Baines</a> <a href="https://telecoda-tees.com/">https://telecoda-tees.com/</a></figcaption></figure><p>All of this using, and thus developing, a large set of the skills mentioned above:</p><ul><li>Some <strong>directly</strong> involving the language I’m learning — I knew nothing about Go or encryption and did a bunch of research for the talk</li><li>Some <strong>indirectly</strong> — e.g. finding out how other companies used Go in their businesses while looking for speakers and sponsors</li></ul><p>So far, it’s been a rewarding experience for a couple of hours a week plus attending the monthly meet-up.</p><p>All in all, it’s easy to get involved, you’ll get the opportunity to work with fantastic co-organisers, meet some lovely people and learn a lot from the experience.</p><p>What are you waiting for? :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F9865450&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fgood-boy-husky-arrived-gif-9865450&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fimages%2Fb94ffa1f656d867cffe1b93dca891fad%2Ftenor.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/af5b0099ed13113be027317af7c7bbdd/href">https://medium.com/media/af5b0099ed13113be027317af7c7bbdd/href</a></iframe><p>Below are some great meet-ups I’ve attended before and who welcome volunteers:</p><ul><li><a href="https://www.meetup.com/Women-Who-Go-London/">Women Who Go London</a></li><li><a href="https://bridgefoundry.org/">Bridge Foundry</a> (umbrella for many languages and groups)</li><li><a href="http://www.codebar.io/">Code Bar</a></li><li><a href="http://womenwhocode.github.io/#how_contribute">Women Who Code</a></li><li><a href="https://anitab.org/get-involved/volunteer-anitab-org/">Anita Borg</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3163143b23e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/getting-involved-in-your-tech-community-as-a-newbie-in-a-language-a3163143b23e">Getting involved in your tech community as a newbie in a language</a> was originally published in <a href="https://medium.com/makers-academy">Makers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero to Launch in 6 Weeks — a Minimum Loveable Product]]></title>
            <link>https://medium.com/@alicespyglass/zero-to-launch-in-6-weeks-a-minimum-loveable-product-2f920f5bc176?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f920f5bc176</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[insurtech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Tue, 01 May 2018 14:32:30 GMT</pubDate>
            <atom:updated>2018-05-01T14:32:30.424Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Flt4IVjEgx87n2%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Frocket-bamboo-lt4IVjEgx87n2&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Flt4IVjEgx87n2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="310" frameborder="0" scrolling="no"><a href="https://medium.com/media/569b19324027d59aecd7040bef0ef2c0/href">https://medium.com/media/569b19324027d59aecd7040bef0ef2c0/href</a></iframe><p>In 2016 there were roughly <a href="http://researchbriefings.parliament.uk/ResearchBriefing/Summary/CBP-7706">11 million private renters in the UK</a>, with that figure looking to rise to a quarter of UK households by 2021. If you’re a private renter in a property managed by a major letting agent, the chances are that you will have been told to get <a href="http://wp.myurbanjungle.com/blog/insurance/tenants-liability-insurance/"><strong>Tenants Liability Insurance (TLI)</strong></a> before signing the dotted line.</p><p>In line with Urban Jungle’s mission to build an insurance provider that our customers love, we believed that by offering Tenants Liability Insurance ourselves, we could help renters in two ways:</p><h3><strong>1. Provide great cover, cheaper</strong></h3><p>Renters resent being forced to buy TLI, particularly when it costs so much. As a lean, online provider, we were confident that we could offer a much better purchase experience, at a lower cost, and pass on the savings.</p><h3><strong>2. Delivering great user experience ❤</strong></h3><p>Buying TLI online can be a real pain; users are often made to answer way more questions than are necessary, only to discover there are surprise add-ons. On top of this, the T’s and C’s tend to be unclear and any claims or changes can take days.</p><p>We knew buying TLI could be done on one page, with fewer than 10 questions and in under 2 minutes. Imagine a world where you can manage your policy online; where documents are readily available and queries are dealt with immediately.</p><p>With this in mind, we set ourselves the goal of launching UJ Tenants Liability Insurance in 6 weeks.</p><p>6 weeks is a punchy target in an industry steeped in regulatory requirements where companies are used to moving at a pace which can only be described as glacial. However, (one of) our mission is to set a new pace in this arena and we had to start with ourselves.</p><p>This blog, the third in our Urban Jungle series on the tech we’re building, focuses on the latter (delivering great user experience) and shares our work as a team in the design and build of the purchase journey. Specifically:</p><ol><li>Journey / Process / Tools — How we did it</li><li>Lessons Learned — what went well and what we’d do differently</li></ol><h3><strong>1. Journey / Process / Tools — How we did it</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F11LK0CKzYtkaic%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fsatisfying-line-production-11LK0CKzYtkaic&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F11LK0CKzYtkaic%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="290" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5902409861279eea47a1ef77d399ce0/href">https://medium.com/media/f5902409861279eea47a1ef77d399ce0/href</a></iframe><p><strong>Scope out the Minimum Loveable Product (MLP)</strong></p><p>Having set ourselves the task of delivering a great <strong>product</strong>, through a purchase <strong>experience</strong> our users would love, in the <strong>minimum time</strong> possible, we had to be clear as to what needed to be done up front. This was no beta launch; we were going straight for alpha.</p><p>This meant articulating the minimum functionality for selling a Tenants Liability Insurance policy; designing what this looked like on the front end, mapping out changes needed in the backend, and planning how the whole journey fit within the tech architecture.</p><p><strong>Set roles</strong></p><p>As our team grows, we are trying to move from a set up where everyone works on the same thing, to having clearer division on roles and responsibilities, but also still working together very closely. After agreeing the appropriate scope for our 6 week target, we divided up responsibilities.</p><p>We used <a href="https://asana.com/">Asana as a project management tool</a> for chunking up tasks and measuring progress.</p><p><strong>Communication</strong></p><p>We set up a cross-functional team including key non-tech stakeholders and held bi-weekly check-ins which increased in frequency once we got closer to launch. In these meetings we would share our progress, as well as get updates on the commercial and operational streams of the product, ensuring we always saw the bigger picture.</p><p>Outside of this, the tech team had weekly engineering meetings, weekly one-to-ones, and would sit next to each other.</p><p><strong>Continuous review in Development</strong></p><p>All of our code is peer reviewed before merging, and a dev build is released for internal testing on desktop and mobile before the public launch.</p><p>In general, there’s always a work in progress on the dev environment with the latest version of the platform. This allows the broader team and some external beta testers to play with our latest ideas and give us immediate UX feedback.</p><p><strong>Debrief</strong></p><p>We collected our thoughts and shared our experience with the team shortly after the public launch. We’ve then been proactive about taking the lessons learned from this debrief to adjust the way we work going forward (see below).</p><p><strong>Bonus step: the follow-through</strong></p><p>Delivering a truly great product, requires real feedback. As quickly as the sales came in, so did customer queries.</p><p>As well as using Hotjar and google analytics to measure user behaviour on the website, all of us at Urban Jungle — from the CEO to software engineers — take shifts on customer service manning the chat and taking phone calls. Based on these conversations that we have with our users, we quickly find out what matters; whether it’s making errors on the page clearer or providing the ability to access documents straightaway and send them to a third party.</p><p>Adding these updates and features quickly post launch has been key to the product’s success. It’s been super satisfying to see the subject of customer service calls turn into raving reviews on Trustpilot.</p><h3><strong>2. Lessons Learned</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F4dqorWV0HjdTy%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwrong-4dqorWV0HjdTy&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F4dqorWV0HjdTy%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="312" frameborder="0" scrolling="no"><a href="https://medium.com/media/2596b2f3c6e771f0251145991842081d/href">https://medium.com/media/2596b2f3c6e771f0251145991842081d/href</a></iframe><p><strong>WHAT WORKED WELL</strong></p><p><strong>Speed</strong></p><p>It was great to set ourselves a punchy target and even better that we met it.</p><p><strong>Wireframes</strong></p><p>We invested the time up front on building visual wireframes; they’re great for making sure both product owners and developers are on the same page and forms the basis for discussion. It’s also useful for backend services as you talk about functionality and how they would be implemented.</p><p>We also created a diagram of our tech stack to outline the work that needed to be done in each part which the non-technical team members found useful.</p><p>There are a lot of shiny tools for drawing wireframes, however, we simply used powerpoint / google slides.</p><p><strong>Clean Codebase</strong></p><p>We reaped the dividends from taking the time to <a href="https://medium.com/urban-jungle/3-front-end-improvements-for-faster-user-experience-2ce2d13efab9">clean up the code base in the rewrite of our website 6 months ago</a>. The modularity of components meant they were easy to reuse and the integration of additional services straightforward.</p><p><strong>External Tools</strong></p><p>Leveraging products from other providers, such as instapages to create landing pages, meant we could use our resources on building things which added the most value.</p><p><strong>WHAT WE’D DO DIFFERENTLY</strong></p><p><strong>Smaller chunking</strong></p><p>After building the journey, we wanted our customers to be able to access their documents online right away as a matter of course.</p><p>However, we underestimated the amount of work involved as it effectively became a redesign of the online account management section of the website.</p><p>Now that we had more than one product, we wanted to design the section so that it could handle customers for not just two products, but thinking ahead, multiple products. This involved rethinking the way we structured our data objects and APIs for calling the data from the backend to be “dumber” or less specific.</p><p>This meant we launched the Tenants Liability Insurance product without the account management capability in favour of releasing a more stable version of the section a few days later.</p><p><strong>More frequent stand-ups</strong></p><p>Ideally, we would have made the above decision to delay the account management feature earlier in the process. Where we sit next to each other and have regular meetings it’s easy to assume everyone knows what everyone else is doing and is thinking the same thing. More frequent stand-ups could help us be more iterative on what should be in the MLP and what could wait until post launch in the future.</p><p><strong>Get multiple versions onto dev earlier</strong></p><p>At Urban Jungle, we are all committed to testing and attempting to break every version which is posted to our dev site, effectively treating it as a draft, or “soft”, production release.</p><p>What this means is that the target dev launch date got set very close to the target prod (hard) launch date, leaving little room to manoeuvre if something unexpected comes up.</p><p>Bearing in mind that most of the time, a product actually takes a number of pieces and ends to come together in order to get a working version onto dev, the lesson is to bear this in mind and setting a wider breathing space between dev and prod targets so that we can include more iterative loops, as well as getting feedback on local versions from other members of the team earlier.</p><p>All in all, the project was a success — we got a new product on the shelf in 6 weeks and sold a policy on the day of launch!</p><p>While it’s great that sales (as well as our tech refinements) are continuing to pick up, the greatest reward for the team has been the overwhelmingly positive feedback on the user experience and value of the product… and the fact that customers took the time to write glowing reviews on <a href="https://uk.trustpilot.com/review/myurbanjungle.com">Trustpilot</a> ♥</p><p>Watch this space for new features, give us a clap or get in touch with your thoughts. <a href="https://www.facebook.com/myurbanjungle/">Urban Jungle</a> would love to hear from you!</p><p><a href="https://medium.com/urban-jungle/3-front-end-improvements-for-faster-user-experience-2ce2d13efab9">Read part 2 of the series, 3 front-end improvements for faster user experience, here.</a></p><h3>About us</h3><p>Urban Jungle is a home insurance business, specialising in renters and sharers. We’re using technology to make insurance better for young people.</p><p>If you’re looking for <a href="https://welcome.myurbanjungle.com/tenants-liability-insurance">Tenants Liability Insurance, get cover for £40 per year here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f920f5bc176" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 front-end improvements for faster user experience]]></title>
            <link>https://medium.com/urban-jungle/3-front-end-improvements-for-faster-user-experience-2ce2d13efab9?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ce2d13efab9</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[home-insurance]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Fri, 24 Nov 2017 11:20:40 GMT</pubDate>
            <atom:updated>2017-11-24T11:20:40.212Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the second part of the <a href="http://wp.myurbanjungle.com/blog/insurance/7-product-features-which-make-urban-jungle-a-better-place-to-buy-insurance/">Urban Jungle blog series</a> on the tech we’re building and why it should make a difference to they way you buy insurance.</p><h3><a href="https://myurbanjungle.com/">Urban Jungle v2.0</a> has launched!</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSQgbkziuGrNxS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSQgbkziuGrNxS%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FSQgbkziuGrNxS%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="272" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee0cf000d6832be216d74458b3f7ba3b/href">https://medium.com/media/ee0cf000d6832be216d74458b3f7ba3b/href</a></iframe><p>On the surface, the look isn’t that different. On the technical side however, we’ve been excited about making the code cleaner, the app faster and hopefully the overall experience for the user, better.</p><p><strong>WHAT WAS THE CHALLENGE?</strong></p><p>At Urban Jungle, we’re all about making it super easy to get your home insurance sorted. So for ease of use and smoother experience, we’d chosen to go with a single-page app (<a href="https://www.codeschool.com/beginners-guide-to-web-development/single-page-applications">SPA</a>) architecture.</p><p>The tradeoff is, the app is loaded up front when a user lands on the site. We were concerned that this meant some users, particularly those with a bad mobile connection, could suffer slow speeds at the previous build size.</p><p><strong>SUMMARY — WHAT DID WE ACHIEVE?</strong></p><p>For users:</p><ul><li>Reducing load time to a third of what it was (from 7.9 seconds to 2.6 seconds based on google analytics)</li><li>Cutting initial bundle size to one sixth(!) of what it was (from 6.2MB to &lt;1MB)</li></ul><p>For us:</p><ul><li>Tighter build-measure-learn loop — faster deployment of a more maintainable library</li></ul><p><strong>HOW DID WE DO IT?</strong></p><p>The team had earmarked 3 months for a rewrite of the site after the launch of v1 (our <a href="https://www.techopedia.com/definition/27809/minimum-viable-product-mvp">minimum viable product</a>) in July. While the aim of v1 was to get something out to test the market, v2 was about streamlining a solid base for vN.</p><p><strong><em>1. Biting the bullet and migrating from Angular 2 to Angular 4</em></strong></p><p>The front end of Urban Jungle is built using Angular, an open-source framework designed by Google who this year released its upgrade (<a href="https://www.valuecoders.com/blog/industry-news/angular-4-release-comparision-angular-2/">good summary here</a>).</p><p>In essence, Angular 4 apps use less space and run quicker compared to Angular 2 apps. However, the decision to migrate is hardly ever (dare I say never?) cost free. We knew we would have to update the codebase and rewrite some key components to accommodate the changes. The technical team made the conscious decision to migrate, and invest the time doing so, to make sure we continue to provide the best product.</p><p><strong><em>2. Utilising Lazy Loading</em></strong></p><p><a href="https://angular.io/api/router/Routes#lazy-loading">Lazy loading</a> speeds up the app by only loading features when the user navigates to their routes. So rather than loading the whole app upfront, this technique breaks it up into smaller bundles that are loaded on demand.</p><p>We then combined this with a <a href="https://vsavkin.com/angular-router-preloading-modules-ba3c75e424cb">pre-loading</a> strategy for setting the order of modules to be pre-loaded in the background, in anticipation of what may be needed next. This reduces build size and contributes to a smoother user experience.</p><p><strong><em>3. Stripping out vendor packages</em></strong></p><p>As a point of general housekeeping, it’s good to delete redundant package imports to a module so that it isn’t bundled unnecessarily with a build. When making a Javascript app, it’s easy to get npm happy; you read about a cool implementation or bug fix in stack overflow and before you know it, you’re 6 months in with a thousand dependencies.</p><p>A solid win from our vendor tidy-up was moving from bundling Auth0 dependency in our app, to using their hosted page solution. This reduced the size of the app by a fair chunk as well as removing a number of javascript dependencies.</p><p>We also looked to make the best use of any external libraries i.e. doing 5 things with 3 libraries rather than 5 (if possible) which meant being more discerning with the libraries we chose.</p><p>All in all, the rewrite gave us the opportunity to revisit those moments which made us go “if I could do this again, I would’ve done it differently”.</p><p>During this period, we took the time to review and tidy up the codebase by making features more modular and the code cleaner (made components more reusable and better use of services). This not only makes for happier development (and developer) but also faster deployment of a more maintainable library.</p><p>Take that <a href="http://agile4life.com/wp-content/uploads/2014/10/techdebt.jpg">technical debt</a> 👊</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FKoE4dzVStw9RS%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FKoE4dzVStw9RS%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FKoE4dzVStw9RS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="330" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf80520b435859ed318ef42efc47cd39/href">https://medium.com/media/bf80520b435859ed318ef42efc47cd39/href</a></iframe><p>Watch this space for new features or get in touch with your thoughts. <a href="https://www.facebook.com/myurbanjungle/">Urban Jungle</a> would love to hear from you!</p><p><a href="http://wp.myurbanjungle.com/blog/insurance/7-product-features-which-make-urban-jungle-a-better-place-to-buy-insurance/">Read part 1 of the series on the 7 product features which make Urban Jungle a better place to buy insurance here.</a></p><h3>About us</h3><p>Urban Jungle is a home insurance business, specialising in renters and sharers. We’re using technology to make insurance better for young people.</p><p>We offer great quality home contents insurance at competitive prices.</p><p>To get a quote <a href="https://myurbanjungle.com/landing">click here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ce2d13efab9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/urban-jungle/3-front-end-improvements-for-faster-user-experience-2ce2d13efab9">3 front-end improvements for faster user experience</a> was originally published in <a href="https://medium.com/urban-jungle">Urban Jungle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MIDDL: Final Project at Makers Academy]]></title>
            <link>https://medium.com/@alicespyglass/middl-final-project-at-makers-academy-3a11f4aba190?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a11f4aba190</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 07:01:00 GMT</pubDate>
            <atom:updated>2017-07-03T07:01:00.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uDyuIMlX76MjSMlReEqjxA.png" /><figcaption>A mobile app to help friends find places to meet. In the middle.</figcaption></figure><p>It’s been an amazing ride.</p><p>Putting everything we’d learned in 10 weeks a Makers; teams of four took an idea to production, culminating in a show and tell pitch to friends and family.</p><p>This blog is a summary of the whys, whats, hows, lows and highs of the project I was a part of via a walkthrough of our final presentation.</p><p>Before we dive in, a shout out to my beautiful team mates who made this last project a joy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CvXPkRHJe6TFG_nSXwok6A.png" /></figure><p><a href="https://github.com/freddyfallon">Freddy “vibe” Fallon</a></p><p>Kittysquee <a href="https://medium.com/u/6c5be452d700">Elaine Osbourn</a></p><p><a href="https://github.com/colinturner">Colin “the Canadian” Turner</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-wCnKQsrYvrTOUAuqb410g.png" /></figure><p>The idea for this app had started percolating about a year ago when I was arranging to meet up with a friend after work; she was working in west London, I was based in the east. However, as much as we loved each other, the idea of schlepping all the way across London appealed to neither of us.</p><p>Meeting in the middle seemed fair, if not obvious. Finding a place was harder as it was neither of our neighbourhoods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngNfJI5zox_Fhd57OGrsVA.png" /></figure><p>Apparently I wasn’t the only person who found this tricky. Many friends felt the same and it was at Makers that I found 3 others who wanted to solve this challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eBXJmhfbVZOkKp6DZFW3Pw.png" /></figure><blockquote>The key to successfully turning an idea into a product is in the planning. This is more a process than a single action or meeting (I’m sure we’ve all had a billion ideas or conversations which has become little more than a one word note on our phones).</blockquote><p>This can also be the part which determines whether the idea turns into a nine headed monster or a <a href="https://blog.leanstack.com/minimum-viable-product-mvp-7e280b0b9418">minimum viable product (MVP)</a>.</p><p>Being programmers, we do love codifying processes so you’ll find different frameworks for running a design sprint, the most popular right now being <a href="http://www.gv.com/sprint/">Sprint, a book by former googlers</a>.</p><p>For team Middl, we were recommended <a href="https://thoughtbot.com/product-design-sprint/guide">thoughtbot</a> by our coach. The summary and checklists were handy.</p><p>The sprint for us consisted of 3 key stages:</p><ol><li><strong>MVP: Define the problem and get creative solving it</strong>. I love this part — constrained only by our imagination, the aim is get crispy (as opposed to vague and fluffy) on our problem statement, then to diverge and explore it from every angle. Throw everything on the board and see what sticks. For a time the conversation diverged to this being some sort of dating app… however, we pulled it back and stuck with <em>“An app to help friends find the best places to meet in the middle”</em>. Success would be an MVP which gave a recommendation of a place in the middle of 2 given locations.</li><li><strong>Choosing the tech stack</strong>. Having defined the problem and end point, we now wanted to find the best tools to make this app. But what kind of app…Android, iOS, web or other (it’s interesting how windows never once crossed our minds until much later)? We split up the research 4-ways for an hour and came back to share what we found with each other along with a recommendation. In the end we chose React-Native (which compiles to both iOS and Android) and its associated technologies, integrated wth google maps api and WhatsApp for contacts and messaging.</li><li><strong>Dive in and get learning</strong>. None of us had used any of the technologies before (besides myself with a little bit of WhatsApp on a previous group project — <a href="https://find-my-train.herokuapp.com/">find my train</a>). With React-Native forming the base of the app, we set ourselves a learning budget (2 days) and dove into tutorials, sharing notes and resources with another group who also decided to do a project in React-Native. <a href="https://www.udemy.com/the-complete-react-native-and-redux-course/learn/v4/overview">This Udemy course was particularly useful</a>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfy1ai_bkwdWcRQb9Y4Emw.png" /><figcaption>Creating an app takes a bunch of technologies</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NAS6VK6E7yJRwQGM042x5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCg7pRFm8PG07N8qomzxLQ.png" /><figcaption>Complete with food themed inspirational quotes to get you excited about meeting your friend</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v58ZY3CH7OuB4hoQkkGaLg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*Xvr835ydj5NmMdUxy7dY7A.gif" /></figure><p>If you would like to be the first to know when the app is released, <a href="http://eepurl.com/cUJyz1">sign up here</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XJMVqODpGHoLjNrIiQqdxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZKW2zaLf2qeAab9SX2QSpg.png" /></figure><h3><strong>How did we manage to get from zero to MVP in 6 days?</strong></h3><ul><li><strong>Daily stand-ups</strong> in the morning to go through the tasks for the day and <strong>retros</strong> at the end of the day to share any learnings or struggles</li><li><strong>Pair programming</strong> nearly everyday. Pairing pragmatically based on what individuals wanted to learn / do balanced with any continuity needed for certain branches or work streams</li><li>Using <strong>trello</strong> as our task manager to keep track of tickets and progress</li><li>Github informs us that we made over 150 commits and 28 branches</li></ul><p>However, it wasn’t always a walk in the park.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yqzHJ6LMY-0dzdUyy84nQA.png" /></figure><p><strong>Learning React Native was hard</strong></p><p><a href="https://github.com/facebook/react-native">React-native</a> is a pretty neat framework, built by Facebook, and popular right now amongst the start up community as it gets apps (iOS and Android) up and running and looking slick in a short time.</p><blockquote>The key here is that it’s a <strong>SHORT</strong> time, not <strong>NO</strong> time. As with anything, there is a learning curve.</blockquote><p>The flip side of having a wealth of resources on the world wide web is, it can get easy to get sucked into doing tutorial after tutorial and get lost in trying to make a dent in the progress bar and never feel like we know enough. There’s always another tutorial, another 3 minute video that will show me how to do this other thing…</p><p>Which is why on Wednesday afternoon, having not written a single line of code for the project, we were getting seriously worried as to whether we would have anything to show let alone freeze in one week’s time. At this point we decided to start building and agreed we would figure it out as we went along. Turns out we’d picked up a lot and were soon implementing features.</p><p><strong>Testing</strong></p><p>Test driven development (TDD) like <a href="https://www.thoughtco.com/essential-sport-climbing-gear-755432">laying the bolts and quickdraws along a rock face for climbing</a> — so that when something breaks, it’s easy to locate and fix rather than finding yourself free falling into debugging oblivion. The testing framework for React-Native is Jest (*insert joke about being made a fool here*). Like learning React-Native, there is a learning curve. Except now you’re learning how to use one thing, so that you can test something else which, you’re also learning…</p><p><strong>Refactoring</strong></p><p>The context for refactoring is “software craftsmanship”. This is essentially about writing <a href="https://cleancoders.com/">clean code</a> so that the next person which comes along who has to try and read or use your code, it doesn’t make them want to cry.</p><p>The thing about working on a cool project is, once you put hands on keyboard, you’re just super happy stuff works.</p><p>And that is how this 300 line monstrosity happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*pcTS7m3cEBSjO9tVrc2uvA.png" /></figure><p>We had a bunch of files, this was just the biggest, baddest one.</p><p>Looking at it, through the lens of a developer, it makes me cringe even more than watching an episode of The Office.</p><p>This is where refactoring comes in. Refactoring is where we use <a href="https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)">SOLID principles</a> to edit and restructure the code. For example, pulling out functions so that methods only had single responsibility and deleting stuff which was no longer necessary.</p><p>After a fair number of hours and even more coffees, we managed to cut this down by over 70% to under 90 lines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cpxG_6LqP984R_5kEayFg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1B2ZaHcgpx07ZYB3JUABw.png" /></figure><p>Taking a step back, to say 4 months ago. If someone had shown me this app (or any of those built by Makers) and said to me…</p><p>…you’re going to build this thing</p><p>……in 6 days</p><p>………from scratch</p><p>…………with 3 other people who also have zero coding experience</p><p>……………I might have asked them… what they were smoking?</p><p>Now, standing on the other side having achieved this, I’d say it’s gone pretty well.</p><p>Something I’ve learnt at Makers is that coding is the easy part. The magic really happens when you put these 3 ingredients together:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pTaN_YnkEEN13FgvRbZtjQ.png" /><figcaption>Love a good Venn</figcaption></figure><p>Finding the right tools, instilling industry best practice and having the right mix of people. For me, I feel lucky to have been in such a great team. We communicated really well.</p><p>Finally, the best thing to have come out of this whole project is that we now have a reason to stay in touch with Elaine…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cpqDRWDPEBr4EnfPHt3bhQ.png" /></figure><h3>Has no one else thought of this already?</h3><p>As it turns out, there are a couple of alternatives out there trying to solve different flavours of this problem — one released just 4 days ago!</p><ul><li><strong>Meetie London</strong>: <a href="http://metro.co.uk/2017/06/28/tube-map-app-helps-londoners-meet-friends-in-the-middle-6739969/">http://metro.co.uk/2017/06/28/tube-map-app-helps-londoners-meet-friends-in-the-middle-6739969/</a></li><li><strong>Meet me halfway</strong>: <a href="https://play.google.com/store/apps/details?id=com.jonathannakhla.meetmehalfway&amp;hl=en_GB">https://play.google.com/store/apps/details?id=com.jonathannakhla.meetmehalfway&amp;hl=en_GB</a></li><li><strong>Whats halfway</strong>: <a href="http://www.whatshalfway.com/">http://www.whatshalfway.com/</a></li></ul><p>However, if you’ve liked what you seen and would like to be the first to find out when Middl is released in android / iOS, sign up here!</p><p><a href="http://eepurl.com/cUJyz1">http://eepurl.com/cUJyz1</a></p><p>Suggestions welcomed ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a11f4aba190" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wk7–8 Makers Academy: “Smooth seas don’t make good sailors”]]></title>
            <link>https://medium.com/@alicespyglass/wk7-8-makers-academy-smooth-seas-dont-make-good-sailors-604f0af6e8c2?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/604f0af6e8c2</guid>
            <category><![CDATA[single-page-applications]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[debugging]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Tue, 09 May 2017 07:31:05 GMT</pubDate>
            <atom:updated>2017-05-09T07:31:05.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toRCHXRT0mbPHzBABQhibw.jpeg" /><figcaption>Stormy seas also make the best art</figcaption></figure><p>I’d like to begin this post by sharing the story of my mate, Dave.</p><p>Dave is a friend from university. He had taken Oceanography as a degree and after graduating, contrary to convention, had actually gotten a job which was related to his studies.</p><p>As might be expected of a typical graduate with a bank balance in red, a niche degree and limited options, Dave had taken the first role he was offered.</p><p>His work involved being on boats for weeks if not months at a time, surveying the ocean floor.</p><blockquote><a href="http://mentalfloss.com/article/60150/10-facts-about-internets-undersea-cables">Did you know…99% of international data is transmitted by wires at the bottom of the ocean?</a></blockquote><p>This company would get commissioned to make sure they don’t lay internet cables into trenches which are too deep. Or that oil companies don’t dig where they shouldn’t.</p><p>As with any job, it had its pros and cons. On the one hand, he got to travel and pretty much sail the 7 seas. On the other, imagine sailing said seas on a leaky boat.</p><p>It was the recession in 2008 and the company took the Make-Do and Mend attitude to its outer limits. Not only was the equipment bad, but management was mean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0XzTcR2XkEvuRBVbtFpouw.jpeg" /></figure><p>After 5 years, he jumped the sinking ship and left shortly before the company folded (and sank).</p><p>Somewhat weary about repeating the experience, he decided to freelance.</p><p>On his first job…he was shocked. He couldn’t believe how nice these other boats were. The equipment was new. Everything was shiny. Things weren’t plastered with duct tape. Stuff actually worked!</p><p>That was…until they didn’t. Week 2 on the first job, he came across a panicked crew in the mess hall. The buoys weren’t working. They needed them to collect the data for the job. No buoys, no data, no pay, more weeks at sea.</p><p>Turns out, Dave knew how to fix the problem. He had faced a similar issue with an older model which regularly became waterlogged and shorted at certain temperatures. The fix was to switch out a part which could actually be found in other, less essential equipment.</p><p>Dave quickly got a reputation as the guy who could fix things, the one you wanted on your team. The years spent solving problems, mending and making do had made him the MacGyver of <a href="http://oceanservice.noaa.gov/facts/bathymetry.html">bathymetry</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vMUMw62XtvTXcVOzXwsTfg.jpeg" /><figcaption>Making creativity sexy since 1985</figcaption></figure><p>The moral of this story is…smooth seas don’t make good sailors.</p><p>Now, having spent several hours delving into just why users couldn’t log in using Facebook in my weekend challenge coding a clone of instagram…. I appreciate the sentiment more than ever.</p><p>Many a coder before me have chosen to laugh rather than cry and generate memes on debugging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*6zbLRw-jj039ERhk1zRBhA.jpeg" /></figure><p>Over the weeks, I’ve learned to embrace the struggle. While computer science may have given context or grounding to some of the problems I’ve come across, in the long run and in the real world, experience is what will save me time and help me get things done. I believe.</p><p>Below are some debugging techniques I’ve learnt and common bugs I have come to squash.</p><p><strong>TECHNIQUES</strong></p><p><strong>Tighten the loop</strong></p><p>What: get specific on what is going wrong.</p><p>How: Follow the stack trace — what is the error message pointing you to?</p><p><strong>Get visibility</strong></p><p>What: Find out what the programme is doing. What do you think the functions should be doing? Are they doing it?</p><p>How: Use a <a href="https://repl.it/">repl</a> and play around.</p><p><strong>Common Errors</strong></p><p>Likely faced, often, which will bring you no joy in fixing. Always check for these first.</p><ol><li>If you get an error message, check the spelling. More than fifty percent of the time, it’s because I’d typed something wrong.</li><li>If the error message mentions syntax error, check the grammar. There’s a stray or missing comma, colon, semi-colon, curly braces etc</li></ol><p><strong>Niche Errors</strong></p><p>Pain you will only know once you start working on specific things.</p><ul><li>Error in Ruby when you ‘know’ everything works — check the order in which programs are `required`</li><li>Working with databases — if you change the database / tables in any way, rake it. If in doubt, rake it again.</li><li>Environment variables e.g. API keys — if you set it locally, each tab in the terminal is technically a different environment. If you then fire up the server, make sure it’s from the same tab or the programme won’t be able to access the key.</li><li>Code wars — the kata is telling you it’s expecting exactly the same answer you’ve given it. Try `return` instead of `puts`.</li></ul><p>For this blog, I had originally considered comparing debugging to going through the 5 stages of grief. Apparently other developers feel the same way. <a href="https://raygun.com/blog/5-stages-of-debugging/">This blog</a> by <a href="https://medium.com/u/3e912712f84d">Raygun</a> is a great example.</p><p><strong>TOOLKIT UPDATE</strong></p><p>New stuff added to the bag</p><p><strong>WK7: Further Javascript</strong></p><p><a href="https://medium.com/@nickrupp95/makers-academy-w7-d2-emotionally-confusing-test-framework-b918e3db0c19"><strong>Naughty News</strong></a><strong> : a single page web app</strong></p><p>Team project with <a href="https://medium.com/u/65b0c4d42377">Edward Ward</a>, <a href="https://medium.com/u/1d5909d62127">Man Vs Code (Nick Rupp)</a>, <a href="https://medium.com/u/fdfad76fb841">Stephanie Crampin</a></p><p>Single page web apps</p><p>Ajax — a broad group of technologies for creating web apps which allows users to interact with the page without having to constantly refresh the page:</p><ul><li>HTML and CSS</li><li>Javascript</li><li>JSON (Javascript Object Notation) — javascript-based data format. Uses JavaScript syntax to share data, however, it is text so can be used in any programming language.</li><li>Document Object Model (DOM) — framework for dynamically displaying and interacting with the page’s content</li><li>XMLHttpRequest (XHR)</li></ul><p>http-server (node) — small library that runs a local server (e.g. my laptop) so I can see what I’m making</p><p>API (getting data from the Guardian, Aylian)</p><p>Writing our own testing framework for javascript</p><p><strong>Wk8: Ruby on Rails</strong></p><p><strong>Chicken Connoisseur: A battery farmed version of Yelp</strong></p><p>Team project with <a href="https://medium.com/u/a5ba9a35e6c6">Emil Iliev</a>, Pete Wilkins, Sean Blundell</p><ul><li>Ruby on Rails — framework for magically automating the creation of an app</li><li>Facebook login — user login authentication</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjAitHIn2lgp0xUdpXmGqA.png" /></figure><p>❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=604f0af6e8c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wk5–6 Makers Academy: “You’re so far past the line, you can’t even see the line.]]></title>
            <link>https://medium.com/@alicespyglass/wk5-6-makers-academy-youre-so-far-past-the-line-you-can-t-even-see-the-line-f9fc38ae3d84?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9fc38ae3d84</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 07:26:01 GMT</pubDate>
            <atom:updated>2017-04-27T07:26:01.741Z</atom:updated>
            <content:encoded><![CDATA[<h3>Wk5–6 <a href="https://medium.com/u/5fa7fd928efe">Makers Academy</a>: “You’re so far past the line, you can’t even see the line. The line is a dot to you.”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*GU6YJrHzc8XXYLB8sqgBQA.png" /></figure><p>I read somewhere, something, about Makers pushing you so far out of your comfort zone, that you won’t remember what “comfortable’ feels like.</p><p>Each week, faced with each new bit of technology, has been like standing at the edge of a swimming pool at 7am; you’re there, you’re committed, you know it’ll be fine once you get in, but the first 3 seconds…. is going to be a shocker. Better just to dive in.</p><p>Having got to a point where coding in Ruby was actually the easiest part of the day, Makers pushed me into a colder pool.</p><h3><strong>Welcome to week 5: JavaScript Week</strong></h3><p>I’d started learning JavaScript through <a href="http://www.freecodecamp.com/">freecodecamp</a> last year when the idea of joining a bootcamp was gently percolating inside me. It’s essentially the tech test for joining <a href="https://foundersandcoders.com/">founders and coders</a>, another bootcamp a developer friend had pointed me to. In fact, it was the nights spent coding through the front end certificate which got me really hooked and made me realise I wasn’t simply enamoured with the IDEA of coding, but actually enjoyed coding itself. The course was a mix of the classic front-end HTML, CSS, JQuery and I distinctly remembered thinking to myself “wow, I really like Javascript”….</p><p>So this week should have been easy, I thought.</p><p>The task was to “simply” rewrite our airport challenge, in javascript. However, instead of taking to the task like a duck to water, I sank somewhat like a duck weighed down with rocks.</p><p>First off, what’s the deal with these semi-colons?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*Dizy3xvujGFSTCSRgWCCeg.jpeg" /><figcaption><a href="http://theoatmeal.com/">http://theoatmeal.com/</a></figcaption></figure><p>An excellent analogy to mental state of the cohort shared by <a href="https://medium.com/u/fdfad76fb841">Stephanie Crampin</a> at the beginning of the week.</p><p>This was rather distressing at first, however, by the end of the week, I was looking forward to my tests failing once more (<a href="https://medium.com/@alicespyglass/a-man-of-genius-makes-no-mistakes-his-errors-are-volitional-and-are-the-portals-to-discovery-90a62ec2cffe">why this is a good thing</a>) and had learnt 2 things about learning to code in a new language:</p><p><strong>1 . It’s not a direct translation</strong></p><p>Similar to copying and pasting text for French homework into a dictionary, trying to directly translate one coding language to another will yield some frustrating results that are less amusing than spoken languages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*leTbG3DbC2CGviEMRX2G4A.jpeg" /></figure><p>This leads to lesson two.</p><p><strong>2. Learn the basics</strong></p><p>This is so that, when writing code and seeing an error, you will know whether it’s because you’re writing <strong>bad</strong> code or not writing code at all (at least in a way which can be recognised).</p><p>As with any language, each code library has it’s own rules and laws. While I could get the gist of what works and what doesn’t by trial and error, I found that, by taking an hour to do a <a href="https://www.codecademy.com/learn/javascript">codecademy intro to JavaScript</a>, my pair partner and I got up to speed and paddling along much more happily. There’re so many free resources online, it would be a crime not to use them.</p><p><strong>Note to self </strong>— if I want to learn a new new language with less support out there (e.g. iOS development in swift), the key things to find out before diving in would be:</p><ul><li>how functions / methods are constructed and called</li><li>how variables are set and accessed</li><li>what are the grammar rules (e.g. in JavaScript, it only recognises a function if brackets are placed after the function name)</li><li>how objects behave</li><li>what is the language’s version of basic syntax and functions e.g. string, text, print</li></ul><p>Having taken a whole week to get to grips with JavaScript (and associated technologies below), Makers once more got us to level up.</p><h3><strong>Welcome to week 6: Project week — Makers BnB</strong></h3><p>You guessed it — let’s get 4 people who’s been coding for 9 weeks (8 in a different language) to recreate the website for an online enterprise <a href="https://techcrunch.com/2017/03/09/airbnb-closes-1b-round-at-31b-valuation-profitable-as-of-2h-2016-no-plans-for-ipo/">valued at $30 billion last year</a>. Why not?!</p><p>The set-up was simple; we were shuffled into random teams, given a list of user stories, a deadline of Friday and off we went into the wild.</p><p>We worked in pairs each day. A typical day would be :</p><ul><li>Start with a stand-up (named after the recommended posture so the meeting would last the minimum time necessary) where we shared what we’d done, whether we got stuck with anything and what we intended to do that day.</li><li>Lunch</li><li>Meditation</li><li>Yoga (Tuesdays &amp; Thursdays)</li><li>Retro —a stand-up at the end of the day where we shared what we learnt, where we got to.</li></ul><p>All with a generous spattering of coffee, chats and general checking in with the other pair.</p><p>The end product — <a href="https://medium.com/@nickrupp95/makers-academy-w6-d4-fake-it-til-you-make-it-34acb7845926">checkout the blog</a> by fellow team member <a href="https://medium.com/u/1d5909d62127">Man Vs Code (Nick Rupp)</a>. His writing is as painfully entertaining as his coding is inspired. Particularly when under pressure.</p><p><strong>Lessons learnt:</strong></p><p>Coding really is the easy part. The levelling up, the fun bit, is learning how to be a real developer; working in a team to solve problems, play with new technologies and build something cool.</p><p>Some reflections the group shared at the end of the week :</p><p><strong>1. Break down the feature before diving into the build</strong></p><p>If I’m honest, I froze a little when it got to the last 30 minutes on Friday and there was so much we could still do. By breaking down each feature into the smallest parts, this makes it simpler for someone else to review, then later to track any issues. This means it’s easier for members of the team to pick up a task. It’s also great simply for the psychological satisfaction of achieving something quickly and more often.</p><p><strong>2. Code reviews are a great way to keep up with what’s going on with the project</strong></p><p>As well as being best practice to have a second pair of eyes to review new code. It’s also pretty satisfying to git like a ninja.</p><p><strong>3. Don’t leave styling to the last (30) minute</strong></p><p>Having poured our energy into building something cool, it’s a shame not to do it justice with an equally inspired visual representation. It’s an age old trade off whether you’re a coder or say, a politician — style vs substance. Ideally, you want both or it’ll be tough to win people’s confidence.</p><p>It’s a testament to Makers and our cohort how much we’ve changed in just 5 weeks. I remember on day 1 how unsure we all were, waiting to be told what to do and where to go. Now, when given a challenge, we simply got on with it. If we didn’t know something, we’d look it up. If we found something cool, we’d share it on slack. If we finish the challenge, we’d look for something new to try.</p><p><strong>UPDATED TOOLKIT</strong></p><p><strong>Web Styling</strong></p><ul><li><a href="https://developer.mozilla.org/en-US/docs/Web/CSS">CSS</a> — join the mozilla developer network. Great resources</li><li><a href="http://html.com/">HTML</a> — learn html if you never did it for mySpace…</li><li><a href="https://jquery.com/">JQuery</a> — dry documentation.</li><li><a href="http://getbootstrap.com/">Bootstrap</a> — make HTML pretty (much like most websites).</li></ul><p><strong>Model (Business logic)</strong></p><ul><li><a href="https://www.javascript.com/">JavaScript</a> — try it out in a game</li><li><a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Statements/debugger">Debugger</a> — JavaScripter’s best friend</li><li><a href="https://jasmine.github.io/">Jasmine </a>— JavaScript testing library</li></ul><p><strong>Developer Tools</strong></p><ul><li><a href="https://waffle.io/">Waffle </a>— like trello, for managing development tasks</li><li><a href="https://developer.chrome.com/devtools">Chrome Dev Tools</a> — CMD + alt + i — try it now in your chrome browser. Dive into any website.</li></ul><p><em>P.S. If you recognised the opening quote, you’re showing your age…and acknowledging mine. It’s used completely out of context but I hope you’ll agree it is a testament to the quotability of the show.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9fc38ae3d84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wk8 Makers Academy : nutritious and delicious]]></title>
            <link>https://medium.com/@alicespyglass/wk8-makers-academy-nutritious-and-delicious-28f29f3adb56?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/28f29f3adb56</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Tue, 11 Apr 2017 07:31:01 GMT</pubDate>
            <atom:updated>2017-04-11T07:31:01.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*ERmzuEkzIpDD7bYU5MWA1g.jpeg" /><figcaption>The stack is coming along nicely</figcaption></figure><p><strong>In this post:</strong></p><ol><li>Want to play? Cool stuff my cohort has built</li><li>How we built this — Peek into my technical toolkit with a list of technologies used so far and where to find out more</li><li>Lessons learnt</li><li>Interesting stuff as a newbie — podcast, geek rave, hackathon</li></ol><p>It’s been a heck of a ride.</p><p>If I thought I’d learned a lot after <a href="https://medium.com/@alicespyglass/wk5-makers-academy-ad1bb2ec73d">one week</a> on site at Makers, a quick peek in my technical toolkit shows just how much has been added. The daily (mental) sweating, battering, baking and sometimes flipping has been to layer our experience with technologies to one big messy, delicious, stack.</p><p>The most exciting thing for me is, we’re beginning to build stuff — web apps — that family, friends and the internet can interact with (if they were so inclined).</p><p><strong>1. WANT TO PLAY?</strong></p><p>The weekend challenges are billed as a chance for us to consolidate our knowledge individually after a week of pair programming. Coincidentally, throw in some creativity, a touch of competition and a healthy dose of humour, this cohort has cooked up some impressive projects.</p><p><strong>Rock-Paper-Scissors</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1lSA2g98FN8waHmqh1KMw.png" /><figcaption><a href="https://github.com/j-rods">https://github.com/j-rods</a> — previously a UX designer, this lady is going to be unstoppable</figcaption></figure><p><strong>Play now</strong>: <a href="https://the-rps.herokuapp.com/">https://the-rps.herokuapp.com/</a></p><p>So simple, so addictive, so beautiful. Better than tossing a coin to resolve stalemates (who carries cash around nowadays anyway?).</p><p>May the best hand win.</p><p><strong>Kitter </strong>by <a href="https://medium.com/u/6c5be452d700">Elaine Osbourn</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZh2jFZVMXxdY0wy4dTHCA.png" /><figcaption><a href="http://kitterapp.herokuapp.com/meows">http://kitterapp.herokuapp.com/meows</a></figcaption></figure><p>Inspired by a site which rhymes with kitter and begins with T… a social network for cats!</p><p>Because they don’t own enough of the internet…</p><p><strong>Knitter </strong>by <a href="https://medium.com/u/2e47d5f5d34f">Naz Malik</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*6xu99ww85jDNeCnI_Jd2xg.png" /><figcaption><a href="https://github.com/nazwhale/knitter">https://github.com/nazwhale/knitter</a></figcaption></figure><p>For sharing knitting tips.</p><p>Heroku is a fickle mistress right now but would definitely checkout the github if not his <a href="https://github.com/nazwhale/knitter">post on medium</a> (all them, <a href="https://medium.com/u/2e47d5f5d34f">Naz Malik</a> is a great writer).</p><p><strong>2. TECHNICAL TOOLKIT</strong></p><p>How did we make this happen? Technologies wise, not quite a full stack, but pretty chunky and packed with a lot of potential.</p><p><strong>DEPLOY — making it real</strong></p><ul><li><a href="https://www.heroku.com/what"><strong>Heroku</strong></a><strong>: </strong>cloud platform for hosting, building and managing web apps (translation: so that the world can interact with our creation/code through a url).</li><li><a href="http://www.sinatrarb.com/"><strong>Sinatra</strong></a>: Ruby-based framework and library for building web apps (translation: a template for structuring code / files so that a platform can translate it to a browser).</li><li><a href="http://rack.github.io/"><strong>Rack</strong></a>: a Ruby Webserver Interface (translation: so that developers can quickly see what they’re making on a browser).</li><li><a href="https://www.twilio.com/what-is-cloud-communications"><strong>Twilio</strong></a><strong>: </strong>cloud communications platform for building / adding messaging, voice and video functionality to web and mobile apps.</li></ul><p><strong>TEST</strong></p><ul><li><a href="http://rspec.info/"><strong>Rspec</strong></a><strong>: </strong>domain specific language written in Ruby to test Ruby code.</li><li><a href="https://github.com/teamcapybara/capybara"><strong>Capybara</strong></a><strong>: </strong>automated web-based software for feature testing web apps (translation: test web apps by simulating scenarios for user stories, without a human tester. Based on behaviour-driven software development ).</li><li><a href="http://www.seleniumhq.org/"><strong>Selenium</strong></a><strong>:</strong> software-testing framework for web apps (translation: combined with Capybara, acts as a translator between the software and test language)</li><li><a href="https://coveralls.io/"><strong>Coveralls</strong></a><strong>: </strong>shows how much of the code are covered by tests. Based on test-driven software development.</li></ul><p><strong>VIEW — how it looks</strong></p><ul><li><a href="https://www.w3schools.com/html/"><strong>HTML</strong></a><strong> (Hypertext Markup Language):</strong> for creating web pages and web apps.</li></ul><p><strong>MODEL</strong></p><ul><li><strong>Ruby: </strong>object-orientated language</li><li><a href="https://www.postgresql.org/"><strong>PostgresSQL</strong></a><strong>: </strong>Object-relational database management system (ORDBMS) (translation: database for storing data)</li><li><a href="https://codahale.com/how-to-safely-store-a-password/"><strong>bcrpyt</strong></a><strong>:</strong> password hashing function (translate: a way to encrypt passwords so that it can be safely stored)</li><li><a href="http://datamapper.org/"><strong>Datamapper</strong></a><strong>: </strong>an object relational mapper (translation: a way to link a programme / language with a database so that they can interact)</li></ul><p><strong>3. LESSONS LEARNT</strong></p><blockquote>Make it work THEN make it pretty.</blockquote><p>For me, this lesson / principle is about focus. Being a visual person, whilst it is deeply satisfying to make something pretty, it is more important as a developer to make something work (first). In fact, make it work in the most minimal way possible and then build on it.</p><p>Which is why right now, my app is “retro” styled i.e. no styling whatsoever. The very fibres of my being cringe at the Times New Roman, however, enormously pleased with the skinny controllers and clean code after refactoring. I will share the shiny thing at some point. Watch this space.</p><blockquote>Coding is easy. Setting up the environment is the hard part.</blockquote><p>You’ll notice that the only languages mentioned in the toolkit are Ruby and HTML. The rest are either ruby-based libraries or frameworks, platforms and software, all of which were used in the development of the Kitter / Knitter apps.</p><p>I must admit, the Makers walkthroughs have been instrumental in my embrace of these new technologies (not all software documentation are made equal, or indeed, comprehensible). However, wading through set-up docs do get easier with practice, patience, play time and a generous helping of curiosity / motivation. Saying that, Twilio was pretty easy and pretty cool. Highly recommend trying and playing with it.</p><p><strong>4. INTERESTING STUFF AS A NEWBIE</strong></p><p><strong>PODCAST</strong></p><p><a href="http://www.codenewbie.org/podcast/take-my-money">CodeNewbie — Ep. 131 Take my money</a></p><p>A podcast channel recommended to us by our coach.</p><p>Sparked from using bcypt to deal with passwords in our apps, this episode on managing payments and things to look out for when using payment systems was interesting and accessible. Bonus he was talking from a Ruby developer perspective. Love that I can understand what he means.</p><p><strong>ALGORAVE</strong></p><p>Algorithm and Rave….For the lovers of code and electro music — now there’s a way to enjoy both at the same time!</p><p><a href="https://algorave.com/news/">https://algorave.com/news/</a></p><p>Live coders write computer programs live, while the programs generate their music with cool visuals.</p><p><strong>HACKATHON</strong></p><p>Prompted by a fellow Makers (thanks <a href="https://medium.com/u/fdfad76fb841">Stephanie Crampin</a>), I’ve just signed up for angelhack London in June!</p><p><a href="http://angelhack.com/">http://angelhack.com/</a></p><p>As I’ll be graduating at the beginning of June, here’s to putting my <em>skillz</em> to use right away.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28f29f3adb56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why attr_reader & attr_writer are windows into object-orientated programming and how they work]]></title>
            <link>https://medium.com/@alicespyglass/why-attr-reader-attr-writer-are-windows-into-object-orientated-programming-and-how-they-work-9bb67014af82?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bb67014af82</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[object-oriented]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 07:17:01 GMT</pubDate>
            <atom:updated>2017-04-06T07:17:01.276Z</atom:updated>
            <content:encoded><![CDATA[<p>Quick blog to illustrate the attr_reader / attr_writer and public / private methods for the Ruby beginner.</p><p>This topic had been a bit of a blocker for me up to week 3, however, after some digging and playing in my<a href="https://repl.it/"> repl</a> sandbox, they finally make sense and now all help me get Ruby to do my bidding.</p><p><strong>Why are these methods useful in the context of Object-Orientated Programming?</strong></p><p>Think of a class or object as a robotic warehouse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*SVGoZEkvi5wz3__0MCcQdw.jpeg" /></figure><p>You want that warehouse to perform certain functions (called methods).</p><p>Much of these involve storing, manipulating or passing pieces of data / parcels (assigned to variables).</p><p>While you will want to share / update some bits of data, what you don’t want is to have that data manipulated / shared / mixed-up / over-written by accident. This is the stuff that bugs and <a href="https://en.wikipedia.org/wiki/Code_smell">code smells</a> are made of.</p><h3><strong>So what do they do?</strong></h3><p><strong>attr_reader</strong> (or attribute reader) can be thought of as a window into the warehouse — it lets you peer in and see a particular bit of data, but you can’t interact with it.</p><p><strong>attr_writer</strong> (i.e. attribute writer) is like a door — it lets you set or overwrite a piece of data (but doesn’t mean you can see it unless combined with attr_reader. So you walk in blindfolded otherwise).</p><p><strong>Public </strong>methods</p><p>All the data in the robot is essentially accessible (or public) — we just need to have the right windows (attr_reader), doors (attr_writer) or methods if somebody wanted to see / interact with them from outside the warehouse (class).</p><p><strong>Private</strong> methods</p><p>Sometimes, there are things which should only be seen / done from inside the warehouse, not necessarily from a security perspective, but more to stop those bugs / accidents from happening.</p><h3><strong>When are these useful?</strong></h3><p>Below summary and some simple examples of what the code and respective output look like using these methods:</p><ol><li><strong>attr_reader</strong> — when data (e.g. an instance variable) needs to be read (called) from outside of the class.</li><li><strong>attr_writer</strong> — when you want to be able to set / over-write data from outside of the class.</li><li><strong>Private</strong> — for information only the warehouse (class) needs to know / action it needs to do. Functions can be nuanced by combining use of attr-reader/writers.</li></ol><h3><strong>1. attr_reader</strong></h3><p>You have an instance variable in this class and would like to see it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CNN68cWIxkb4wl8AYFgOpA.png" /></figure><p>With an attr_reader, now you can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bGJKdKGWdL3MA-Jr3Je8Q.png" /></figure><p>It has essentially made a method of the variable, like so:</p><pre>def peek<br> @peek = “aboo”<br>end</pre><p>Which is handy, because imagine you have a bunch of information in a class. Now instead of writing 3 lines of code for each, you can simply add it to attr_reader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*r8wXckYM6eDB4RHSxDcRxg.png" /></figure><h3>vs.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*DHefdvUNMv1Hx7Ly45hWqg.png" /></figure><h3>2. attr_writer</h3><p>You have set a value for a variable, but would like to change it (I’m including attr_reader here so it should be able to be read).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqmRY8IfbYuixawAGvOOgA.png" /></figure><p>By using attr_writer, now you can over-write the value of the variable @pulitzer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_2IFEhFLPfgsEmis4kOoA.png" /></figure><h3>3 . private methods</h3><p>Anyone can access the account’s dollar data by calling on the balance method:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PfwzRfCa3ciChYcRZzsXg.png" /></figure><p>You can seal off the data by putting it under <strong>private:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JpPJZprLk9kp5iGHFvD6_A.png" /></figure><p>To make sure data isn’t overwritten by accident like so…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okL8t9URM8S63TgCR2w5DQ.png" /></figure><p>Put the method under private:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*weQuGD6gvhWdTp2COEhiyA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bb67014af82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“A man of genius makes no mistakes. His errors are volitional and are the portals to discovery.”]]></title>
            <link>https://medium.com/@alicespyglass/a-man-of-genius-makes-no-mistakes-his-errors-are-volitional-and-are-the-portals-to-discovery-90a62ec2cffe?source=rss-d748beb3d4c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/90a62ec2cffe</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[tdd]]></category>
            <dc:creator><![CDATA[Alice Cheung]]></dc:creator>
            <pubDate>Tue, 28 Mar 2017 07:17:00 GMT</pubDate>
            <atom:updated>2017-03-28T07:17:00.453Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“A man of genius makes no <strong>mistakes</strong>. His errors are volitional and are the <strong>portals</strong> to <strong>discovery</strong>.”</blockquote><blockquote>~Ulysses, James Joyce</blockquote><p>Week 2 of makers proper (wk6) was tough. However, at the end of it came another revelation.</p><p>The beginning started out well; I was riding on the excitement of week 5, I’d picked up some awesome shortcuts (and was hardly using the mousepad), I was really enjoying getting to know my cohort in pair programming, even coding for the week’s challenge (an <a href="https://github.com/Alicespyglass/oystercard">Oystercard</a>) seemed deceptively easy until….exercise 18, Thursday.</p><p>Turns out, the exercises up to that point had been designed to lead us astray and programme a beast of a card object so that it could teach us a lesson. About extracting classes for <a href="https://en.wikipedia.org/wiki/Dependency_injection">dependency injection</a>. All in the name of writing good code based on <a href="https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)">SOLID principles</a>.</p><p>In short, the Oystercard was doing too many things (tapping in/out, charging fares, logging journeys). So we had to pull out (<strong>extract</strong>) different responsibilities and create Journey_log and Journey classes (and <strong>inject</strong> functionality back in).</p><p>This all sounds very sensible, reasonable even, and in all likelihood as a developer, a very real part of the job. Which is why it was distressing when my pair and I were essentially stuck for 36hrs (including sleep, and a different pair partner). If we weren’t caught in a loop for the logic of one part of the problem, it was in failing the Rspec test for another. To top it off, the free ride that were the code walkthroughs were no longer an option. There were just these sample Rspec tests which only raised more questions than they answered.</p><p>In a way, it was comforting to know that the whole cohort also got stuck at the same part. I kept hearing the word “journey”. Sometimes I wasn’t sure if it was someone saying it, if it was my own voice or even if it was out loud. The word had lost all meaning by 1pm.</p><p>Eventually, eureka moments were had, high-fives were made and we all got on with our lives.</p><p>On reflection, I am grateful I had mentally prepared myself to find parts difficult, to struggle with some concepts and made an allowance to go at a slower pace — just generally to be kinder to myself and enjoy the process. If not, this week may well have seen me experiencing the “<a href="http://startupbros.com/21-ways-overcome-impostor-syndrome/">imposter syndrome</a>” I had been warned of.</p><p>However, the real revelation wasn’t until the Friday retrospective where we shared our challenges, victories and suggestions as a group. Someone put the misleading part of the challenge under challenges. Our coach responded that this had been done on purpose — it was a “d*** move” but it was intentional. This was a similar response from a different coach on the Student’s Directory challenge (for week 3 of the pre-course). It was meant to be hard. The point had been for us to feel the struggle.</p><p>That was when it really clicked for me and I saw coding in a new light.</p><blockquote>In order to succeed as a developer, you have to be prepared to fail.</blockquote><p>Fail up front. Fail a lot. Fail all the time. Look for ways to fail. Because that’s how you learn. That’s how great software is made. And then that’s how everything is made even better.</p><p><strong>KEY TAKEAWAYS</strong></p><p><strong>The whole point of testing is to fail</strong></p><p>Test Driven Development (TDD) — you start by writing tests which you expect to fail (never have I dreamed I would get frustrated at seeing tests pass).</p><p><strong>The only way to learn is to fail</strong></p><p>There are three certainties in life — death, taxes and bugs — somewhere, somewhen down the line, something will break. Get good at stack tracing and bug hunting.</p><p>So while the sentiment of this lesson / blog is more<em> portals to discovery</em> than the genius Joyce refers, I feel this sums up the whole thing nicely:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FnyPZB25Mg1pe%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fjourney-nyPZB25Mg1pe&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FnyPZB25Mg1pe%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/4149bce685bfc07c4ebd2abb89b670ca/href">https://medium.com/media/4149bce685bfc07c4ebd2abb89b670ca/href</a></iframe><p>❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a62ec2cffe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>