<?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 Tyler Garlick on Medium]]></title>
        <description><![CDATA[Stories by Tyler Garlick on Medium]]></description>
        <link>https://medium.com/@tylergarlick?source=rss-28f7a17710d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SSVWhFPgn6wkKPBQyyQDSQ.jpeg</url>
            <title>Stories by Tyler Garlick on Medium</title>
            <link>https://medium.com/@tylergarlick?source=rss-28f7a17710d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:06:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tylergarlick/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[Helping hands, not handouts]]></title>
            <link>https://medium.com/truth-over-party/helping-hands-not-handouts-71355d664ec4?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/71355d664ec4</guid>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Thu, 19 Jul 2018 15:26:24 GMT</pubDate>
            <atom:updated>2018-07-19T15:26:24.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kNHK0U1gqT6JaxeTf9yzQQ@2x.jpeg" /></figure><p>Why do we say, “…we have helping hands, not handouts…?” That phrase barricaded that truth inside me since I was younger. I have had many opportunities to be a helping hand. I’ve also dealt a few convenient handouts (since usually it’s all about convenient).</p><blockquote>A handout is unsolicited, awkward, shunned, and out of place.</blockquote><p>Helping hands are always aware of the end goal. It’s quite literally the helping hands responsibility to provide all necessary resources to teach the person being helped the appropriate experiences to maintain the next level of learning. We gravitate towards people like this — usually they have a helping hand guiding them along as well. It is inspiring.</p><p>A handout is unsolicited, awkward, shunned, and out of place. Why does the feelings of charity and love systematically turn to chaos of expectations? Are the expectations realistic? The handouts are not an easy task.</p><p>We all know the few bad apples that “rig” the game. Ironically, those people have used the handouts maliciously, and like all extreme cases, the anomalies tend to make the normal suffer. The problem runs deeper past the resourceful, malicious predators advantageously preying on the weak. Imagine the system we could have with using their resources to elevate and help those around them. That is besides the point, but an interesting one none the less.</p><p>Another truth resides in this metaphor. As a beneficiary of a helping hand, and. the aforementioned primordial system, we learn that the hand being helped can let go of help at any given time. We then need to question why the benefactor of a helping hand would let go of help?</p><blockquote>No one is bound to a helping hand</blockquote><p>Because there is choice. A decision to let go. No one is bound to a helping hand. Absent choice we loose the ability to control, and that handout causes chaos because there is no help beyond a resource.</p><p>Why would you then support a system that fundamentally doesn’t work? Isn’t that “charity?” Clearly, a helping hand is more charitable than a handout. It’s even more beneficial to the one helping than receiving.</p><p>Stop taking handouts and give more helping hands!! A handout is tossed in the wind because it’s as common as toilet paper and the reason toilet paper is made. To capture the consciences blinded by systematic shit.</p><p>Society needs more choices and not support system absent of choice and consequences. It is only moral and true that you only pay for your choices and consequences.</p><blockquote>Pay it forward with a helping hand.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71355d664ec4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/truth-over-party/helping-hands-not-handouts-71355d664ec4">Helping hands, not handouts</a> was originally published in <a href="https://medium.com/truth-over-party">Truth Over Party</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Reasons to use GraphQL and Prisma]]></title>
            <link>https://medium.com/tyler-garlick/5-reasons-to-use-graphql-and-prisma-bd0c42448962?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd0c42448962</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[prisma]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Thu, 19 Apr 2018 06:05:00 GMT</pubDate>
            <atom:updated>2018-04-19T06:05:00.254Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been using <a href="http://graphql.org/">GraphQL</a> for about a year now. I absolutely love it. At the moment, when I’m building an application–I’m going to use GraphQL. Let me take you down the path of how I got here, and why we should all be thinking about it, and ultimately using it now.</p><p>It all started like it normally does being a developer at <a href="http://github.com/">GitHub</a>. I’m not entirely sure when GitHub did the change to GraphQL, but I remember the day in class vividly. We were trying to get repository information for a user. I went to GitHub’s api documentation and saw that they had release a new version. I stumbled upon my first GraphQL endpoint. According to GitHub this was staying around for now, and they wouldn’t be releasing a REST API because this was the replacement for it.</p><p>I couldn’t believe it. Not only had GitHub drawn a line in the sand, but they have drawn a line in the sand with how to build software. I couldn’t agree with them more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PpS33q5FE68nBJwsz0Lp0w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/1UxXuT0Ml_E?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alessio Lin</a> on <a href="https://unsplash.com/search/photos/graph?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I was on a mission at that point:</p><ol><li>Why would I use it?</li><li>When should I use it?</li><li>How do I incorporate it into my daily development?</li></ol><p>I started like I tend to do a lot now at the <a href="https://github.com/chentsulin/awesome-graphql">awesome-graphql github repo</a> and was blown away at what was there.</p><p>Here is what I noticed, even in GraphQL’s infancy and we’re seeing the benefits of what happens today when a community gets behind something because it just makes sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFDeSO9ljiYaszZk1FXm8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/wn-KYaHwcis?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jesus Kiteque</a> on <a href="https://unsplash.com/search/photos/graph?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Productivity</h3><p>One of the most challenging things as a developer is to always be asking, “Is this the right tool for the job?” and “Can I be better at what I’m doing by using a different tool?”</p><p>I admit at first, I was super clumsy with all the different ideologies. It was hard to see that what GraphQL was building for me (by thinking about my data in types which is always more natural to me) was a REST endpoint. A single endpoint that understood what a GraphQL query is, and returns the query in a formatted response.</p><p>The productivity gained from thinking about your data’s relationships was exponentially productive from traditional approaches of database modeling and application modeling. Both, equally important, and usually the same types at first. GraphQL allowed us to build a server that communicated in types. That alone made me productive and excited.</p><h3>Simplicity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twylzDYrf2yNYwQ9C07eog.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/PM4Vu1B0gxk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Spratt</a> on <a href="https://unsplash.com/search/photos/simplicity?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><a href="https://www.prisma.io/">Prisma</a> (kudos) has simplified the boundaries of a database service, and an application service (both residing usually within the same application). These abstractions helped us understand that we wanted to think about our data and application services in types, and once again these types weren’t mutually exclusive with each other.</p><p>Recently, <a href="https://www.prisma.io/">Prisma</a> team released bindings that allow us to share data between different services using familiar constructs and ultimately stitching together schemas providing a single source of querying all the data that our domain focuses on.</p><p>Wow, I was shocked how easy it was yet the power behind separating our services in familiar constructs of micro-services without being clunky or weird.</p><h3>It’s Still REST</h3><p>The real kicker with all of this: It’s still REST. That one took me awhile to come to terms with. As I inspected the network traffic all the queries were going to the same endpoint. The data came back in a unified format. It was simplistically elegant.</p><h3><a href="https://www.prisma.io/">Prisma</a>/<a href="http://graph.cool/">Graph.cool</a> is awesome!</h3><p>When I first started my journey graph.cool was one of the best ways to get started with GraphQL because it allowed me to think in types, and generate a database that would conform to my types.</p><p>I must admit for teaching graph.cool was amazing because it allowed my students to start thinking about their domains without getting stuck on the gritty details of databases, functions, etc.</p><p>As the graph.cool platform grew, the team realized they wanted to give back to the community and open source their platform. I was skeptical at first as the perceived undertaking. I was blown away when they released a version 1.0 of Prisma and it was different, not as sexy as graph.cool, but understandably simple and elegant in it’s own fashion.</p><p>I’ve grown to love how Prisma thinks about data and how it works. I’ve even dabbled in using TypeScript to get some benefits of their binding types, but still using TypeScript like JavaScript.</p><h3>Use as much or little as necessary</h3><p>As with many skeptics you might ask what was the catch. There isn’t one. Because it was built upon a foundation of principles we are using it fit in using a much or little as you needed.</p><p>It allowed us to look at our REST api’s and wrap the endpoints in a GraphQL type and stitch together out data models so we could finally see data (just enough data might I add) without harming our old legacy tooling.</p><p>Mind blown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0_qyTxdta9nnufQMEyDcag.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/C2a4RGapd8s?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Peter John Maridable</a> on <a href="https://unsplash.com/search/photos/enlightened?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve decided in my role at work to embrace this pattern (as our industry partners have started using it as well) and teach our students. From my perspective this is where we are going. Our students are much more valuable by having a solid knowledge of GraphQL, relational databases, and data modeling concepts. We embraced it, and never looked back.</p><p>This is one of the biggest reasons why <a href="https://heliotraining.com/outcomes?source=tylergarlick.com">we have the best students</a> at <a href="http://heliotraining.com/?source=tylergarlick.com">Helio Training</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd0c42448962" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/5-reasons-to-use-graphql-and-prisma-bd0c42448962">5 Reasons to use GraphQL and Prisma</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why are we so anxious in classrooms?!?]]></title>
            <link>https://medium.com/tyler-garlick/why-are-we-so-anxious-in-classrooms-4b5baab27cfd?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b5baab27cfd</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Wed, 01 Nov 2017 11:40:16 GMT</pubDate>
            <atom:updated>2017-11-01T11:40:16.774Z</atom:updated>
            <content:encoded><![CDATA[<p>Over a year ago I joined <a href="http://heliotraining.com/">Helio Training</a>, and became an instructor at our bootcamps. It’s been a very exciting and interesting space to be part of. I never thought I’d be teaching students whom have no industry knowledge — some haven’t even touched a computer before. The aftermath of the course in a mere 13–16 is outstanding. The joy of seeing lives changed by new careers brings tears of joy.</p><p>The joys of teaching is what we all cling to as instructors. It keeps up going, when bombarded by inquires from students and provides sufficient energy to endure to the end of a course.</p><h4><strong>IT’S A JOURNEY!</strong></h4><p>When’s the last time you had to learn something completely out of your comfort zone and unfamiliar? I think we struggle in this space, and I’ve observed countless hours of commitment spent sometimes in desperation of seeking knowledge or simply a job. It’s hard!</p><p>To these people, I applaud your efforts. I stand by you and support you. Sadly, this is not a majority. I actually don’t get some of the students now-a-days. I’m not sure why we think we can learn by absorption and osmosis — it never works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkJjVienOb3w1L1vtgejuA.jpeg" /><figcaption>I know Kung-Fu — Neo</figcaption></figure><h3>In the Matrix</h3><p>I’d love to live in the Matrix where knowledge is a simple as a disc loaded into your conscience and all the muscle-memory attributed to it. In the Matrix, Neo declared, “I know Kung-Fu,” and Morpheus decided to test that out in the movie. The real question is did he actually learn Kung-Fu or was it just a representation inside of the Matrix?</p><p>I suppose one day we might have a system that mimics the Matrix from that perspective. I wonder if we will become even more lazy as google, the internet, and straight-up information have saturated our daily lives providing an information-overload we try to escape all the time.</p><p>Perhaps we will all be equally smart with knowledge at our fingertips. How boring! Shouldn’t we celebrate cultural differences, and knowledge passed down form generation-to-generation? Would we really understand the information? I don’t think so.</p><p>Look at society right now. We are a hot-mess of information-overload sprinkled with half-truths and scared to talk to each other in a respectful manner (politicians are the worst). What if we had absolute knowledge of everything. I bet we’d still try to sway others in our beliefs and passions. The frivolous pursuit of knowledge would be silenced by looks of disbelieve when someone with the exact same “knowledge” would disagree. Would violence manifest itself because we probably would have even worse forms of communication in this system. Or would we transcend into a form of uber intelligence?</p><p>I digress. Our situation now is pretty pathetic. I’m not sure if it’s fear, lack of motivation, procrastination, or boredom that disrupts our classrooms today. Maybe it’s everything combined. I know we have fear when we’re learning something drastically new (no other experience is similar and we’re totally out of our comfort zones). In my classes, I call it the freak-out. Quite literally there is a time-frame right in the middle of the course when our brains become anxious with the learning. I imagine that our cognitive load is heavy, and it’s hard to keep going (it’s been awhile since I’ve been a student in a classroom — I try to empathize as best I can).</p><p>I’ll give you the anxiety attacks. I could have those given the right circumstances. The rest of the symptoms are different. In some ways we can control a majority of them. In others, maybe it’s something like my A.D.D. where I seriously could not focus without medication. There is something that is still missing. I’m not sure what it is, and I often times blame work ethic as the cause — even though I know it’s not that.</p><p>A lot of times I know that a lot of confusion is onset by not knowing what to ask exactly. Lack of vocabulary or conceptual theories to support the necessary questions to provide clarity. I can accept that as a barrier or struggle. A course is usually designed to guide students through the myriad of new vocabulary (especially in technology).</p><p>Welcome to the club. I don’t know what it is that makes the classroom oftentimes a place of frustration. It’s hard to see students walk home lost, hopeless, and maddened because they can’t quench their thirst of knowledge. Oftentimes I reflect on what I can do to improve and minimize burnout — it is part of my job.</p><p>Next time you’re in a classroom learning something new. Take mental note of the steps you use to open your mind to soak in the new knowledge. Share those steps with your family, and kids. Help them become curious to ask the right questions (even if they don’t know how to articulate them).</p><p>Stay curious.</p><blockquote>It’s not a faith in technology. It’s faith in people - Steve Jobs</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b5baab27cfd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/why-are-we-so-anxious-in-classrooms-4b5baab27cfd">Why are we so anxious in classrooms?!?</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Bootcamps are the future… all industries will be impacted]]></title>
            <link>https://medium.com/tyler-garlick/coding-bootcamps-are-the-future-all-industries-will-be-impacted-9317bbcedc47?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9317bbcedc47</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Thu, 24 Aug 2017 09:40:20 GMT</pubDate>
            <atom:updated>2017-08-24T09:46:56.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xs_1SsknKt1q4P32063urw.jpeg" /><figcaption>Check out <a href="https://heliotraining.com/?source=tylergarlick">Helio Training</a></figcaption></figure><p>A lot has changed in education. We’ve decided in technology to hire individuals based on performance rather than a degree. I have positive and negative feelings towards our industry, but that point is mute–bootcamps are here to stay.</p><p>There are a plethora of reasons why bootcamps have emerged as venue for newcomers into the software space. I’d like to us to focus on how we got here, and how others will be impacted.</p><h3>Criteria of the Bootcamp</h3><p>We should set up some expectations so we can syntesize our thoughts accordingly. First, we are discussing a full stack bootcamp. Full stack bootcamps are important because they teach a student how to build a mininimum viable application. This knowledge will help the students contribute to a team (frontent or backend). It’s not to say that a frontend or backend bootcamp aren’t worthwhile–we want to observe what happens when we teach skills that stretch beyond basics. The duration of the bootcamp should be more than 12 weeks to ensure that the required skills for a full stack application are attainable.</p><p>A bootcamp’s message should be upon completion the student will have the skills to be in a junior role. Honestly, this is the biggest misconception that I see. It’s true that the amount of practice during the bootcamp will correspond to the level of salary and strength of the candidate. A bootcamp that promises more should be approached with extreme caution.</p><p>The curriculum is subjective, but should teach enough skills that the student can be proficient in doing anything in the full stack. We use JavaScript because we don’t have to lose focus on another language for the backend. This makes life easy as we can use concepts in the browser and on the server (with big air quotes). With that in mind, a Node/JS bootcamp that doesn’t teaach the ins and outs of NPM is a complete waste. I found that as I hired bootcampers I would be underwhelmed with the knowledge of how the language worked. For example, I don’t expect them to be NPM masters, but I do expect to be able to delete the node_modules folder and they know what to do from there.</p><p>We need these pillars so we can discuss why we are here.</p><h3>The 20 to 1 Problem</h3><blockquote>We have 20 jobs for every engineer (in Utah), and it’s only going to get worse</blockquote><p>Technology is becoming a huge focus on a ton of diverse industries. As the need for engineers increases, we are fixing the supply of new engineers every year. In fact, growth is exponential and the number of “new” engineers is linear. We have a huge problem. This problem is good for existing engineers becuase it has as direct correlation with our salaries :)</p><p>For a company, it’s a lot harder now to keep talent. For that reason, companies are more willing to take a junior candidate, invest some time, and grow a new developer. The problem is: the company doesn’t have time to develope a curriculum, invest resources to new candidates, find new candidates, etc.</p><p>The concept of a bootcamp was born to provide some relief to the technology space. Instead of waiting for more CS gradudates to matriculate, employeers assume that an apprenticeship would provide enough foundation to contribute–data shows that the assumption is correct.</p><h3>Other Industries</h3><p>This is pure speculation, but as these bootcamps prove the model–I think we’re going to see a ton spring up as supply and demand drive companies to hire. Other countries have students work in an apprentiship role, and as they grow and study under the craftsman they aquire skills that even the best university couldn’t duplicate.</p><p>The apprentiship model establishes a network of people that can maintain standards, provide help/feedback, and inspire new people to enter the industry. I’m not sure why we don’t have a more formalized model here in the United States–at least one that meausres the progress under the craftsman.</p><h3>Objective Driven instead of Ego Driven</h3><p>We’ve all had that professor/teacher that you wrote a paper for and completely disagreed with their views, but succumbed to their egos strictly to progress. What use is it–to have different thoughts and philosophies that are squashed because someone didn’t agree. To be fair, we have a lot of sociatal problems that orbit listening and communicating, but I digress.</p><p>Building an objective driven path or measurement would alleviate (especially if we could measure progress objectively) the friction of a person, and/or ego. We call this competency driven learning, and I think that this learning is the future. Competencies are small measurements of success that are binary. Simplistically it’s a small objective that has a true/false outcome. For example, “Students can use the const keyword correctly”–you either can or can’t do that.</p><p>Until we find a common currency to measure this progress we will always be lying on our resumes upon graduation saying we are experts in X, Y, and Z. The nice part about having a currency also is we can acquire and measure knowledge outside of a classroom, and as educators, we have the ability to associate different learning paths dependent on prior knowledge. We can also build a curriculum customized for a particular student without needing to repeat or focus on unnecessary topics.</p><h3><a href="https://heliotraining.com/?source=tylergarlick">Helio Training</a></h3><p>Check out my <a href="https://heliotraining.com/?source=tylergarlick">employer</a> if you’re interested in getting into software development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9317bbcedc47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/coding-bootcamps-are-the-future-all-industries-will-be-impacted-9317bbcedc47">Coding Bootcamps are the future… all industries will be impacted</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular 2, The Black Sheep]]></title>
            <link>https://medium.com/tyler-garlick/angular-2-the-black-sheep-9234aa943ed3?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9234aa943ed3</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[angular2]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Fri, 16 Jun 2017 22:56:02 GMT</pubDate>
            <atom:updated>2017-06-16T22:56:02.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjBkNFqPiojpXGIfx-tWJA.jpeg" /><figcaption>Photo Credit: <a href="http://maxpixel.freegreatpicture.com/Black-Sheep-Heidschnucke-Grey-Horned-Heidschnucke-2150627">http://maxpixel.freegreatpicture.com/Black-Sheep-Heidschnucke-Grey-Horned-Heidschnucke-2150627</a></figcaption></figure><h3>Google’s Web Strategy</h3><p>After Google’s latest I/O event it left me pondering — where was Angular amid all the latest hotness… There was a single talk for the whole conference, and Google said loud and clear “We ❤️ Web Components!”</p><p>Google’s strategy is seemingly clear — you build applications using Web Components (and Polymer to help).</p><p>This signal from Google puts Angular 2/4/(hell if I know) at the bottom of my list of frameworks to use. Honestly, it’s kind of dead to me.</p><h3>How did Angular die?</h3><p>Death among frameworks usually involves quality, lack of documentation, over complexities, or better options. I think that it’s suffered some if not all of those symptoms over time.</p><p>Don’t get me wrong, I loved Angular 1 when front end frameworks and single page apps were born. I don’t wish to talk about developer abandonment here, but that played a huge role into the current situation.</p><p>I think fundamentally Angular was wrong about components in 2.0, and the genealogy of how Angular built components from the early days has made it obsolete.</p><h3>Web Components != Angular Components</h3><p>To clarify and shed light on why Angular really screwed up components we must first define Web Components.</p><p><strong>Abstraction</strong>. It’s that simple. As web developers we use controls like a textbox. The “guts” of a textbox are hidden away from us. The browser has some HTML, CSS, and JS that make it so we can write &lt;input type=”text” /&gt;. There are all sorts of events firing when I hover, type, click, etc. Isn’t it nice that we don’t have to think about all of that? That is a web component.</p><p>When we build a custom component using something like Polymer we leverage native specifications to create a new HTML elements. Using a component is simple we import in an HTML file and that contains all the pieces necessary to render that element. Done! Publishing the element to something like bower/yarn/npm is super easy. The only integration needed is a polyfill, if necessary, to support the full specification. No framework installation is needed.</p><p>Superficially Angular components mimic features of Web Components. Implementation of how the component isn’t really the topic of interest for this article. Publishing the components to share with others is.</p><p>Browse the documentation and there is no obvious path to publishing their own components via NPM. How the hell do you build a custom component to share with everyone?!? Well it depends on who you ask, and that is the real grind.</p><h3>To publish or not to publish…</h3><p>Even with anemic documentation on the process it comes with a side effect of requiring Angular and more as a dependency. This is where they screwed up in my opinion.</p><p>I have to ship and package Angular with a component I built. Yet, a specification exists for web components and a good way to package them.</p><p>Again it’s not saying that you couldn’t do that or use them inside of Angular, rather, there no direction on this.</p><p>On top of that, there isn’t a good ecosystem for distributing these components out.</p><p>I think the whole framework is over engineered and over complicated by the infatuation with TypeScript and dependency injection.</p><p>Again just my observations, and maybe I’m totally wrong. To me though, this is why at Google I/O 17 we heard very little on Angular.</p><p>If I were Google, I’d hand the project to Microsoft — they seem extremely interested in contributing and maybe with more “passion” and direction they could change it.</p><p>For me and my house, I choose Polymer and React.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9234aa943ed3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/angular-2-the-black-sheep-9234aa943ed3">Angular 2, The Black Sheep</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to embrace failures]]></title>
            <link>https://medium.com/tyler-garlick/learning-to-embrace-failures-ecb13733c631?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecb13733c631</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Wed, 11 Jan 2017 17:02:26 GMT</pubDate>
            <atom:updated>2017-01-11T17:02:26.029Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Stay thirsty for knowledge, and hungry for failure</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zdmNqus8YW6fPI9FNVRpqw.jpeg" /></figure><p>As a teacher, I love observing learning. The way the mind works is fascinating. We have an impressive body and mind. I’m continuously fascinated with how our minds work. Particularly how the brain stores new information has always fascinated me. Conditioned societal prejudices can silence our minds — the main culprit is our fear of failure.</p><p>Failure should be welcomed and explored in learning. Let’s be clear, when discussing failure, I reject laziness and lack of motivation as a definition of failure.</p><p>I define failure as an alternate way of doing something that doesn’t result in the desired outcome (or most optimized outcome). Often we see creators “fail,” and usually that type of failure is ok. I often ponder what societal constraints we have surrounding experimentation and failure.</p><p>Personally, I’ve discovered that there is a trifecta of skills needed to learn at the maximum efficiency. The skills are experimentation, refinement, and failure.</p><h4>Style of Learning</h4><p>I’ve always been inquisitive of how things work. At a very young age, I would ask “Why,” and challenge ideas and philosophies that I was taught. I must admit in my teenage years my parent’s high standards for my success in school. In those years, I often relied on others belief systems and didn’t expand my experimentation of theories much. I must say, I did know what I wanted to do when I grew up. I wanted to be an engineer. Particularly, a Software Engineer on this new internet thing (I knew in high school that it would be necessary and applications would be built on top of browsers).</p><p>I was passionate about technology. I quickly consumed all the classes that were offered at my high school. When I was a junior, I created my own “classes” by becoming TA’s to the teachers that maintained the web pages and network at my school. I was entrusted with a lot of access and frequently helped update our school’s website. (Back then it was pure static HTML)</p><p>I learned that I was a tactile learner. Asking why while prodding source code yielded the quick discovery of the things I needed to build applications. After messing around with HTML layouts, I’d quickly experiment and refine my ideas. Some of them were great. Others sucked. I wasn’t afraid of putting in a wrong tag and had mastered most layout elements. My teachers marveled at the things I was creating (to me it was always “ok, ” and I always had something driving me towards another idea).</p><p>When I plateaued at one thing I would expand my horizons on something else. Always seeking guidance from people that I knew were good. That ultimately landed me a job with a software engineering company to further explore my passions. <br>I always chuckled at people who praised my efforts. I felt like I was a hack in a way. Always trying to break and stretch how things worked. Mainly to grasp the nature of the things I was using. I didn’t realize that what I was doing was failing, experimenting, and refining my knowledge.</p><p>This philosophy drove my learning in my higher education courses (particularly in my engineering courses since it was easy to experiment).</p><p>Regardless of how you consume new information — there must be a process of experimentation, refinement, and failure. In fact, one of Scrum’s philosophies is to fail quickly and pivot. I’ve seen various ways that others consume new information with the other styles of learning. <br>I haven’t yet found evidence that the learning style is the culprit or catalyst of fearing failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uE0mY_hoctt1W9wIzIzY2g.jpeg" /></figure><h4>Your Environment</h4><p>I think in our early years of developmental we’re impacted tremendously with our concept failure. I feel like we start a conditioning of whether a failure to us is catastrophic or merely a common element of life.</p><p>To the parents out there — how many times have we protected our children from failure? Obviously, as responsible parents, we need to cushion some failures (like burning a hand in a fire, etc.). However, I often catch myself protecting my little ones from experiences and situations that would benefit them to experience. I often watch my little ones absorb new information, and do my best as a parent to create a conducive environment for experimentation, refinement, and failure.</p><p>An experience that I had with my son was the time we decided to build a robotic crane. I have to admit that I was as equally excited about the project. I often had to hold myself back from letting myself short circuit some of the design choices he was making. We designed a crane that was functional and pragmatic. We drew iterations of the crane and finally he came to the conclusion that it was feasible (with the things we had around the house) and doable. The project gave my son the confidence to question design decisions (to this day he asks about everyday things that he thinks are “bad” decisions).</p><p>Although an environment can be a huge impact on an individual — it’s not the only culprit of fearing to fail.</p><h4>Lack of Science</h4><p>The scientific method is taught to us at a young age. The scientific method encapsulates the three skills needed to learn. I always gravitated towards science. The labs in the classroom were laborious (unless we were in chemistry where an “A” was awarded to the students that created the biggest explosion) and repetitive. I never understood why we continuously patterned our activities into a consistent format. I realized that I embraced the methodology by incorporating it into my daily life. Simple decisions would be compared and contrasted (on the fly I might add) to the scientific process. Evidence of outcome was how I continued to make decisions.</p><p>That, of course, implies that failure must happen to achieve success — unless you’re perfect. Refining without simple success scenarios mixed with failure is impossible. It’s the currency of refinement.</p><p>I’ve become unfamiliarized with the curriculum (common core) taught to students — especially the scientific method. Is the scientific process applied as rigorously to young students as when I was going through school? I feel that young students encounter it, but don’t absorb it. We’re extremely fascinated with other scholarly measurements like standardized testing that suffocate our nature intuition and learning. I’ve consistently observed that we’ve lost a tremendous amount of skills in critical thinking, logic, and reasoning.</p><h4>Start Now!</h4><p>These observations are something that I share with my students on the first day of classes. I do it because the faster in my classroom we can shed the fear of failure — the faster we can learn.</p><p>When you sit in a meeting/class/social setting and you are scared to ask a question — you are letting societies notion of failure consume you. You have a right to knowledge (beware that knowledge isn’t always what you anticipate). Let me reiterate; you have a right to knowledge. This right is part of what you pay for as “tuition” in a classroom setting. Shed yourselves of this fear of failure and embrace the small failures as commodities. My Dad has said it best over the years, “When one is humble, they are teachable…” Imagine an environment where the teach and student(s) are learning together because as a student explores various areas of study they encounter anomalies — then share the hidden knowledge with the classroom.</p><blockquote><strong>Stay thirsty for knowledge, and hungry for failure.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecb13733c631" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/learning-to-embrace-failures-ecb13733c631">Learning to embrace failures</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Falling for Web Components]]></title>
            <link>https://medium.com/tyler-garlick/falling-for-web-components-a96d0ff51b31?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a96d0ff51b31</guid>
            <category><![CDATA[polymer]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[web-components]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Thu, 01 Sep 2016 22:52:53 GMT</pubDate>
            <atom:updated>2016-09-01T22:52:53.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*zcqcEPFkyczIJj-kiAhLyA.jpeg" /></figure><p>The first day I saw <a href="https://www.polymer-project.org/">Polymer</a>, I LOVED IT! It just felt right, kinda like when you hand fits nicely in theirs. The code was concise, neatly groomed. For years, I was in lust with Angular and loved how she disrupted the SPA space. Polymer, made me forget about Angular, and I never really looked back.</p><p>What was it about Polymer that captivated me? ABSTRACTION. How nice was it that I could include a file at the top of my page and have a new custom tag. &lt;google-map&gt; that provided a succinct interface peeling away the complexity of Google’s map API.</p><pre>&lt;!-- Polyfill Web Components support for older browsers --&gt;<br>&lt;script src=&quot;components/webcomponentsjs/webcomponents-lite.min.js&quot;&gt;&lt;/script&gt;<br><br>&lt;!-- Import element --&gt;<br>&lt;link rel=&quot;import&quot; href=&quot;components/google-map/google-map.html&quot;&gt;<br><br>&lt;!-- Use element --&gt;<br>&lt;google-map latitude=&quot;37.790&quot; longitude=&quot;-122.390&quot;&gt;&lt;/google-map&gt;</pre><p>This is what I was looking for, the HTML abstraction that got out of the way. Behind the scenes it loaded JS, HTML, CSS so I could focus on the task at hand. Composing new reusable components was easy. No weird directive syntax like Angular. Plus, she played nice with everyone…. on the <a href="https://www.youtube.com/watch?v=hKWmFWRVLlU">hotness scale</a> she is that unicorn.</p><p>When you start building components the CLI generates a HTML page that allows you to visualize your API, a demo page, and testing baked right in. Wow! I could share my element with the world and it would do a lot of that hard lifting for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*A2Pq-9V-zNwLbGxXMS94zg.png" /></figure><p>At first, I was tempted to bring Angular along with me because my new Polymer friend didn’t seem to provide things like routing, controllers, etc. it was then I realized I didn’t need to because you could use existing frameworks or a web component that did that for you. I almost cried as I looked at Polymer in the eyes, your my soulmate.</p><p>Just like a normal relationship we got out of the honeymoon stage and the community that was also in love with Polymer worked hard to release 1.0, but then seemed disinterested in her. I was forced to start looking elsewhere because I was superficial and wanted validation from my friends that my new love was the hot sexy one that I knew she was.</p><p>I started dating other frameworks like <a href="https://facebook.github.io/react/">React</a>. Don’t get me wrong they were nice, but Polymer just seemed to get me. I also thought more like she did. I missed her.</p><p>It was during Google’s I/O 2016 that it all made sense. Polymer was still being worked on, and then community was there. It was just being incorporated into Google’s product offering. They used her in almost all new products. I was blown away at how the tooling has matured.</p><p>I saw this from the beginning, the web component specification was going to rock the world. It definitely has! Only one piece left on Mozilla’s a Firefox and web components would be native, no more poly fills. Yay!</p><p>Sometimes love is hard, but it does make one appreciate all the things Polymer does for us. Hopefully, you can see how to love her too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a96d0ff51b31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/falling-for-web-components-a96d0ff51b31">Falling for Web Components</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust built for years, yet destroyed instantly]]></title>
            <link>https://medium.com/tyler-garlick/trust-built-for-years-yet-destroyed-instantly-cea262250a7b?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cea262250a7b</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Thu, 12 May 2016 00:58:47 GMT</pubDate>
            <atom:updated>2016-05-12T22:16:37.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JnQmCf_2t7Y4FZZKQjCZOA.jpeg" /></figure><p>Building relationships in business, personal life or strangers is built upon a foundation of trust.</p><p>My Dad once told me:</p><blockquote>Trust is built like a brick wall, brick upon brick. These walls we build though slow to build can be destroyed with one simple action. Like a tornado, the wall can be destroyed instantly.</blockquote><p>I often find myself at work assessing the trust I give my team, my colleagues, bosses, CEO’s, etc. It is the currency by which we work together.</p><p>Trust laden environments exhibit creativity — the ability to know that if you screw up you have someone to rely on. I always think of it as a safety net. When walking a tight rope of a new idea, a trusted environment provides the safety net below incase you fall. Adversely, the lack of trust causes blame, conflict, anger, and estrangement. This is a cancerous, and must be removed immediately.</p><p>Interestingly, I often find myself casting judgement and summing up the level of trust I to strangers. I admit, I am really bad at this. I often ponder why are some naturally trustworthy, yet others can make my skin crawl. The sad part is I’ve been horribly wrong giving trust as well as being cautious for reasons that are unnecessary.</p><p>Here’s the thing, after we engage socially and with the initial judgement out of the way — my trust meter is usually spot on.</p><p>I often ponder why is it that the trust meter is so good a picking out the lemons among the genuine people. I believe we all interact similarly to the game <strong>The Sims</strong> either provides positive or negative trust. During the interaction, we use body language, words, or even gestures to add-to or subtract-from our trust.</p><p>Reflection and introspection has been familiar routine lately in my life. I attribute this to a couple of situations and just a natural desire to do better.</p><p>Trust had been a topic of critical analysis and sifting through emotional, intellectual, and physical information that I’ve seemingly attracted lately.</p><p>One such scenario from work is often a topic we involuntarily return to a couple times a week. I’ll sum up the situation.</p><p>We’ve been under pressure for a couple of months to deliver a new product. Leadership has been blinded (a different story for a different time) by situations, pressures, and sheer fear. Our team is one of the most fun, productive, awesomest, etc. We are efficient and able. As such we discovered that we could optimize our production to help speed up production and literally deliver our product in a couple of weeks rather than months. Excitement spread like wildfire. We had found a way to over deliver without much additional work. We committed to the task and started communicating our discovery and plan. It was genius. We circled around the room looking each other in the eyes committing to the plan. There was one person at the table, Richard (name changed) who I knew would need by in — mainly because we were trusting in him to provide a barrier while we worked. I remember looking in his eyes, asking, “Do you believe and support us.” Richard said, “I’m going to get beaten up, but it seems like it’s a good path . I support and believe in you all.” I was stoked. I rallied to troops again reaffirming this would happen. Everyone was on board.</p><p>Imagine the trust level at this moment. As we continued explaining our plan, it caught on. We left that day from the office — energized, driven, and relentless. We talked that night about finer details. I decided I would relax and come back to some decisions that was being made.</p><p>Just before I went to bed I decided I’d jot down a couple ideas. That’s when I saw the icon on my Mac bouncing up and down as if a small child had consumed a couple mountain dews and was looking for the next sugar rush. I was encouraged by this so I decided to see what the fuss was about. My heart sank as I started reading. My boss sent out and email, which in a nutshell communicated that our plan was not a good idea. Richard had no confidence in our ability to perform, and used the veto to stop all work. Needless to say, we still don’t know why that happened, nor is it really the point.</p><blockquote>Man to man, I had lost faith, hope and more importantly trust in Richard.</blockquote><p>I know lots of people don’t value commitments or their “word” for doing something, however, our team had this level of understanding. When we say we will do something — it will happen. How did we get to here. How will I able to ever trust Richard again. To me, this wasn’t the first time, yet the handshake and verbal affirmation made it his word and his bond.</p><p>Retrospectively, I knew why this happened from Richard’s perspective — fear and lack of communication. The harder thing to discover was how did I fail? I believe that most of the time failure is shared by both parties. So what did I do wrong?</p><p>This is my question I leave you with. How will I ever restore trust that had been so maliciously violated? How will I ever trust Richard again?</p><p>This is my journey, and perhaps the mysteries of that experience will be revealed over time. Until then I will for a long time second guess Richard’s motives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cea262250a7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/trust-built-for-years-yet-destroyed-instantly-cea262250a7b">Trust built for years, yet destroyed instantly</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing disruption by throwing your “X” up…]]></title>
            <link>https://medium.com/tyler-garlick/bringing-disruption-by-throwing-your-x-up-5ad17ae29331?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ad17ae29331</guid>
            <category><![CDATA[electronic-music]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Fri, 22 Apr 2016 21:34:56 GMT</pubDate>
            <atom:updated>2016-04-22T21:34:56.272Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qF_JxqFGr3mnQ7teZxKGQ.jpeg" /><figcaption>Meeting Excision (middle) for my birthday</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rZJz7L16R_2ue9sCxN9i4Q.jpeg" /></figure><p>The moment you walk into a Disney theme park — you enter a world of fantasy and magic. It’s not like any other theme park. Even in Orlando Universal’s park is not “magical,” though it’s one of my favorites as an adult. There is something different about a disney theme park.</p><p>In the same vein, Apple has a similar vibe. The unveiling of any new Apple product is an experience that is unique. The cult followers are obsessed with opening their new product first. There is a lot of impulse purchasing going on.</p><h3>The X Factor</h3><p>I admit I don’t know very much about Walt Disney’s life. I know that he took great pride in his theme parks, movies, etc.</p><p>I’m extremely versed in Apple’s history, and if you read anything about Steve Jobs it’s apparent that he cared about every small detail. I recall one story out of Job’s autobiography when they were building the Apple I. Wozniak was not as tidy as Jobs would’ve liked. He complained to Wozniak, to which Woz indicated that no one will see it. Jobs was infuriated and made sure that the inside was as beautiful as the outside. That set the tone for Apple. Everything relentlessly perfected inside and out. Apple oozes perfection and quality (whether you agree with their philosophies, products, etc. is not as important as observation). The phone/computer industry is a prime example. Laptops need to be thin.</p><p>These leaders relentlessly pursued the experience as seen through the glass of their consumers. As for Jobs be ruined friendships, lives, ideas as he molded reality from his vision.</p><blockquote>Having a vision that is acted upon every second of the day is fundamental to the X Factor.</blockquote><p>One hypothesis I have is the ability to control the experience wholistically. Attention to the small details is essential.</p><h3>Resisting to settle on ordinary</h3><p>I’ve observed ordinary. It’s background noise. It’s boring, it’s always there.</p><p>Disruption is the sound that is heard when ordinary is the norm. It’s even louder when you aren’t expecting it. I’d like to share one such experience.</p><p>I was disrupted through music recently. I love music, and I absolutely love going to concerts. Live performances are always exciting, fun, and a memory building experience.</p><p>The first time I went to an <a href="http://excision.ca/">Excision</a> concert changed my perspective on concerts forever. I now measure all concerts I attend against that experience. I’d like to share what made this experience different for me.</p><p>Most electronica artists or DJ’s are the same. They have good music. They get the crowd dancing, hell they even have really cool lasers. They don’t control usually the whole experience. They are slaves to the venues constraints — the audio and visuals. It’s still fun, but it’s not mesmerizing — it’s just ordinary.</p><p>The first Excision concert was far from ordinary. It started out normal. The night, the friends, the venue were an atypical outing when we started out — hell, even the opening DJ’s were entertaining. It was when the music stopped that it started for me. The chatter of the crowd was overwhelmed by 125,000 watts of bass. I couldn’t breath. I had never ever felt so much bass in my life. Then it happened, the curtain dropped with a <a href="https://www.youtube.com/watch?v=SX46ZN88lXw">3-d stage</a> (Sorry for the audio, there was a lot of bass) with projectors making this stage look like real life things (robots, spaceships, etc). Each object interacting with the song. The bass hits, a robot pounds the ground. I was mesmerized. During the next two hours my face melted with bass, the stage had set a whole new level of visualization for me, and part of the ceiling started to fall on the crowd as a result of the bass. I was in love. I joined the headbanger cult. Almost instantly, I was an avid Excision fan.</p><p>Excision captured the whole experience. The venue was at the mercy of his creativity. I thought that it was the pinnacle of stages. I wouldn’t ever see or experience anything like that. Excision could have kept on going with the stage and wowed people for a long time. Except he didn’t stop. He continued to innovate. To put it mildly he way outdid his first stage with a new version deemed the <a href="https://www.youtube.com/watch?v=3DBPelF3TNY">paradox</a> (sorry for the shaking, it was hard to stand still).</p><h3>Be controlling</h3><blockquote>Let me see you throw your <strong>X</strong> up!</blockquote><p>Controlling the whole experience allows one to do things that are different and disruptive. If Apple just made simple computer, or Disney a simple theme park would those products/services survived? Probably. However, the experience is what matters. It’s what produces that sense of exclusiveness and following. That breeds culture, and when you win the superbowl or something huge you probably wouldn’t receive the social media message with the beloved coined phrase “I’m going to Disneyland” probably on an iPhone.</p><p>As Excision says, “Let me see you throw your X up!” To me this means outside of his music, build something that is amazing by disruption. Disruption breeds innovation. Innovation is what sets you apart from everyone else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ad17ae29331" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/bringing-disruption-by-throwing-your-x-up-5ad17ae29331">Bringing disruption by throwing your “X” up…</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum: The Buy In]]></title>
            <link>https://medium.com/tyler-garlick/scrum-the-buy-in-2e98d93db766?source=rss-28f7a17710d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e98d93db766</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Tyler Garlick]]></dc:creator>
            <pubDate>Tue, 19 Apr 2016 06:35:42 GMT</pubDate>
            <atom:updated>2016-04-19T06:35:42.410Z</atom:updated>
            <content:encoded><![CDATA[<p>To an engineer — using an agile methodology (scrum or kanban) for a project done right is a really good way to ensure success in the project. It caters to our weaknesses. It amplifies our strengths. We have a medium to talk about our awkward personalities, processes, and what we could do better. In math’s sense, it’s the best law-of-average project management tool that we have. When done right, these processes are time consuming, and allow use to do what we are good at. Deliver!</p><h4>Organizational Dysfunction — The Scrum Way</h4><p>Does above sound like a dream in paradise? Usually, it seems like scrum is just a thing we do. I need to let me team know what i’m doing. Damn, the demo is tomorrow… <em>Guess, I’m doing an all nighter. Damn it! I want to just deliver.</em></p><p>Countless retrospectives later (if you are even doing them) and you tend to ask yourselves… Where did we fail? Does scrum work with just the “engineer’s doing it?” Then like the habitual c++ developer, we cave back to our old habits.</p><blockquote>Sorry product, I need you to define everything so I can make sure I can really do what you want…</blockquote><p>These are my opinions and observations. I’m sure they aren’t very abstract or foreign if you’ve been in an organization that is ill on their own processes.</p><h3>Symptoms</h3><p>Let’s be clear. Not all organizations suffer from all symptoms. I’ve worked on a scrum team that was highly functional. Thus, I’d like to compare and contrast these teams.</p><h4>The top priority, the processes, and the paradigms are different when they shouldn’t be…</h4><p>The hardest part about doing scrum effectively is getting the buy in from the top to the bottom. Without a complete buy-in you are going to do scrum half-assed. The easiest way to identify this is to ask people, what is your top priority.</p><h4>More than one priority</h4><p>Without alignment, everyone will scramble to their tool of choice and show a bunch of top priorities. To be clear, sometimes departments, or organizations have more than one priority. However, everyone should be driving towards a company wide epic, and the supporting epics/stories should support that top priority. Therefore, you always have one priority.</p><p>Different priority streams will come down the pipeline because not everyone is aligned in purpose.</p><h4>Unclear expectations</h4><p>Assuming that the prioritization is happening, or not without a clear expectation or definition of done you will fail. Epics/stories should always declare when a demonstrable is done by acceptance criteria. The criteria clearly states how it will be consumed and validated.</p><h4>Knee-Jerk Reactions</h4><p>Usually these knee-jerk reactions occur because there are too many priority streams to consume. They constantly fight for resources. One one of my teams we liken this to playing football.</p><blockquote>Imagine taking a football from your own in-zone to the 5 yard line on the other side of the field. Upon reaching the 5 yard line, you immediately drop the ball, and run to the in-zone again awaiting a new ball to field. Then someone asks to pick up the other ball on the 5 yard line. The problem is, the ball isn’t there anymore, it’s magically moved to the 35 yard line (contextual reloading of tasks), and now it takes that much more effort to drive it in… We just want to score damn it!</blockquote><p>Whoever has the loudest voice usually wins the knee-jerk reaction war. Scrum is about agility and the ability to pivot. However, this practice I’ve decided is anti-scrum. Without purpose or vision the “shifting” is not “agility” it’s contextual shouting that damages velocity.</p><h4>Lack of Vision/Execution</h4><p>When your blind to your goals — it’s impossible to have success. Vision is hard — especially as an engineer who is knee-deep in code. We rely on organizational leadership to provide the necessary guidance. I find that the engineers usually in a leaderless organization know more about the vision that the executives do. Why does this happen? We are problem solvers. We want to know what problem we are solving for, and so we figure it out.</p><p>Usually the lack of vision indicates that the problem being solved for is unknown. It’s possible that the leadership doesn’t know what they want (a common thing I hear constantly). I challenge this mentality. If they don’t know what they want, I doubt they know what their customers want.</p><h3>What do we do?</h3><p>I’ve learned countless times that an organization is like an organism. You can’t bring too much change to the organization without catastrophic failure.</p><h4>Start from the top</h4><p>You will immediately be tempted to start with the engineers and let them “lead” by example. Resist as much as possible. Instead, focus on consolidating the priority streams at the top. Work on identifying processes that support your workflows downstream. Don’t try to change everything at once.</p><blockquote>Best advice a wise person once told me, Small victories with constant praise is better than complaining… Who wouldn’t want to win?</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e98d93db766" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tyler-garlick/scrum-the-buy-in-2e98d93db766">Scrum: The Buy In</a> was originally published in <a href="https://medium.com/tyler-garlick">Tyler Garlick</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>