<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brock Lanoza on Medium]]></title>
        <description><![CDATA[Stories by Brock Lanoza on Medium]]></description>
        <link>https://medium.com/@brockinit?source=rss-e3ce6144e6f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*BfroXk627lARvOejag1MKA.jpeg</url>
            <title>Stories by Brock Lanoza on Medium</title>
            <link>https://medium.com/@brockinit?source=rss-e3ce6144e6f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:12:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brockinit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Learn how others see you]]></title>
            <link>https://medium.com/@brockinit/learn-how-others-see-you-23874e36d527?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/23874e36d527</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Thu, 29 Nov 2018 05:44:08 GMT</pubDate>
            <atom:updated>2019-04-25T03:29:43.715Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fbd43TvOAbJj-XAKmj-MTg.jpeg" /><figcaption>This is what came up when I googled “perspective”</figcaption></figure><p>One of the most potent, yet challenging ways of promoting personal growth is to enlist the feedback of others. As humans, we’re exceptionally good at spawning our own narratives about how people perceive us, how well we do at certain tasks, and how poorly we do at others. For example, while I think of myself as quite the comedian, the awkward pity laughs that crackle through the room each time I tell a joke seem to contradict that notion. On the flip side, I used to question my ability to communicate effectively at work before I learned from others that it was one of the things they appreciated most about working with me.</p><p>Despite the constant invention and evolution of these views of self, they’re never quite 100% aligned with reality. We tend to realign our self perspective with the perspective of others over time, but when this process is left on auto-pilot, it’s lethargic and inefficient. As a result, time that could be spent improving weaknesses is wasted. How so? Let’s illustrate this with an example:</p><p>Early in my career as a software engineer, I saw myself as kickass at reviewing pull-requests. I left thoughtful and insightful commentary for my coworkers to cherish and worship. “Our codebase is a safer and happier place, thanks to the metaphorical guardrails that my comments provide”, I thought to myself. Unfortunately, my coworkers didn’t seem to agree. My reviews were hack-y, at best. The comments were littered with irrelevant suggestions and the code examples provided offered little to no benefit over existing implementations.</p><p>Herein lies the problem. Because I didn’t see pull-request reviews as a personal weakness, I wasted time attempting to grow in other areas that weren’t necessarily weak in the first place. When it comes to personal growth, identifying weaknesses quickly and focusing on them is what matters. This is how you create leverage.</p><p>Fortunately, I’ve found a way to defeat this type of inglorious ignorance. By taking advantage of 1 on 1 meetings with coworkers and/or managers, it’s possible to get feedback in a quick and effective manner that allows you to identify your areas of weakness. The method I’ve come up with was inspired by “The Art of the Awkward 1–1”, by Mark Rabkin. As the name of the article of inspiration implies, you gotta get awkward and pretty uncomfortable for this to work. More specifically, it’s necessary to be willing to <em>make it easy for people to be critical of you and offer constructive criticism</em>.</p><h3>Steps to make the most of your 1 on 1 time</h3><ul><li><strong>Create a list of areas that you see as your strengths and weaknesses. </strong>These can be directly related to the tasks you tackle at work or simply general characteristics.</li><li><strong>During the 1–1, ask your coworker/manager to identify which areas they see as strengths and which they see as weaknesses. </strong>This is the time to encourage them. Welcome their unfiltered opinion. People are often reluctant to call out weaknesses directly, even when prompted, so you want them to feel comfortable in giving a candid answer.</li><li><strong>As an optional exercise, ask them to apply a letter grade to each area. </strong>The letter grade assignment has been especially helpful in my experience. Where asking “How am I doing in this area?” is too open ended to elicit an honest and accurate response, asking for a hard letter grade can get the other person to give an answer that’s more meaningful and useful overall.</li><li><strong>Compare their answers to your own and discuss the discrepancies. </strong>This is where you begin to bridge the mental gap between your perception of self and the perception others have of you. Don’t worry if you find that they see things far differently. You don’t always have to agree with the other person. The grand prize here is the <em>awareness</em> that you build by having these conversations.</li></ul><p>Unsurprisingly, this can be unsettling and difficult to do at first. But by utilizing this technique during 1–1s, you’ll push the conversation away from the fluff of small talk and into the realm of real talk, and that’s where positive change happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23874e36d527" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Host Multiple Serverless APIs Under the Same Domain]]></title>
            <link>https://medium.com/type-faster/how-to-call-multiple-serverless-micro-services-under-the-same-domain-972b5b9e49dd?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/972b5b9e49dd</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloudformation]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[serverless-architecture]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Fri, 30 Mar 2018 00:09:55 GMT</pubDate>
            <atom:updated>2018-03-30T15:57:37.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vJoNzPZwtG7_0uVDFi3KmQ.jpeg" /></figure><p>Did you ever wish that people would just shut-up about serverless? It’s rare that one makes it out of a tech conference these days without hearing endless utterances of the term “serverless”. Annoying as this may be, the concept of serverless itself is incredibly inviting. Think about it; allow developers to write code and build applications without having to deal with all of the underlying infrastructure that more often than not becomes difficult to maintain and scale? It’s a pretty wonderful thing.</p><h3>Serverless APIs: A blessing and a curse</h3><p>If you’ve tried The Serverless Framework out, you’ve seen how easy it is to setup and deploy a live API by leveraging cloud services such as AWS Lambda. At the company I work for, Redshift Digital, we’ve used Serverless on a few client projects that needed a slim, simple backend to serve some content to the frontend application. In that situation, it worked very well and allowed us to move much quicker than would have been possible without such technology.</p><p>Unfortunately, our honeymoon with Serverless came to an abrupt end. While working on a recent project, I was merrily watching our API deploy when the following happened:</p><pre>Serverless: Uploading CloudFormation file to S3...</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*PZgT_L7dxU-fj4cX68Subg.png" /></figure><pre>The CloudFormation template is invalid: Template format error: Number of resources, 212, is greater than maximum allowed, 200</pre><p>Where did this come from? As it turns out, this was an issue with Amazon and not Serverless. Under the hood, when creating services deployed to AWS, Serverless compiles a CloudFormation script from the code you wrote and uploads it to the cloud. CloudFormation can be thought of as the control center for your AWS account. Anything that you can do through the console in AWS can be scripted through CloudFormation and deployed in an automated fashion. Sadly, AWS currently imposes a <strong>hard limit of 200 resources</strong> when deploying a CloudFormation script.</p><p>After digging a bit deeper into what was actually getting deployed with each Serverless package, it was easy to see how we were exceeding this limit, even with only about 30 endpoints in our API.</p><h3>The extra baggage of a Serverless function</h3><p>You don’t need a Nvidia GPU to determine that 30 &lt; 200. That said, how were we hitting the CloudFormation limit? The reason for this can be summed up as such:</p><pre>30Functions != 30Resources</pre><p>Let’s assume you created a Serverless API with 30 functions that acted as endpoints. For every function in your API, you also get the following resources:</p><ul><li>Version (of your Lambda function)</li><li>Log Group (on CloudWatch)</li><li>Permissions (Allowing API Gateway to call your Lambda function)</li><li>Resource path (of the API Gateway endpoint)</li><li>Method (of the API Gateway endpoint)</li></ul><p>In total, you get <strong>6 resources per function</strong> in addition to the few global resources shared by entire API. Although some app APIs can get by with such a limit in place, there are plenty of APIs out there that just simply require more than 30 endpoints to do their job. How can we get around this limit and still use a Serverless API to meet our needs?</p><h3>Microservice architecture</h3><p>To combat this resource limit, our team decided the best course of action was to split up our API into separate micro-services. For each resource in our REST API (users, organizations, etc), we created a new Serverless service with its own serverless.yml` file. By doing this, we realized a few benefits:</p><ul><li>Our code was separated in a way that made it easier to maintain</li><li>We avoided the hard-limit imposed by CloudFormation (hooray!)</li><li>Deployments were faster since we were only deploying a few of the API functions at a time, rather than all of them at once</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*gjxgod-aKTNumxHJGyFWXg.png" /><figcaption>Sample directory structure</figcaption></figure><p>Alas, this did not make a complete solution. At this point, we were left with a number of API hosts generated by AWS (one for each service). Ya know, these things:</p><pre><a href="https://zdqdd62gz9.execute-api.us-west-1.amazonaws.com/development/">https://sougly1337.execute-api.us-west-1.amazonaws.com/development/</a></pre><p>Luckily, it’s possible to alias each of these as base paths of a single API using m̶a̶g̶i̶c̶ a custom domain on API Gateway.</p><h3>Setting up a custom domain on API Gateway</h3><p>To setup a custom domain, go into your AWS console and navigate to the aptly-named “Custom Domain Names” section. Click on “Create a Custom Domain Name” and you will be greeted by this screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbtwSkzAl1VtVNZcDnq07Q.png" /></figure><p>Assuming you have the domain that you want to use handy, you can type it in here and click the appropriate radio button under “Endpoint Configuration”. Generally speaking, the option you select will be determined by the purpose of your API.</p><ul><li>End-user facing APIs will use <strong>Edge Optimized</strong> since this will take advantage of the underlying CloudFront distribution to quickly get data to your users in whatever region they may reside.</li><li>If you API happens to talk exclusively to internal resources, such as an EC2 instance, then you would want to use <strong>Regional</strong> since this would optimize the API for the single region that it has to communicate with.</li></ul><h3>Base Path mappings are friend, not foe</h3><p>Now that we’ve done that, we’re ready to bring it all together and map the microservices to this domain. By adding a base path and choosing the correct microservice to point to (destination), you make it possible to access your individual Serverless services all through a single API endpoint.</p><p>In this case, mediumarticlesarecool.com/users would call the previously mentioned users service. Be aware, creating a custom domain can take up to 45 minutes to finish since it has to spin up a CloudFront distribution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*eWJ5AO0SzSOiJDr-26V5aw.png" /><figcaption>Don’t worry, organizations is plural</figcaption></figure><h3>Conclusion</h3><p>If you’ve stuck around for this long, you’ve hopefully learned a useful way to implement a large REST API using Serverless functions all whilst avoiding the dreaded CloudFormation resource limit error. Next time, I’ll be writing a piece explaining how we used CircleCI to automate the deployment of our microservices.</p><p><em>Disclaimer about using Serverless APIs in production:</em></p><p><em>It should be noted that while this worked for our particular situation (our serverless API was acting as a middleware layer between the frontend and other backend services), it may not work for you. For as great as serverless can be, there are some pain points that make it more of a hassle than it’s worth in certain situations. For example, dealing with connection pooling is notoriously difficult since Lambda functions are stateless. Make sure your understand your application’s specific needs before going all-in on serverless.</em></p><p><em>Brock Lanoza creates product solutions at </em><a href="http://www.redshiftdigital.com/"><em>Redshift Digital</em></a><em>. When not pondering the finer points of human-computer interaction, he can be found shamelessly spam-posting pictures of Persian cats to the internet.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972b5b9e49dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/type-faster/how-to-call-multiple-serverless-micro-services-under-the-same-domain-972b5b9e49dd">How to Host Multiple Serverless APIs Under the Same Domain</a> was originally published in <a href="https://medium.com/type-faster">Type Faster</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prioritization: You’re doing it wrong]]></title>
            <link>https://medium.com/@brockinit/prioritization-youre-doing-it-wrong-c58ff1325fe8?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c58ff1325fe8</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[effective-learning]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 04:53:10 GMT</pubDate>
            <atom:updated>2018-02-07T05:16:40.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_aigzrAeuhsvzKlLSCqu3Q.jpeg" /></figure><p>Two weeks ago, I <a href="https://medium.com/@brockinit/education-hacking-my-alternative-to-getting-a-grad-degree-e10870cd9a40">wrote a post</a> about the curriculum I created exclusively from online resources that would be used to help me learn about the process of deriving useful insights from data (data science, as the cool kids call it these days). I promised myself that while taking these courses, I’d write a post each week, reviewing what I had learned from the previous 7 days. Two weeks into the program and I’ve learned a humbling lesson:</p><blockquote>Teaching yourself new skills and concepts can be difficult, but trying to effectively manage your time sucks.</blockquote><h3>I’ll defeat procrastination…eventually</h3><p>Excited and ready to get started, I began with the first course on my list. The initial lessons crawled by, as they mostly dealt with very basic programming concepts in python that I already had quite a bit of experience with. Committed to sticking to the roadmap, I pushed forward and devoted my study hours during the week to what amounted to little more than answering trivial questions and performing simple exercises.</p><p>After the first week, I felt like I hadn’t made any progress. To compound this problem, reviewing material I already knew caused me to lose steam. In the next few days that followed, I hacked on other unrelated projects after work or relaxed in the evenings instead of continuing along the course’s path. If you’re like me, then you know how frustrating this can be. The dreaded feeling of guilt creeps up as you realize that you aren’t making the most of your time. Sadly, this kind of remorse conveniently sets in after it’s too late and you’ve successfully procrastinated.</p><p>I realized that there was something fundamentally wrong with my approach. I wasn’t playing an active role in my learning. I wasn’t <em>prioritizing</em>, and it was hurting my ability to move forward.</p><h3><strong>Aggressive Prioritization: The key to getting shit done</strong></h3><p>In “The Effective Engineer” by Edmond Lau, there is an entire chapter devoted to the importance of prioritization. The author champions the idea of <strong>working on things that</strong> <strong>directly produce value</strong> and devising if-then plans to facilitate action and reduce procrastination. This means forgoing “easy wins” to work on harder tasks that drive progress. By pushing items that “move the needle” to the top of your list of todos, you extract the most value out of your time. While that may sound obvious, the nuance that makes this brutally effective is the act of repetition. Rather than prioritize once and complete all of your tasks, it’s better to “aggressively prioritize” and constantly revisit your list, reordering the tasks as you see fit.</p><p>While this piece of advice is given in the context of software engineering, it can be applied to just about any area of your life that could use optimization. Had I applied it to my learning situation, I would have realized early on that the correct move would be to review the course I was taking on a more granular level prior to starting. Doing this would have given me the opportunity to prioritize the material and put the important sections first, rather than blindly starting at the beginning.</p><p>Taking time to frequently recognize which tasks are most vital to your success keeps you mindful of your motivations, your goals, and most importantly, what the steps to reach them look like.</p><p><em>Brock Lanoza creates product solutions at </em><a href="http://www.redshiftdigital.com/"><em>Redshift Digital</em></a><em>. When not pondering the finer points of human-computer interaction, he can be found shamelessly spam-posting pictures of Persian cats to the internet.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c58ff1325fe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Education Hacking: My Alternative to Getting a Grad Degree]]></title>
            <link>https://medium.com/@brockinit/education-hacking-my-alternative-to-getting-a-grad-degree-e10870cd9a40?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e10870cd9a40</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-learning]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 06:17:25 GMT</pubDate>
            <atom:updated>2018-01-25T04:44:51.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nC9o498X7ACIxXtBrPJvnQ.jpeg" /><figcaption>Photo credit: my archaic iPhone</figcaption></figure><h3><strong>The problem</strong></h3><p>A lifelong learner, I’ve always felt compelled to be constantly seeking out new avenues of personal growth. I love to learn, to pick up new skills, and to feel ever-evolving. It’s one of the reasons I was immediately attracted to the software industry.</p><p>Over the course of my career in Software Development, I’ve come to discover which niches in particular intrigue me. Alongside writing full-stack JavaScript applications and studying serverless architecture, uncovering valuable insights using data has excited me the most.</p><p>This affinity for data has flourished since <a href="https://www.bizjournals.com/pacific/blog/2015/11/devleague-site-crunches-hawaii-tourism-stats-for.html">I worked on a web app that provided data analytics for The State of Hawaii using tourism data</a>.</p><p>After landing a new job in San Francisco and finalizing my move from Hawaii, I decided it was time to take the next step and get serious about learning how to work with data. Realizing that I wanted to learn more about machine learning, applied statistics, and data science in general, I started seeking out ways to obtain the skills and knowledge I wished to acquire.</p><p>Initially, I had considered going back to school to earn a graduate degree in Applied Statistics, or Computer Science. It seemed like the right move, given that it would fill the gaps in my education and provide me with another credential to put on my resume. I have a habit of compulsively researching every feasible option before making any significant decision, so I took to the internet and started seeing what other routes were practical. After looking at tuition rates, discovering the depth of MOOCs available on the web, and taking into account the resources available in my new city, I came to an abrupt conclusion:</p><blockquote>Fuck grad school.</blockquote><h3><strong>The solution</strong></h3><p>While I see the value in higher-education, I also see the value in efficiency. In my particular case, I don’t think that going to grad school is the most efficient option. Attending a graduate degree program would offer me 3 things:</p><ol><li>New knowledge and skills</li><li>A shiny new credential</li><li>Mentorship</li></ol><h3><strong>New knowledge and skills</strong></h3><p>This one was easy. With the inception of MOOC (Massively Open Online Courses) sites such as edX and Coursera, real-life university classes from top-tier programs are available for $free.99 online. These kind of options make spending 30k+ on a graduate degree a hard sell.</p><h3><strong>A shiny new credential</strong></h3><p>While I admit that it doesn’t hurt to have a degree, I’ll vehemently defend the notion that getting a degree is not required to find success. Employers are looking for information about you and a degree is just one piece of information they can use in their evaluation.</p><h3>Mentorship</h3><p>Ok, this is something I believe I’d miss out on if I didn’t go for the degree. Every time that I’ve learned effectively, I’ve had someone there to bounce ideas off of and receive constructive criticism from. Mentorship can accelerate your learn-rate in a way that pure, self-study simply cannot. I learned this first-hand while attending <em>(incoming shameless plug)</em> <a href="https://www.devleague.com/">the world’s most badass web development bootcamp.</a> Fortunately, by moving to San Francisco I’ve landed in a hot bed of meet-ups, conferences, and like-minded people who are on the cutting-edge of the industry. With that being the case, the only thing that should prevent me from finding mentorship is lack of effort.</p><h3>So what’s the plan?</h3><p>Rather than jump haphazardly into a random array of online courses and hope for the best, I’ve developed a curriculum that I’ll follow for the next 12 months as I teach myself statistics, machine-learning, and data-engineering.</p><h3><strong>Le Curriculum</strong></h3><p><strong>Practical Foundation (Get excited, be able to produce something with new skills)</strong></p><p><a href="https://www.dataquest.io/dashboard">Dataquest.io Data Science Track</a> (10 weeks) Ends April 1st</p><p><strong>Deepen Applicable Skills (Voyage into advanced techniques and deep learning)</strong></p><p><a href="http://course.fast.ai/index.html">Fast AI Deep Learning pt.1</a> (7 weeks) Ends May 20th</p><p><a href="http://course.fast.ai/part2.html">Fast AI Deep Learning pt.2</a> (7 weeks) Ends July 8th</p><p><strong>Data Engineering (Distributed architecture in the cloud for developing data pipelines)</strong></p><p><a href="https://aws.amazon.com/certification/certified-big-data-specialty/">AWS Big Data Certification</a> (3 weeks) Ends July 29th</p><p><strong>Stats and Mathematics (Fill the gaps in theory and math)</strong></p><p><a href="https://www.youtube.com/playlist?list=PLtmWHNX-gukIc92m1K0P6bIOnZb-mg0hY">Linear Algebra</a> (8 weeks) Ends October 7th</p><p><a href="https://www.coursera.org/learn/probability-intro">Intro to probability and data</a> (3 weeks) Ends October 28th</p><p><a href="https://www.coursera.org/learn/inferential-statistics-intro">Inferential Statistics </a>(3 weeks) Ends November 11th</p><p><a href="https://www.coursera.org/learn/linear-regression-model">Linear Regression and modeling</a> (2 weeks) Ends November 25th</p><p><a href="https://www.coursera.org/learn/bayesian">Bayesian Statistics</a> (3 weeks) Ends December 16th</p><p><a href="http://Statistics with R Capstone">R Capstone</a> (1 week) Ends December 23rd</p><h3>Conclusion</h3><p>This post kicks off my journey. Each week, I’ll be posting a short piece on the things I’ve learned, what I’ve built, and what problems nearly sent my laptop out the window. Although I’m mainly writing these posts as a way to hold myself accountable, It’s my sincere hope that I’m able to chat with others who might be undertaking a similar #educationquest. If you too geek out on data or enjoy giving people’s lives an easy button with great software, I’d love to hear from you.</p><p><em>Brock Lanoza creates product solutions at </em><a href="http://www.redshiftdigital.com/"><em>Redshift Digital</em></a><em>. When not pondering the finer points of human-computer interaction, he can be found shamelessly spam-posting pictures of Persian cats to the internet.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e10870cd9a40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stupidly Simple Static Hosting with S3]]></title>
            <link>https://medium.com/@brockinit/stupidly-simple-static-hosting-with-s3-edf8aa026128?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/edf8aa026128</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[create-react-app]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[static-site]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 03:46:45 GMT</pubDate>
            <atom:updated>2017-06-28T07:57:10.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*EvS1HpPprkIxqXsBfs5F3g.jpeg" /></figure><h3>About S3</h3><p>One of the backbones of the AWS platform is its Simple Storage Service, or S3. The more one learns about AWS, the more you realize <a href="http://blog.catchpoint.com/2017/03/01/aws-s3-outage-impact/">how dependent the internet is on its existence</a>.</p><p>A lesser known feature of S3 however, is the ability to host static websites. By making your bucket publicly available, it quickly can become your interweb-facing beacon, hosting your personal site, portfolio, or teenage mutant ninja turtle blog. Another cool thing about S3 is that you don’t have to manage any servers. That’s great because when you let AWS manage those things, your site can go viral and <a href="http://blogging.alastair.is/how-i-served-100k-users-without-crashing-and-only-spent-0-32/">scale without issue for pennies on the dollar</a>.</p><p>A key thing to note is that the site <em>must</em> be static. Sorry Wordpress fans, that means no PHP or other server-side scripting. For this tutorial, we’re going to stick to using a popular React library called <a href="https://github.com/facebookincubator/create-react-app">Create React App</a>. For the purpose of this article, I created a sample site that can be cloned from Github.</p><h3>Let’s Learn!</h3><p>Before we start, let’s get a high-level overview of what we’re going to do:</p><ul><li>Clone the sample site from Github and get it running</li><li>Upload the site to an S3 bucket using the AWS console</li><li>Learn to automate deployments to S3 using the AWS CLI tool</li></ul><p>To kick things off, we’re going to get the site’s code from Github. Go into your terminal and run the following:</p><p>git clone git@github.com:brockinit/s3-create-react-app.git</p><p>If you’d like to see the site in all its completely stock glory, run npm start and navigate to localhost:8080 in your browser.</p><p>Now that we’ve gotten the site setup, let’s prepare to move it to S3.</p><ul><li>Run npm run build</li></ul><p>This will create the /build folder which will contain all of our compiled code.</p><p>With that out of the way, it’s time to move the site into S3. The next step is to log in to your AWS console. If you don’t have an account yet, be sure to make one at <a href="http://aws.amazon.com/">the AWS homepage</a>. While not necessary for working within the AWS console, it’s important to get to your Access Key ID and Secret Access Key from your IAM Management console if you wish to access S3 via the command line. Amazon has thorough documentation on how to accomplish this <a href="http://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html">here</a>.</p><p>Upon successfully logging in to your AWS console, click over to the S3 dashboard. You’ll be greeted with a screen like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDPDRYhl27Bwx4v6227MMQ.png" /><figcaption>Hooray! We made it.</figcaption></figure><p>S3 stores objects in resources called “buckets”. To host our site, we need to create a bucket and make it available to the public. To do this, click on the “Create Bucket” and you’ll land here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1Y4j4tl2NsHLsPTS7u3Ww.png" /></figure><ul><li>Give the bucket a name.</li></ul><blockquote><strong>IMPORTANT</strong> Bucket names are unique across all of AWS. The bucket name that you choose must be the only instance of its kind out in the wild.</blockquote><ul><li>Click next and next again in step two to arrive at the “Set permissions” step.</li><li>Click into “Manage public permissions”</li><li>Check “Read” for both objects and object permissions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cTgeW4heF95yan2NTGfmg.png" /></figure><p>The only thing we want to change here is public access. In order for our site to be served from this bucket, it’s necessary to make it visible to the world. If you don’t do this and people try to visit your website, they’ll be met with a sad 403 error and nobody likes those.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*tbKpQkCdnV-Vj-xS5RGK1w.jpeg" /><figcaption>Me IRL after getting denied access to your bucket</figcaption></figure><p>Once this has been completed, you can keep everything else at their default settings and finish creating the bucket!</p><p>Luckily for us, configuring a bucket to host a website is a breeze. To do this, we have to click into the bucket and check the “Properties” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVTHC37N-fjb6sifWX3Agw.png" /></figure><p>From here:</p><ul><li>Go to “Static website hosting”</li><li>Check the button “Use this bucket to host a website”</li><li>Add “index.html” to both the index document and error document</li><li>Hit “Save”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZmT-9pmWDdFGAI8bVD-Ig.png" /><figcaption>Setting the index document tells the bucket which file to serve as your site’s root</figcaption></figure><p>The final step is to take the contents of your /build directory from earlier and upload them to your bucket. Remember to set their public permissions to “Read” like you did for your bucket. Click on the endpoint listed for your bucket under “static website hosting” (example in above picture) and if all goes well, you should be looking at your newly deployed site!</p><h3>Next steps: Automated deployments</h3><p>Repeating these steps every time you make a change to your site can quickly become tedious. Fortunately, there’s a much simpler way to deploy changes in seconds using the AWS CLI tool.</p><p>If you don’t have the AWS CLI tool yet, be sure to run:</p><p>pip install --upgrade --user awscli</p><p>Before you can use the CLI tool to talk to your S3 bucket, you must configure it with your access keys. Here are the steps required:</p><ul><li>aws configure</li><li>Enter your access key id and secret access key when prompted <em>(these can be found by going to the IAM service in the AWS console and navigating to Users &gt;&gt; Some_User &gt;&gt; Security Credentials)</em></li></ul><p>Now that the CLI tool is setup and configured to communicate with our S3 bucket, we can run our deployment script to send our updated website files up to the cloud!</p><p>From the website’s root directory, run the following commands:</p><pre># Create a new build folder with bundled assets<br>npm run build</pre><pre># Move into the build directory<br>cd build</pre><pre># Copy the contents of the build folder into your S3 bucket and make # them publicly available<br>aws s3 sync . s3://your_bucket_name --delete --grants read=uri=<a href="http://acs.amazonaws.com/groups/global/AllUsers">http://acs.amazonaws.com/groups/global/AllUsers</a></pre><p>That’s it! Anytime you make an update to your site’s code, simply run that list of commands and your changes will be effective immediately on S3.</p><h3>Conclusion</h3><p>S3 is an immensely powerful service and as you can see, it can easily work in tandem with app scaffolding services such as create-react-app to rapidly develop and deploy static site solutions.</p><p>If you’d like to streamline the deployment process further, I’ve included the commands above as a bash script which can be found in the <a href="https://github.com/brockinit/s3-create-react-app">Github repo for this example</a>. As always, if I’ve made a mistake or you think I could have done something another way, feel free to let me know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edf8aa026128" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t just look fit]]></title>
            <link>https://medium.com/@brockinit/don-t-just-look-fit-308c1f0d4c9?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/308c1f0d4c9</guid>
            <category><![CDATA[health]]></category>
            <category><![CDATA[movement]]></category>
            <category><![CDATA[fitness]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 06:06:54 GMT</pubDate>
            <atom:updated>2016-02-10T06:06:54.525Z</atom:updated>
            <content:encoded><![CDATA[<p>As a fitness fanatic, trainer, and someone who makes an unnecessary amount of puns about being “at the bar” on Friday nights, I’ve found plenty of reasons to cringe lately. It seems as if I can’t so much as dip into the Internet without being bombarded by a slew of faux-fit garbage.</p><p>Sadly, it seems as if the American public has become accustomed to a distorted definition of ‘being fit’. Washboard abs and chiseled biceps are now of top priority when it comes to getting into shape. Hardly ever do we come across articles that champion the progression of our movement capabilities, but rather we look for ways to quickly achieve hypertrophy with no other benefit in mind. The idea we’re supporting goes something like this, “Who cares if I can’t touch my toes and maintain my joint mobility into my 50’s as long as I can see a little more definition in my arms?” There are a few reasons why this aesthetic affliction is destined to do more bad than good in the long run.</p><blockquote><strong>Hypertrophy is only one piece of the fitness pie</strong></blockquote><p>Of course, we all to some extent want to build lean muscle and pack on size. I’m an ectomorph myself, so I’ve always had to work extra hard to achieve hypertrophy. My issue lies with the plate-selector machines and other heavily marketed contraptions that are touted as a <em>grea</em>t way to get into shape. Yes, if you bombard your body with drop-set after drop-set on machines you can elicit muscle growth. Yes, if you are a newcomer to the gym that hasn’t experienced the slightest hint of neuromuscular adaptation, you will see gains in the beginning with machines. That being said, you won’t be adding much in terms of practical strength and will end up as that guy/girl who is “all show and no go”.</p><p>I will always place an emphasis on functional training. This includes, but is not limited to barbells, dumbbells, and calisthenics. By avoiding machines, you take on exercise movements that force you to stabilize the weight yourself. Having the ability to stabilize weight from various positions decreases you chance of injury during all real-life lifts and movements. I’ve encountered plenty of times where having a strong deadlift has benefited me in everyday life, but so far I haven’t had to bust out a quick set of hip abduction while doing yard work or moving furniture. <em>Given proper nutrition, resistance, training volume, and recovery, hypertrophy will happen</em>. Unless you are competing in a bodybuilding competition where your appearance trumps all, focus on functionality. I guarantee that you will see positive gains in appearance as well.</p><blockquote><strong>When you’re older and getting out of bed is a challenge, how much you bench suddenly isn’t of paramount concern</strong></blockquote><p>In high school, I had one goal: to get as big and as strong as possible. I feel as if this is a fairly common mindset amongst teenage boys. At this time, you feel invincible and are blissfully unaware of the future consequences your actions may have. It wasn’t until I had surgery on my right-shoulder due to poor lifting technique that my perspective changed. At physical therapy, I was the youngest one there, and it was interesting to see the older patients all share the same thought process. They had such a simple goal in mind: <em>move like I used to</em>. I realized at this moment, that from this point forward, my primary fitness goal would be to preserve my strength, flexibility, and athleticism as far into life as I could. I’d be more careful about the way that I lifted, the way I trained in general, and the way that I recovered. In recent years as a personal trainer, I’ve strived to educate my clients on how to prioritize fitness goals so that they are providing themselves with not just a better body, but also a better quality of life.</p><p>Fitness can be a gateway to a ton of benefits. Make the conscious decision to master movement in a way that can be translated into physical benefit outside of the gym walls. If you move more efficiently, you’ll feel more confident trekking through hikes, in the city, and at home. At 60, instead of talking about the things you used to do at 25, you’ll actually be doing them. When constructing a fitness regimen, aim for a well-rounded approach. Keep it simple. Make sure that what’s possible today isn’t impossible tomorrow. And most importantly, never stop.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=308c1f0d4c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The sort of stuff I enjoy: Sorting Algorithms]]></title>
            <link>https://medium.com/@brockinit/the-sort-of-stuff-i-enjoy-sorting-algorithms-21c4d10f474e?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/21c4d10f474e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Tue, 29 Sep 2015 20:19:39 GMT</pubDate>
            <atom:updated>2017-10-17T06:09:12.121Z</atom:updated>
            <content:encoded><![CDATA[<p>Defined as “a process or set of rules to be followed in calculations or other problem solving operations, especially by computer”, algorithms are a standard tool in the utility belt of developers. Although many algorithms are proprietary in nature and created to appease the needs of a unique project, there are a few that are timeless, taught in nearly every entry level computer science class, and still used in certain languages to this day. I’m of course, speaking of sorting algorithms.</p><p>Long before we had computers, humans had to rely on dreadfully slow methods of sorting data, making it nearly impossible to analyze it in the way that we do today. With the introduction of sorting algorithms, a computer could be programmed to take in a data set and sort it accordingly. In the most basic examples of bubble sort, merge sort, selection sort, insertion sort, and quick sort, this data set is typically made up of numeric values that are intended to be sorted in either ascending or descending order.</p><p>Each of these algorithms accomplishes the same thing; sorted data. The difference lies within the speed of the operation. Efficiency is of utmost importance when dealing with a large amount of data. Simply put, the faster the data can be sorted, the quicker someone can analyze it and retrieve the patterns and information they were searching for. Due to external factors beyond the control of the algorithm being implemented (processor speed, what other tasks are being run on the computer, etc..), the factor we are most concerned with is the<em> rate at which the run time grows as the data increases in size. </em>Potential run times can be expressed through what is called “Big-O Notion”:</p><ol><li>Constant time O(1) : In this case, the speed of the function is all the same, regardless of size. It could be sorting 2 items or 2000 items, either way it would still only require one step.</li><li>Linear time O(n) : This works a bit differently. The number of steps is directly related to the number of items. If there are 2 items, it has 2 processes. If there are 2000 items, there are 2000 processes.</li><li>Quadratic time O(n^2) : The slowest and usually worst case scenario, quadratic time happens when things like nested for loops occur. The iteration of one loop being held up by the iterations of the next exponentially increase the time it takes for the operation to complete.</li></ol><p>This all sounds far more complex than it actually is when put into words. To make things easier, let’s walk through and example of bubble sort vs merge sort so that the difference becomes more clear. This will be done using Javascript.</p><pre>function swap(items, firstIndex, secondIndex) {<br>  var temp = items[firstIndex];<br>  items[firstIndex] = items[secondIndex];<br>  items[secondIndex] = temp;<br>}</pre><pre>function bubbleSort(items) {<br>  var len = items.length;<br>  var i;<br>  var j;    <br>  var stop;</pre><pre>  for (i = 0; i &lt; len; i++) {<br>    for (j = 0, stop = len - i; j &lt; stop; j++) {<br>      if (items[j] &gt; items[j + 1]) {<br>        swap(items, j, j + 1);<br>      }<br>    }<br>  }</pre><pre>  return items;<br>}</pre><p>As you can see, there are two for-loops. This ups the complexity and puts bubble sort firmly in the quadratic time category. Its worst case scenario and average case scenario are both the same, implying that this is not the algorithm we want to use. Bubble sort works by taking the first number in the array, and comparing it to the next number over. If the adjacent value is larger, it is compared to the number adjacent to it. If not, the first number continues its path and is compared to that number. After one pass, the largest number is to the far right. Bubble sort repeats this process until the array is sorted from lowest to highest, left to right. Now, let’s take a look at merge sort.</p><pre>var a = [34, 203, 3, 746, 200, 984, 198, 764, 9];<br>function mergeSort(arr) {<br>    if (arr.length &lt; 2) return arr;<br>    var middle = parseInt(arr.length / 2);<br>    var left = arr.slice(0, middle);<br>    var right = arr.slice(middle, arr.length);<br>    return merge(mergeSort(left), mergeSort(right));<br>}<br>function merge(left, right) {<br>    var result = [];<br>    while (left.length &amp;&amp; right.length) {<br>        if (left[0] &lt;= right[0]) {<br>            result.push(left.shift());<br>        } else {<br>            result.push(right.shift());<br>        }<br>    }<br>    while (left.length) result.push(left.shift());<br>    while (right.length) result.push(right.shift());<br>    return result;<br>}<br>console.log(mergeSort(a));</pre><p>The difference here, is that merge sort has an average and worst case scenario of O(n), or linear time. Quadratic time is not a concern, regardless of the data size. Merge sort works by splitting the array into two equal or nearly equal halves. It then sorts them separately using recursion, and then finally, combines the sorted halves back together while sorting the merged result.</p><p>This covers the basics of sorting. To learn more about different sorting algorithms and to see some sweet animations of the sorting algorithms in action, check out my Github repo at the link below :</p><p><a href="http://brockinit.github.io/sorting-algorithms/">http://brockinit.github.io/sorting-algorithms/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21c4d10f474e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Closures in JavaScript: So easy your grandmother could learn them.]]></title>
            <link>https://medium.com/@brockinit/closures-in-javascript-so-easy-your-grandmother-could-learn-them-4b760725675e?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b760725675e</guid>
            <category><![CDATA[closure]]></category>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Thu, 10 Sep 2015 00:00:55 GMT</pubDate>
            <atom:updated>2015-09-10T00:00:55.238Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there, Grandma…</p><p>This may be news to you, but the object oriented language Javascript, has some pretty cool features. It can do awesome things that make building impressive software even easier than ever before. One thing Javascript can do, is stack functions inside of functions using a format called a “closure”.</p><p>I may have lost you on that first part, so allow me to explain. Functions are simply put, the logic that we define that allows computers to take action. For example, I could write a function that tells the computer to print, “Hi, Grandma!” This is what that would look like:</p><pre>function sayHello (name) {<br>   console.log(&quot;Hi,&quot; + &quot; &quot; + name + &quot;!&quot;);<br>}<br>sayHello(&quot;Grandma&quot;);</pre><p>See the word “name” in parentheses on the first line? That is called a parameter. It lets us fill in the statement and say “Hi” to whomever we please. In this case, I asked the computer to say “Hi” to you on the bottom line. By the way, that bottom line is called “invoking the function”, or in other words, telling the computer to execute the command! While using one function at a time can be useful for basic tasks, it’s sometimes helpful to enlist the assistance of closures to complete more complex operations.</p><p>A closure is a function that sits inside of another function. Weird, right? The reason this is so useful is because the inner function is able to utilize not only its own parameters and variables, but also those of the outer function. What’s a variable, you ask? Those are easy to understand. A variable can be thought of as a place holder for information. By telling the computer to store a variable, you are telling it to save this information for later down the road. Remember that bingo tournament coming up? You brain acted like a computer by storing the date for that event. You’ll recall it when you need to, just a like a computer recalls variables when necessary.</p><p>Bingo aside, let’s talk closures. Here is an example of a basic closure to help you visualize what they look like:</p><pre>function showName (firstName, lastName) {<br>  var sayName = &quot;Your name is&quot;;</pre><pre>// Look below this line now for the inner function</pre><pre>  function constructName () {<br>    return sayName + &quot; &quot; + firstName + &quot; &quot; + lastName;<br>}</pre><pre>return constructName();</pre><pre>}</pre><pre>showName(&quot;Super&quot;, &quot;Grandma&quot;); <br>//This returns &quot;Your name is Super Grandma&quot;</pre><p>This isn’t as confusing as it looks. The inner function is greedier than Gretchen in the buffet line. Like I mentioned earlier, it has access to its own variables/parameters as well as those located in the outer function. This is particularly useful because it enables us to be more creative with the things we make the computer do. Look at the inner function. It uses “firstName” and “lastName” from the outer function as well as its variable to string together a full statement. Below the inner function, we see the computer putting this all together with, you guessed it Granny, the function invocation.</p><p>Closures can’t have all the fun though. There are some limitations. One of the most notable are the access rights outer functions have (or don’t have). While inner functions can streeeettttcccchhhh outward and use variables and parameters from outside functions, the same cannot be said for those function sitting at the top. This is due to a conflict in scope.</p><p>Scope defines what each function can and can’t access. Think about this: you can leave your house to go to the Antique Expo downtown, but the people at the expo aren’t able to show up at your house and take antiques from your collection. Your house can be thought of as being within the local scope. This represents the inner functions. The Antique Expo represents the global scope. Inner functions will always have access to functions that encompass them as well as variables in the global scope; or those defined outside ALL the functions.</p><pre>var sayName = &quot;Is your name really&quot;;</pre><pre>function showName (firstName, lastName) {<br>     sayName = &quot;Your name is&quot;;</pre><pre>// Look below this line now for the inner function</pre><pre>function constructName () {<br>  return sayName + &quot; &quot; + firstName + &quot; &quot; + lastName;<br>}</pre><pre>return constructName();</pre><pre>}</pre><pre>showName(&quot;Super&quot;, &quot;Grandma&quot;); <br>//This returns &quot;Your name is Super Grandma&quot;</pre><p>Why didn’t the computer output something different this time? The variable up top should have changed sayName, right? This is false because the variable “sayName” was reassigned a new value inside the outer function. When the function is invoked down below, the variable is set to the value up top (global scope), but is quickly changed once the outer function is initiated.</p><p>There is much more to closures than I’ve written about here, but hopefully this makes more sense than it did when we started. See you at bingo.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b760725675e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevLeague Day 1: All the Downloads]]></title>
            <link>https://medium.com/@brockinit/devleague-day-1-all-the-downloads-ab96bd04e8d5?source=rss-e3ce6144e6f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab96bd04e8d5</guid>
            <category><![CDATA[devleague]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Brock Lanoza]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 20:02:21 GMT</pubDate>
            <atom:updated>2016-02-09T03:14:12.693Z</atom:updated>
            <content:encoded><![CDATA[<p>Up until yesterday, I had wondered what to expect. I knew that my time spent at Dev League would be an arduous and mentally exhausting experience, but that was about it. Walking into the “classroom” on the first day immediately invoked feelings of anxiousness, excitement, and the thought, “A/C in Hawaii? I really am on a spaceship”.</p><p>It becomes rather easy to get discouraged when envisioning yourself working for 11 hours a day, 6 days a week for any extended period of time. Couple that work load with other responsibilities and your hopes of any type of social life are rapidly crushed. The idea of “burning out” down the road treads water in your thoughts.</p><p>Luckily, I’ve stumbled into a great cohort that seems to be made up of a group of dedicated, passionate, and positive-minded people that are fully prepared to commit a sizable chunk of their waking hours with me in our journey to becoming coding ninjas. Sometime over the next 12 weeks, I hope to go from a lowly programming neophyte to a respectable JS developer with practical skills that I can actually put to use.</p><p>Although I’m less than two days into my time at Dev League, I’ve already learned a few things about myself:</p><ul><li>Standing desk = requirement. Health and fitness have always played a large role in my life and despite the fact that I’ve spent many hours behind a computer screen, I’ve never gone this many consecutive hours in a seated position. My cervical spine approves of this message.</li><li>I genuinely enjoy this work. I knew this was true to an extent prior to coming to Dev League, but I was certain that the first long day would really challenge this notion. *Disclaimer*: I reserve the right to revoke this statement two weeks from now when I’m repeatedly bouncing my head off of the keyboard amidst confusion, frustration, and feelings of worthlessness.</li></ul><p>I came to Dev League because I love to learn. I feel that this environment will also facilitate a more engaging, rewarding, and practical learning experience than any traditional institution (college/high school). The immersive environment and “learning by doing” structure of Dev League seems promising and I hope to tune back in later to reflect on my time here.</p><p>See you all on the other side.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab96bd04e8d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>