<?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[Techspiration + Ideas + Making It Happen - Medium]]></title>
        <description><![CDATA[Drinking from the firehose, and thriving. - Medium]]></description>
        <link>https://medium.com/techspiration-ideas-making-it-happen?source=rss----f9f250c74f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Techspiration + Ideas + Making It Happen - Medium</title>
            <link>https://medium.com/techspiration-ideas-making-it-happen?source=rss----f9f250c74f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:21:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/techspiration-ideas-making-it-happen" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I was rejected by Harvard, Stanford, Facebook and Google — my notes on failure]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/i-was-rejected-by-harvard-stanford-facebook-and-google-my-notes-on-failure-5e84a2a12f2c?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/5e84a2a12f2c</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[rejection]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Teodor Cataniciu]]></dc:creator>
            <pubDate>Tue, 30 May 2017 18:13:13 GMT</pubDate>
            <atom:updated>2017-05-30T18:13:12.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQqCved70zjHUbUYVmdqKw.png" /></figure><p>It’s been a few days now since our graduation at Restart Network, where people from war-torn countries work to start a new life through a career in technology. After each graduation I take a few days off to think about the good things that happened, and <strong>what can I learn from when I failed</strong>.</p><p>I am aware that my journey, through the lens of social media and public events, appears to be a constant stream of victories. I received heartfelt messages of support, heard about how I inspired others through my work, people share my TEDx talk, can read about my achievements in magazines and newspapers, and see my name in fancy lists such as Forbes Romania’s 30 Under 30 or the FD Best Entrepreneurs Under 35. I owe this to the incredible <strong>people around me</strong>.</p><p>And so, it would be a disservice to all the people who want to leave a dent in the world to leave the picture like that. Few people know that before creating Turing Society or Restart Network I wanted<strong> </strong>to help other people <strong>in their pursuit</strong> to make the world better, so I applied to both Facebook and Google for internships or entry level jobs — anything that would get me closer to working on something important. I got rejected every time. And the NOs follow to this day, both Harvard Business School and Stanford GSB sent me beautiful rejection letters wishing me the best on my path.</p><p>What I’m saying here is that winning and failing are just <strong>part of this game</strong>. You cannot have one without the other, taking risks will sometimes pay off and other times will hinder you. The most successful people on this planet have high failure rates. They stand successfully because, on average, we just need <strong>one strong YES</strong>, that will fade the hundreds of NOs in oblivion. We got to learn fast, and stand up a little wiser. What <strong>I’m most afraid of</strong> is in 80 years time to look back and wonder what if. The fear of not trying is greater than the fear of failing.</p><p>In our startup bubble, I hear a lot of people talking about celebrating failure. Always wondered what they mean… That we should smile when things break, that we should appreciate the learning opportunity in front of us, that failing is good? <strong>Failure hurts.</strong> We weren’t good enough, we did not work hard enough, we let ourselves and those around us down.</p><p>But here’s the secret.</p><p>In basketball, there are matches where the top player throws five times behind the three-point line and scores each time — people go crazy, perfect strikes. But matches are not won like that, if an average player shoots 50 times and maybe hits the hoop 20 times, the team ends up with a lot more points. <strong>Quality comes from quantity</strong>, to truly know what works we must be okay with failing to achieve our goals.</p><p>I must say this because we live in a world where every day we see on our screens, in our news, and social circles, people who celebrate their success and understandably omit their failures — I do it, too. But I realise that those of you out there who have something burning inside and want to use that flame to build something in the world that moves us all forward will be discouraged to try. Because people around you always seem to get that deal, speaking gig, news coverage, or award, that you were also working for, but missed.</p><p>Failure is a cold friend, keeps us humble, but fuels our next move. I feel good when I fail, how lucky must I be to have the privilege to try.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e84a2a12f2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/i-was-rejected-by-harvard-stanford-facebook-and-google-my-notes-on-failure-5e84a2a12f2c">I was rejected by Harvard, Stanford, Facebook and Google — my notes on failure</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I wrote and published my novel using only open source tools]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/how-i-wrote-and-published-my-novel-using-only-open-source-tools-5cdfbd7c00ca?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/5cdfbd7c00ca</guid>
            <category><![CDATA[kindle]]></category>
            <category><![CDATA[self-publishing]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Gabriel Gambetta]]></dc:creator>
            <pubDate>Thu, 18 Aug 2016 19:24:25 GMT</pubDate>
            <atom:updated>2016-08-18T19:24:25.527Z</atom:updated>
            <content:encoded><![CDATA[<h4>From Markdown to paperback and Kindle without proprietary software.</h4><p>I&#39;ve recently published my first novel <a href="https://www.amazon.com/dp/B00QPBYGFI"><strong>The Golden Legacy</strong></a> on Kindle and paperback through Amazon, achieving very professional results. Along the way, I created a process and a couple of tools based exclusively on open source software. Here’s my process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zzdPQ4u61Q5rS6m_nqafQ.jpeg" /></figure><h3>The manuscript</h3><p>The most important piece of content for publication is the <em>manuscript</em> (i.e. the text of the novel). I originally started writing this in a Google Doc, but it soon became apparent that Offline Mode wasn&#39;t as robust as I expected (this was critical for me, since <a href="https://medium.com/@gabrielgambetta/how-i-wrote-my-first-novel-during-my-daily-commute-e1d02c9447b9">I wrote the whole novel during my daily commute</a>), and Docs had latency problems handling a really big document. So I wrote a quick script to export the text to <a href="https://en.wikipedia.org/wiki/Markdown">Markdown</a> and abandoned the Google Doc.</p><p>There are many editors for Markdown. For a brief period of time, I used <a href="http://texts.io/">Texts</a> on Mac, but in the end I went the old-school way with <a href="http://www.vim.org/about.php">vim</a> (gvim on Linux and mvim on Mac).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ne8aeFiS6CQE-b_oJCpiKg.jpeg" /><figcaption>Yes, that’s gvim running on Fedora 20.</figcaption></figure><p>I didn&#39;t use much formatting. I used # for chapter headers, ## for chapter subtitles (e.g. dates and locations), and indented text for preformatted monospaced sections (the novel includes some encrypted text the protagonists attempt to decode).</p><h3>Kindle and epub</h3><p>I created a separate Markdown file for the <em>front matter</em> of the book, that is, all the text that comes before the text of the novel itself (I consider the Prologue and the Epilogue integral parts of the story). The front matter includes the title page, colophon, and acknowledgements. I also had the book cover as a separate file.</p><p>The magical tool that converts this into an epub file is the fantastic <a href="http://pandoc.org/">pandoc</a>. Besides the text (both front matter and manuscript), it can also take the filename of a cover image, a metadata file, and a stylesheet file.</p><p>The metadata file is an XML file with <a href="http://dublincore.org/documents/dces/">Dublin Core</a> tags such as title, author, and copyright line. Although this information is already included in the front matter, this is metadata for the epub file itself, and not part of the text visible to the reader.</p><p>The stylesheet file is a CSS file that lets you customise the appearance of the book. In my case, I just modified the Header tags to be centered, but used the defaults otherwise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*12pKEzXbmypmFCjaXeGlaQ.jpeg" /><figcaption><strong>The Golden Legacy</strong> on a Kindle.</figcaption></figure><p>Pandoc produces a very good epub file with these inputs, but I wanted further customisation. Since an epub file is a zip file with some HTML and metadata, I wrote a quick Python script that unzips the file, moves a few things around in the content.opf file, and reassembles the epub.</p><p>This epub file is directly readable by Apple iBooks and Google Play Books. For Kindle, you create the same epub file but without the cover, and then upload the epub file and the cover image separately during the setup process in the <a href="https://kdp.amazon.com/">Kindle Direct Publishing</a> site.</p><h3>Paperback</h3><p>Creating the ebook files is straightforward. Paperback is substantially more complex, since you have full control over the formatting of the book.</p><p>I went with <a href="https://www.createspace.com/">CreateSpace</a>, which does print on demand, and is fully integrated with Amazon. For CreateSpace you need a cover file and an interior file.</p><p>The cover file is a high-resolution PDF file with the back cover, the spine, and the front cover, with a blank space where CreateSpace inserts the ISBN. There are templates and very exact guidelines on their website; just ask the cover designer to follow them.</p><p>The interesting part is the interior file. This is another PDF file which will be printed <em>exactly</em> as it looks, so it’s extremely important to get it right.</p><p>To create this file, I used Pandoc again, this time to convert the Markdown files to ODT (OpenDocument Text), which can be read by <a href="https://www.libreoffice.org/">LibreOffice</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bR5ADXdYso_OKGlk7a-UCA.jpeg" /><figcaption>Customising page styles in LibreOffice.</figcaption></figure><p>The key step is to provide a reference ODT file to Pandoc. Pandoc takes the styles, headers, and footers from this document and applies them to the output. So here is where you define the page headers and footers, the way chapter headings and subheadings look, and so on.</p><p>LibreOffice has many page formatting options that are non-obvious but incredibly important. For example, I wanted the first page of each chapter to be a right page, and to exclude the page header. I defined my chapter heading style to have a “page break before” and set a page style of “first page” (which is a right page without a header), which is followed by “right page,” which is followed by “left page,” which goes back to “right page.”</p><p>Getting the spacing right for the title page was tricky as well. I wanted it vertically centered, which doesn’t exist as a concept in Markdown, so I just inserted empty lines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T4BQzL-thqvXmaxQL-6rXg.jpeg" /><figcaption>The subtle details in formatting make a huge difference in how “professional” the book feels.</figcaption></figure><p>Once you’re satisfied with the result, you can print the document to PDF and upload it to CreateSpace.</p><h3>The results</h3><p>I couldn&#39;t be happier with the finished book — it looks fantastic! Give CreateSpace correctly formatted PDF files, and they will give you an absolutely professional-looking book. And holding your actual, tangible, physical book in your hands is hard to describe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*kQfsbqaLSukANX7LeN4d8Q.jpeg" /></figure><p><strong>The Golden Legacy</strong> is available on <a href="https://www.amazon.com/dp/B00QPBYGFI">Kindle</a> and in <a href="https://www.amazon.com/dp/1505522439">paperback on Amazon</a>. If you want to read it but not buy it, <a href="/service/mailto:gabriel.gambetta@gmail.com">contact me</a> and I’ll be happy to get you a copy. This is my first novel, so feedback is extremely welcome!</p><p><a href="https://medium.com/@gabrielgambetta/how-i-wrote-my-first-novel-during-my-daily-commute-e1d02c9447b9">How I wrote my first novel during my daily commute</a></p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cdfbd7c00ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/how-i-wrote-and-published-my-novel-using-only-open-source-tools-5cdfbd7c00ca">How I wrote and published my novel using only open source tools</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technophobe Turned Coder]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/technophobe-turned-coder-48ced37dd0e4?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/48ced37dd0e4</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[freecodecamp]]></category>
            <dc:creator><![CDATA[Who Cares]]></dc:creator>
            <pubDate>Tue, 16 Aug 2016 14:57:49 GMT</pubDate>
            <atom:updated>2018-04-18T20:44:48.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OZPvHCYM8tmDZ1inTAF86A.jpeg" /></figure><p>If you are new to coding, or even considering it, you may be able to relate to my experience. Happy reading.</p><p>For whatever reason, I’ve decided to subject myself to facing certain fears in life. In this case, overcoming my anxiety-driven chest-compressing crippling vexation of technology. And what better way to do that than to learn a little coding.</p><p>Up until this last year, had you asked me to code something (or just troubleshoot an issue with your computer), I would have likely started foaming at the mouth, convulsing, and breaking out in cd-sized hives before giving it a go.</p><p>To say computers are out of my wheelhouse is an understatement.</p><h4>Totally Green</h4><p>Since I’m notably north of 30, it’s a little embarrassing to admit I’m not <em>in the know</em> on a lot of things. I don’t play Pokemon Go, my daily makeup routine isn’t Insta-glam, and while I use a computer daily — up until a few years ago I knew very little about the inner workings in general.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*MecjIYNgBIlhCv_CcYirOQ.jpeg" /><figcaption>The guts</figcaption></figure><p>How did I get by in this tech-obsessed world you may wonder?</p><p>While I had been computer literate enough to function day-to-day, I had been more the type to date or befriend my tech support than to <em>be </em>my own tech support. But I realized it was high time I learned.</p><p>So began my journey of Googling every little problem I encountered and overcoming a couple BSoD episodes solo. Thanks randomly buggy Windows update!</p><p>Then a couple of months ago, I accepted that I was also going to have to make a change in my skill-set. While I’ve been in research and data management for over a decade now, I hadn’t really embraced the full potential of the tools available to me.</p><p>Again, I’d be on the slow track with tech because of the sheer intimidation factor. That, and I’m one of those people who invariably has a tech problem, seeks out assistance, and as soon as tech support is within eye-line of my computer, it suddenly begins to function as it is supposed to.</p><p>I think my computer gets some perverse pleasure in toying with me.</p><p>While hesitant, I too had fallen prey to the siren song of the everyone should learn to code initiative. Seeing the betterment in automating a few mundane tasks, I started to do a little research.</p><p>There are so many articles, massive online open courses (MOOCs), YouTube tutorials, and books.</p><p>I was literally overwhelmed with <em>where to start</em>? Initially, I did the thing you are <strong>not</strong> supposed to do and spread myself extremely thin. I reviewed vast amounts of ecourseware (MIT, EdX, Udemy, Code Academy, Code School, etc…) and books, all touting to have me tech-zen in 15-minutes or within a day tops, depending on the topic.</p><p>Sidebar — While some of these books make excellent reference material, unless you have some preexisting knowledge of things like HTML, CSS, JS, C, PHP, etc., they are not going to have you coding your own website by the hour’s end.</p><h4>You have to crawl before you can walk. And sometimes you are going to trip and land on your face when you do.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UP6xlc1DKjrW6E7pfQKtFw.jpeg" /></figure><p>Unsure of my best first step, and figuring I needed to get this ship into the water already, I signed up for a computer science course on EdX.</p><p>This one caught my eye primarily because it was free (as many MOOCs are) and the course description detailed the following:</p><blockquote>“This course covers concepts of abstraction, algorithms, data structures, encapsulation, resource management, security, software engineering, and web development along with the familiarity in a number of languages, including C, PHP, and JavaScript plus SQL, CSS, and HTML.<em>”</em></blockquote><p>I was primarily drawn in by SQL as it applied to my current job; everything else was Greek to me. After I invested about a month of my time, having had an opportunity to pull and review the materials necessary for the course, I realized the bulk of the computer programming course leaned <strong>heavily </strong>in C, the supposed Latin of coding languages.</p><p>I wasn’t particularly interested in using C but as a newbie I just assumed it was the natural progression of a programmer. They had all cut their teeth on C programming and I would be no different. In order to be a good programmer/developer I was going to have to learn it.</p><p>Before you message me, telling me what a silly notion that was, remember I was super-green and phobic. I’d also neglected to make my co-workers (most of them programmers) aware of my educational pursuits primarily because I dislike the feeling of ignorance. Backwards, right? These were the key people who could have steered me in the right direction, yet out of nothing more than silly pride I wanted to figure it all out myself.</p><p>I’ve been <em>adulting </em>it for a long time now and assumed I could handle things solo.</p><h4>Not Everyone is a Coding-Savant</h4><p>While I understood the general principles and structure, and managed to create and code a few things in it, C was possibly one of the worst languages for me to use.</p><p>There were several nights of rants and tears, but I was determined to finish what I started, no matter how much I vehemently hated the class.</p><p><em>Disclaimer: in retrospect, the class itself wasn’t bad, it was just a bad fit for me. Everyone learns differently, and while the resources were good, I felt I needed a little more hand-holding and guidance than what was being provided.</em></p><p>While struggling through my primary lessons, I experimented with various other languages. Basically, I was throwing darts at anything that looked remotely appealing — spreading myself even thinner and frustrating myself further.</p><p>I was growing increasingly consumed with self-doubt and was very discouraged. To make matters worse, the group forums for the class were full of people boasting about how they would breeze through their challenges with the same effort it takes to compose a grocery list whereas I would spend hours, in some cases days, crafting the same algorithm. If you are that lucky tech-savant, in the future, please don’t do that thing where you say something like, “Wow, it took you 2 days to figure it out [what took me 20 minutes] … ”. You come off sounding like a smug tool.</p><p>I digress, something had to change in my tech journey, else this ship was going to crash and burn.</p><p>Having my ego bruised around the edges, I nearly abandoned my coding experiment altogether. I was working full-time and when I could get through a lesson, which alone took hours to read and watch everything before even starting the assignment, I would struggle trying to piece it together. I’m sure others can relate when I say I started to wonder if I was just too stupid to learn code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*fVQ9FCnChKcIEZZ0pl-G4w.jpeg" /><figcaption>My first week studying code via EdX</figcaption></figure><p>One random day, a co-worker (programmer) noticed I was learning about do-while loops and clued into the fact I was studying coding. Brilliant deduced, given the picture from my FB (above).</p><p>He recommended <a href="https://www.freecodecamp.com/">Free Code Camp</a>, having used it himself to round out his skill set with front end development. My programmer friend was looking to become more <a href="https://en.wikipedia.org/wiki/T-shaped_skills">T-shaped</a> at work. Note: Up to this point I’d still been a little fuzzy on what front end, middle, back end development and full stack was. All I saw was a blur of coding languages and assumed programmers had to know them all.</p><p>In the end, I realized my biggest hurdle was simply finding a good start-point. I had desperately needed a well-laid-out lesson plan that outlined what I should study in hopes of being successful in whatever area of development I ultimately chose. Instead, I just tried to study too many things at once without really knowing what they were about.</p><p>Free Code Camp was an excellent start-point. Their course modules have provided wonderful tools to <strong>build </strong>from. Thus far, the most valuable lesson I have learned from this experience is to research, research, research. While FCC points you in the right direction, it is still up to you to take the steps necessary to learn how to go about furthering your coding knowledge. While the EdX course would have required the same, FCC presented the material a little differently and in a more cohesive laid-out plan that worked — at least for me.</p><h4>When you dance with the devil, the devil doesn’t change, the devil changes you.</h4><p>Now I’m not saying coding is the devil, but to someone new and a hint phobic, it might as well be. I found the analogy to be true, just the same. Once I started dancing (<em>attempting to code my first few projects</em>) and having several “Aha” moments, I immediately wanted to learn more, do more, create more. Hence why I likely went a little too far too fast, and nearly burnt out. Now I focus on building good foundations with my languages before moving along to the next one; though it is so tempting when you hear about things like Sass, bourbon, and bitters — oh my.</p><p>Often times, when I solve something I’ve been attempting to un-puzzle for a few hours or days, I burst out in diabolical laughter, or I practically leap from my chair to do a little dance, or I announce it to everyone in the house and force them to “<em>Come see what I did!</em>” like I’m a kid who just finished my masterpiece of macaroni and glue.</p><h4>The perfectionist in me loves and hates it …</h4><p>There are moments I feel like a complete moron, a poser, and impostor. Yeah, it’s defeatist, but it’s true. And we all suck at something until we learn how to do it, right? But we all want to be like Neo and have the knowledge jacked into our brains as quickly as possible, not stumble along for months or years laboring to hone our skill with a handful of languages.</p><p>Learning to code will make you humble, at least for some of us. The problem-solving is not what I dislike. It’s the embarrassment I feel because I assume others are “<em>getting it</em>” faster than I am. It is having to acquiesce and utter the phrase, “I don’t know what that is” or “I’ll have to do some research and figure out how that works.”</p><h3>Megan Charles on Twitter</h3><p>23 #100DaysOfCode: Feel more like a researcher than a coder most days. Troubleshooting conflicts in code.pic.twitter.com/2oNSvvaVp2</p><p>I’m still very green. The perfectionist in me wants to code and code well — code clean, beautiful lines, and know how the ballet of pre-processors and libraries work. But I get that I have to crawl before I can walk, and I labor each day at whenever I can fit in.</p><p>There is just so much to learn (so many little tricks, so many tutorials, so may resources). At times I doubt my ability to absorb it all. One moment when I think I’ve got something solved, I realize my way is sloppy and might look like crap when I go to view it on different browsers and/or devices. And yet even I have gotten offers for website work — primarily from acquaintances who want a few static pages, or help fixing what they have. I take on these tasks because it is an excellent way to problem solve and learn. Even now I can recognize where I went awry on earlier projects and have since gone back to “fix” or improve them.</p><p>Alongside the occasional project that comes my way, I am taking three different developer-related courses on Udemy and I’m still plugging away at my FCC coursework. I’m taking three because each one offers a little something different (filling in the gaps the other might fail to cover), each instructor teaches with their own spin, and each offer a host of different resources (like free web hosting for a year or a few bootstrap templates).</p><p>My FCC is on pause at the moment though as I’m building (donating) a site to a local group that is due at the end of this month, and I still have my day job. But once it’s done, I’ll be picking up where I left off.</p><p>Ideally, I’m hoping to finish out my Front End Web development certification with FCC by the end of this year, or before next summer. I would have hoped for earlier, but I am an adult with adult responsibilities, a full-time job, and a website to build here and there.</p><p>I do have to thank the following for my progress: Quincy Larson (FCC, a given), seeing as he is the one who created the platform that got me going. <a href="https://www.youtube.com/user/DevTipsForDesigners/featured">DevTip’s </a>Travis Neilson, <a href="https://www.youtube.com/user/QuentinWatt">Quentin Watt</a>, and The <a href="https://www.youtube.com/channel/UCW5YeuERMmlnqo4oq8vwUpg">Net Ninja</a>. These others are just a few of the people I follow on YouTube who have awesome, informative tutorials. Travis (who works for Google now) + his friend Los are especially entertaining and Quentin and the Ninja both have dreamy accents.</p><p>Also, I’d like to thank the friend who recommended FCC to me (Chris Morgan). Had he not, I likely would have given up.</p><p>For the other unsure newbs out there, who like me have already been in other careers for a while, I recommend listening to the <a href="http://www.codenewbie.org/podcast">CodeNewbie podcast</a>. The podcast is composed primarily of interviews with people who decided they wanted to go from one field of study or occupation to coding, and they offer advice and resources as well. In their archive, there is an interview with Quincy where he details how he went about creating FCC.</p><p>Between the two communities (FCC and CN), I found people akin to myself who had experienced the same doubt and struggle.</p><p>Therefore, as a productive member of the coding world, I’m going to impart some of the best (unsolicited) advice I can give:</p><ol><li>Get over your ego and be prepared to ask a lot of questions.</li><li>Research.</li><li>Outline what skills you’d like to learn or what kind of work you think you’d like to do. For example, programming in C is different than doing website design. There are oodles of programming languages, and the types of programming/developing jobs can vary by skill.</li><li>Find related podcasts and YouTube videos. They provide additional resources that can be extremely helpful.</li><li>Join coding forums and blog groups.</li><li>Try meeting up with a group in your area (hang with people who code, even if you are not on “their” skill level). If this intimidates you, please reference back to item #1 on this list.</li><li>Try a few freebie online courses to get your feet wet.</li><li>Don’t get too hung up with your text/code editor starting off. Pick an editor— whether it’s brackets, Atom, Notepad++(or play with an online one like Codepen)— and just get to work. Over time you’ll find what works best for you — who has what plugins, etc., and there are dozens of helpful overviews of these editors on YouTube if you need help deciding.</li><li>Many of the forums you join will be composed of your classmates so congratulate your fellow coders on a job well done, even if it seems it was so much easier for them than it was for you. You have no idea what their background is or what challenges they overcame.</li><li>Further expounding on #9— Do not compare yourself or your work to other programmers/developers. Sure, look at other code and learn from it, open-source code is a wonderful resource, but don’t debase yourself because you didn’t just magically know how they went about building something in the first place. They had to learn it just as you did.</li><li>Consider a longer-term course of study either with a bootcamp or other MOOCs to fill in some of the gaps in your learning. Trust me, there are thousands of classes out there marketed with various price points. You will start to feel like a professional e-class taker before you know it. But be sure to read the reviews or touch base with anyone who might have taken the course before paying for something, as not all bootcamps or classes are the same.</li><li>Also consider learning about what <a href="https://en.wikipedia.org/wiki/GitHub">GitHub</a> is and how to use it. I’m still trying to figure that one out.</li><li>Try taking challenges like #30DaysofCode or #100DaysofCode. It forces you to be accountable and code daily. There are also other sites that offer daily coding challenges, many similar to the lessons on FCC.</li><li>Treat yourself for the little victories — you earned it.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HU6xXCAPlujvKEMJnFR7CQ.jpeg" /></figure><h4>I do not blindly advocate that everyone learn to code.</h4><p>Afterthought Disclaimer: I’d be remiss if I didn’t note the following. I do not blindly advocate that everyone learn to code. It is definitely an acquired taste, one I’m still trying to assess if I am suitable for.</p><p>And for those people who say it is <em>easy</em>, sure, maybe it is/was for you. I’ve seen you [random tech-genius person] fly through lessons and humble-brag with compensatory narcissistic false modesty about your seemingly superhuman understanding and skill, blazing through a six-month course in a quarter of the time. However, you fail to note that you also have a preexisting background in computers/programming, are a math savant, are currently not working, you have no responsibilities in need of your attention, no kids, and someone else is paying all of your bills right now.</p><p>You [tech-genius person] set the bar rather high and make those of us who struggle with it in the beginning feel lesser, fueling our self-doubt because we assume we should be picking it up faster than we are when you say coding is <em>easy</em>.</p><p>The point of my diatribe here isn’t to evangelize coding like it’s the next generation of required literacy, nor am I trying to bash anyone who brags about their accomplishments. I just want those people who seem to get it with a Neo-like ability to have some perspective that for many of us it’s not that easy.</p><p>In closing, I simply wanted to share my experience so that others, who may be reluctant to learn something new, will consider giving it a chance. And I hope something I’ve said here is beneficial.</p><p>Best of luck!</p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48ced37dd0e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/technophobe-turned-coder-48ced37dd0e4">Technophobe Turned Coder</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Things I Wish I Knew When I Started Charging Money for Programming]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/10-things-i-wish-i-knew-when-i-started-charging-money-for-programming-ac463041d673?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/ac463041d673</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Reuven Karasik]]></dc:creator>
            <pubDate>Tue, 26 Jul 2016 21:17:25 GMT</pubDate>
            <atom:updated>2016-07-26T21:17:24.769Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvMMN_BQ0IZU2JWjzHfU7g.jpeg" /></figure><p>Learn from my mistakes, rather than yours…</p><p>I’m Reuven Karasik, 15-year-old web developer. I’ve been programming since I was 7, but I only started charging money for programming in the spring of 2013.</p><p>So I started “having clients” (charging money for programming) around 2 years ago. Today, after many clients, many mistakes, and many wrong decisions made over those couple of years, I just wish I could go back in time and tell myself a few things that could’ve made my life easier. Since I can’t do that, the best I can do is share it with you, in hopes that you will do better than me with your first clients.</p><h3>Clients</h3><p>These rules, of course, do not apply to <strong>all</strong> clients. But consider them when dealing with an average client.</p><h4>1. The client doesn’t know what‘s good for him.</h4><p>Clients often have no idea what is recommended and what they should avoid. It applies to design, to user experience, and simply to decisions that should be made. If a client asks you to put red text with a yellow background on top of a 50px * 50px picture stretched to be full-width, it’s best not to listen to them. Stand up for what would make a good product and for what would look good in your portfolio.</p><h4>2. The client can’t evaluate work properly.</h4><p>Clients can say sentences like, “Yes, look, if you don’t mind, and if it’s not too much trouble, and of course only if it doesn’t take more than a few hours, would you please increase the font size by 1px?” on one hand, but, “Oh– and it’s probably going to take a few minutes– but I need you to redesign the entire website and add a comment system to the app. Shouldn’t be too hard, right?” on the other. Clients don’t know what’s easy for us and what’s hard.</p><h4>3. The client sometimes needs to know how much things cost.</h4><p>Some people think a complicated social network should cost $100, and some think a 3-paged website should cost $3,000. Our job is to be fair with them, but to make sure we get paid what we deserve for the work we’ve done. Be careful when you give a price tag to a potential client, they might hang on to it later. (More on payments later.)</p><h3>Getting (to) work!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Lvpct1eq9cjBgFWI2wJ3g.jpeg" /></figure><h3>4. Choose your projects carefully.</h3><p>One really important thing to know when you get offered a project is when to accept it and when not to. If you don’t have time for that project, or you feel like you wouldn’t want to work with the person, or even if the project just doesn’t seem like something you’d like to do, say no. I can’t stress this enough.</p><h4>5. Say no.</h4><p>Learn how to say <strong>no</strong>. Not “yeah, maybe, but...” — just <strong>no</strong>. Whether it’s a project you don’t want, a deadline you don’t think you’ll reach, or anything that isn’t going to happen, the client should know about it as soon as possible. Countless times, I’ve told clients I’ll do something even though I realized there’s probably no way I can make it within the timeframe, and each time, I regretted it.</p><blockquote>A great way to say no because of time limits is, “I wish I could.” It compliments them.</blockquote><h4>6. Payment &amp; work evaluation.</h4><p>Some people may disagree with me, but I believe — from my experience — that the best way to get paid for a project is per hour (unless there’s a <strong>very specific</strong> specification). Clients <em>always</em> add things to the list after the work begins, and if you set up a fixed price, you might have to “work for free” eventually. Set up a price per hour and keep a record of your time. I think the client would also feel that this way is fairer.</p><h3>Learning</h3><h4>7. Don’t let your clients hold you back.</h4><p>Two years ago, I wanted to learn so many things. I was a 13-year-old guy with great plans for the future and a clear vision of where he wanted to be in two years. Today, I’m 15, and although I’m very happy with all the things I do and I’m satisfied with where I am right now, I have to say that I didn’t learn even half of the things I wanted to learn. My projects held me back and didn’t let me learn new technologies (unlike when I was programming for myself). Keep time for learning.</p><blockquote>When you stop learning, you start dying.</blockquote><h4>8. Use cool technologies.</h4><p>I was once offered a project, and I had to choose between using jQuery (which I know well) and Angular.js (which I was only a bit familiar with). I didn’t want to waste my client’s time, so I chose jQuery. Very good, huh? A month later, I had to face the same choice with a different project. That loop exists as long as you keep choosing what you already know. Once I chose Angular, a few things happened: A, I learned angular (which is good for me), and B, the web app was much faster (which is good for the client). You can also add C, next time I won’t have to learn it again (which is good for future clients). Everybody wins.</p><h4>9. Don’t be lazy.</h4><p>Like the previous tip, this one requires not making the easier choice. When you work in a company where you know others will read your code, you try (I hope) to make your code more efficient and readable. But when working on a small project for a client, you have the temptation to just finish with it as quickly as possible, and not come back to the project ever again. Many freelancers do that, unfortunately, and I’ve seen horrible pieces of code written by developers who were simply <strong>lazy</strong>. But what you don’t know is that at some point, the client will want to change something, and another developer will have to read your code (or even worse — you!). At that point, you will either seem unprofessional, or (if you’re the lucky guy) you’ll want to erase everything and start from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HdW7WAN6GyqZh45mOXQdDQ.jpeg" /></figure><h3>One for the road!</h3><h2>10. Keep growing.</h2><p>Don’t get stuck in one place. Always keep growing and learning. Don’t stop being interested in what you do. Always challenge yourself.</p><blockquote>return true;</blockquote><p><strong><em>Please </em></strong>let me know what you think about the tips above! I would love to get some feedback about the article.</p><h4>This first appeared on my blog, <a href="http://reuven.karasik.org/blog">Geek It</a>: <a href="http://reuven.karasik.org/blog/2015/07/10-things-i-wish-i-knew-when-i-started-charging-money-for-programminglearn-from-my-mistakes-rather-than-yours/">10 things I wish I knew when I started charging money for programming.</a></h4><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac463041d673" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/10-things-i-wish-i-knew-when-i-started-charging-money-for-programming-ac463041d673">10 Things I Wish I Knew When I Started Charging Money for Programming</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Man in the Arena]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/the-man-in-the-arena-5a690dc63a5b?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/5a690dc63a5b</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Teodor Cataniciu]]></dc:creator>
            <pubDate>Tue, 26 Jul 2016 15:07:33 GMT</pubDate>
            <atom:updated>2016-07-26T15:07:33.172Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A critical view on the powerful trends driving change in the world today.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LCPLe2CB9UV1hxBE5GUnuQ.jpeg" /></figure><h4>A Pale Blue Dot</h4><p>In the past 100 years, we have achieved previously unimaginable milestones as a species. As <a href="http://www.ted.com/talks/peter_diamandis_abundance_is_our_future">Peter Diamandis</a> observed, the cost of food, communication, electricity, transport has decreased 10 to 1000 times. The average human lifespan more than doubled, the average income per capita, adjusted for inflation, tripled. Contrary to what news networks want you to believe, we are now living in the most peaceful times in our history.</p><h4>The Singularity</h4><p>Progress today is not linear. Moore’s Law, named after <a href="https://en.wikipedia.org/wiki/Gordon_Moore">Gordon Moore</a>, is the most popular example of exponential growth. Moore observed, in 1965, that the number of transistors on a circuit board, or the speed as counted in operations per second, doubles every 12 to 18 months for the same dollar amount. From a cost perspective, a $100 processor in a year should be twice as powerful as a $100 processor today.</p><p><a href="https://en.wikipedia.org/wiki/Ray_Kurzweil">Ray Kurzweil</a> takes this trend a step further. He argues that Moore’s Law can be generalized. Not only is the performance of computer processors described by exponential growth, but any information technology. His examples include DNA Sequencing, Internet Speed and Adoption Rates, or the Size of Computers and Integrated Circuits. In one of his <a href="https://en.wikipedia.org/wiki/The_Singularity_Is_Near">books,</a> he describes the Singularity: a point in time where human life as we know it would be impossible without the use of computers, where our species is fully dependent on intelligent computers to exist and function. He predicted, based on these growth trends, that this point will be reached within our lifetimes, in 2045.</p><p><a href="https://en.wikipedia.org/wiki/Peter_Thiel">Peter Thiel</a> is one of the most influential critics of this tech-optimistic view. He argues Moore’s Law will come to a stop around 2020 due to manufacturing costs: shrinking the size of transistors will soon cease to be economically feasible. In his book, Zero to One, he argues that we are too focused on our phone screens to realize that besides advancements in IT, not much has changed since the 1960s. We travel at the same speed, powered by internal combustion, and live in homes with appliances not much different from those of the last century. In his words: <em>We wanted flying cars, instead we got 140 characters.</em> Future IT advancements are undeniable, yet they will not replace the human element, but enhance it.</p><h4>Leverage Your Moonshot</h4><p><em>Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it’s the only thing that ever has. </em>A quote attributed to Margaret Mead, is now more relevant than ever. The debate between the tech-optimists and tech-pessimists is quite entertaining, but an undeniable point both parties will agree on is that this is the best time in our history to shape the world. Let me explain.</p><p>In 2016, 46% of the world population has access to Internet. By 2020 we expect more than a billion people to join this global conversation — for many, the only source of education, medical information, and job opportunities. This is huge. We are one click away from billions of people. This was unthinkable only decades ago. No matter who you are or where you live, I believe you can truly change the world because of this.</p><p>Leveraging exponential technologies empowers people of all backgrounds to impact their community and world. From a college kid in a dorm room to a farmer in some remote region of the world, we should all have access to the same information and resources to learn and create. A century ago, it was the case that you had to be a king or a head of state to even dream of reaching so many people. Today, the world is different. Students in dorm rooms can <a href="http://facebook.com/">build great things</a>, and so can you.</p><h4>Be the Man in the Arena</h4><p>The title of this article is inspired by Theodore Roosevelt in his speech at the Sorbonne in 1910. I left it for you to enjoy or critique at the end of this piece. Remember, it takes little courage to watch from the side, and a great deal to enter the arena and fight for something. It seems to me that the risk of not trying is greater than the risk of failing.</p><p>There are a great amount of people, including the undersigned, who seek to push this message that you should not stop at reading about technology, but aim to leverage it. Ideally, for a big goal. Don’t listen to us. It is up to you to decide if the best place for you is in the arena. I just want you to know that no matter what your goal is, right now, you have the best odds– in history I may add– to turn it true.</p><p><em>Excerpt from the speech “Citizenship In A Republic” delivered at the Sorbonne, in Paris, France on 23 April, 1910:</em></p><blockquote>It is not the critic who counts; not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; who strives valiantly; who errs, who comes short again and again, because there is no effort without error and shortcoming; but who does actually strive to do the deeds; who knows great enthusiasms, the great devotions; who spends himself in a worthy cause; who at the best knows in the end the triumph of high achievement, and who at the worst, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who neither know victory nor defeat.</blockquote><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a690dc63a5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/the-man-in-the-arena-5a690dc63a5b">The Man in the Arena</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My journey into the world of programming]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/my-journey-into-the-world-of-programming-fbc01e725d8d?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/fbc01e725d8d</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Kosy Anyanwu]]></dc:creator>
            <pubDate>Fri, 22 Jul 2016 15:27:34 GMT</pubDate>
            <atom:updated>2023-01-26T18:57:09.031Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of us go through school learning and amassing a variety of information with no idea of the real-life applications. I fit this mould.</p><p>After my degree in Computer Science, I realised I was not competent enough to face the ICT world. I registered for a Cisco Certified Network Associate (CCNA) programme just to try my hands at networking, and got interested in Cyber Security. I started applying for a master’s degree scholarship to study either Computer Forensics or Network Security. While going through the requirements for Computer Forensics on a UK university website, something caught my attention — “you will learn a scripting language so that you can develop your own forensic tools.” That was when I realised I needed to learn a bit of programming; something I had tried so hard to avoid while I was in school. Programming was the one part of Computer Science that did not appeal to me, so much so that I refused to accept a programming final year project. I insisted I was going to do an animation project instead, not knowing that I was going to end up in a programming field.</p><p>I tried learning Python programming on <a href="http://www.coursera.org/">Coursera</a>, but could not follow through as I needed to travel for various scholarship exams. Back in school, I had tried learning Java, C++, and Visual Basic.NET; all to no avail.</p><p>A friend of mine randomly sent me a link to some new company called <a href="http://www.andela.com/">Andela</a> that was hiring people to train and pay them to be software developers. I had given up on applying for scholarships as each one I applied to sent me a rejection mail. Besides, I did not want to be a Software Developer. I just wanted to be a Cyber Security expert. My friend encouraged me to give it a shot, and I did. Again, I got rejected. “No big deal,” I thought. A few months later, Andela sent me a mail for an all-female recruitment. I hesitated initially, then applied again. I was called for an interview, and then a two-week bootcamp.</p><p>Bootcamp at Andela was challenging: I learnt Javascript, HTML, and CSS. It was tough for me, but the thought of becoming a Cyber Security expert in the future kept me going. After the bootcamp, I was invited into the fellowship.</p><p>On February 2nd, 2015, I started my journey officially into the world of programming as an Andela fellow. I started with Javascript, then moved to Python. Now I have fallen in love with <a href="https://en.wikipedia.org/wiki/DevOps">DevOps</a>, all these still with the dream of becoming a Cyber Security expert.</p><p>One thing I have learnt so far is that you never know your abilities till you try, and sometimes you cannot really try till you are given the opportunity to. When you are not given such an opportunity, you need to find a way to create one for yourself. I cannot say I did it all by myself, either. Being part of the Andela fellowship has helped a great deal. You can apply <a href="http://apply.andela.com/">here</a> if you also want to be part of the Andela community. Try to take chances and put yourself out there without giving up. Perseverance is key and keeping your mind open to changes as they come helps, too. Never ever say you cannot do something.</p><p>Thanks for reading.</p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbc01e725d8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/my-journey-into-the-world-of-programming-fbc01e725d8d">My journey into the world of programming</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Algebra of Programming]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/the-algebra-of-programming-e0bdbc59dc65?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0bdbc59dc65</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kevin Welcher]]></dc:creator>
            <pubDate>Mon, 18 Jul 2016 14:21:12 GMT</pubDate>
            <atom:updated>2016-07-18T14:21:11.666Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*e28quglsISfaTMbh4NNmQg.png" /></figure><p>Have you ever stopped and thought, “Man, laws are really great!” Nope? Imagine something super mundane. How about driving to the store and buying some bread. Boring right? Now, imagine doing that <em>without</em> laws. Driving would be madness. If you made it to the store, you would then have to convince the store to exchange bread for bits of paper. By having laws, it makes this seemingly boring task trivially easy without much thought</p><p>Am I mincing concepts, loosely interchanging laws, rules, and maxims? Yes… Just squint your eyes and bear with me. Why is this even worth thinking about? When our world has rules, we can trust those rules to hold true and spend our time doing other things. Laws even let us <em>bridge paradigms</em> such as languages and disciplines.</p><p>How can this benefit us in programming? To list a few things, laws can:</p><ul><li>Let us think at a higher level</li><li>Make refactoring trivial</li><li>Help improve the modularity of our code</li></ul><p>To show this, let’s start with another discipline, math.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/1*I2cpGNe0Kp57QylgNpRoww.png" /></figure><h3>Arithmetic Algebra</h3><p>Programming is more than just coding, it is about <em>solving problems</em>. In <a href="https://en.wikipedia.org/wiki/How_to_Solve_It">How to solve it</a>, Pólya shows us that we can add to our repertoire of problem solving solutions by linking problems together. In other words, we find patterns outside the realm of our current paradigm and apply them to our current situation.</p><p>So how can algebra help us? Let’s look into a few laws algebra has that are interesting.</p><pre><strong>Identity</strong>: These are properties that do not modify the equation.<br>- Addition: x + 0 = x<br>- Multiplication: x * 1 = x</pre><pre><strong>Associative</strong>: Within multiplication and addition we can group similar operations together. The following are equal.<br>- 1 + 2 + 3<br>- 1 + (2 + 3)<br>- (1 + 2) + 3</pre><pre><strong>Distributive</strong>: We can distribute and factor out operations. The following are equal.<br>- 2(x + y)<br>- 2x + 2y</pre><p>Why are these laws interesting? We can refactor equations within these operations with confidence that we are not actually <em>changing</em> anything. We can simplify equations just by applying laws.</p><pre>3(x + 4xy) + 3yx   : Our starting equation<br>3x + 12xy + 3yx    : Distributive<br>3x + (12xy + 3yx)  : Associative<br>3x + 15xy          : Addition<br>3x(1 + 5y)         : Reverse Distributive</pre><p>Scary? Not at all! We used our laws to simplify our equation. In fact, there are many, many ways we could have applied various laws to transform this equation. How cool is that? Take a moment to process this small feat. We have an equation which we have no idea what it models and are able to transform it with confidence. What if we could do this elsewhere…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/170/1*-VB-VRZalW_zEiFjc5lixw.png" /></figure><h3>Boolean Algebra</h3><p>Let’s move out of arithmetic into something we use more often, <a href="https://en.wikipedia.org/wiki/Boolean_algebra">Boolean algebra</a>. Instead of having numbers as our domain we have true and false, and instead of addition and multiplication we have AND (&amp;&amp;) as well as OR (||).</p><p>We use Boolean algebra <em>all the time</em>, whether it is writing if-statements or branching our code in other capacities. Just like we were able to refactor our equations in arithmetic algebra, we can do the same with Boolean algebra.</p><p>What laws are we going to use? The same laws as before!</p><pre><strong>Identity</strong>:<br>- A &amp;&amp; true == A<br>- B || false == B</pre><pre><strong>Associative</strong>: The following are equal.<br>- (A &amp;&amp; B) &amp;&amp; C<br>- A &amp;&amp; (B &amp;&amp; C)<br>- A &amp;&amp; B &amp;&amp; C</pre><pre><strong>Distributive</strong>: The following are equal.<br>- A &amp;&amp; (B || C)<br>- (A &amp;&amp; B) || (A &amp;&amp; C)</pre><p>Using these laws, let’s take an if-statement you might come across and simplify it.</p><pre>if(<br>    (isUser || isAdmin) &amp;&amp;<br>    hasPosts &amp;&amp;<br>    (isUser &amp;&amp; canMakePost) ||<br>    (isAdmin &amp;&amp; canMakePost)<br>)</pre><p>A bit gnarly right? I write this garbage daily — let’s try to clean it up. To simplify things, instead of names, we will use letters.</p><pre>A = isUser<br>B = isAdmin<br>C = hasPosts<br>D = canMakePost</pre><pre>(A || B) &amp;&amp; C &amp;&amp; (A &amp;&amp; D) || (B &amp;&amp; D)</pre><p>Let’s churn this alphabet soup!</p><pre>(A||B) &amp;&amp; C &amp;&amp; ((A&amp;&amp;D) || (B&amp;&amp;D)) // AND Associativity<br>(A||B) &amp;&amp; C &amp;&amp; (D &amp;&amp; (A||B))      // Factor out D Associativity<br>(A||B) &amp;&amp; C &amp;&amp; D &amp;&amp; (A||B)        // AND Associativity<br>(A||B) &amp;&amp; (A||B) &amp;&amp; C &amp;&amp; D        // AND Commutativity<br>(A||B) &amp;&amp; C &amp;&amp; D                  // Idempotent law (A &amp;&amp; A = A)</pre><p>We start off grouping expressions with the associative law. With elements grouped we can then more readily see how we can factor out and distribute variables. We continue shifting, grouping, and factoring expressions until we can’t go any further.</p><p>Plugging back in our variable names we now have:</p><pre>(isUser || isAdmin) &amp;&amp; hasPosts &amp;&amp; canMakePosts</pre><p>Much easier to read! Was this process drawn out? Yes. Did we need to follow every step? No. We do most of these things intuitively. The fact that it <em>can</em> be done without much thought is an indication to the power of these laws. They let us trivially refactor expressions and know that those expressions will still work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/198/1*4ym6KSdsx4rrx1Ujpq6Uyg.png" /></figure><h3>Functional Algebra</h3><p>How we can use these laws in functional programming? Just how we described the domain for Boolean algebra (true, false) and operations (&amp;&amp;, ||), we will do the same here. Our domain is pure functions and functors and our operations will be map and compose.</p><p>Just a heads up, this section assumes familiarity with <a href="https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch4.html">currying</a>, <a href="https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch5.html">composition</a>, and <a href="https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch8.html">functors</a>. <em>Don’t get discouraged if you have not heard of these things!</em> Just like with the prior two examples, we are focusing more on the laws than the code itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/162/1*NhQI2c_ZrcD-kYidozCLKA.png" /></figure><h4>Compose</h4><p>First, a refresher on compose. Function composition is simply stringing functions together. We feed the result of one function to the input of another, starting from the right and flowing to the left.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09e1231acf33090bd8f95ed948915b3b/href">https://medium.com/media/09e1231acf33090bd8f95ed948915b3b/href</a></iframe><p>Want to know something really cool about composition? Functions in composition are associative!</p><pre><strong>Associative</strong>: The following are equal.<br>- compose(a, b, c)<br>- compose(compose(a, b) c)<br>- compose(a, compose(b, c))</pre><pre>- compose(add1, add1, double)<br>- compose(add1, compose(add1, double))<br>- compose(compose(add1, add1), double)</pre><p>Remembering back to arithmetic and Boolean algebra, associativity is often the first step to refactoring. Once we group elements together we can factor, distribute, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/170/1*bydaxgh3WyiGtd7tXWvOKA.png" /></figure><h4>Functors</h4><p>The second part of our domain is functors. In <a href="https://medium.com/@kaw2k/a-map-to-success-functors-in-javascript-6eb6638ce966#.5bj8jmgyf">an earlier post</a>, we talked about how functors are just objects that implement a map method <em>which obeys with a few</em> <em>laws</em>. Here is a refresher of those laws.</p><pre>// F is a functor Functor<br>function identity(x) { return x }</pre><pre><strong>Identity</strong>: <br>- F.map(identity) == F</pre><pre><strong>Composition</strong>: The following are equal.<br>- F.map(f1).map(f2)<br>- F.map(compose(f2, f1))</pre><p>Let’s use a slightly more concrete example to see these laws play out.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/74afdfc0a5a88c80dbd51d2d668450fa/href">https://medium.com/media/74afdfc0a5a88c80dbd51d2d668450fa/href</a></iframe><p>Identity tells us that when we map over the identity function, our original functor is unchanged. Composition tells us that we can chain maps together or compose their functions within one map. Let’s rewrite these laws in a slightly different (point free) notation.</p><pre><strong>Identity</strong>: <br>- map(identity) == identity</pre><pre><strong>Composition</strong>: <br>- map(compose(f2, f1)) == compose(map(f2), map(f1))</pre><p>Do they look familiar? With our composition rule, we can take similar maps and factor them out of our compositions. To be explicit:</p><pre><strong>Boolean Distributive</strong>: <br>- (A &amp;&amp; B) || (A &amp;&amp; C) == A &amp;&amp; (B || C)</pre><pre><strong>Functional Composition:</strong> <br>- compose(map(f2), map(f1)) == map(compose(f2, f1))</pre><p>Just like how we were able to factor out the A in the Boolean algebra example, we are able to factor a map out of compose!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/144/1*LMx96Ba-P7c8qbrhsoJZTQ.png" /></figure><h4>Composing it Together</h4><p>How about we render some blog posts to the screen? We have three hypothetical helper functions:</p><pre>// getPosts : search -&gt; [PostId]<br>// fetchPost : PostId -&gt; Promise Error Post<br>// renderPost : Post -&gt; HTML</pre><ul><li><strong>getPosts</strong>: Takes in a search keyword and returns an array of post ids from somewhere.</li><li><strong>fetchPost</strong>: Takes in a post id and returns a Promise of the server response*.</li><li><strong>renderPost</strong>: Takes in post data and produces some HTML.</li></ul><p>Using these three methods, we will use compose to build up a function to render a Promised array of HTML posts. Let’s make a new function, <strong>searchAndRenderPosts, </strong>with compose that takes in a search string and returns some HTML.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4786ed5da059b44fd5d3a0dbd2a3ed8d/href">https://medium.com/media/4786ed5da059b44fd5d3a0dbd2a3ed8d/href</a></iframe><p>The search string is fed to <strong>getPosts</strong> which returns an array of PostId’s</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/162e900fc3596ccf01b19cf118bc5701/href">https://medium.com/media/162e900fc3596ccf01b19cf118bc5701/href</a></iframe><p>The array of PostId’s from <strong>getPosts </strong>gets fed to the next function in the composition.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ea262e663193060462cd9a84159083f3/href">https://medium.com/media/ea262e663193060462cd9a84159083f3/href</a></iframe><p>Since the value coming out of <strong>getPosts</strong> returns a functor (an array in this case), we need to use map to modify its value. Here we are running <strong>fetchPost </strong>over each value coming from <strong>getPosts. </strong>Now<strong> </strong>we have transformed our array of ids into an array of Promises.</p><p>Next we need to iterate over this array of Promises and turn it into some HTML.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c61dc9333e3ae23d6b17a5911fc2198a/href">https://medium.com/media/c61dc9333e3ae23d6b17a5911fc2198a/href</a></iframe><p>Why do we have <strong>renderPost </strong>wrapped in two maps? Again, <strong>map(fetchPost) </strong>returns an array of Promises. We use the outer map to modify the array, and we use the inner map to run <strong>renderPost</strong> over the Promises within the array**.</p><p>If this was a bit hard to grasp, don’t fret. Just like with Boolean algebra, we could work with the equations without needing to know the details of each value. Similarly here, we will work within our laws to change this code without worrying about the details. Let’s remember our laws:</p><pre><strong>Associativity</strong>: Functions in composition are associative. The following are equal.<br>- compose(a, b, c)<br>- compose(a, compose(b, c))<br>- compose(compose(a, b), c)</pre><pre><strong>Composition</strong>: Functors chain map calls. The following are equal.<br>- map(compose(f2, f1))<br>- compose(map(f2), map(f1))</pre><p>Ok, on to the good stuff.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba57fee8a8cf38e885f5cdc254f0559b/href">https://medium.com/media/ba57fee8a8cf38e885f5cdc254f0559b/href</a></iframe><p>Take a moment to digest what we just did. We started with a function that composed three other functions. We isolated two functions that were logically grouped together (<strong>renderPost</strong> and <strong>fetchPost</strong>), extracted them out and made a new generic function, <strong>fetchAndRenderPost</strong>. Don’t forget that we did not have <em>any insight</em> into the workings of the three helper functions. It didn’t even matter, we were <em>still</em> able to work with the code.</p><p>In arithmetic and Boolean algebra, the laws helped us reason and massage our values. In functional programming, functions <em>are</em> our values. Who ever thought functions could be so fun?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/142/1*ytkqPRAGGNOyL5TXxKakrw.png" /></figure><h3>Conclusion</h3><p>Taking a step back, what did exploring algebraic laws actually give us? We learned that laws surrounding equations and operations allowed us to easily transform those equations from something complex to something more manageable. The types and operations in functional programming share many of these law (and more) affording us enormous reasoning and refactoring power that spans across languages.</p><p>For example, the other day I was talking with two coworkers, one uses Swift and the other uses Scala. We were playing around with some Swift code, refactoring some hairy logic. Even though only one of us knew Swift, we were all able to contribute.</p><p>This is one of the <em>many</em> things that is so exciting about functional programming. Could you ever imagine doing this in an imperative world where functions modify state willy nilly? It would be like hot potato with grenades! If something as simple as <em>laws</em> are this cool… what is next? :D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*Eeu16YkA4Av6ctaTkufWFg.png" /></figure><h4>Footnotes</h4><p>* For the sake of simplicity we use Promises, however Promises are not functors. We would want to use <a href="https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch8.html#asynchronous-tasks">Tasks</a> instead.</p><ul><li>* You might notice that the types don’t match up in this example. We say we are returning HTML but are really returning an array of Tasks. We would normally <a href="http://ramdajs.com/0.19.1/docs/#sequence">sequence</a> and flatten this array of Tasks.</li></ul><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0bdbc59dc65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/the-algebra-of-programming-e0bdbc59dc65">The Algebra of Programming</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The worst part about programming…]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/the-worst-part-about-programming-cf45854a7814?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/cf45854a7814</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Felix Geisendörfer]]></dc:creator>
            <pubDate>Mon, 18 Jul 2016 14:19:15 GMT</pubDate>
            <atom:updated>2016-07-18T14:28:03.158Z</atom:updated>
            <content:encoded><![CDATA[<p>…is realizing how impotent we are.</p><p>Everything is so <a href="http://danluu.com/everything-is-broken/">completely and utterly broken</a>. There is not enough time to fix all the stupid stuff we run into on a daily basis, and most companies and people don’t even care about the science and knowledge that exists around producing better software.</p><p>And even when you work in an environment where everything is done the right away, creating correct software that’s actually useful and easy to use, is anything but a repeatable process.</p><p>Eventually you realize that the stuff you made sucks too and you’ve just contributed to the chaos you hate so much.</p><p>&lt;/rant&gt;</p><p>This is what my brain looks like on a bad day.</p><p>I’ve actually made a bunch of stuff that has survived the test of time, and I still feel good about. I also enjoy programming and problem solving. A lot!</p><p>But sometimes, I just want to burn every single line of code ever written.</p><p>My heart goes out to everybody else out there, trying to create stuff. Don’t get discouraged. I think we can all agree it’s not easy.</p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf45854a7814" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/the-worst-part-about-programming-cf45854a7814">The worst part about programming…</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Underestimate your Programming Abilities]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/in-a-commercial-context-underestimate-your-programming-abilities-ccc56c4f99eb?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/ccc56c4f99eb</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[fronx]]></dc:creator>
            <pubDate>Thu, 14 Jul 2016 16:04:15 GMT</pubDate>
            <atom:updated>2016-07-14T16:04:15.200Z</atom:updated>
            <content:encoded><![CDATA[<p>At the beginning of their career, it is common for programmers to think that the main thing that prevents them from delivering working software in a predictable way is lack of technical skill. And there is some truth to that. However, one thing I’ve learned over the last 8 years is that <strong>the fact that there is a boundary to your abilities will never go away, and it will never feel like that boundary is far away</strong>.</p><p>Part of what it means to mature as a professional programmer is getting better at gauging what is or isn’t within your abilities. Whenever there is a chance that you might cross the line that divides things you know how to do from things you might be able to figure out how to do, it is advisable to be very careful and <strong>think about, and also openly talk about, the estimated cost, risks, and benefits of potential choices</strong>. Otherwise, you will be yet another programmer who keeps promising more than they can deliver, who keeps being surprised by unexpected complications, who keeps getting stuck after biting off bigger chunks than they were able to chew. That’s the risk of not learning how to recognize and work with the ever-present limit of your abilities.</p><p>The basic method I am presenting in this article involves the following steps:</p><ol><li>Categorize the predictability of different approaches you could take.</li><li>Do the most predictable thing first.</li><li>Investigate if the riskier approaches are worth it.</li></ol><p>When confronted with a technical problem, there is usually a range of solutions you can come up with, which can roughly be divided into three categories:</p><h4>The Safe Bet</h4><p>You have done basically the exact same thing before, and all you have to do is do it again.</p><h4>The Puzzle</h4><p>You are confident that you are able to get through it, maybe after doing some research and talking to people.</p><h4>The Opportunity</h4><p>You have a great, novel idea for how to solve something a lot of other people have struggled with.</p><p>Given the choice between three potential technical solutions where one is a Safe Bet, the other a Puzzle, and the other an Opportunity, which one would you choose, intuitively? Depending on how confident someone is in their abilities, they might go for the most promising, but also most risky solution they can think of—something that they hope <strong>might stretch their abilities</strong>, something that they <strong>hope to be proud of</strong> when it’s all done. From a personal development perspective, that can be a good strategy. If you are working on a private project and it doesn’t really matter that much whether or when it will be finished, feel free to go wild with your ideas and throw predictability out of the window if you feel like it.</p><p>However, in a professional context, your personal satisfaction and learning experience are usually not the top priorities. What is much more <strong>important for companies is the ability to decide what to deliver, make a plan for how to do it, and execute it</strong>. Any technical decision that doesn’t contribute to that jeopardizes the success of the project. (Even if there are areas where the company wants to innovate, that doesn’t necessarily mean that the technical execution must also be novel.) The reality of things is that if projects take longer than expected, companies can eventually run out of money. So what they tend to do instead of waiting indefinitely is redefine goals, move people around, switch focus, and limit scope, hoping to reach some level of stability. Companies want to be able to have answers to the questions: what are you working on, how much will it be worth when it’s done, and how much are you expecting to invest in it until then. They pay you money because they rely on your ability to do what is necessary for them to deliver a product that enables them to survive—not because your solutions are creative and challenge and stretch your abilities.</p><p>What follows from that is that, in a commercial context, given the choice between three approaches, where one is a Safe Bet, the other a Puzzle, and the other an Opportunity, it makes sense to go for the Safe Bet before investigating whether the other approaches are worth spending additional time on. And if there really is no Safe Bet, you either have a good reason to solve a Puzzle instead, or the problem you are trying to solve is too big and should be split into smaller chunks first.</p><p>You might ask: but if there is a great Opportunity, isn’t it a waste of time if you implement the Safe Bet first? And what if you don’t get around to investing in the Opportunity? What if we’ll be stuck with the Safe Bet forever? Wouldn’t that be kind of sad? I agree, it does seem a bit sad. On the other hand, <strong>delivering a technical solution that is so boring that you were able to make a plan, estimate the effort, and make it work in time, is actually a great achievement.</strong></p><p>Doing work that doesn’t exceed your ability has traditionally been the exception for software developers. We are so used to the feeling that we can do everything, anything, but unfortunately only relatively poorly and with low predictability, that <strong>it takes conscious effort to focus on doing what you know how to do</strong>. Especially if there isn’t a lot of continuity in the type of work that you do, it can be hard to recognize that even though you are fairly certain about a technical solution you’ve chosen, you don’t know enough about it for it to qualify as a Safe Bet. In fact, most of the work programmers do lives somewhere on the spectrum between those categories. If you want others to rely on you, it is better to underestimate your abilities and overestimate risks than to go in a direction that actually involves more uncertainty than you can justify.</p><p>Over time, your abilities will grow, and some approaches that used to be Puzzles will become Safe Bets, and some Opportunities will become Puzzles, but the categories themselves won’t go away. It is worth learning to recognize and work with them.</p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccc56c4f99eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/in-a-commercial-context-underestimate-your-programming-abilities-ccc56c4f99eb">Underestimate your Programming Abilities</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Error 404: Education Not Found]]></title>
            <link>https://medium.com/techspiration-ideas-making-it-happen/error-404-education-not-found-a740ced7923?source=rss----f9f250c74f---4</link>
            <guid isPermaLink="false">https://medium.com/p/a740ced7923</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[college]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Teodor Cataniciu]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 20:14:58 GMT</pubDate>
            <atom:updated>2017-02-20T15:33:55.788Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introduction</h4><p>This article is based on a talk I gave at <a href="http://vencaf.nl/">Venture Cafe Rotterdam</a>, in which I argue why formal education fundamentally fails to educate leaders. In the past couple of months, I gave this topic more thought and refined some of my ideas. You are reading the result.</p><h4>Where I’m coming from</h4><p>I was born the same year the first McDonald’s opened doors in my country. One of the first symbols of capitalism crossing our borders after the fall of the communist regime. Many things changed, but one that did not was education. The same dense, unappealing curriculum, taught from dusty books wore by many generations of students who endured them before us.</p><p>Throughout the beginning of my formal education, I was at best mediocre. And so it came that every year that passed, school and I grew further apart. I was not doing well in class, yet I had a great way to understand how the system worked. I was quick to realize that it was not studying hard or asking questions about the topics I was curious about that would bring me good results. Quite the opposite, I was in a constant game of guessing what topics would be on an exam, superficially connecting concepts, using plastic phrases that would please my teachers. It is sad because it worked. By the time I finished high school, I had one of the best GPAs in my school.</p><p>My dream was to study at one of the best universities in the world. I truly believed they would understand education is more than crunching information and regurgitating it after a few weeks. They would know studying and learning are two very different concepts. I was wrong.</p><h4>The First Spark</h4><p>Being young and overall clueless about the world, I wanted nothing to do with school. I found myself spending all my free time creating various, now embarrassing, YouTube videos. From Mafia movies with guns and VFX explosions, to cheesy comedy pieces inspired by foreign TV channels that I got my hands on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*eNIm34YyYk9ppS64VbHy5Q.jpeg" /><figcaption>Snapshot from one of my early Mafia childhood productions</figcaption></figure><p>Creating and carefully crafting my films was a way out of that school mess I so much despised. I felt special doing it; for the first time in my life I was passionate about something. I was learning, not studying. When I turned 15, an opportunity showed up to move to Los Angeles for the summer. I was to join a program made possible by Warner Bros. and USC– at the time the best film school in the world. Needless to say, I was ecstatic.</p><p>All summer, I woke up and went to bed thinking about my movies. The camera angles, the cast, running around town to get film permits and lock locations. I was everywhere but in a classroom; in a way, the city was my classroom. Surrounded by 80 or so people with the same dreams, coming from all over the world, working together to create the very best pieces of film we could. I was genuinely happy. This experience sparked something in me: it fundamentally proved there was a better way to learn. It showed, to me at least, that the folks at home got it wrong. I needed to get out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5ZswxW2LYunaet05VQRiQ.jpeg" /><figcaption>Cast of ‘With Life’, shot on location at Warner Bros.</figcaption></figure><h4>A Cold Shower</h4><p>I made it my main objective, if not my life goal, to get into one of the best schools in the world. Of course, I was naive in my thinking. The tuition fees of most ‘top schools’ were out of my realm. And even though to this day I am in love with filmmaking, I followed my brain and the advice of my family to go to a business school instead of a film school — maybe this deserves a post on its own. Most importantly, it was one I could afford that offered the same promise I was set on: to take part in world-class education, to learn not to study. I went to the Netherlands.</p><p>I’d like to make it clear: the following experiences have nothing to do with my study program, nor are they specific to my university. Counting opinions of friends from San Francisco to Bucharest, I believe the next paragraphs are equally applicable to any business degree or university out there.</p><p>A room with close to 500 students. A PowerPoint presentation longer than I imagined possible. Locked in courses, taking everyone from A to B, usually by means of long multiple-choice exams. My first year of university started with the promise that we would be ready to tackle complex business problems in international environments. That was something I refused to believe.</p><p>I believe the biggest issue we face today is that we assume education is a production line. Taking components from station A to station B, and you better pray you look no different from the other components. Formal education is preparing people for a world that does not exist anymore. When Henry Ford was blowing minds with his assembly line, there was a real need for replicable pieces. One worker was injured or did not want to work? No problem, there are hundreds just like him.</p><p>Today, we live in a different world. One in which workers on an assembly line will soon be seen in pictures in a history museum. One where our passions, creativity, and will to better the world around us will prime in front of our mechanistic aptitudes. You want to know who the 6th President of the United States was? Hey Siri.</p><h4>Crafting Your Education</h4><p>To the benefit of business school, and other non-technical majors generally, there is plenty of time to pursue your passions on the side. I took this to an extreme. At the time of writing this post, I am 6 months away from graduating and have not attended a class in more than a year. Most people will take this badly: what’s the point of wasting your time in school then? The reality of this is simple. When you are 20, there is no better place to surround yourself with smart people and open opportunities than a university campus. Notice I did not suggest you have to be enrolled.</p><p>I believe that in this day and age, it is up to you, each one of you, to craft your education by what you do besides your studies. For me, this meant refocusing my energy into learning computer programming and running two organisations. For the past 12 months, all my work has had nothing to do with studying business, but to learn as much as I could about technology. And trust me, I learned a lot more about business in the process than any business school course ever taught me.</p><h4>End of Class</h4><p>My work today is fueled by my passion, just like in the days of film school. I made it my goal and obligation to share my thoughts on what makes good education and empower others to build and create. I surrounded myself with amazing people, who share this mission.</p><p>I am in no position to give advice, so please do not regard my thoughts as such. The past couple of months were humbling for me. I learned how powerful it can be to work in a team driven by a transformative goal. I will continue on this path, of crafting my own education: out of my experiences, the people I meet, and my successes and failures. Indeed, this was the only thing that ever made me learn, not study.</p><p><em>P.S: You can read about our mission at </em><a href="http://restart.network/"><em>Restart Network</em></a><em> and </em><a href="http://tsociety.io/"><em>Turing Society</em></a><em> and help us make world-class tech education a reality for anyone.</em></p><h4>Published in Techspiration + Ideas + Making It Happen.</h4><figure><a href="https://medium.com/techspiration-ideas-making-it-happen"><img alt="" src="https://cdn-images-1.medium.com/max/720/1*n0J_5QvGZeLGFZnFnmsfQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a740ced7923" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techspiration-ideas-making-it-happen/error-404-education-not-found-a740ced7923">Error 404: Education Not Found</a> was originally published in <a href="https://medium.com/techspiration-ideas-making-it-happen">Techspiration + Ideas + Making It Happen</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>