<?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 Luke Aveil on Medium]]></title>
        <description><![CDATA[Stories by Luke Aveil on Medium]]></description>
        <link>https://medium.com/@lukeaveil?source=rss-302305d6e7b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZjfpUbsxsL6iF0lU.</url>
            <title>Stories by Luke Aveil on Medium</title>
            <link>https://medium.com/@lukeaveil?source=rss-302305d6e7b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:57:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lukeaveil/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[From Zero to Convergian]]></title>
            <link>https://medium.com/converge-io/from-zero-to-convergian-71ba0d05f237?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/71ba0d05f237</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 16:16:06 GMT</pubDate>
            <atom:updated>2018-01-29T16:16:06.466Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The 9th January 2018 marked my first year anniversary working at </em><a href="https://converge.io/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=lukes%20post"><em>Converge</em></a><em>, and this also marked one year of professional experience as a software engineer. You might be thinking that this is my first job after graduating from university, alas I am nearly 33 and graduated 8 years ago (with a degree in photography). My journey from fresh-faced arts grad to full-stack Javascript engineer wasn’t simple. It involved many hard decisions, countless hours of work, and spanned three different continents…but I’ll cover all of that below.</em></p><p><strong>In the beginning…</strong></p><p>Whilst at university I had my first encounter with coding: to make an interactive photograph using Adobe Flash. This brief flutter with ActionScript certainly switched on some light bulbs in my head, but they were switched off pretty rapidly after coming to the conclusions that: a) I surely wasn’t smart enough to study computer science at university (because that’s what you need to do to become a software engineer right?) and b) there was no way I could afford (mentally and financially) to drop out halfway through my current degree and start a new one.</p><p>Finishing university in the middle of the recession was terrible for any graduate, let alone one with an arts degree. What followed was a year of trying to get my foot in the door (aka work for free for an unspecified amount of time) at any company willing to take me on, which was none.</p><p>One day during the summer of 2011 I got an email from the founder of Documentary Arts Asia, a Thailand based NGO that tackles social and environmental issues in Southeast Asia through the mediums of photography and film. They offered me an internship and my main task would be to help them setup and run their first gallery/events space in Chiang Mai.</p><p>It was a massive jump into the unknown, but with the monotony of daily life in the UK and no sign of things improving I seized the opportunity to live and work in a far away land. I only had a few months to prepare myself (and my family) for this sudden decision, and on 12th January 2012 I said goodbye to my friends and family and boarded a one-way flight to Bangkok.</p><p>I could write a book on what happened in the following years, but we shall fast forward to 2014, by which point I was living in Melbourne with my girlfriend and starting the process to apply for Australian permanent residency.</p><p><strong>This is where it began…</strong></p><p>Initially I started to learn to code out of curiosity to learn something new and the desire to teach myself a new skill set. Even after my initial foray into the world of software engineering I was blown away by the overwhelming number of resources out there and it wasn’t long before I had signed up to Codecademy.</p><p>Progress was slow but I was working my way through the Codecademy courses on HTML, CSS and Javascript. Before long, I started thinking that if I put in some serious hours I might be able to actually start building a website for myself or a friend that might need one, I was however lacking some direction and focus. Looking back I am glad I spotted this early on as the vastness of the software development ecosystem is a scary realm for any engineer, let alone a novice, and it is very easy to lose your way whilst trying to traverse it.</p><p>Someone suggested I try Treehouse (a fantastic online coding resource for self-learners) to have a structured curriculum to follow, and as such I started a free trial and within two weeks I was hooked and started paying for a full membership. I worked my way through the front-end focused curriculum, which was a real step-up from the Codecademy tutorials I had dabbled with previously. I certainly felt as though I was getting somewhere, although at that stage I wasn’t sure where that “somewhere” actually was.</p><p>A lot of people think that if you work through online resources such as Codecademy and Treehouse then you can code by the end of it (I was one of those in the beginning), but after spending a lot of time on both platforms it became clear that this was obviously a naive assumption. Tutorials are a great tool for becoming familiar with a new language or concept (I used Codecademy earlier this week to brush up on my SQL basics), but they can only take one so far and the best way to really learn is to work on a real life project. So, I set myself the challenge of building a photography portfolio site, and it was during this period that I started toying with the idea of coding for a living. A lot of research into how to become a professional software engineer without a relevant degree followed, and something that kept popping up were articles about coding bootcamps.</p><p><strong>Learn to code in 12 weeks…</strong></p><p>Time was a problem for me whilst self learning. Working full time then coming home to try and squeeze in a few hours of coding was tough to say the least. I knew I had to do be doing this full time, but a degree wasn’t an option and part time courses took longer than a degree. The only other option on the table was a coding bootcamp. The premise of a coding bootcamp: an intensive full time course (usually 3 months or more) by the end of which the student is armed with the skill set to work professionally as a junior software engineer.</p><p>I did a lot of research and found numerous positives and negatives to enrolling on such a course. My main concerns about taking the plunge were: a) they are expensive (but still less than a degree) b) was I smart enough? It would be an expensive way to find out I wasn’t, and c) you can’t actually learn to code in 12 weeks, would I be able to get a job at the end of it?</p><p>I remember the day well: we were at the 1st birthday party of our friend’s son and I got chatting to someone about how I was teaching myself to code. I also mentioned I was debating with the idea of enrolling at General Assembly (Melbourne’s only bootcamp at the time), in response he said “I have just hired some graduates from that course”. Little did I know it at the time, but attending Noah’s 1st birthday party changed the course of my life.</p><p>I was now sold on applying for a spot on the General Assembly course, but before that could happen my partner and I needed to get our permanent residency sorted and I needed to figure out how I was going to pay the fees and not be employed for several months.</p><p><strong>Life got turned upside down…</strong></p><p>I can’t remember the exact date but sometime in September 2015 we were on holiday in Vietnam when we got the devastating news that Australian immigration had changed the rules surrounding permanent residency applications and that we no longer qualified.</p><p>This was obviously a shock and completely unplanned, coding was pushed down the list of priorities whilst we organised our lives and shipped them back home (via a three month adventure in Asia). This also meant that I wasn’t able to apply for General Assembly in Melbourne, but all was not lost as there was a campus back home in London, along with various other bootcamps.</p><p><strong>Best of the bunch…</strong></p><p>By the time I touched down at Heathrow I had two interviews lined up: one at General Assembly and one at Makers Academy. The latter is regarded as the best coding bootcamp in Europe and is renowned for its tough application process, as such they only accept around 10% of applicants. Based on all that I knew of Makers it was my preferred choice, but I didn’t get my hopes up as I had a lot of prep to do before the interview. The prep wouldn’t have normally been a problem, but I was halfway into an adventure through Asia (sans laptop and reliable internet), and by the time we got home I had less than two weeks to get up to speed.</p><p>During my second interview at Makers they stepped the technical test up a gear (Ruby katas in Code Wars) and drilled further into my approach to solving problems. I was shown around the office and it was clear it was a special place and head and shoulders above the rest. The buzz in the main space was amazing, students were taking time out by playing table tennis, there were sleep meditation and yoga classes taking place, and most importantly everyone was clearly enjoying themselves whilst working their socks off. Later that day I got the call saying I had a spot on the May 2016 cohort, I couldn’t quite believe it. Maybe leaving Australia wasn’t going to be so bad after all?</p><p><strong>Back to school…</strong></p><p>Rather than give an account of my time at Makers you can checkout a series of posts I wrote whilst I was <a href="https://medium.com/@lukeaveil">there</a>, but unfortunately I found myself short on time and brainpower near the end of the course so the final weeks are not covered.</p><p>The amount of information that we had to absorb was something I was not really prepared for, and I never knew it was possible to be so exhausted through exercising your brain. There are two things in particular that I would class as the most valuable skills I learnt during those 16 weeks, and that I am still improving upon to this day: a) learning how to learn, and b) being comfortable with feeling out of my depth all the time.</p><p>Being in an environment that allows me to be learning something new everyday is what made me want to become a software engineer. In such a profession it is important to be able to pick things up fast and efficiently, which can be made difficult by things such as poor documentation (sometimes no documentation even exists) or the complexity of the concepts or technology that need to be understood. Over the duration of the course I learnt how to approach something completely alien and extract what was needed to build an overall understanding of how it worked, such as understanding the ins and outs of a poorly documented Node module by looking at it’s source code.</p><p>Something that I (and most other new engineers) experience almost every day is a feeling of being out of one’s depth. This was particularly the case whilst at Makers but is still true to an extent today. As human beings most of us don’t like being wrong about something, we get frustrated when we try to understand something really complex but we just can’t “get it” and failing at a task makes us start to question our own abilities. A combination of some or all of those situations happened everyday at Makers and sums up what I mean by “feeling out of my depth”.</p><p>Throughout the duration of Makers I got used to this feeling and it has set me up in good stead for being a professional engineer. This is not to say the previous situations don’t happen virtually on a daily basis, but I am now well versed in dealing with them and actually enjoy being wrong about something as it is an indication I haven’t fully understood the problem and I need to dive in deeper.</p><p>My time at Makers flew by and before I knew it I was giving a presentation to over 100 people about our final <a href="https://www.youtube.com/watch?v=OYk-d6q4iWI">project</a>. If I was to sum up those 16 weeks in one sentence: a life changing experience that challenged me every minute of every day.</p><p><strong>The job hunt…</strong></p><p>Simply put: finding a job after Makers was tough, really tough. Despite the rejections, false leads, time wasters, numerous tech tests, even more interviews and altogether bizarre behaviour from several potential employers I battled on for 3 months before things started getting serious with my application for an IoT startup called <a href="https://converge.io/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=lukes%20post">Converge</a>.</p><p>The biggest single problem with graduating from a coding bootcamp (even from one that is regarded as Europe’s best) is that most employers don’t take you seriously and think you can’t possibly have gained the skills to work as a junior engineer. Part of this first hurdle is taken care of by the careers team at Makers as they have a network of employers that see the benefits of hiring one of their graduates.</p><p>I came across <a href="https://converge.io/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=lukes%20post">Converge</a> at the second careers fair put on after my graduation, and they were my pick of the bunch of the companies I wanted to work for. I was eager to apply because the nature of the business sounded fascinating and full-stack JavaScript was the technology I wanted to be working with. I must admit I wasn’t feeling overly confident due to my experiences over the past few months of job hunting and my knowledge of React was non-existent, which is not great when you get sent a React based tech test to complete.</p><p>With hiring any engineer it is important that you are satisfied the candidate meets all the required technical criteria and fits in well with the team. This is amplified when you are a small team (I think I was employee number 10 overall and the 4th to join engineering) and even more so when you are hiring a junior engineer with no professional experience. The process for me was rigorous (a tech test and three interviews from what I can remember) but very interesting and at every stage made me want the job even more. I wasn’t however putting all my eggs in one basket and during this time I was also at various stages of the application process with a couple of other companies.</p><p>By mid December 2016 I had made it to the end of the last stage of the process with Converge and had to play the waiting game to find out if I had made the cut. To say the wait was excruciating would be an understatement, but I got the best Christmas present I could have hoped for just before new year: an email from Gideon saying they would love to have me join the team.</p><p>I couldn’t quite believe it, and sometimes to this day I still have to pinch myself.</p><p><strong>Today…</strong></p><p>It feels as though I have been in the industry for a lot longer than 12 months, but it wasn’t all that long ago that I was signing up to Codecademy to try my hand at HTML and CSS.</p><p>Working as a software engineer is everything I had hoped for, and thanks to the team at <a href="https://converge.io/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=lukes%20post">Converge</a>, a lot more. I work alongside a group of very smart people from various backgrounds and all corners of the globe, which along with the awesome things we build is one of our greatest assets. As a junior engineer being in such an environment is hugely invaluable to my personal development and improving my knowledge and skill set, I know quite a few juniors that haven’t been so lucky in their first roles.</p><p>I was pleasantly surprised that from day two I was thrown in at the deep end and started working on a feature that would be rolled out to production when it was complete. I think within my first month I had built two features that were in production: building something and then it being rolled out into the wild for the first time was and still is my proudest moment in my journey as a software engineer.</p><p>Over the course of the year I have worked on several projects of varying importance, complexity and size, and in each one I have been able to build upon knowledge I gained in the previous project. This structure of building upon the previous project’s learnings has almost felt like an extension of my time at Makers Academy (with the added bonus of being paid), and much like Makers I have at times had a few bouts of imposter syndrome.</p><p>Imposter syndrome isn’t an unusual feeling for a software engineer (those with more experience just become better at dealing with it), but it is certainly more prominent in juniors, and particularly those that have come out of a coding bootcamp. On a daily basis I am surrounded by very smart people with academic backgrounds in mathematics, physics and engineering, all of which sets one up fairly well for a career in tech. This was not an environment I was used too, and in a weird way my arts background and not so typical path to becoming an engineer (at 32 years old) made me feel very much like an imposter that had sneaked into this realm.</p><p>Thankfully, however, I have mostly overcome the imposter syndrome and when it does rear its head I deal with it in a much more structured manner, but as a result of my early bouts I came across a fantastic book called “The Imposters Handbook”. The book is written by an engineer with decades of experience, but much like myself became an engineer without an academic background. This has proved to be a fantastic resource in helping me understand various computer science concepts that I never got the chance to learn about at school or university, and has gone a long way in helping me to better understand documentation and literature that I come across whilst at work.</p><p><strong>Onwards…</strong></p><p><a href="https://converge.io/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=lukes%20post">Converge</a> is growing fast: we were a team of 10 in a small co-working space when I joined, and now a team of 20 in our own office. The engineering team is set to grow further which will give us the resources to work on new exciting projects and features, my second year as a software engineer is shaping up to be even better than the first.</p><p>I hope sharing my experience will show those of you that are interested in breaking into the tech industry (or looking to take any other jump into the unknown) that it is possible to achieve anything you put your mind too. The next jump into the unknown for me arrives in April 2018 in the form of my first child, anyone know of any good dad bootcamps?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71ba0d05f237" width="1" height="1" alt=""><hr><p><a href="https://medium.com/converge-io/from-zero-to-convergian-71ba0d05f237">From Zero to Convergian</a> was originally published in <a href="https://medium.com/converge-io">Converge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A lot has happened since my last post….]]></title>
            <link>https://medium.com/@lukeaveil/a-lot-has-happened-since-my-last-post-a63f2f04c35c?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a63f2f04c35c</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[crowdsourcing]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Tue, 13 Sep 2016 18:36:21 GMT</pubDate>
            <atom:updated>2016-09-13T18:36:21.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-UTXnBqX35sO3ILTSzhlmQ.png" /></figure><p>….including graduating from Makers Academy!!! But I shall come back to that in another post, first up I need to fill in the blanks.</p><p><strong>Week 9: </strong>This was makerthon week, we pitched ideas of things we wanted to build and everyone could choose which project they wanted to work on. I decided to be part of the team that was to build Crowd Code, a platform for project managers to crowd source developers to work on projects.</p><p>From the get go we were very organised, spending a good 5 hours as a group discussing and diagramming how we were going to build the project. We decided that we wanted to build our app in Rails: this would allow us to practice skills we had picked up the previous week, and given the short time frame we had it would allow us to get setup quickly….and Rails is awesome.</p><p>The preceding three days were run in a very organised fashion and with military precision. We had standups every morning and halfway through the day, along with code reviews where we all became familiar with the code the other pairs (there were six of us) had written.</p><p>We had our MVP completed with a day to spare so were in a great position to add extra features and get the front-end looking amazing.</p><p>We presented our project on the friday morning to the rest of our cohort, coaches and the cohort below. There were a good 60 people in the room so a fairly nerve-racking experience for all of us, but very good practice for final projects where we would be presenting to at least double that!</p><p>I was really pleased with what we achieved in a relatively short space of time and was proud of how we all worked together so well and without any major hurdles. The key to our success was extensive planning before any code was written and constant communication between all members of the group. The repo for our project can be found <a href="https://github.com/LukeAveil/crowdcode">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a63f2f04c35c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 8……Ruby on Rails]]></title>
            <link>https://medium.com/@lukeaveil/week-8-ruby-on-rails-bbc5a57baea5?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbc5a57baea5</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[mvc-frameworks]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[junior-developer]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Tue, 09 Aug 2016 17:36:03 GMT</pubDate>
            <atom:updated>2016-08-09T17:36:03.385Z</atom:updated>
            <content:encoded><![CDATA[<p>Ah rails, you couldn’t have come at a better time! Week 7 was tough, really tough, I was feeling incredibly deflated and even more out of my depth than normal. In true Makers fashion I had been pushed pretty much to my limit before having some sort of breakdown, and then they reeled me back in with niceness that is Ruby on Rails.</p><p>So what is this? Ruby in train form? Well kind of. Rails is a popular Model View Controller (MVC) web application framework, as opposed to Sinatra which is just a web application framework. This means that Rails provides a lot of guidance over high level architecture, which means setting up MVC’s is a lot more straightforward and ultimately saves a lot of time.</p><p>The project this week was to build a clone of Yelp, a popular restaurant review web app.</p><p>I really enjoyed the project this week, and came across cool things such as Devise and OmniAuth to allow a user to sign up/in with Facebook. I also learnt that Rails doesn’t really like to be forced to come off the Rails, it favours convention over configuration.</p><p>It is also worth noting that Rails can be quite overwhelming at first, there is a lot going on and it is easy to get lost trying to find a file in the sidebar of the text editor.</p><p>All in all I felt positive by the end of the week and was looking forward to giving the weekend challenge my best shot, to build a clone of Instagram. Next week is makerthon week: in groups we have a week to build a project of our choice…I imagine everyone will be working with Rails!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbc5a57baea5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 7……further JavaScript]]></title>
            <link>https://medium.com/@lukeaveil/week-7-further-javascript-a648a62e62e6?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a648a62e62e6</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Sun, 24 Jul 2016 20:05:11 GMT</pubDate>
            <atom:updated>2016-07-24T20:05:11.589Z</atom:updated>
            <content:encoded><![CDATA[<p>Our cohort was the subject of a two part experiment this week. First up the course usually covers Ruby on Rails at this point, but instead our coaches decided to mix it up and cover further JavaScript this week and Rails during week 8. For the second experiment was were given a totally different curriculum to what has been taught in the past, the cohorts prior to us all learnt Angular (a JavaScript framework) but we were now instructed to essentially build a one page app without any framework and then extract a framework of our own from the code we had written.</p><p>Safe to say this was the hardest and most frustrating week I have had so far!</p><p>I am not going to talk about the technical side of the week too much, this is because I learnt a lot about was how I tackle being way out of my depth and in the unknown.</p><p>The new technologies I was introduced to: node.js (JavaScript is no longer just run in the browser, with node we can run JS on the backend), mocha (a testing framework that runs on node), chai (a TDD assertion library that is paired with mocha) and zombie (for testing client-side JavaScript code in a simulated environment). An initial time consuming struggle was getting everything setup and working as it should, this turned out to be a lot more complicated than anything I had experienced with Ruby or setting up an app with Sinatra.</p><p>There were no walkthroughs and minimal hand holding this week, this meant we had to go out and find things out for ourselves and read documentation (a lot of language related documentation is pretty poor!) and trawl through various resources. Obviously this is how things go in the real world when we are working in our new careers, but this resulted in two major problems during the week: what we were being asked to do was fairly advanced for someone who only had a few days JavaScript experience under their belt, and secondly I spent far too much time trying to understand something that I didn’t need to!</p><p>In retrospect the latter problem was kind of silly, and I have definitely learnt from my mistake…don’t dwell on something for 6 hours when you are getting nowhere! The major issue I had for the week though was the fact that my base knowledge of JavaScript was not at the standard it needed to be to understand node and how to use purely JS to build a web app. Although come Friday I had a completed project that met the brief (created a to-do list, minus extracting a framework), I couldn’t help but feel somewhat deflated and frustrated.</p><p>After some much needed beer and a good sleep I started my weekend feeling more positive about the struggles I had during the week. The major takeaway I got from the week was that my area of focus for the rest of the course and the coming months would be to really get to grips with JS in all its weird and wonderful forms. It was also worth remembering what we actually achieved during the week, that was to understand what goes on beneath the hood of a framework such as Angular. Whilst it was incredibly tough going at times, when it comes to learning JS frameworks I will be in a position not take their workings for granted and have some understanding on how they work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a648a62e62e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 6….Lab Week]]></title>
            <link>https://medium.com/@lukeaveil/week-6-lab-week-ff8f5331fe7e?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff8f5331fe7e</guid>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[junior-developer]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Sat, 16 Jul 2016 16:57:29 GMT</pubDate>
            <atom:updated>2016-07-16T16:57:29.144Z</atom:updated>
            <content:encoded><![CDATA[<p>This week was exciting for two reasons: it marked the halfway point of my 12 week adventure, and is was also the first week we got to work on a project in teams.</p><p>The premise of the week was simple: build a clone of Airbnb in groups of 4, in my case a group of 6. The idea was to practice our new found developer skills and use the technologies we had covered thus far, however if we were brave enough we could try learning and using new technologies.</p><p>As a group we quickly decided that we were going to stick with what we knew and polish the skills we had been working on already, some crazy cats did decide to man up and try their hands at node.js, with vary degrees of success come the end of the week!</p><p>Our team members were chosen at random, I ended up with three of the most ‘advanced’ members of the cohort! I was initially nervous about this due previous unenjoyable pairing experiences I had with some members of the ‘advanced’ bunch. The main issue as a complete noob is that more often than not when I was paired with someone well ahead of me, I found that I didn’t really learn a great deal as my pair partner steamed ahead or sometimes grew frustrated when I held them back.</p><p>I was pleasantly surprised during the first three days that my peers kept things at a pace where I could understand about 80% of what was going on! Come the latter half of the week I started losing steam and my peers pulled away from me a bit and I struggled to keep up. This wasn’t all bad though as I ended up working on some frontend stuff (under the guidance of our design maestro Kenneth), and managed to implement a few cool visual tweaks to our error messages.</p><p>My proudest moment of the week was figuring out how to upload images, store them and resize them. This was a massive milestone for me, in that I managed to figure out a large part of a feature that I had previously never come across during my coding career.</p><p>By the end of the week our Makersbnb was looking amazing!! It was a tough week and was by no means straightforward, but ultimately I proved to myself I was capable of work on a project in a team of individuals that I would have previously felt unfortable being partnered with.</p><p>I shall post a link to the site once I have got round to putting it up on Heroku, in the meantime here is a link to the code…<a href="https://github.com/LukeAveil/makers-bnb">https://github.com/LukeAveil/makers-bnb</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff8f5331fe7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 5, JavaScript….]]></title>
            <link>https://medium.com/@lukeaveil/week-5-javascript-cd4433620342?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd4433620342</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[ajax]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Sat, 09 Jul 2016 17:32:27 GMT</pubDate>
            <atom:updated>2016-07-09T17:32:27.356Z</atom:updated>
            <content:encoded><![CDATA[<p>After a week of constantly feeling as though I never quite fully understood what was going on, I was looking forward to this week. Although much like last week, week 5 holds a kind of mythical status at Makers: the week when you ‘learn’ JavaScript in a couple of days!</p><p>The main aim of the week was to essentially get to grips with JavaScript and a few other related front-end technologies. Our challenge was to create a thermostat app that allows us to set the temperature in our home by clicking on buttons to increase and decrease the “temperature”.</p><p>When I first started on my journey to become a developer I tried the Codecademy course for JavaScript and really struggled to get to grips with things in the latter part of the course. I was intrigued to see how I would fair now, having spent the past couple of months with Ruby and learning various development concepts and processes.</p><p>The biggest challenge was making the switch from Ruby to JavaScript syntax and getting to grips with a new testing suite, Ruby is a very elegant and forgiving language, JS is quite the opposite. By this point I have switched from Sublime Text to Atom (Atom is awesome!!!) and installed a package that flags any syntax errors in the JS you type, this proved essential in helping me get to grips with those pesky semi-colons.</p><p>Another big learning curve was when it came to testing, I have got so used to Rspec that the switch to Jasmine was pretty tough going. I really struggled figuring out what the errors actually meant, as Jasmine doesn’t give you much to work with. It seemed as though this battle was made even harder purely due to the fact that I don’t know enough about JS to be able to make the tests past. One incredibly helpful toolkit to figure out what is going on is the developer console in Chrome, learning to use this proved more helpful than most of the error messages I was getting from Jasmine.</p><p>The later part of the challenge involved using jQuery to help make our app interactive and enabled logic to happen in the back-end when a button was clicked or checkbox ticked. I have touched on jQuery before, but this time round it was great to see how it fits into the puzzle with the HTML, CSS and Vanilla JS(pure javascript).</p><p>We also had our first introduction to Ajax and API’s, which is a way to bring in data to our web app or change something on the page without having to load a new page. This was really cool to have a play with, but I felt that they are definitely technologies that will be taking up a lot more of my time in order for me to get to grips with.</p><p>By the end of the week I had something that resembled a thermostat web app, albeit an unstyled one. JS was fun and I enjoyed diving into the front-end side of things, but do I feel like I learnt JS in a week….obviously not! But I do feel more comfortable with it than I did on Monday morning. I know that it will take me some time yet to feel truly at one with the language in it purest form, but I am keen to dive into a few JS frameworks such as Angular and React to see what I can come up with.</p><p>Next week is project week, so I do not think it will be to JS heavy and we will predominately be sticking with Ruby, but who knows what Sam and Mary will throw at us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd4433620342" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4, Databases….]]></title>
            <link>https://medium.com/@lukeaveil/week-4-databases-8d78d42d2d4f?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d78d42d2d4f</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Wed, 06 Jul 2016 20:10:35 GMT</pubDate>
            <atom:updated>2016-07-06T20:10:35.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*0gzizGhTEY6yisA-sIzQRg.png" /></figure><p>In our first week someone asked our coaches “which week is the hardest”, Sam’s response (with a smirk on his face) “week four”. I am writing this at the end of five, and I can safely say that Sam wasn’t wrong….</p><p>Everyone knew on monday morning we were going to jump head first into a subject that was pretty much a first for everyone: how to create a database and store and retrieve information from it. Sounds relatively straightforward on paper, but I was under no illusions that the coming week was probably going to be my most challenging yet.</p><p>As with every week so far, our learning is centred around a core project that is broken down into smaller ‘sprints’. Our challenge this week was to build and create a bookmark manager for saving weblinks. Features we needed to implement were: create a new user account, sign in and out of said account, store the url of web pages, view the links in chronological order, and tags to the links and then be able to filter the links by their tags.</p><p>The previous week had introduced to us how the web works by building a pokemon style battle game, but it was lacking a means of being able to store anything more than tiny snippets of data. Databases are how information that is inputted into a website is stored, for example this blog post is stored on a database and every time someone visits this page the data (the post) is retrieved and displayed on the page. Another example is when we sign up to something (say facebook), and our signup details (email, password, name etc) are written and stored on a database.</p><p>You have a few options when it comes to creating databases, but we used PostgreSQL, rather than taking up a whole blog post explaining what this is, here is what wikipedia has to <a href="https://en.wikipedia.org/wiki/PostgreSQL">say</a>.</p><p>The initial setup and creation of database was fairly straight forward, and getting to grips with how postgres works was really interesting. It wasn’t long before the “brain melting” side of things started, and for me this point was when we were introduced to Data Mapper. Data Mapper allows you to manipulate a database and interact with it by using Ruby, which is super cool, but super hard for me to get my head around!</p><p>Another really interesting topic that came up this week was how sensitive information is stored on a database (such as passwords), and what measures have to be taken to ensure such information is handled correctly. Cyber security is a massive topic, but we touched on the bare bones on how to encrypt a password using <a href="https://github.com/codahale/bcrypt-ruby">Bcrypt</a>.</p><p>Another interesting technology we were introduced to was Datamapper. Using Datamapper allowed us to communicate with our databases using Ruby, which is a very neat but also quite confusing to set up and get to grips with.</p><p>By the end of the week my brain was frazzled by the amount of new material we had covered, and although it was really tough being constantly out of my depth, I felt fairly positive going forward into week 5.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d78d42d2d4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Makers Academy Week 2 and 3….]]></title>
            <link>https://medium.com/@lukeaveil/makers-academy-week-2-and-3-448b3c3707a6?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/448b3c3707a6</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Thu, 16 Jun 2016 20:31:38 GMT</pubDate>
            <atom:updated>2016-06-16T20:31:38.695Z</atom:updated>
            <content:encoded><![CDATA[<p>This post is well overdue!</p><p>I am writing this whilst coming to the end of week four, so I think it is best to give a recap on what went down during the past couple of weeks at Makers Academy….</p><p>After week one I was feeling fairly happy with the progress I had made and didn’t feel too out of my depth, which was fairly short lived once week two got underway. That’s not to say I wasn’t happy with my progress during the week, but I certainly started feeling I was wading out to sea and having trouble staying afloat at points.</p><p>Week two built upon concepts we learnt in the first week, but this time round we focused more on the concepts behind object orientated programming and how to design a program more effectively and efficiently. The aim of the week was to design an Oyster Card system, which was similar to the Boris Bikes challenge but with a few more additional features that demonstrated the importance of object orientated design.</p><p>The weekend challenge was a real struggle for me, mainly due to my poor time management and not being in a great mental state. I attempted to complete the task of making a takeaway menu ordering system, but rather than split my time evenly over both days, I decided to dedicate all of Sunday to it. This wasn’t the best approach and led me to becoming frustrated and stressed when I couldn’t work out solutions or didn’t know what avenue to take.</p><p>Week three started by feeling pretty rubbish off the back of the weekend challenge, but it seemed as though I wasn’t the only one, which was reassuring!</p><p>This week focused on taking new skills in TDD, BDD and OOD, to create a web app using Sinatra and Capybara. This turned out to be a great week, and whilst very challenging (not surprisingly) it was great to start putting the pieces of the puzzle together and to start learning how an app is created.</p><p>Then came the dreaded weekend challenge, all started well and I reverted back to splitting my time evenly across Saturday and Sunday, but again I ended the weekend not feeling too great about my efforts.</p><p>The struggle didn’t come from my time management, but was due to not having a step by step guide on what route to take the project (unlike in the weekday challenge). I understand the solutions of others and can read their code whilst understanding how it works, but when it comes to creating my own programs from scratch I am finding it difficult to figure out a solution and path to take.</p><p>This is an issue I am sure I will conquer over time (it is only week three after all), I have to focus on the positives and take a step back to see how far I have in such a short space of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=448b3c3707a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Makers Academy….Week 1]]></title>
            <link>https://medium.com/@lukeaveil/makers-academy-week-1-e3a8d0266490?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3a8d0266490</guid>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Thu, 02 Jun 2016 16:44:43 GMT</pubDate>
            <atom:updated>2016-06-02T16:44:43.523Z</atom:updated>
            <content:encoded><![CDATA[<p>Wow!!!!</p><p>I am writing this post on Tuesday after my first week at makers academy, I would have completed it sooner but I have not had a chance in between coding, eating, sleeping and dreaming about rspec tests.</p><p>As expected my first week was a shock to the system, both mentally and physically. I knew it would be full on but I wasn’t quite sure how I was going to handle such and intensive form of education, it turns out that being exhausted due to taking in some much knowledge and learning so many things in a short space of time really does take it out of you.</p><p>The week introduced us to two main cornerstones of how makers academy operates…..test driven development(TDD) and pair programming. The latter I have found very beneficial thus far, bouncing ideas off your partner and constantly dealing with a new code base is a fantastic way to learn. TDD on the other hand was a struggle and a totally new way of working for all of the cohort, it was refreshing to see even the most advanced classmates struggling!</p><p>The thing that I have found amazing is that come the end of the week when I close my laptop I felt completely overwhelmed and my brain absolutely frazzled, but upon opening my laptop on Saturday afternoon I surprised myself by the amount of knowledge I had absorbed. By the end of Sunday I had given the weekend work a good shot, and although not complete, I felt as though I had cemented a lot of the concepts we had learnt during the week.</p><p>We are constantly told that completing every single challenge isn’t that important, it is more important to absorb information and develop new skills as opposed to racing through the work to get to the end. At first I admit I was concerned that I was “behind” on some things compared to others, but after the first week I have shaken this trail of thought and am solely concerned where I am at it this insane journey into becoming a web developer in three months.</p><p>Our amazing coaches tell us to ask ourselves each day “am I a better developer than I was yesterday?”….it’s safe to say that I am a better developer by the afternoon than I was when I woke up that morning.</p><p>Role on week two!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3a8d0266490" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Photographer to programmer in 12 weeks….the journey has offically begun!]]></title>
            <link>https://medium.com/@lukeaveil/photographer-to-programmer-in-12-weeks-the-journey-has-offically-begun-4548cefe7049?source=rss-302305d6e7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4548cefe7049</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Luke Aveil]]></dc:creator>
            <pubDate>Mon, 23 May 2016 21:15:35 GMT</pubDate>
            <atom:updated>2016-05-23T21:15:35.746Z</atom:updated>
            <content:encoded><![CDATA[<p>It has been a long time coming, but today I started at Makers Academy…the first day of the rest of my life.</p><p>I decided to start learning to code last year after turning 30 and really having a kind of breakdown about where I was going in life and lack of fullfilling career.</p><p>I had full intention of attending a bootcamp in Melbourne where I was living at the time, but due to Australia’s harsh immigration policies we had to return to the UK out of the blue.</p><p>Although moving back to the motherland wasn’t planned and certainly not what we wanted, it has been a blessing in disguise as I got accepted onto the Makers Academy course. Since then I have been preparing best I can for the start of the course, lots of ruby and command line practise has been the flavour of the past 4 weeks!</p><p>I knew the precourse was going to be tough, but I didn’t realise exactly how tough I was going to find it. By the end of it I was itching to get started with the course proper, and today was the day that I began the journey to transform the rest of my life.</p><p>Let the adventure commence!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4548cefe7049" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>