<?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 Hanna Aikas on Medium]]></title>
        <description><![CDATA[Stories by Hanna Aikas on Medium]]></description>
        <link>https://medium.com/@hannaaikas?source=rss-c9ca3decddcb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1lWVUJjLOEi_doKQnNfrfg.jpeg</url>
            <title>Stories by Hanna Aikas on Medium</title>
            <link>https://medium.com/@hannaaikas?source=rss-c9ca3decddcb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:44:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hannaaikas/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[Hanna’s Adventures in Codeland — Chapter 5]]></title>
            <link>https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-5-49c63b6d3639?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/49c63b6d3639</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[makers-students]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 11:40:42 GMT</pubDate>
            <atom:updated>2019-09-26T11:40:42.392Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Hanna’s Adventures in Codeland — Chapter 5</strong></h3><h3>The World Needs Another Blog</h3><p>When I decided to join a coding bootcamp, I found the blogs written by other students to be really useful. They provided a great mixture of entertainment and information, and helped me prepare for the adventure that lay ahead.</p><p>That made me wonder — is this something I could do? <strong><em>Could I write a blog that would serve some sort of purpose for someone in this world?</em></strong> Or does the world already have enough blogs?</p><p>I’d like to tell you the story of why I decided to start this blog, in the hope that it’ll inspire you to have a go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6d6igv855Vh-kburVNdZaQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@corinnekutz?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Corinne Kutz</a> on <a href="https://unsplash.com/search/photos/blog?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In my life before coding (the BC era) I was already a writer of sorts. My banking job involved writing reports analysing the companies that we were lending money to. But as you can imagine, these reports didn’t allow for much creative flair, so I liked the idea of blogging as a way to try out creative writing.</p><p>However, I was tormented by the usual questions:</p><p>- What if my blogs are <strong><em>terrible</em></strong>?</p><p>- Will I have <strong><em>time</em></strong> to write a blog, if I’m busy learning computer programming?</p><p>- What if my <strong><em>family / friends</em></strong> read them and think they’re rubbish? Or even worse, what if <strong><em>prospective employers</em></strong> see them and decide against hiring me based on the blog?</p><p>In particular, the last question troubled me — would I be sabotaging my chances of getting a good job? If I was going to write about coding bootcamp, it would be pretty apparent from the content that I’m really new to the world of tech, and hadn’t even written a single line of code until I found out about Makers Academy.</p><p>I talked it over with my boyfriend, and then completely ignored his advice (which was: do not do the blog). I figured that if prospective employers are looking for someone who has been programming since childhood, then I probably don’t want to work for them anyhow. I want to work somewhere where I can be honest about what I can and can’t do, and have support to develop further.</p><p>And as for what my friends and family might think about my blog — who cares! They already accept me as I am, so a blog won’t make much of a difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*38T2QHQ1nW8SDb44Yejq8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@chang612?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chang Duong</a> on <a href="https://unsplash.com/search/photos/friends?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>That just left two questions: <strong><em>How will I ensure that the blogs are not terrible? </em></strong><em>and </em><strong><em>Will I have time to write a blog?</em></strong></p><p>Well, let’s try to imagine a bunch of people who have to write informative and entertaining material quickly and to a high standard. Oh, I know — journalists! And so, I decided to take a 1-day course on Online Journalism at a school called City Lit. At that point, I still had a bit of spare time on my hands (this was before the coding bootcamp had started), and I figured that £59 would be a good investment if it gave me an intro into creative writing.</p><p>The day got off to a fun start — we compared the content of paper magazines to online ones and learned about the art of click-bait headlines and punchy content with good visual appeal. The afternoon was focused on a groupwork exercise, where we wrote a pitch for an article that we would try to sell to an editor. My group came up with a hilarious article on the sex lives of people in their 70s and 80s! I can’t remember quite why we chose this topic, but I’m guessing we were going with the “sex sells” mantra, and managed to get quite creative in our pitch…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*juOAbB1v1_rMVSkYRm8e1A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@alexharvey?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Harvey 🤙🏻</a> on <a href="https://unsplash.com/search/photos/elderly?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The following morning, I was brimming with confidence from the course and set about writing my very first blog post. I got completely into the zone, hammered out my text within the space of an hour and then proudly handed it over to my boyfriend for review.</p><p>His response: “<em>I think you should put this away and come back to it in 2 weeks’ time. You can do much better than this.</em>” Damn, that was not the response I was expecting.</p><p>But you know what? Turned out he was right. I’m not sure whether it was wisdom, or just luck, but it worked. When I picked up the draft after 2 weeks, I was able to see with crystal clear vision what was wrong. My blog post was just a brain dump of random thoughts, anecdotes and bad jokes. <strong><em>I realised that I needed a sense of purpose for the blog, and a theme to bind the content together.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2KhDOt8Dgcq17b-8rlMsig.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@emilymorter?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Emily Morter</a> on <a href="https://unsplash.com/search/photos/question-mark?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Here’s what I came up with: <strong><em>the purpose of my blog would be to provide encouragement to anyone else contemplating a career change into tech</em></strong>. I imagined my reader as someone roughly similar to how I was a year ago — looking for something new to do with their life, but not convinced that they should / could work in tech.</p><p>As for the theme, it came about by chance. I happened to be reading Alice’s Adventures in Wonderland that week, and I liked the idea of things being opposite to what they usually are. Obviously, I didn’t take this theme too literally (and it’s not even noticeable in the content of my blogs), but having this theme lurking in the background helped me to stay focused. For example, I ruled out the idea of doing technical blog posts, on the basis that my aim is to practice creative writing by telling stories. Of course, technical topics can be conveyed via stories, but I’ll save that challenge for some other time!</p><p>With this renewed sense of purpose, I completely re-wrote my first blog post and sent it off to Makers for checking.</p><p>I wanted my writings to be part of the “official” Makers Academy blog on Medium, so that prospective students would have more of a chance of seeing them. To make this happen, each of my blog posts needs to be reviewed by the lovely Haylee from Makers. She’s great at giving feedback and suggesting edits, which gave me confidence that what I was about to publish wasn’t entirely awful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAVENA_U6V32wXSWiovI8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@craiggarner?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Craig Garner</a> on <a href="https://unsplash.com/search/photos/glasses-laptop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Once Haylee had done her proof-read, the big moment arrived — my first blog post was published. Amazing! I hesitated for a split second about who to share it with, but then decided — sod it, let’s just tell everyone! I posted it on Slack, Twitter, LinkedIn, Instagram, Facebook and for good measure emailed it to my dad (he doesn’t do social media).</p><p>The reception was just fantastic. Every word of encouragement I received was great, and what particularly warmed my heart was when people I had lost touch with ages ago contacted me to say “well done”.</p><p><strong><em>That’s the story of how this blog came to be. I still don’t know whether it’s been useful to anyone, but at least it’s been fun to write!</em></strong></p><p>I’m now in week 10 of the coding bootcamp, so only 2 weeks left! Hence, I’ll have to take a little break from blogging, in order to get my final project done and then start looking for a job as a software engineer. I hope to come back to blogging someday, but in the meantime, find me on Twitter (@hannaaikas) or LinkedIn.</p><p>To finish up — a quote from Alice’s Adventures in Wonderland:</p><p><em>“Would you tell me, please, which way I ought to go from here?”</em></p><p><em>“That depends a good deal on where you want to get to,” said the Cat.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49c63b6d3639" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-5-49c63b6d3639">Hanna’s Adventures in Codeland — Chapter 5</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[Sprint 5 — The Last Blog!]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-5-the-last-blog-2d28148d8fb2?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d28148d8fb2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 20:27:39 GMT</pubDate>
            <atom:updated>2019-09-19T20:27:39.157Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Sprint 5 — The Last Blog!</strong></h3><p>All good things must come to an end…</p><p>Russ volunteered to be Scrum Master for our last 2-day sprint, and I volunteered to be Blogger. I should clarify that “Blogger” is not an official role under Scrum methodology, it’s a role that our team invented in order to document our learning…</p><p>So, what happened in our last sprint?</p><p>We kicked off the morning with a really strong stand-up meeting, which our Scrum Master had prepped on the previous evening. He had gone through the bother of splitting out tickets and thinking through the current user journeys for our app. Hence, we were all greeted with a delightfully clear diagram on a whiteboard, as shown in the picture below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0T3IHmQcyACg-SxleGyOQ.jpeg" /><figcaption><em>Scrum Master Russ and Equally Important Person Kriss admiring the whiteboard</em></figcaption></figure><p>We kicked off our stand-up meeting with the usual check-in, this time “Which book/film describes how you feel this morning”…</p><p>· Hanna — Brave New World (book — both in the optimistic sense, and the dystopian sense)</p><p>· Farnaz — Eat Pray Love (Farnaz’s favourite film ever)</p><p>· Kriss — Quiet (best book ever for introverts) and Good Will Hunting (best film ever)</p><p>· Russ — Catcher in the Rye (strange book choice, I forget the reason why, maybe Russ is trying to shoot John Lennon) or Atlas Shrugged (book about people who get sh*t done)</p><p>We quickly realised during the stand-up meeting that we had more tickets then we could possibly handle, given we had only 1.5 days left, and that time would also be interrupted by various other very important things like the CV workshop and 121s with coaches.</p><p>Hence, we prioritised ruthlessly — Farnaz and Kriss picked up the big ticket on implementing a Friends feature (which we were all super excited about) whilst Hanna and Russ picked up a ticket about users posting on their own wall vs. other users’ walls vs. the “big wall” that shows everyone’s posts. We were feeling so optimistic that we even discussed what other tickets we could pick up from the “bit ’n’ bobs” section once we finished our allocated tickets…</p><p>Oh, how cute.</p><p>With hindsight — it’s great to have optimism and ambition, but actually both our tickets turned out to be rather demanding. Farnaz and Kriss had an early break-through, but then hit a minor hitch that took up a lot of time. Meanwhile, Hanna and Russ got off to a decent start, then had a brain wave about how to do the job “properly”, decided that would be impossible given time constraints, then proceeded to hack their way through to something acceptable.</p><p>Earlier in the day, some hesitation had emerged on the topic of “what, we have to do a presentation tomorrow?…”. But we decided to shelve that concern for now, just focus on getting stuff done between now and Friday mid-day, and then figure out the presentation on Friday at 2–3pm. This was the only rational option, seeing as we would only receive instructions about the presentation on Friday morning, so no point worrying about tomorrow’s problem.</p><p>As I write this text, it is now Thursday 9pm, and I know you’re all dying to hear how it went on Friday… Did the final version of the app work? Was it awesome? Did the presentation blow everybody’s minds?</p><p>Sadly, you will never know. This morning we decided that the duties of “team blogger” end tonight, so there will be no further blogs.</p><p>If you really want to know how the story ended, you’ll just have to offer one of us a job as a software developer and then we promise to tell you the end… Find us on linkedin/twitter/elsewhere.</p><p>It’s been wonderful! Yours truly,</p><p>Farnaz</p><p>Hanna</p><p>Kriss</p><p>Russell</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d28148d8fb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-5-the-last-blog-2d28148d8fb2">Sprint 5 — The Last Blog!</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hanna’s Adventures in Codeland — Chapter 4]]></title>
            <link>https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-4-d9648f7880ae?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9648f7880ae</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Fri, 13 Sep 2019 14:02:35 GMT</pubDate>
            <atom:updated>2019-09-13T14:02:35.069Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hanna’s Adventures in Codeland — Chapter 4</h3><h3>Learning to Fail</h3><p>I decided to learn to code because I wanted a challenge. A <strong><em>really hard challenge</em></strong>, so that I could push myself to develop. So, I taught myself the basics of coding, joined a bootcamp and guess what happened?</p><p><strong><em>It was really hard, and I failed.</em></strong> Not completely, just a bit of a meltdown in my first weekend. I’d like to share this story with you, in the hope that if you experience something similar, you’ll know that you’re not alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_rEbecg3oWhHurOMl6PMg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dchuck?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniel Chekalov</a> on <a href="https://unsplash.com/search/photos/homework?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>First, a bit of context — before my adventures in coding, I thought of myself as a “<strong><em>high achiever</em></strong>”. Not in the sense of “millionaire before 30”, but in the sense that my career had panned out better than I expected, I lived in a nice place and had a great boyfriend with whom I could share the good things in life.</p><p>Things seemed to come easily to me. Well, actually, my other half would tell you that I’m lying, as he still remembers having to pick me up off the floor when I went through a couple of stressful episodes. But in my mind, these were just little hick-ups in an otherwise happy-go-lucky existence.</p><p>When I joined a coding bootcamp (Makers Academy), they introduced us to the concept of <strong><em>growth mindset</em></strong>. In a nutshell, it means: don’t define yourself by fixed labels (e.g. “I’m great at this because I’m intelligent”), but instead praise the process (“I worked hard, and learned something today”). They instil this mindset via the mantra that success at Makers is defined by two things: (1) am I a better programmer today than I was yesterday; and (2) am I having fun.</p><p>In theory, growth mindset sounded great, and I diligently repeated the mantra “I will not compare myself to others”. I even went and bought Carol Dweck’s book on growth mindset (in French because I don’t like to make things easy for myself…). And to top it all off, I embarked on an evangelical mission to tell everyone else in the world that they should get a growth mindset. It totally made sense.</p><p><strong><em>Until it didn’t.</em></strong> I had got through the first week of bootcamp just fine, and all I needed to do was to complete the weekend homework. But if you happened to read my last blog post, you’ll know that the weekend turned into a bit of a disaster.</p><p>We were supposed to create a simple Ruby app called Airport, that theoretically allows planes to take off and land, subject to there being no stormy weather and the airport not being full. But unfortunately, my airport ended up resembling Berlin Brandenburg (i.e. pretty much the worst airport in the world!).</p><p>Never in my life had I failed to complete homework. Or at least if I did it was for a cool reason like “I was out partying so hard that I didn’t have time”. <strong><em>Never had I actually tried and failed.</em></strong></p><p>Now, I know what you’re thinking. “Big deal, you didn’t do the homework, get over yourself”. But if you identify as a “high achiever” then failing at something that ought to be doable really can mess with your mind. In my case, it put me on a massive downer and I was not looking forward to going back to school the next week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_uRnMJcLDwn6YK5Gym2gmg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@nate_dumlao?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nathan Dumlao</a> on <a href="https://unsplash.com/search/photos/failure?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Monday came around, and we were told to get together in small groups and review each other’s code from the weekend homework. Everyone else seemed happy to chat about how they approached the task, whereas I just sat there in a huff. It got worse when we regrouped with the rest of the cohort, and people shared their experiences and questions. I sat there not being able to even follow the conversation, let along take part.</p><p>All I could think was “those people are doing so well, whereas I’m a terrible programmer and I’m even worse at growth mindset”.</p><p>I spoke with other students and told them I was feeling crappy, but hopefully it would pass. Maybe I was just having a particularly difficult week, and it would get better next week. But one of the students who had been at Makers longer overheard this, and burst my bubble by saying “Nope, it continues to be difficult during your whole time here”. Oh no.</p><p><strong><em>How on earth would I survive 12 weeks of coding bootcamp, if every single week would be difficult?</em></strong> Sure, I had asked for a hard challenge, but this was way too much.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nsgqSvCBHkaINMHx0Mt9rg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@staticlaw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Fabrizio Conti</a> on <a href="https://unsplash.com/search/photos/uphill?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It was time to get some help. <strong><em>The great thing about being at Makers is that everyone has your back and they all want to see you succeed.</em></strong> I reached out to my mentor, discussed it with other students and got help from the coaches (especially Dana, who is amazing at listening and giving good advice!). Eventually, I put the pieces together and mapped out a way forward.</p><p>What I needed to understand was this: My “high achiever” mindset had served me well in the past, and there was no point in trying to delete this side of who I am. In fact, those traits might still come in handy someday. However, for now, what would serve me best was a different mindset, one that involved being a bit kinder to myself. There was no point in pushing myself to work harder to catch up with the “clever people”. The reason why they were ahead was generally because they had practiced programming for longer than I had, and there was no way to catch up. Well, not unless I invented a time machine!</p><p>And as for me being terrible at growth mindset — ironically, the fact that I was frustrated about not having a growth mindset was actually a sign that I was on the way to developing one. It’s just that it’s hard and you have to keep working on it every day, by noticing unhelpful thoughts and having an outlet for pent up frustration.</p><p>Having understood these things, I decided to drop the whole story of me being a terrible programmer. I put an end to the pity party and told myself <strong><em>“You’re doing fine, because you’re putting in the right amount of effort and you’re gradually becoming a better programmer”</em></strong>. And, as if by magic, the very next day I was able to help one of the more experienced students solve a problem with their code!</p><p>What an awesome feeling that was — I had actually helped someone with their code! I was back in the game!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqL1bfAZhND39Fv0IgC1Yg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@robbie36?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Robert Collins</a> on <a href="https://unsplash.com/search/photos/game?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The moral of the story is this: being in a coding bootcamp is hard, so you really have to treat yourself kindly. Especially if you’re used to being a “high achiever”. Your fellow students will be from all walks of life, some people will be more experienced at programming, but even those students will face tough moments. You’ll all get through it somehow, so just hang in there and ask for help when you need it.</p><p><strong><em>That’s the story of how I set out on the path to develop a growth mindset. The journey continues!</em></strong></p><p>Thanks for reading this, and extra special thanks if you’ve managed to read all 4 blog posts that I’ve published so far. Coming up next time — I’d like to tell you the story of how I got into blogging. See you in 2 weeks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9648f7880ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-4-d9648f7880ae">Hanna’s Adventures in Codeland — Chapter 4</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[Sprint 2, Day 2]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-2-day-2-611f5350d4c0?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/611f5350d4c0</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 12 Sep 2019 19:39:30 GMT</pubDate>
            <atom:updated>2019-09-12T19:39:30.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*CbDDd5zYtXa6PCywPY200g.png" /></figure><p><strong>Stand-up Meeting Agenda:</strong></p><p>- Check ins- give your theme song for the morning</p><p>- One thing you have learnt</p><p>- What you want to work on</p><p>- Possible blockers</p><p>Then:</p><p>- Review yesterday/merge requests</p><p>- Choose tickets for the day</p><p>- Split tickets</p><p>- Assign pairs/branch names</p><p><strong>Agreed in Stand-Up Meeting:</strong></p><p>- Lessons Learned: When planning, decide what names we’ll give each branch, and put branch name in Trello ticket</p><p>- Open Questions: Ask Sophie (coach) about how the Router fits in with the MVC model (MVC stuff is in app folder, router is in config folder of our Rails app)</p><p><strong>Key Points from Q&amp;A with Sophie:</strong></p><p>- In Rails, do we need to do Unit Tests (to test stuff that Rails builds for us) or focus more on Feature Tests? Answer: Focus on Integration Tests and Feature Tests. Integration tests are testing interaction between controller/model/database, but they leave out the browser (unlike a Feature Test which also involves the browser).</p><p>- [See above question on MVC + Router]. Answer: The router changes the routing that has been set up when we implemented a given Rails scaffold. To find out what the ‘root’ does (e.g. ‘posts#index’), click on the link right below it in the comments! To understand full MVC model, see link below (at end of blog — link from Farnaz).</p><p>- What do CI tools actually do? You set it up to run the linter and the tests, and your code will not deploy to production until these pass. Have to tell the CI tool how to build your app. Common errors:</p><p>o Bundler version dependencies</p><p>o Gemfile missing dependencies</p><p>o Enviroment settings production/development/tests</p><p><strong>What we did - morning &amp; afternoon shift:</strong></p><p>- Not a full day, as we had Q&amp;A at 11 and careers talk at 3pm. So we effectively just did a half day</p><p>- Farnaz and Hanna worked on database — set up associations — one user has several posts.</p><p>- Kriss and Russ worked on closing out remaining tickets on sign in, sign up, routing. Also picked up new ticket on adding line breaks to posts.</p><p>- All tickets completed and moved to In Production by end of shift! Wooohoooo!</p><p><strong>Feedback from Sophie:</strong></p><p>- Make sure your README is up to date, and would be useful to anyone joining the project tomorrow</p><p>- Nice to see lots of closed PRs, consider putting in place an approval check point on GitHub and protecting the master branch so it can’t be pushed to.</p><p>- Would also be great to see more discussion on PRs, you can comment on the PR as a whole or on individual lines of code. Can speed up workflow and help make sure everyone understands the code.</p><p><strong>End of Sprint Retro — Key stuff:</strong></p><p>- <strong>What went well in sprint?</strong></p><p>o Through experience we improved as a team vs. Sprint 1</p><p>o Sat close to each other</p><p>o Did branches well on Day 2</p><p>o Did Trello tickets well on Day 2 -&gt; clarity</p><p>o Positive vibes!</p><p>-<strong> What to improve?</strong></p><p>o Even workloads / swapping driver role / committing</p><p>- <strong>Favourite feature in our app?</strong></p><p>o Line breaks in posts</p><p>o 1-to-many relationships</p><p>o All the Travis stuff, Linter, Tests pass!</p><p>- <strong>What to improve in our app?</strong></p><p>o Styling</p><p>o Refactor tests, adding helpers</p><p><strong>Notes — Technical resources:</strong></p><p>- From Russ: Article on how to create associations between 2 Active Record Models: <a href="https://guides.rubyonrails.org/association_basics.html">https://guides.rubyonrails.org/association_basics.html</a></p><p>- From Farnaz: Picture on MVC model incl. DB and router: <a href="http://images.thoughtbot.com/ember-rails-terminology-differences/rails.png">http://images.thoughtbot.com/ember-rails-terminology-differences/rails.png</a></p><p>- From Kriss: command to access the heroku database: heroku pg:psql</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=611f5350d4c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-2-day-2-611f5350d4c0">Sprint 2, Day 2</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 2, Day 1]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-2-day-1-eabb3d3205c1?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/eabb3d3205c1</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 19:38:58 GMT</pubDate>
            <atom:updated>2019-09-11T19:38:58.806Z</atom:updated>
            <content:encoded><![CDATA[<p>After the fantastic 1st blog post from Russ, I’m going to lower the standards a bit!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaHekHK81t98PE8PyOQ6fw.jpeg" /><figcaption>Russ being the boss (and proving that he doesn’t look like himself in photos). He’s pointing at the thing Hanna &amp; Farnaz were not meant to work on in the afternoon!</figcaption></figure><p>Key stuff we did / learned today:</p><p><strong>Roles for sprint 2:</strong></p><p>- Scrum Master = Russ</p><p>- Blogger = Hanna</p><p>- Equally Important Team Players = Farnaz &amp; Kriss.</p><p><strong>Agenda for stand-up (posted on Slack by Russ):</strong></p><p>- Check-ins: give the food that reflects your state.</p><p>- One thing you have learnt since last meeting</p><p>- One thing you want to work on this sprint</p><p>- Possible blockers</p><p>Then:</p><p>- Decide on tickets; Split tickets</p><p>- Choose the one task to mob</p><p>- Assign pair tasks; Assign pairs</p><p>- Separate for mob research</p><p><strong>How the stand-up went:</strong></p><p>- Russ brought a magic frog — whoever holds the frog speaks!</p><p>- Meeting went well except Farnaz was stuck in commuting hell (trespasser on line…)</p><p><strong>Feedback from Sophie (Makers coach):</strong></p><p>Good stuff:</p><p>- Mood check-ins</p><p>- Rotating roles</p><p>- Fitting in own work e.g. stop at 4:30pm for process workshop</p><p>- The magic frog!</p><p>- Looking at Trello board in meeting</p><p>Stuff to improve:</p><p>- Too many items on Trello board “In progress” column</p><p>- Hesitating at estimating ticket sizes — just guess, refine later</p><p><strong>What we did — morning shift:</strong></p><p>Kriss &amp; Hanna read up on Rails. Russ &amp; Farnaz tried to fix Travis issue.</p><p>Attended a Q&amp;A lead by Katerina.</p><p>Then split into pairs:</p><p>- Russ &amp; Kriss sorted deployment issues (Travis / Heroku)</p><p>- Farnaz &amp; Hanna did user authentication. Also, Farnaz got help from Katerina on testing, Hanna asked Sophie to clarify user requirements.</p><p><strong>What we did — afternoon shift:</strong></p><p>Caught up after lunch, then split up into pairs again. BUT being a bit of a fool, I forgot which task which pair were working on, so led my pair to work on the same damn thing as the other pair… Oops. Apparently it was fixed in the end, will find out in tomorrow’s stand-up.</p><p><strong>Summary</strong></p><p>Good stuff:</p><p>- Stand-up meeting</p><p>- Pairing</p><p>- Got stuff working in the end</p><p>- Forgiving when someone screws up…</p><p>Room for improvement:</p><p>- Being 100% sure who is working on what (make it idiot-proof!)</p><p>- Co-authoring git commits…</p><p><strong>Notes / Technical resources:</strong></p><p>- From Russ: walkthrough we used for generating sign up via devise in Sprint 1: <a href="https://medium.com/@mchisti/creating-simple-users-in-rails-with-devise-gem-tutorial-cd91d2ef36d5">https://medium.com/@mchisti/creating-simple-users-in-rails-with-devise-gem-tutorial-cd91d2ef36d5</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eabb3d3205c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-2-day-1-eabb3d3205c1">Sprint 2, Day 1</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kick-off!]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/kick-off-f6e0c0448d37?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6e0c0448d37</guid>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 11:08:20 GMT</pubDate>
            <atom:updated>2019-09-09T11:08:20.104Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog will be used to document our learning from the AceBook project.</p><p>Our team is called Fantastic Four, and we are:</p><p>Kriss Wiltshire<br>Russell Wind<br>Hanna Aikas<br>Farnaz Ardenti</p><p>First update coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6e0c0448d37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/kick-off-f6e0c0448d37">Kick-off!</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hanna’s Adventures in Codeland — Chapter 3]]></title>
            <link>https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-3-7cb15e0ae306?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cb15e0ae306</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Fri, 30 Aug 2019 09:16:27 GMT</pubDate>
            <atom:updated>2019-08-30T09:16:27.904Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hanna’s Adventures in Codeland — Chapter 3</h3><h3>Bootcamp for Introverts</h3><p>My previous blog post told the story of how I taught myself the basics of programming and managed to secure a place at a coding bootcamp (Makers Academy).</p><p>Up to this point, it had been a solitary journey, but I was about to have company! Bootcamp would start soon, so my thoughts turned to what it would be like to learn programming with other people. Whilst I was excited about the prospect of making new friends and embarking on this adventure together, I was also apprehensive.</p><p>I’m an introvert, and social situations can be a bit stressful for me. But I thought — surely, during my time at coding bootcamp I’d be surrounded by other introverts and we’d just sit there all day, happily writing code in silence, wearing noise cancelling earphones. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vvoXzdCswOYqzJwPrUoJw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@septillion?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Frank Septillion</a> on <a href="https://unsplash.com/search/photos/earphones?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Wrong. This should have been clear from reading the Makers Academy website. <strong><em>They consider coding to be a team sport.</em></strong> Turns out I couldn’t just leave all my extrovert skills at the door. In fact, on this journey I would face some of the biggest challenges I’d ever encountered on my travels in this world ruled by extroverts.</p><p>Let’s start by clearing up a misconception — being an introvert doesn’t mean I dislike social situations, it just means that afterwards I need to recharge my batteries by being alone (as opposed to an extrovert, whose batteries recharge when they’re in company and drain when they’re alone). One theory is that introverts respond more strongly to their environment, so the sights, sounds and buzz of social situations can overwhelm the senses of an introvert, and hence we need a break from time to time.</p><p>Before deciding to learn computer programming, I worked in banking, where the name of the game is to behave like an extrovert, or face comments like “you should work on raising your profile”. Hence, I spent years trying to mimic the behaviours of extroverted colleagues. That good old “fake it ’til you make it” strategy. It worked fine, and in fact these days most people refuse to believe I’m an introvert. But the truth is that whilst I might be talkative, I definitely need a bit of downtime. Hence, we instituted a “do nothing on Sundays” rule in my household, to give me and my equally introverted boyfriend a full day off to recharge.</p><p>I took it for granted that that’s the way life is — I simply had to act like an extrovert during the week, recharge at the weekend, and rinse and repeat. But one day I stumbled upon a TED talk by Susan Cain on the power of introverts. Her message is: the world should adapt to us introverts, rather than us having to put up with success being defined by extroverts. We shouldn’t be forced to act like them, and should instead be given the space to be who we truly are. This would lead to greater productivity and happiness for all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RAxRtjQtibKFEWiK1A-EFg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@simonmigaj?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Simon Migaj</a> on <a href="https://unsplash.com/search/photos/alone?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>After hearing Susan’s battle cry for introverts, I thought that one of the benefits of switching career would be that I would finally get to embrace my introvert tendencies.</p><p>Turns out… that was not the case!</p><p>The first major challenge arrived before I even started at Makers. There was a little message on Twitter from Amina, a lovely programmer I met at a Codebar workshop. She innocently suggested that I take part in a YouTube livestream with other junior developers, to talk about how we got into tech. My first reaction — Hell, no! I wince at the thought of having my photo taken, let alone being videoed. Let alone being videoed and it being broadcast live. But Amina is super nice, so I really couldn’t say no. I agreed to do it, and told myself that if it all goes wrong, I’ll just go live in another country, one where they don’t have YouTube.</p><p>However, one of the benefits of being an introvert is that I generally do a good job prepping for any major events (according to Susan Cain, this is typical introvert behaviour, whereas extroverts are happy to wing it). Hence, before the livestream, I spent 2 hours talking to myself (out aloud) about how I got into tech. And thanks to that prep, the livestream went absolutely fine — the two hours flew by, I said some coherent things, and the only hick-up was when I dribbled water on my chin as I was attempting to drink from my water bottle live on air.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAGnB5e8ytJDgfAzQQ34MQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kushagrakevat?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kushagra Kevat</a> on <a href="https://unsplash.com/search/photos/broadcast?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Phew, livestream over, back to normal life. And then to coding bootcamp.</p><p>At this point, I had accepted that the Makers Academy experience would not involve sitting around in silence. I was pretty apprehensive, and imagined that pair programming (i.e. programming with another person, rather than by yourself) would be a painful experience that I’d just have to learn to tolerate.</p><p>The thing that concerned me was that, whilst working in banking, I was only expected to display extrovert behaviours in specific situations (e.g. meetings). Aside from that, the business of doing analytical work was a solitary pursuit. Gradually, as I progressed to more senior roles, more extroversion was expected of me, but at least there was a clear separation between analytical work vs. the parts of my job that involved talking. I was worried that coding bootcamp wouldn’t allow for this separation into thinking time vs. talking time. According to some theories, introverts find it difficult to perform to the best of their abilities if their senses are distracted by things like social interaction. <strong><em>So, how on earth could I learn to code as a team sport?</em></strong></p><p>Day one of coding bootcamp came along. That was fine, we were just talking, not actually doing any programming. Fine so far. Day two involved writing some code, but nothing too heavy. Day three — things got real.</p><p>That afternoon, I was pair programming with the lovely Jodi, one of the fellow students of my cohort. We hit a frustrating obstacle right at the start of the process (a Github forking/cloning issue) and another issue half way through (turns out a bit of our code was in the wrong file). These process issues seemed determined to keep us from actually writing any code. I was incredibly tempted to declare, Greta Garbo style, that I want to be alone. Alone, so that I could fix this problem and then return to the pairing thing.</p><p>But that’s not how pairing works… I knew this, so I worked hard to squash my inner Greta Garbo, and stay in the situation with Jodi. We kept talking through the problem and eventually managed to get everything working. Whilst our fellow students may have written more code that particular afternoon, we became the masters of fixing github issues, making sure code is in the right files and generally being awesome at pair programming. All this thanks to behaving like extroverts and sticking together.</p><p>After that, the week rolled on just fine, we wrapped up on Friday and were off to enjoy the weekend. Well, not enjoy it too much, as we had our weekend homework to do. I thought “<strong><em>great, I finally get to work on my own</em></strong>”. But ironically, that’s when the meltdown happened. Left to my own devices, I found every possible way to sabotage my programming efforts.</p><p>I started off with procrastination — far too much time wasted on choosing what music to listen to whilst I write code. I then launched into writing some amazing code that had nothing to do with the spec. That swallowed up roughly 90 minutes, after which I realised my mistake and deleted the whole thing. Next, I actually wrote some decent code for a while, but then inexplicably had a crisis of confidence and deleted the whole lot (again!). At that point, I was just crying for someone to come sit with me and work through it together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T83XNdLgY9YTrZKJgMeU_g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thomasdes?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thomas Despeyroux</a> on <a href="https://unsplash.com/search/photos/lightbulbs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>What on earth had happened?</p><p>I was only one week into coding bootcamp and already I, Hanna Aikas, card-carrying member of the introvert club had turned into someone who prefers pair programming over flying solo. Didn’t see that coming!</p><p><strong><em>That’s the story of how I learned that coding bootcamp might be challenging for introverts, but if you’re open to it, you’ll learn new behaviours and might even surprise yourself!</em></strong></p><p>Coming up next time in this blog — how to survive coding bootcamp if you’re used to being a high achiever. See you in 2 weeks’ time!</p><p><em>PS. If you’re interested in the YouTube livestream I mentioned — do a search for the Code Mortals YouTube channel. It’s run by the lovely Eddie and Andrew, and their mission is to support the tech industry on open source and best practices.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cb15e0ae306" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-3-7cb15e0ae306">Hanna’s Adventures in Codeland — Chapter 3</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[Hanna’s Adventures in Codeland — Chapter 2]]></title>
            <link>https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-2-b4f24d019739?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4f24d019739</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[makers-students]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 15 Aug 2019 07:21:54 GMT</pubDate>
            <atom:updated>2019-09-02T09:44:26.766Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hanna’s Adventures in Codeland — Chapter 2</h3><h3>Coding for Technophobes</h3><p>My previous blog post told the story of how I decided to quit my job and learn to code. Making that decision was the easy part. <strong><em>Now I just needed to — you guessed it — learn to code.</em></strong> Or at least learn enough to pass the entry requirements for Makers Academy, the coding bootcamp I wanted to join.</p><p>When I set out on this journey, my level of technical proficiency could be described as non-existent. Well, not quite. After all, I could operate a smartphone, so that put me at Level 1, just above my mum who is very much at the baseline (sorry mum if you’re reading this, you’re wonderful, just not that strong with technology!).</p><p>Where to start? I’m a bit of a bookworm, and hence my natural inclination was to find a book that could teach me. I googled book suggestions, went on Amazon and ordered Code, Clean Code and Pragmatic Programmer. This seemed like a sensible thing to do, until I stumbled upon the claim that learning to code by reading books is like learning to swim by walking. Now, whilst I object to the poorly crafted analogy, I got the point. <strong><em>No more dillydallying, put the books away, time to code!</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kKI6L1BGz_mXdtrSZRuA0g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kaimantha?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Claudia</a> on <a href="https://unsplash.com/search/photos/books?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The internet is full of wonderful free resources that teach you to code, but I started off by falling into the trap of trying something called “Learn to code in 15 minutes”. The tutorial started out with an instruction to type something into your Terminal. Fine if you know what a Terminal is… And, unlike many other tech terms, Terminal is not easily googleable.</p><p>After some trial and error with other online learning resources, I found the promised land that is Codecademy. They do a good job of treating you like an idiot, which is how I prefer to be treated when I’m learning new things. They don’t do ambitious things like asking you to find the Terminal on your computer. I signed up to the “Learn Ruby” course and was good to go!</p><p>I religiously practiced on Codeacademy each Sunday throughout December and January. The course got a bit complicated towards the end, so once I was done, I gave myself a big pat on the back and headed over to something called Codewars. It sounded ominous, but came with a strong recommendation as a good place to develop coding skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aF0OppaR5RwjnS1RMBktSA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@idgeek?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Samuel Ramos</a> on <a href="https://unsplash.com/search/photos/war?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I logged into Codewars, selected that I want to learn Ruby and I want a challenge (or kata as they insist on calling them) from the easiest possible level. And then I just stared at the screen… and stared… Where are the instructions? What, I’m meant to just figure it out? How?</p><p>Clearly, Codewars is the big boys learning club where they take the training wheels off. And you realise that <strong><em>Codecademy was just a warm-up</em></strong>. Now is when the real learning starts, by solving problems using your own wits, rather than by obediently following a set of instructions. I’ll admit that the only way I got through my first kata was to stare at it for long enough and then hit “unlock solutions”. I’m not proud of that, but we all have to start somewhere, and eventually I got better.</p><p>The thing about Codewars is that even after you’ve solved the kata i.e. your code works, it’s not over yet! You might feel happy that the tests are green, but that happiness ends pretty abruptly when you submit your solution and get to see how other people did it. Suddenly your 10 lines of amateurish code look a bit basic next to someone’s fancy one-line solution. Now, you’ve got two options here: either be angry about how clever other people are; or try to stay constructive and learn something from the clever people and their fancy solutions.</p><p>This became my new Sunday routine — I’d put on my battle gear (sweatpants) and charge into Codewars for a 3-hour session. Whilst my code continued to look rather amateurish one week after the next, I was able to slowly but surely accrue points and move up from Level 8 (rock bottom) to Level 7. And that meant one thing… <strong><em>I was ready for pair programming</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yfjvR5gGFIQAluxjBMBq-Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@johnschno?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">John Schnobrich</a> on <a href="https://unsplash.com/search/photos/work-together?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>For those who don’t know, pair programming is when you sit with another programmer (either side by side, or sharing your screens remotely e.g. via Skype), and you take it in turns to be the driver (who writes the code) and the navigator (who looks ahead and supports the driver). This rite of passage would apparently dramatically increase my chances of getting into Makers Academy, and they even provide a platform through which to find someone to pair with. I spent 2 hours on a Sunday being patiently guided by a more experienced programmer on how to get the basics right. At the end, he bestowed upon me the blessing “<strong><em>I think you’re ready to apply for Makers</em></strong>”. Wow.</p><p>I did not believe this to be true, but thought “what the heck, I’ll go fail the interview once for practice, and then apply again later”. I booked a day off work, lined up my interview with Makers for the morning (which is actually a pair programming session, rather than a traditional interview), and scheduled visits to two other bootcamps for the afternoon. I figured it would be good to have a Plan B and Plan C, seeing as Makers are selective in who they take.</p><p>The big day came around, I arrived at Makers’ Shoreditch building ridiculously early, so spent 20 minutes in the coffee shop across the road, staring into a cup of tea, telling myself to keep it together. The seconds melted slowly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0sf2p4dv7-xFTTAJv8z27A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@replicantman?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Drew Taylor</a> on <a href="https://unsplash.com/search/photos/cup-of-tea?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Finally, it was only 10 minutes ahead of time, so I abandoned the tea, went across the road, and waited in the Makers reception. I tried to look clever by leafing through one of the coding books that was casually lying around, but quickly abandoned it out of fear that my interviewer might ask me what I thought of the book (umm… great book). Instead I just stared at the wall and suppressed panic until the friendly-looking interviewer finally came to collect me.</p><p>I wish I could tell you what passed in that interview/pairing session, but I really cannot recall. I must have written some valid code, because at the end the wonderful interviewer said “We’d love to have you join Makers”. Oh my god! Really! I threatened to hug him, but the expression on his face made it clear that he did not consent. Instead I blurted out my thank yous, flew out the door, down the stairs, onto the street, found a second coffee shop and phoned my dad to say “I passed!”.</p><p><strong><em>That’s the story of how I transformed myself from a clueless technophobe to someone who could at least dream of becoming an awesome programmer. And I found the coding bootcamp where I could pursue that dream.</em></strong></p><p>Coming up next time — how to survive coding bootcamp if you’re an introvert. I’ll be publishing that blog post in 2 weeks’ time, hope to see you then!</p><p><em>PS. If you’re interested in the nitty-gritty of what happens at Makers Academy, follow me on Twitter (@hannaaikas). During my time on the course (22 July — 11 Oct 2019), each weekend I’ll do a series of tweets on what I learned that week.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4f24d019739" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-2-b4f24d019739">Hanna’s Adventures in Codeland — Chapter 2</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[Hanna’s Adventures in Codeland — Chapter 1]]></title>
            <link>https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-1-e4973ddc4144?source=rss-c9ca3decddcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4973ddc4144</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[makers-students]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 10:50:00 GMT</pubDate>
            <atom:updated>2019-08-01T21:07:42.422Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Hanna’s Adventures in Codeland — Chapter 1</strong></h3><p><strong>How I Quit My Job to Do What I Hate</strong></p><p>The internet is awash with stories about bankers/lawyers/accountants who chuck in their high-paying jobs to work with food. Why? Maybe because lunch break was the only intermission of joy in their otherwise mundane working days. Maybe because food seemed familiar and easy to grasp. Maybe because triple chocolate cake really is the path to self-actualisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdP39qqs-AUccIiUL_byoQ.jpeg" /><figcaption>Photo by Toa Heftiba on Unsplash</figcaption></figure><p>So, did I follow this well-trodden path when I succumbed to mid-career existential angst? Did I follow the cake trail and go into food? Or did I go into something else I love, like wine, yoga or the arts?</p><p>No. <strong><em>Instead I decided to go for the one thing that I hate — technology. </em></strong>Yes, you heard that right, I decided to embark on a new career in technology despite being a grade-A certified technophobe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iuSKK3d30UFIb_vNPdftjQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@alexkixa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alexandre Debiève</a> on <a href="https://unsplash.com/search/photos/technology?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let’s back up a little to make sense of this story.</p><p>In the beginning, I was working in banking, happily I should add, and had been doing so for a while. But something was off. A sense of familiarity was not so much creeping in as stomping around loudly. And whilst my job was never easy, the hard parts were more to do with people and politics rather than pure intellectual challenge, which is what I was craving.</p><p>So, it was time to make a change. Time to do something so hard that I might fail. Not in the physical sense — no mountain climbing or marathon running for me, thanks — but hard for the brain. I considered going back to school, and came dangerously close to applying for a masters at the London School of Economics. But then I woke up and remembered that I actually hate economics.</p><p>Instead I wanted to combine intellectual challenge with doing stuff. Making stuff, things of practical value. But what on earth could I make? Other than cake?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3LZBxVxTTGcqCSN6i8tmw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thifalin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thiébaud Faix</a> on <a href="https://unsplash.com/search/photos/business-school?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The angel of revelation arrived in the form of an email from a women’s network — ignore the usual stuff about conferences, training events, mentoring etc and skip to the random shout-outs at the end of the email — it said: Makers Academy is for career changers and they will teach you to code.</p><p>Code? Like computer coding? Could that be what I was looking for? Well, the name says Makers and, yes, I suppose coding is a form of making something… and it’s bound to be hard.</p><p>But here’s the thing — I hated computers. Technology. The whole lot. When they gave us iPhones at work I had to ask the graduate how to get my emails on it. I was the archetype technophobe, and proud of it too. I read books you see. I have a bookshelf, not a pile of devices and their assorted chargers.</p><p>Yet somehow, in that moment of seeing the words Makers Academy, I suddenly abandoned the technophobe cause and thought: <strong><em>Because I am bad at this, it is exactly what I must do</em></strong>.</p><p>And so, one evening in November, I went along to a Makers Academy open event. I was used to attending all sorts of networking events, but the minute I stepped into their exposed-brick Shoreditch building, I regressed straight back to being a teenage introvert wallflower. It took every inch of mental strength to pick myself up and go talk to those people with their shiny MacBooks. What was I meant to even say — hey, how’s your coding been today? But I got over myself, and an hour later I was sold. <strong><em>Because this is so scary, it is exactly what I must do.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NlqpTTAM8DbGl4paBmjE_g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Christopher Gower</a> on <a href="https://unsplash.com/search/photos/coding?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>So what’s the moral of the story? Don’t judge a book by its cover. Tech is two things — hardware (things you can touch) and software (code). I still have little enthusiasm for learning the details of how a computer physically works, but I love writing code. <strong><em>It’s hard but not impossible, and rewards you with moments of unadulterated joy when you finally get your code to work.</em></strong> It’s the best possible feeling — the code works! Hallelujah! Praise the almighty gods of code! Woohoo!</p><p>What do you reckon — do you fancy giving coding a go? Or are you being held back by stereotypes that are as outdated as Alabama’s political views? No, you don’t need to be a maths genius to code. No, you don’t need to be the prototype engineer who spends their free time disassembling household appliances. No, you don’t even have to like computers. What you need is the ability to think logically in order to solve problems. And bunch of other stuff, but I won’t stress you out by compiling a list of all the traits of a “perfect coder”. As Salvador Dali said, don’t worry about perfection, you’ll never reach it.</p><p>Or you could just learn to bake triple chocolate cake instead.</p><p><strong><em>So, that’s the story of how I ended up doing what I hate. And I absolutely love it!</em></strong></p><p>Coming up next time — how I taught myself to code and navigated the entry process for Makers Academy. I’ll be publishing that blog post in 2 weeks’ time, hope to see you then!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4973ddc4144" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/hannas-adventures-in-codeland-chapter-1-e4973ddc4144">Hanna’s Adventures in Codeland — Chapter 1</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>
    </channel>
</rss>