<?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 Nikesh on Medium]]></title>
        <description><![CDATA[Stories by Nikesh on Medium]]></description>
        <link>https://medium.com/@nikeshashar?source=rss-ee56ad19eaa4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*prjmzIWxpitkhpohwXHZag.jpeg</url>
            <title>Stories by Nikesh on Medium</title>
            <link>https://medium.com/@nikeshashar?source=rss-ee56ad19eaa4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:21:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikeshashar/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[Everyone’s guilty of that sideways smiley face , Purple Heart  and the occasional blush☺️.]]></title>
            <link>https://medium.com/@nikeshashar/everyones-guilty-of-that-sideways-smiley-face-purple-heart-and-the-occasional-blush-%EF%B8%8F-e23ffcc3f2c6?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e23ffcc3f2c6</guid>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Fri, 12 Jul 2019 10:10:11 GMT</pubDate>
            <atom:updated>2019-07-12T10:10:11.985Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone’s guilty of that sideways smiley face 🤣, Purple Heart 💜 and the occasional blush☺️. What am I talking about?</p><p>Emoji’s of course.</p><p>However with the increased usage of Slack, what’sapp and other social communication tools – have you thought about what it costs a company in time and money to find *that* perfect emoji?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*kDq8k25MxIRcaqGD2lFGyA@2x.jpeg" /></figure><p>There are <a href="https://emojipedia.org/faq/">2,823 emoji’s at the time of writing</a>. Imagine (generously) that you can get to 80% of these quickly (or ignore them) that leaves 20% of these which an average person might spend 30 seconds or so finding it.</p><p>This equates to roughly 4.7 hours of emoji finding time! #quickmaths</p><p>On an average salary of £35k that’s around £65 per month spent on emoji usage or £39k a year for a team of 50!</p><p>Better start working on those keyboard shortcuts….</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e23ffcc3f2c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An introduction to TDD in Ruby]]></title>
            <link>https://medium.com/makers-academy/an-introduction-to-tdd-in-ruby-72f0a8536509?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/72f0a8536509</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Tue, 28 Mar 2017 10:02:02 GMT</pubDate>
            <atom:updated>2017-03-28T10:02:02.686Z</atom:updated>
            <content:encoded><![CDATA[<p>The goal of this blog post is to introduce you to Test Driven Development (TDD). We are assuming you have some knowledge of Ruby or code and are using a computer that is ready to code. You will need to know or be setup with :</p><ul><li><a href="https://blog.makersacademy.com/playing-in-irb-34e5498f7cd5#.dmqxohm7k">IRB</a></li><li><a href="http://www.github.com/">Github</a></li><li><a href="https://www.sublimetext.com/">Sublime Text</a> / <a href="http://www.atom.io/">Atom</a></li></ul><h3>What is Fizzbuzz?</h3><p>Fizzbuzz is a simple coding challenge, often described as a <a href="http://codekata.com/">code kata</a>. The objective of Fizzbuzz is to create a program with the following specification:</p><ul><li>The program can be passed a number.</li><li>When passed a number that is a multiple of 3, the program returns the message ‘Fizz’.</li><li>When passed a number that is a multiple of 5, the program returns the message ‘Buzz’.</li><li>When passed a number that is a multiple of <em>both</em> 3 and 5, the program ignores the previous 2 rules and returns the message ‘Fizzbuzz’.</li><li>In all other cases, the program simply returns the given number.</li></ul><p>When complete we should be able to play in irb like so:</p><pre>irb 2.2.1 <br>:001 &gt; require &#39;./lib/fizzbuzz&#39; =&gt; true 2.2.1 <br>:002 &gt; (1..20).each {|number| puts &quot;#{number} --&gt; # {fizzbuzz(number)}&quot;} <br>1 --&gt; 1 <br>2 --&gt; 2 <br>3 --&gt; fizz <br>4 --&gt; 4 <br>5 --&gt; buzz <br>6 --&gt; fizz <br>7 --&gt; 7 <br>8 --&gt; 8 <br>9 --&gt; fizz <br>10 --&gt; buzz <br>11 --&gt; 11 <br>12 --&gt; fizz <br>13 --&gt; 13 <br>14 --&gt; 14 <br>15 --&gt; fizzbuzz <br>16 --&gt; 16 <br>17 --&gt; 17 <br>18 --&gt; fizz <br>19 --&gt; 19 <br>20 --&gt; buzz</pre><h3>Introducing TDD</h3><p>Test driven development is a software programming practice that can radically increase code quality and program design. It is used throughout top software development companies and we are hardcore advocates of it here at Makers Academy.</p><p>It can be a bit strange at first, but once you get used to it, it will help your designs to <em>emerge</em> and accelerate your coding skills remarkably.</p><h3>TDD in a nutshell</h3><h4>Step 1: Write a failing test (RED)</h4><p>We begin by describing a single expectation of our program. We do this using a testing framework. There are a number of frameworks to choose from, but we prefer <a href="http://rspec.info/">RSpec</a>.</p><p>We make no immediate assumptions about what the program is, or how it should work; we simply <strong>write the code we wish we had</strong> to satisfy the expectation we are describing.</p><p>What makes this step particularly unusual for people starting TDD for the first time, is that we already know this test is going to fail for multiple reasons. Nevertheless, we do not write a single line of production code until there is a <strong>failing test</strong> in place to justify it.</p><h4>Step 2: Write the simplest code possible to pass the test (GREEN)</h4><p>This is the second reason why TDD is so peculiar at first. It is likely that the simplest code possible is also, initially, <strong>the wrong code</strong>. Yet we write it anyway. The reason is, at this point, our only motivation is to pass the test. We make no assumptions about future requirements of the code.</p><p><strong>Future requirements will only be satisfied when they are proven by the introduction of another test.</strong></p><h4>Step 3: Clean up (REFACTOR)</h4><p>The final step is to double check that <em>all</em> current tests are still passing and to tidy up and improve the structure of the code (<em>without adding any additional functionality</em>) where appropriate. We can improve the code with considerable confidence, because running our tests will always prove that the current expectations of the code are being met.</p><h4>Step 4: Repeat until all expectations have been specified.</h4><p>Choose the next expectation and return to Step 1. This process is also known as:</p><p>RED — GREEN — REFACTOR</p><p>You will experience TDD and pair programming throughout the Makers Academy.</p><h3>Starting Fizzbuzz</h3><p>Open up your terminal, and use Unix commands to move to and/or create a folder somewhere in which to place projects.</p><p>Now type the following:</p><pre>$ mkdir fizzbuzz <br>$ cd fizzbuzz <br>$ git init</pre><p>You will need the <a href="https://github.com/rspec/rspec">RSpec gem</a> installed:</p><pre>$ gem install rspec</pre><p>RSpec provides a convenient command-line option to initialize your project. Type the following:</p><pre>$ rspec --init</pre><p>You should now see the following file structure</p><pre>└── spec <br>    └── spec_helper.rb</pre><p>We have reached a suitable commit point, so let’s check our repository status:</p><pre>$ git status</pre><p>Did you notice anything strange? Is there a .rspec file that you hadn&#39;t noticed before? Why doesn&#39;t it show when you do ls? Try ls -a instead.</p><p>Commit your changes with a suitable message:</p><pre>$ git add . <br>$ git commit -m &#39;initializes rspec&#39;</pre><p>We are going to need somewhere to write our tests. So let’s create a spec file:</p><pre>$ touch spec/fizzbuzz_spec.rb <br>$ git commit -am &#39;adds fizzbuzz_spec.rb&#39;</pre><p>Notice the file is in the ./spec folder and has the suffix _spec.rb. Discuss the reasons for this with your pair partner.</p><p>Finally, run RSpec and ensure ‘everything is green’.</p><h3>Writing the first test</h3><p>Switch roles again :twisted<em>rightwards</em>arrows:. In your favourite editor, type the following code in ./spec/fizzbuzz_spec.rb:</p><p><strong><em>You must type all code in these walkthroughs by hand. DO NOT copy and paste. Speed is not the objective and you will learn more effectively by manually typing code.</em></strong></p><pre>describe &#39;fizzbuzz&#39; do it <br> &#39;returns &quot;fizz&quot; when passed 3&#39; do <br>   expect(fizzbuzz(3)).to eq &#39;fizz&#39; <br> end <br>end</pre><p>Discuss this code with your pair partner. What does each line mean? Read the <a href="http://archive.makersacademy.com/p/pills/rspec.md">RSpec pill</a> and ensure you understand exactly what is going on.</p><h3>Running the first test</h3><pre>$ rspec</pre><p>RSpec should now report that you have one failing test. If not, carefully check you have correctly followed the steps. If you need further help, please ask an <a href="https://github.com/makersacademy/course/blob/master/toc.md#resources">Alumni Helper</a>.</p><p>Discuss the RSpec output with your partner. What does it mean? How would you use this output to drive the next step in the process?</p><h3>Passing the first test</h3><p>Now we have a failing test, we can actually write some production code. To keep our production files and test files separate, we will put our production code in a folder called lib.</p><pre>$ mkdir lib $ touch lib/fizzbuzz.rb</pre><p>Now, in your text editor, edit lib/fizzbuzz.rb:</p><pre>def fizzbuzz <br>end</pre><p>What are we doing here? Our RSpec output told us undefined method &#39;fizzbuzz&#39;, so we are simply attempting to change that message - nothing more. Run $ rspec again. Have we changed the message?</p><p>Although we have now defined the method fizzbuzz, RSpec is still unable to see it. This is because RSpec knows nothing about the file fizzbuzz.rb. We have to tell it. In fizzbuzz_spec.rb, add the following line to the top of the file:</p><pre>require &#39;fizzbuzz&#39;</pre><p>Notice we did not specify the lib folder or the .rb extension. Should we have done? Discuss this with your pair partner. Note also that the following two alternatives are also valid:</p><pre>require &#39;./lib/fizzbuzz&#39; <br>require_relative &#39;../lib/fizzbuzz&#39;</pre><p>Discuss these three alternatives with your pair partner. Which one do you prefer? Why?</p><p>Now run RSpec again. Have we changed the message? Do all three of the above alternatives result in the same message? Discuss the output with your pair partner. You may or may not wish to switch roles at this stage</p><p>It’s important to question scenarios like the one above and not simply accept that they work ‘by magic’.</p><p>Do some research online — try to understand what’s happening behind the scenes. In this case, RSpec actually adds lib to its LOAD_PATH by default. This means that it will look for required files in lib automatically, which is why we can simply require &#39;fizzbuzz&#39;.</p><p>Ruby will infer the .rb extension if it is omitted, so this is optional too.</p><p>You should be seeing the message wrong number of arguments (1 for 0). We have not specified the arguments in our method definition. When doing TDD for real, you would probably not stoop to this level unless you were practicing &#39;One-undermanship&#39;.</p><p>Nevertheless, let&#39;s fix the message:</p><pre>def fizzbuzz(number) <br>end</pre><p>Run RSpec again. Still failing? Good. Now let’s pass the test :twisted<em>rightwards</em>arrows:</p><pre>def fizzbuzz(number) <br>  &#39;fizz&#39; <br>end</pre><p>Seriously? Yes. The critical point to understand here is that our production code <em>now fully meets the expectations defined in our tests</em>. But we clearly haven’t satisfied the specification of the program.</p><p>We can see this by running the program in irb:</p><pre>$ irb 2.2.1 <br>:001 &gt; require &#39;./lib/fizzbuzz&#39; =&gt; true 2.2.1 <br>:002 &gt; fizzbuzz 3 =&gt; &quot;fizz&quot; 2.2.1 <br>:003 &gt; fizzbuzz 4 =&gt; &quot;fizz&quot;</pre><p>We strongly recommend that you regularly check the functionality of your code in IRB as you go along. We can see clearly here that we ‘fizz’ for 3, but we also do so for every number. We need more tests!</p><h3>Writing the next test</h3><p>It should be clear now that we have two objectives in TDD:</p><ol><li>Write production code that fully meets the expectation of our tests.</li><li><strong>Write tests that fully meet the specification of the progam</strong>.</li></ol><p>Once we have achieved both of those objectives, we know with absolute confidence that we are ‘code complete’ and that our program works exactly as it should. And what’s more, as an added and incredibly valuable bonus, anyone new to our codebase does not need to trawl through our production code trying to understand what it does. They can simply read our tests and (assuming the tests all pass) know exactly what the code <em>should</em> do and also that <em>it does</em>.</p><p>Commit your code to git then discuss with your partner what the next test should be.</p><h3>Finishing Fizzbuzz</h3><p>Continue with the RED — GREEN — REFACTOR (commit) process until you have completely specified and coded Fizzbuzz.</p><p>Use irb to run further manual tests. Are there any edge cases that you have missed? If so, write a test to cover each edge case. Why is this so important?</p><p>Try running Fizzbuzz for all numbers from 1 to 100 in irb. Discuss with your pair partner different ways to do this. Can you use Ruby to do this in one line of code (N.B. it must be elegant and readable)?</p><p>When you are finished, please find a coach or <a href="https://github.com/makersacademy/course/blob/master/toc.md#resources">Alumni Helper</a> to verify what you have done.</p><h3>Further exercises</h3><p>Once you have completed Fizzbuzz, please delete your fizzbuzz directory and start over from scratch with opposite roles. (You read that correctly - please delete the entire directory and start again.) Do as much of it as you can from memory. Practicing repeatedly this way will accelerate your learning.</p><p>To make it more interesting, try to solve the Fizzbuzz problem in different ways. For example, here’s an alternate version of the first test:</p><pre>it &#39;returns &quot;fizz&quot; for the number 3&#39; do <br>  expect(3.fizzbuzz).to eq &#39;fizz&#39; <br>end</pre><p>Can you code the whole of Fizzbuzz this way?</p><p><strong>Supporting materials</strong></p><ul><li><a href="http://codekata.com/">Code kata</a></li><li><a href="https://github.com/rspec/rspec">RSpec gem</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72f0a8536509" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/an-introduction-to-tdd-in-ruby-72f0a8536509">An introduction to TDD in Ruby</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[It’s not all Ruby — reasons to choose Makers Academy to learn JavaScript]]></title>
            <link>https://medium.com/makers-academy/its-not-all-ruby-reasons-to-choose-makers-academy-to-learn-javascript-f65db5fdcf78?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f65db5fdcf78</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Tue, 10 Jan 2017 11:02:01 GMT</pubDate>
            <atom:updated>2017-02-08T17:27:12.620Z</atom:updated>
            <content:encoded><![CDATA[<p>A common question we get from potential students is:</p><blockquote>“Why don’t you teach [insert technology here]?”.</blockquote><p>We also sometimes hear it as,</p><blockquote>“I heard/my developer friend/a random blog on the internet [delete as applicable] said that Ruby/Ruby on Rails is soooo last year and no-one uses it any more. Why’s it on your curriculum?”.</blockquote><p>The answer is simple: <strong>we aim to produce language-agnostic graduates who have a strong grasp of programming fundamentals.</strong> That’s a bit of a mouthful, so in a nutshell:</p><blockquote><em>we train people in the skills they need to become amazing junior developers</em> — <em>not specific technologies</em>.</blockquote><p>We start people’s programming journey in Ruby because we believe that Ruby is a great first language for beginners — it gets out of the way quickly and allows learners to think about the actual problem at hand, rather than getting trapped by syntax and language oddities. Also, the Ruby community is awesome for beginners — one of the community’s mottos is <a href="https://en.wikipedia.org/wiki/MINASWAN">MINASWAN</a></p><p>The same thing applies to Rails — despite the internet consistently<a href="http://www.itworld.com/article/2851688/losing-steam-don-t-drop-everything-to-learn-ruby-on-rails.html"> announcing</a><a href="https://www.quora.com/Now-that-Ruby-on-Rails-is-declining-does-it-still-offer-a-good-career-for-junior-developers-who-want-to-work-as-Ruby-on-Rails-developers"> Rails’ demise</a>, it’s still an extremely effective way to learn about<a href="https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller"> MVC architecture</a> and the basics of<a href="http://rest.elkstein.org/"> REST</a>.</p><p>We also continue to consistently place graduates in Rails jobs, not least at the <a href="https://www.gov.uk/government/organisations/government-digital-service">Government Digital Service</a>, who builds the UK government’s digital infrastructure using open source software.</p><p><strong>But enough about Ruby.</strong> To give a slightly more detailed answer, let’s talk about one of the major current technology trends: JavaScript. JavaScript has become extremely popular in the last few years, leading to some bootcamps switching to an all-JavaScript curriculum. Many current jobs on the market are for full-stack JavaScript developers, As a result, we often get applicants asking, “why choose Makers Academy for JavaScript?”.</p><p>Some may think that we lag behind current trends and risk becoming outdated if we don’t follow the all-JavaScript trend. That’s because we think it’s better to focus on universal skills, which are applicable in a wide array of languages, then figure out the exact details and we see what kinds of jobs are available on the market.</p><p>Here are three reasons why Makers Academy is the right choice to learn JavaScript, and indeed any technology:</p><ol><li>Fundamentals are always fundamentals</li><li>We always consider the market</li><li>We also do… lots of JavaScript</li></ol><h4>Fundamentals are always fundamentals</h4><p>Here is how you map over things, in Ruby:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c005d864ff3e128ee403be111932b4e5/href">https://medium.com/media/c005d864ff3e128ee403be111932b4e5/href</a></iframe><p>And again, in JavaScript:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e72785349ce42f66cb4ba3539179fb67/href">https://medium.com/media/e72785349ce42f66cb4ba3539179fb67/href</a></iframe><p>While the syntax is different, the underlying concepts are the same — take an array (1), call the “map” method on it (2), pass an anonymous function (also known as a block in Ruby) (3), with a parameter representing each element of the array (4); then apply the body of the function (5). This concept of “mapping” is fairly universal across most programming languages — if you understand the concept, the actual implementation in each language comes naturally. If you don’t understand the concept — that’s what we’re here to help you with!</p><h4>We always consider the market</h4><p>Programming languages and frameworks (especially front-end JavaScript frameworks) come and go, depending on current trends. For back-end: we’ve seen Rails ride to the top then become a mainstream technology, Node.js becoming a viable alternative for big enterprise, Java and .NET’s popularity rise, fall and rise again. For the front-end: we’ve watched the transition from jQuery to Knockout, from Knockout to Angular, then from Angular to React/Ember/Angular. Our curriculum has shifted from being an all Rails course, to having one week of JavaScript, then two… then realising that if students get the fundamentals right and learn how to pick up frameworks quickly, we don’t need to specifically focus on a technology until applying for a job that uses it.</p><p>In 2016, we added Node.js to the course due to an upsurge in its popularity, then replaced it with Angular as the market shifted. Right now, we’re sitting tight and seeing how things unfold as ES6, Web Components, React and other ground-breaking new innovations start to see widespread adoption. Ultimately, we always want to make sure our graduates are prepared to enter the job market with the skills that are highly in demand, and will continue to adapt the curriculum to make sure that’s the case.</p><h4>We also do… lots of JavaScript</h4><p>Coming back to the main point of this article — there’s plenty of JavaScript on the course. Two whole weeks are currently dedicated to it, as well as it being an option many teams choose for any of the project weeks. We expect students to pick up enough JavaScript to build projects in just two weeks, and not just superficially — they go deep into the gnarlier parts, such as callbacks, promises, and event-driven programming, as well as learning about testing in JavaScript, build tools and the wider ecosystem. They also learn to build their own testing library, and have the option to pick up Node.js themselves with the materials we previously created, as well as leveraging a carefully selected list of online resources.</p><p>All that said, it might be easier to look at actual data: with this approach, we’ve successfully placed graduates in companies using all of the current major JavaScript frameworks (Angular/Ember/React/NodeJS), as well as jQuery roles and pure JavaScript for companies that prize raw speed and quick page load times.</p><p>Beyond that, we also have graduates working in almost every language under the sun: a quick (and incomplete) list includes: C++, C#, F#, Java, Go, Scheme, Swift, Objective-C, Python, SQL (used as a full programming language, and not just for queries!).</p><p>All that, with just 12 weeks of Ruby and JavaScript</p><p>Do you want to change your career in 2017? Head on over to our site and apply now for a place!</p><p><em>Liked this post? Share it with someone by clicking on the heart below</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f65db5fdcf78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/its-not-all-ruby-reasons-to-choose-makers-academy-to-learn-javascript-f65db5fdcf78">It’s not all Ruby — reasons to choose Makers Academy to learn JavaScript</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[RSpec & failing fast— make life quicker!]]></title>
            <link>https://medium.com/makers-academy/rspec-failing-fast-make-life-quicker-3e238bbd97b8?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e238bbd97b8</guid>
            <category><![CDATA[rspec]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[tdd]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Thu, 15 Dec 2016 11:11:01 GMT</pubDate>
            <atom:updated>2016-12-15T11:11:01.544Z</atom:updated>
            <content:encoded><![CDATA[<p>All of the code we write at <a href="http://www.makersacademy.com/">Makers Academy</a> is tested in one way or another. With our Ruby code, we prefer RSpec. And it’s perfectly fine to use — until you make one little change somewhere and everything breaks.</p><p>Then you start debugging —an important skill our students practice constantly throughout the course.</p><p>Recently we launched a new exercise for students to learn and I thought I would give it a go. After setup — I naturally ran RSpec in my terminal and was presented with this :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/55fe5df58028ab655db67816aeb6af23/href">https://medium.com/media/55fe5df58028ab655db67816aeb6af23/href</a></iframe><p>Lots of failures. Handy for me RSpec has a feature built into it that will allow me to concentrate on one fix at a time!</p><p>Enter….<strong> — fail-fast</strong></p><p>I simply open up my code files, find the .rspec file and add</p><pre>--fail-fast</pre><p>at the bottom.</p><p>Now my .rspec file looks like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*hBIkDE60sox6LNME6fHo2g.png" /><figcaption>Editing my .rspec file</figcaption></figure><p>And running RSpec on my project will give me one error at a time!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpV4fP9rPHvZwNcLB1nY-w.png" /><figcaption>Single failure — much easier to handle.</figcaption></figure><p>To read more about how RSpec works and it’s features head on over to the docs <a href="http://www.relishapp.com/rspec/rspec-core/docs">here</a></p><p><em>Found this article useful? Let someone else know too by clicking on the green heart!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e238bbd97b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/rspec-failing-fast-make-life-quicker-3e238bbd97b8">RSpec &amp; failing fast— make life quicker!</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[Coding101: An intro to Ruby Methods]]></title>
            <link>https://medium.com/makers-academy/coding101-an-intro-to-ruby-methods-3cb6b7904c5a?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cb6b7904c5a</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[makersacademy]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 11:01:02 GMT</pubDate>
            <atom:updated>2016-11-17T11:01:02.293Z</atom:updated>
            <content:encoded><![CDATA[<p>When people come to interview to learn to code at Makers Academy, they tend to get stuck on the creation of methods. In this code-along tutorial, we’ll explore the basic constructs of methods in Ruby that will help you out on your journey to learn to code.</p><p><strong>Note : to effectively go through this post, you should ideally have your </strong><a href="http://www.preparetocode.io/"><strong>development environment setup</strong></a><strong> correctly and have read through our previous blog post titled : </strong><a href="http://blog.makersacademy.com/playing-in-irb"><strong>Playing in IRB.</strong></a></p><p>Anything you see</p><pre>in grey boxes</pre><p>is Ruby code and can be run in your local editor <strong>and / or </strong>in IRB</p><p>A common developer acronym is <strong>DRY</strong> — <strong>D</strong>on’t <strong>R</strong>epeat <strong>Y</strong>ourself.</p><p>What this means is: avoid repetition in your software. Write the code once and then you can use it over and over.</p><p><strong>Methods</strong> help us with this. In this article, I’m going to show you how methods work.</p><p>A method is made up of just a handful of elements:</p><ol><li>The ‘def’ keyword</li><li>The name of the method</li><li>0+ arguments (which we can name whatever we want)</li><li>The code to be executed when the method is called</li><li>The ‘end’ keyword</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5p8HIUs7rzvSd2aC.jpg" /></figure><p><em>Image credit : </em><em>Roi Driscoll</em></p><p>Here’s an example:</p><pre>def hello(name)  <br>  puts &quot;Welcome to learning how to code #{name}&quot;<br>end</pre><p>That’s how we define a method. We’ve named this method <strong>“hello”</strong>and it takes an <strong>argument</strong> called <strong>“name.”</strong> Arguments exist to allow us to pass objects <strong>in</strong> to the method so we can use them in the executing code.</p><p>When we call the method “hello”, it will execute the code before the<strong>”end”</strong> statement — the <strong>“end”</strong> keyword simply exists to tell Ruby that the function is finished.</p><p>Now we can run this:</p><pre>hello(&quot;Rob&quot;)  <br>hello(&quot;Jane&quot;)  <br>hello(&quot;Pete&quot;)</pre><p>Create a new hello.rb file in SublimeText, and copy out the code below.</p><p><strong>DON’T COPY AND PASTE!</strong></p><p>Once saved, you can run the code by pressing Cmd-B (or, you can just run it from the terminal as usual if you prefer).</p><pre>def hello(name)  <br>  puts &quot;Welcome to learning how to code #{name}&quot;<br>end</pre><pre>hello(&quot;Rob&quot;)  <br>hello(&quot;Jane&quot;)  <br>hello(&quot;Pete&quot;)</pre><p>This is <em>a lot cleaner</em> and <em>less repetitive</em> than writing out three long “puts” statements:</p><pre>puts &quot;Welcome to learning how to code Rob&quot;  <br>puts &quot;Welcome to learning how to code Jane&quot;  <br>puts &quot;Welcome to learning how to code Pete&quot;</pre><p>We can also create functions that take more than one argument. Let’s modify our hello.rb file to now read like this:</p><pre>def hello(name, age)  <br>  puts &quot;Welcome #{name}, #{age} is definitely not too old to learn how to code.&quot;<br>end</pre><pre>hello(&quot;Rob&quot;,30)  <br>hello(&quot;Steve&quot;,72)  <br>hello(&quot;Jenny&quot;,55)</pre><p>You see how “Rob” is passed in as the “name” variable and 30 is passed in as the “age” variable in the first example?</p><h3>Method chaining</h3><p>In Ruby everything is an object and every object has methods. This enables us to “chain” several method calls together. You’ll see this pattern often:</p><pre>&quot;hello, world&quot;.slice(0, 5).capitalize.sub(&quot;o&quot;, &quot;0&quot;)</pre><p><strong>Try this in </strong><a href="http://www.blog.makersacademy.com/playing-in-irb"><strong>IRB</strong></a><strong> — what happens?</strong></p><p>This line takes the string “hello, world”, then slices five characters starting with the first one (index 0). This operation will return “hello”. Due to us chaining methods, the output of this ‘slice’ method is passed as input to the ‘capitalize’ method, which will return “Hello”. This then is passed to the ‘sub’ method, where we substitute the letter “o” with number “0” (sub stands for substitution). That’s how we get “Hell0” as the result — each function does it’s own small bit and passes it’s output as input to the next command in the chain.</p><p>This technique of calling methods directly on the return value of the previous method call is called <strong>method chaining</strong>. It can allow you to do fairly powerful data transformations in just one line.</p><p>All methods used above are part of the <strong>class String</strong>, so you can read about them in the documentation (do you remember how to find Ruby classes documentation by googling?).</p><p>What else can you create? Tweet us your code snippets :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cb6b7904c5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/coding101-an-intro-to-ruby-methods-3cb6b7904c5a">Coding101: An intro to Ruby Methods</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[Our start dates are changing]]></title>
            <link>https://medium.com/makers-academy/our-start-dates-are-changing-a8663e24f1c0?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8663e24f1c0</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Fri, 07 Oct 2016 09:30:56 GMT</pubDate>
            <atom:updated>2016-10-13T16:17:08.286Z</atom:updated>
            <content:encoded><![CDATA[<p>A little while ago we <a href="https://blog.makersacademy.com/were-changing-our-prices-5efe67645978">changed our pricing</a> to reflect the changing market for coding bootcamps in Europe. As we enter 2017 and demand continues to grow, we’ve made a strategic decision to offer <strong>more</strong> classes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*RCuCQ7lph-jCLuXTzPh0hw.png" /></figure><h3>We’re pleased to announce today that from February 2017, Makers Academy will be starting a new class <strong>every 4 weeks.</strong></h3><p>Our class sizes in 2017 will be slightly smaller than they are now — around 24 students, which will allow us to maximise the space we have in our London HQ and offer a more streamlined service to our Hiring Partners.</p><p>While we grow our Careers team to meet this demand, we aim to provide a much more personalised and effective service by also integrating a bunch of new materials into our course — materials based around being an effective Junior Developer and the “soft skills” that are come with such a coveted title. You can read more about this in Zara’s post about <a href="https://blog.makersacademy.com/were-deprecating-hiring-week-here-s-why-9bc7e7aa2b16">deprecating Hiring Week</a></p><p>If you have any questions about an application you’ve made already feel free to reach out to <a href="/service/mailto:onboarding@makersacademy.com">onboarding@makersacademy.com</a> and a member of the team will be glad to help.</p><p><em>PS: We’re still hiring. Check out our jobs here : </em><a href="http://makers-academy.breezy.hr/"><em>http://makers-academy.breezy.hr</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8663e24f1c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/our-start-dates-are-changing-a8663e24f1c0">Our start dates are changing</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[How You Can Contribute to the Makers Blog]]></title>
            <link>https://medium.com/makers-academy/how-you-can-contribute-to-the-makers-academy-blog-4d83b03c609e?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d83b03c609e</guid>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[makers-students]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Wed, 10 Aug 2016 11:25:06 GMT</pubDate>
            <atom:updated>2019-02-06T13:00:49.892Z</atom:updated>
            <content:encoded><![CDATA[<p>Makers’ blog get 000’s of views, and we’re always looking for quality content to share with our community.</p><p>If you’re a current Maker, a potential student, an educator or you’re technically gifted, and you’d like to share your thoughts with the Makers network, we want to hear from you!</p><p>This page should give you all the info you need on what we look for and how to submit to us.</p><blockquote><em>A note to Makers grads: We </em><strong><em>highly</em></strong><em> recommend you submit at least one blog (on your Makers experience or on something technical) either while studying or job hunting. It’ll massively improve your chances of landing a job!</em></blockquote><h4>What We Look For</h4><ul><li>Authenticity content. Don’t worry about sounding like a pro, we want to hear your experience and your opinions!</li><li>Technical content aimed at beginners</li><li>Non-technical content about your experiences at Makers</li><li>Technical content about specific projects you’ve worked on</li><li>Non-technical opinion pieces about the tech industry &amp; breaking into the industry</li><li>Pieces on diversity and inclusion in tech</li><li>Something different, how your other interests relate to coding.</li><li>Posts with images, code snippets and multimedia content</li></ul><h4>How To Submit a Post</h4><ul><li>Write a draft blog post on your Medium account</li><li>Send Haylee your Medium username via Slack or email (haylee@makers.tech), with a link to your draft blog post so you can be added as a contributor.</li><li>Once you’re added, go to your post and click the cog button then Edit Story.</li><li>Click the three buttons, Add to publication and choose Makers.</li><li>We will make any necessary comment / edits, approve the post and publish it</li></ul><p>If you have any questions, please ask them in the comments :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d83b03c609e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/how-you-can-contribute-to-the-makers-academy-blog-4d83b03c609e">How You Can Contribute to the Makers Blog</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[Playing in IRB]]></title>
            <link>https://medium.com/makers-academy/playing-in-irb-34e5498f7cd5?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/34e5498f7cd5</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[coding101]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Fri, 06 May 2016 10:21:50 GMT</pubDate>
            <atom:updated>2017-02-23T15:16:28.669Z</atom:updated>
            <content:encoded><![CDATA[<p>Now that you’ve got <a href="http://www.preparetocode.io/">Ruby installed</a>, let’s start coding!</p><p>With your terminal open, type the following command:</p><pre>irb</pre><p>This will open up the interactive ruby console and you should see a prompt like this: “&gt;”. With irb, you can type ruby code that’s instantly run in your terminal.</p><p>The ‘irb’ is a Ruby <a href="http://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop">REPL (read-evaluate-print loop)</a> because it waits for you to enter a Ruby expression, reads it, evaluates it and prints the result of the evaluation back to the terminal. So, if we put 2 + 2 into irb, it will evaluate it using Ruby and show the result: 4.</p><pre>&gt; 2 + 2 =&gt; 4</pre><p>Irb is very useful for playing with Ruby. Whenever you think “Hey, what would this bit of code do?”, the answer is <strong>not</strong> to google it, read about it &amp; try to <strong>memorise</strong> what it does…</p><p>It’s much easier, and you’ll learn a lot more, if you play with it in irb and see if it does what you think it should do. Learning through exploration and play is <strong>vastly</strong> more effective than memorising other peoples words.</p><p>Sometimes you’ll be surprised by what you find when you play in irb. For example, what will this code do?</p><pre>5 / 2</pre><p>You may expect that it will evaluate to 2.5 but you’ll be wrong.</p><pre>&gt; 5 / 2 =&gt; 2</pre><p>This is not a mistake, it’s a pecularity of Ruby language. We’ll discuss why it evaluates to 2 instead of 2.5 shortly.</p><p>Don’t assume that irb is only good for relatively simple snippets of code. You can put something really sophisticated into irb as well (and you will, as you learn more about Ruby).</p><p>In particular, you can enter blocks of code that span multiple lines. If a line cannot be evaluated because you haven’t finished entering it yet, irb will wait for you to continue on the next line. Try hitting ‘enter’ after the plus sign, for example.</p><pre>&gt; 2 + &gt; 2 =&gt; 4</pre><p>Since you pressed enter after the plus sign (line 3), it’s obvious to Ruby that you haven’t finished entering the expression to evaluate, so it will wait until you finish it on the line 4 and only then print the result (“4”).</p><p>This also happens if you enter text into irb. A piece of text is called a “string” in Ruby (because it’s a “string” of characters) and must be enclosed in quotes. If we enter a string into irb, it is just returned back to us.</p><pre>&gt; &quot;Hello, Makers!&quot; =&gt; &quot;Hello, Makers!&quot;</pre><p>If, however, we forget to close the string by omitting the double quote, irb will wait until you enter it because it will assume you’re still entering the string. This is a very common source of confusion among beginners because it will look like the irb isn’t responding. This is what’s happening here:</p><pre>:001&gt; 2 + 2 =&gt; 4 <br>:002 &gt; &quot;Hello, Makers <br>:002&quot;&gt; I forgot to close the quote <br>:002&quot;&gt; so even if I press &#39;enter&#39;, it doesn&#39;t do anything <br>:002&quot;&gt; 2+2 <br>:002&quot;&gt; it doesn&#39;t print &#39;4&#39;, because we&#39;re still typing <br>:002&quot;&gt; the string that began with &#39;Hello, Makers&#39; <br>:002&quot;&gt; Ok, let&#39;s stop this nonsense and close the quote&quot; </pre><pre>=&gt; &quot;Hello, Makers\nI forgot to close the quote\nso even if I press &#39;enter&#39;, it doesn&#39;t do anything\n2+2\nit doesn&#39;t print &#39;4&#39;, because we&#39;re still typing\nthe string that began with &#39;Hello, Makers&#39;\nOk, let&#39;s stop this nonsense and close the quote&quot;</pre><p>Note that lines 7 to 12 (when the string was still not “closed”), there was a quote character before the prompt (:002&quot;&gt;) instead of a space (:001 &gt;). This was an indication that irb is waiting for the closing quote.</p><p>When you want to quit irb, just type exit.</p><h3>Demo</h3><p><a href="https://asciinema.org/a/0d5tn72b2oye7l1owqw31lqk1">Playing in IRB</a></p><p>Here’s a short video that shows you how to use IRB</p><h3>Advanced IRB</h3><p>You can control what happens when you start irb using a .irbrc file placed in your home directory, e.g.</p><pre>Dir[&#39;./lib/*.rb&#39;].each { |f| require f }</pre><p>will autoload ruby files from your lib directory.</p><p>Now that you’ve see what can be done, stop focusing on memorisation of syntax!</p><p>Remember to <strong>“play in IRB”</strong>, use it to try out ideas for code solutions and to <em>actually</em> test what your code does before you suggest it as a solution to a challenge.</p><p><em>Originally published at </em><a href="http://blog.makersacademy.com/playing-in-irb/"><em>blog.makersacademy.com</em></a><em> on May 6, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34e5498f7cd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/playing-in-irb-34e5498f7cd5">Playing in IRB</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[Passing the Makers Academy PreCourse]]></title>
            <link>https://medium.com/makers-academy/passing-the-makers-academy-precourse-61b59261fa76?source=rss-ee56ad19eaa4------2</link>
            <guid isPermaLink="false">https://medium.com/p/61b59261fa76</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[makersacademy]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Nikesh]]></dc:creator>
            <pubDate>Thu, 08 Oct 2015 16:07:25 GMT</pubDate>
            <atom:updated>2017-02-23T15:10:00.072Z</atom:updated>
            <content:encoded><![CDATA[<p>At Makers Academy, we pride ourselves on being a selective bootcamp. People often ask about how we select our students; what drives our decision-making process when acting as judge, jury and occasionally executioner when it comes to allowing candidates to join our community.</p><p>Usually the first interaction we’ve had with a potential student is their application: you must be able to write coherent sentences. A big red flag for us is applicants who submit incoherent applications, or clearly ill-considered responses to the questions we pose. We reject one in ten applications at this stage alone.</p><p><strong>Wait, I’m applying to learn to code — why do I need to write full sentences?</strong></p><p>We have a duty of care to our customers. We have a responsibility not to take someone’s life savings if we don’t honestly believe we can turn them into a developer. Submitting a considered, legible application tells us you’re serious about wanting to spend a significant amount of money on a career change. It will also reassure us that we are going to be interviewing a candidate that can write in English and we can then work on teaching you how to communicate effectively — you’ll be spending over 80% of your time at Makers Academy pair-programming after all!</p><p>The second step is the interview. We give every applicant two pieces of work to prepare for their interview at Makers Academy. This is where we get to see again how serious people are. At every stage of your journey through the course, we’ll always aim to challenge you. What you learn each day will be more challenging than the day before.</p><p>When we pair program with you in an interview, we’ll always make things tougher than what you learnt through <a href="http://pine.fm/">Chris Pine’s Learn to Program</a> and <a href="http://www.codecademy.com/tracks/ruby">Codecademy Ruby</a>. We’re not looking for raw coding knowledge (it does help :) — but it’s not required). We want to see how you approach solving problems and what you’ve been able to absorb in a short amount of time.</p><p>We can pretty much tell immediately if someone hasn’t done the work. Lots of our applicants will go through at least two rounds of interviews, if not more. We do everything we can to ensure you’re the right person for the course.</p><p>This leads us to the PreCourse — our final selection phase. Every six weeks we start a new four week PreCourse. This is where you learn the basic development skills you’ll need for the rest of your career. In recent iterations of the PreCourse, we’ve raised our entry criteria after feedback from students and our coaching team.</p><p>Of course, we want everyone who starts the PreCourse to start the main course four weeks later, and the vast majority do. But every now and then we’re forced to refuse someone entry onto the main course. Below are six things you can do to ensure that you fly through your PreCourse.</p><p><strong>1) Do the work you’re set</strong></p><p>We’ve spent the past few years, in partnership with some awesome <a href="http://www.makersacademy.com/employers">hiring partners</a>, refining what needs to be learnt if you want to be a valuable junior developer. It’s essential that you take the PreCourse as seriously as you take the main course, and don’t cut corners or skip anything, even if you think you already know the subject. We have a number of systems in place to monitor and measure all of your activity, so we can tell that you’re progressing and support you if you’re not. Do the work you’re given, and we’ll have no reason not to accept you onto the main course.</p><p><strong>2) Communicate, communicate, communicate</strong></p><p>Students are often surprised to hear us say that communication is one of the most valuable skills you’ll develop here at Makers Academy, as well as being one of the key attributes our partners look for in a new hire. We use Slack as our primary communication tool, and we’ve seen that the more that students share their struggles and support each other — even in the PreCourse — the better they perform on the course. If you haven’t spoken to anyone in your cohort or even chatted to your mentor by the time you finish the PreCourse, we’re likely to be a little concerned about your communication skills.</p><p><strong>3) Ask for help when you’re stuck</strong></p><p>We advise students to spend no more than 20 minutes on a problem before reaching out for help — whether that be from other students in your cohort, senior students at Makers Academy, Alumni Helpers or MA coaches. We also have to remind people that googling for solutions, looking things up in the documentation, asking for help from other students or friends who are developers — <em>none</em> of this is cheating. You’re expected to do this as part of your learning process throughout your career. Even Makers Academy Senior Engineers have Ruby documentation open for most of the day. If you can’t admit when you’re stuck and ask for help, you might struggle in your future life as a developer</p><p><strong>4) Follow instructions</strong></p><p>Being able to follow instructions is a critical skill for a developer. Attention to detail is equally important. The instructions we give you will be accurate and all-encompassing. If they’re not — it’s intentional. We look for students who carefully and methodically go through any README files, or any emails that we send with information on what you should be working on or what your weekly challenge will be. Our hiring partners will ask us, ahead of meeting you, how good you’ve been at following instructions. If you haven’t managed to get a tick in that box in the PreCourse, it’s risky for us to think you’ll change if we let you sit the main course. One thing we’ll never do is lie to our hiring partners — so following the instructions you’re given is an easy way to get a big fat recommendation from us!</p><p><strong>5) Share your code with the world</strong></p><p>Makers Academy students pride themselves on sharing their code and their journey with the world. Yes — your PreCourse code will be messy and embarrassing and you’ll look back on it and cringe. BUT — you should celebrate what little you do know: it will feel amazing when you look back on it when you graduate, and, more importantly, it gives our hiring partners a convenient way to see how far you’ve come. It also allows us to track your progress, to check that you’re learning, keeping up with your cohort and doing the work that we’ve prescribed. We want you to develop a certain ‘Maker mindset’, and sharing your (beginner-level) code with the open source community is part of this. This is also why so many of our students write blogs, but that’s a topic for another blog post :)</p><p><strong>6) Trust us</strong></p><p>We’ve coached hundreds of people through this journey, and everything we do is geared towards making you a valuable software developer once you graduate. If we ask you to do something, you should do it. Even — actually <em>especially</em> — if you’ve done it before. Most people have unknown gaps in their knowledge, and the time you spend as a student at Makers Academy is a great opportunity for you to plug those gaps. In the end, those gaps will be found out — by then the course will be moving at the fast pace that it does, and it will be much harder to go back over those materials.</p><p><strong>Why are we telling you all this?</strong></p><p>We want 100% of our PreCourse students to join us on the main course, and rather than giving this talk to each student individually, we thought we would share it publicly as an affirmation of our vision. We want the best students we can get, and we want to train them into amazing developers, as our hiring partners require. Without the ability to do this, we would not be able to operate the highly successful course that we do. Hopefully this advice will help interested students to know if our course is right for them, and will help us get to the point where every single student absolutely smashes our PreCourse.</p><p><a href="http://blog.makersacademy.com/how-we-find-the-best/www.makersacademy.com">Makers Academy</a> is a 12 week intensive bootcamp — it’s what we do best. Our daily lives include a lot more than code. You can find yourself doing yoga, meditating, networking, relaxing and making lifelong friends in a friendly, inclusive environment while learning all the skills needed to build an awesome new career. However, in order to access this, we ask that all candidates acknowledge the points above — it’ll give you a solid foundation for your life ahead as a developer.</p><p><em>Originally published at </em><a href="http://blog.makersacademy.com/how-we-find-the-best/"><em>blog.makersacademy.com</em></a><em> on October 8, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61b59261fa76" width="1" height="1" alt=""><hr><p><a href="https://medium.com/makers-academy/passing-the-makers-academy-precourse-61b59261fa76">Passing the Makers Academy PreCourse</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>