<?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 Slytrunk on Medium]]></title>
        <description><![CDATA[Stories by Slytrunk on Medium]]></description>
        <link>https://medium.com/@slytrunk?source=rss-6ecec3503078------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JVNeavGQLZ6WNV_EB1-2-A.png</url>
            <title>Stories by Slytrunk on Medium</title>
            <link>https://medium.com/@slytrunk?source=rss-6ecec3503078------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:22:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@slytrunk/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[Finding bugs in the long tail of your App’s crash report]]></title>
            <link>https://medium.com/ios-os-x-development/finding-bugs-in-the-long-tail-of-your-apps-crash-report-ce07c60b8b33?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce07c60b8b33</guid>
            <category><![CDATA[crashlytics]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Mon, 22 Aug 2016 15:17:03 GMT</pubDate>
            <atom:updated>2016-08-22T15:17:03.458Z</atom:updated>
            <content:encoded><![CDATA[<p>The subject of my Masters thesis was a microarray data set from UCSF which captured the gene expression of tens of thousands of genes from placental tissue at various stages of fetal development.</p><p>We knew the data contained insights that would help focus the medical research striving towards identifying the cause of, and cure for preeclampsia and other complications affecting pregnancy. But we worried that some of the more subtle details were being lost because the size of the data precluded the expert biologists from participating in the analysis.</p><h3>Humans vs. Computers</h3><p>Data mining techniques provide a way to tease out information from large data sets. Our collaborators at UCSF had already <a href="http://www.ncbi.nlm.nih.gov/pubmed/21743843">published a paper</a> rooted in clustering, complete with the pretty scatter plots that attempt to make the results less opaque. But data mining results are often hard to understand, hard to trace, and are heavily parameterized.</p><p>Humans on the other hand are terrible with large amounts of data, yet are good at spotting patterns and applying knowledge and experience. That is especially true of experts analysing their own large data sets. Computers are good at storing, recalling, and manipulating lots of data. Humans are good at extracting meaning from observations.</p><p>Combining the two, and letting humans lead an analysis of data, while letting the computers disguise the size and complexity of the data is where the magic happens. And that was my goal; writing software that enabled experts to explore and experience their data directly.</p><p>All of this was over 10 years ago, but the experience and philosophy has affected almost every aspect of my professional life.</p><h3>Crashlytics</h3><p>Recently I had an experience with one of our Crashlytics integrations, which made me realize that their unconventional product focus is heading in exactly this direction, and it’s thrilling to see it being developed on such a huge scale.</p><p>We’ve been using Crashlytics (now part of Fabric, from Twitter) since our 2014 builds of the Official NFL Fantasy Football mobile Apps. Combined with Fabric’s Answers product, we’ve come to rely on it to get a daily feel for the adoption, performance, and usage of the mobile apps we build.</p><p>During that first season, we saw a spike in a specific application code bug, and Crashlytics fell short of actually enabling us to pin point the exact time of the first crash. And when we pressed on the issue, it was clear there were limitations to the questions we could get meaningful answers to, via Crashlytics. (Side note, they were actually super helpful via email — shout out <a href="https://medium.com/u/ff78a68692b5">Hemal Shah</a> and team).</p><p>This was just one example of many times we found ourselves scratching our heads about apparent gaps in their product, thinking that conventional wisdom would have filled them long ago. But recently, it’s becoming clear that rather than providing exhaustive access to the data they’re collecting (like Google Analytics, for example), they realize that the real value of a platform such as theirs is in surfacing data in a way that the developer can identify problems, and begin to interpret, rationalize and solve them. It’s software, empowering developers to understand their application code across platform heterogeneity (different devices, OSs etc.) and countless other variables.</p><h3>Listening to the data</h3><p>Using Answers and Crashlytics, we know that push notifications for Fantasy Movie League lead directly to spikes in sessions, and those sessions decay rather gradually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*Gu2eSZ14-HkKNR0nPChMEA.png" /><figcaption>Friday Morning spike letting folks know their Cineplexes are about to lock</figcaption></figure><p>For World Surf League, we noticed that folks are self organizing to show up when Kelly Slater surfs a heat. We also noticed that crashes build with the populartity of event broadcasts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*A1KXvtdO9P8mLla5T5Jxaw.png" /><figcaption>Crash frequency building towards the final day of the Men’s and Women’s Vans US Open of Surfing</figcaption></figure><p>And that there are some lingering iOS 8 issues in our long tail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SlGiNi1vPuZ6F8if4LFcgQ.png" /><figcaption>iOS 8 only crashes, affecting a span of App versions</figcaption></figure><p>The most impressive application of Fabric came this week though with the rollout of OOM reporting:</p><h3>Crashlytics on Twitter</h3><p>We&#39;re extending our crash coverage! Say hello to OOM reporting: https://crashlytics.com/blog/introducing-oom-reporting ...pic.twitter.com/2L0SQsVEXA</p><p>For a long time I’ve suspected that many of our long tail of crashes — the 1–20 occurance type issues — were really just the app dumping out under OS or resource pressure. Here’s a snippet of our newly-available OOM crashes for the World Surf League:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*poKM40why1P0PmeQsLXdHg.png" /><figcaption>Devices ranked by % OOM-free sessions</figcaption></figure><p>I sent the link to <a href="https://medium.com/u/f6c6448edf0f">David</a> because we hadn’t seem OOM data flowing yet, and his first question was “what’s the deal with iPad Pro?!”. It’s easy to gloss over how powerful this insight is. iPad Pro is the best resourced iOS device in existence, but it’s got the most OOM crashes. It’s modest usage had, until now, hidden this particular feature.</p><p>This cut and presentation of data had identified an app-code issue that, as the developer, I could diagnose and fix. That is magic.</p><h3>Explaining the feature (aka fixing the bug)</h3><p>So what was different about iPad Pro? My thoughts turned to how we request and cache images. We rely on <a href="https://github.com/path/FastImageCache">Fast Image Cache</a> to maximize the fps while scrolling on the home feed, which basically takes images we load of a predetermined size and reads them in and out of a much larger in-memory image. We’ve been doing that for over a year, without any negative side effects.</p><p>The second component is that we re-write URLs to get images at an appropriate resolution and quality for the device. The thinking was that on iPhone 5, we should be getting images 320px wide, and on iPad, we should be getting larger images to look good on the larger screen. That logic extends to iPad pro, where the images getting requested are, well, yuge.</p><p>So, an in-memory cache that scales with the size of the images it’s initialized to contain. Bingo.</p><h3>Don’t neglect your tail</h3><p>It’s natural to focus on chasing your noisiest crashes, and the summary stats. But we’re increasingly able to identify and tackle app-code issues in the long tail, whose impact may be more modest, but no less satisfying to solve. I’m looking forward to rolling a build that will make the World Surf League more stable for our largest iOS screens.</p><p>And if your engineering team isn’t pouring over Crashlytics and Answers on a daily basis, encourage them to, because this is one of a growing number of tools that are becoming indispensable to a modern dev team.</p><p>— <a href="https://medium.com/u/703210619c16">Ben Dalziel</a>, <a href="https://medium.com/u/6ecec3503078">Sly Trunk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce07c60b8b33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ios-os-x-development/finding-bugs-in-the-long-tail-of-your-apps-crash-report-ce07c60b8b33">Finding bugs in the long tail of your App’s crash report</a> was originally published in <a href="https://medium.com/ios-os-x-development">iOS App Development</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Codifying style guides in Swift]]></title>
            <link>https://medium.com/ios-os-x-development/codifying-style-guides-in-swift-6a27b742f441?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a27b742f441</guid>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Tue, 07 Jun 2016 19:08:43 GMT</pubDate>
            <atom:updated>2016-07-27T22:44:46.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h6g0qZPcHu35iGEKMHq7Qg.jpeg" /></figure><h4>Embracing change and befriending designers</h4><p><em>[A follow up to this post is available, called </em><a href="https://medium.com/@bdalziel/advanced-baseline-grids-for-ios-cf7b59b9bfe6#.8cjcwqxug"><em>Advanced baseline grids for iOS</em></a><em>]</em></p><p>There was a time where I would press designers to give me verbal confirmation that the style guide they were handing off was <strong>final</strong>. “<em>Ok</em>”, I’d reply cautiously. “<em>That’s it. No more changes. Hands off. You’re done!</em>”.</p><h3>PHD Comics on Twitter</h3><p>Premature file naming happens to all of us: http://phdcomics.com/comics.php?f=1531 ... (new comic!)</p><p>Anytime someone says <em>final</em> or <em>last version</em>, this comic pops into my head and makes me smile. The reality that I’ve come to accept across all aspects of life, and especially across product development, is that <strong>there is no such thing as final</strong>.</p><h4>Change Happens</h4><p>If we focus on the style guide as a key interface between design and engineering, I’ve found there are two big types of change.</p><ol><li>The details of the style guide can change: “<em>let’s make that purple a touch darker</em>”; or “<em>let’s add an alternate purple</em>”</li><li>The application of the style guide can change: “<em>let’s use the other beige for that text</em>”; “<em>let’s use the secondary button type there</em>”</li></ol><p>When you accept this, the style guide stops being a contract that you can bludgeon the designer with, and instead merely captures a snapshot along the path of product development. So what does this look like in practice? For simplicity, let’s reduce the problem space to focus on the coding of colors from a style guide (although the same concepts can, and have been applied to fonts etc.):</p><p><strong>Characteristics of a flexible style guide implementation</strong></p><ul><li>We want to <strong>limit the UI to a finite color palette</strong> — guarding against random RGB/Hex codes littering your code</li><li>We need some <strong>flexibility with the alpha channel</strong> of palette colors</li><li>It needs to be possible to see <strong>which UI elements use a particular color</strong></li><li>We need the <strong>ability to change a color across the whole app</strong> (“<em>Make that purple darker</em>”)</li><li>And the <strong>ability to change a UI element color</strong> without affecting everything else (“l<em>et’s use beige for that text</em>”)</li></ul><p>I’ve found that constraining the implementation of style guides in a certain way can lead to a subsystem that actually <strong>liberates the design and style guide</strong> in a way that is tremendously rewarding and continues to pay dividends long after it is established.</p><h4>Prerequisites</h4><ul><li>Programmatically setting colors — no XIB or Storyboard colors</li><li>If you want to use colors in Interface Builder, be diligent about programmatically re-setting them in awakeFromNib, or viewDidLoad</li><li>In interface builder, use a custom palette with your style guide colors specified by hex value (to avoid frankly disgusting color profile nonsense with RGB and your screen color profile)</li></ul><h3>The Solution</h3><h4>Part 1: Establish your Palette</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/95d4442951824b76bddfc59de1acc915/href">https://medium.com/media/95d4442951824b76bddfc59de1acc915/href</a></iframe><p>Want to tweak a hex value? Do it here. And have confidence that the entire UI will get the updated value. Want to check you’re consistently setting colors via code? Change these values one-by-one to be something starkly different (bright green is a good one) and see what is left over when you load up the app.</p><h4>Part 2: Enumerate the UI which needs color</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee882ad805ecb605b69b82a890724b6d/href">https://medium.com/media/ee882ad805ecb605b69b82a890724b6d/href</a></iframe><p>This is not a place for generalizing. Generalizing will be your undoing when a change request breaks that generalization. Be as specific as you can, and you’ll maximize your flexibility when the changes start flowing.</p><h4>Part 3: Associate your UI with the palette</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e0db737dec0f047b05737afd155ca36/href">https://medium.com/media/1e0db737dec0f047b05737afd155ca36/href</a></iframe><p>Now you can match up your UI with their assigned color. You can see exactly which UI gets which color, and adjust at your leisure. Fabulous.</p><p>The whole <a href="https://gist.github.com/bdalziel/8774cec94b0486b1e7c83a3dfe77b820">ColorUtil.swift</a> file for Fantasy Movie League, along with <a href="https://gist.github.com/bdalziel/e640d5de6db89113429d0de91dd704ee">FontUtil.swift</a> (which is based on the same concepts) are provided for reference. Please comment on the gists with any feedback/edits/improvements.</p><p>Check out <a href="https://itunes.apple.com/us/app/fantasy-movie-league/id1089244568?ls=1&amp;mt=8">Fantasy Movie League</a> for iPhone to see the beautiful, consistent, and flexible realization of <a href="https://medium.com/u/b181e4d6b05a">Tav Calico</a>’s <a href="http://tavcalico.com/work/fml/">designs</a>.</p><p>— <a href="https://medium.com/u/703210619c16">Ben Dalziel</a>, June 2016</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a27b742f441" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ios-os-x-development/codifying-style-guides-in-swift-6a27b742f441">Codifying style guides in Swift</a> was originally published in <a href="https://medium.com/ios-os-x-development">iOS App Development</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best #SB50 Ads]]></title>
            <link>https://medium.com/@slytrunk/the-best-sb50-ads-7ee22a399b02?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ee22a399b02</guid>
            <category><![CDATA[advertising]]></category>
            <category><![CDATA[super-bowl]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Mon, 08 Feb 2016 03:35:30 GMT</pubDate>
            <atom:updated>2016-02-08T04:31:22.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lxfl5AhC1bHVgOsbkLoasw.png" /><figcaption>All that money, all that creativity, all those hashtags!</figcaption></figure><h4>Via the science of Brackets!</h4><p>It’s striking how insignificant the actual Big Game is. The day is enormous, don’t get me wrong, but the actual game? A sideshow. For many, the commercial breaks are time to break from conversations mid sentence, and stare open mouthed as hundreds of thousands of advertising dollars flash before our eyes. How do they make us feel, how do they grab our attention, who has the worst hash tag (#PuppyBabyMonkey, maybe)? It all boils down to which ad and brand is most talked about on Monday. But we’re turning the decision over to our trusty brackets, where the wisdom of crowds can tell us once and for all; which is the best 2016 #SB50 Ad! <a href="http://brackify.com/b/170/best-2016-super-bowl-commercials-bracket">Make your picks now</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GH6MEp0tkZqFUsoGVN3RvQ.png" /></figure><p>Watch all the ads, pick your favorites and see which ones are dominating the bracket over on <a href="http://brackify.com/b/170/best-2016-super-bowl-commercials-bracket">brackify.com</a>.</p><p>We also wrote about why we’re creating this fun experience as a way to raise awareness of something we think fits into Super Bowl weekend pretty nicely, over on the <a href="http://slytrunk.com/posts/398/super-bowl-2016-ads-bracket">Sly Trunk Blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ee22a399b02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is it really worth learning a modern web stack?]]></title>
            <link>https://medium.com/developers-writing/is-it-really-worth-learning-a-modern-web-stack-7ac781485b?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ac781485b</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Fri, 05 Feb 2016 17:43:42 GMT</pubDate>
            <atom:updated>2016-02-05T17:43:42.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*yCrsrQOYWwS5iN7jHmgScQ.jpeg" /></figure><p>When I first learned to develop for iOS, it took 3 months until I felt comfortable and productive. But it was a steady march towards something mature and well thought out. It was fun and I felt like I was growing and getting better as a developer. I look back on that time fondly.</p><p>Fast forward to late 2015, and I was excited to start all over again building modern web apps. I expected it to be the perfect marriage of familiar web technologies and the rigor of programming a true app experience that I’d learned developing for iOS. I’d built “apps” using the YUI App Framework way back in the day, so it felt like a natural fit. I was wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*U3viPVCfI-YB80iwwJkjYA.jpeg" /></figure><p>For the past few months I’ve been writing code on a stack composed of a dizzying array of packages, acronyms, technologies, patterns, tools, choices, and alternatives. The hard work was done by Phil, who pieced together a stack that does every aspect of modern web development in a modern way, and then wrote a significant amount of application code on top of it.</p><p>For a while now I’ve been hoping for a breakthrough. Hoping to see the light or some promise in the stack. But here I am ending another week exhausted, exacerbated and thoroughly disheartened*.</p><p>I’ve tried to cheerlead for it. I’ve tried to give it time. We get the feeling this is the future, so we should embrace it. But I long to return to familiar technologies to be productive again. I long to understand what the hell is going on. I long to reload my browser and for a dev page to appear in under 10 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/236/1*h4tQ9wPx03yCK_-1dyUmaw.jpeg" /></figure><p>As I sat down to write — with a large glass of wine — I planned to share specific grievances to illustrate how frustrating this new world is, but that isn’t the point. There’s a counter point to every one of my grumbles. There’ll be npm packages I should install to solve XYZ, and I’ll need to think differently about ZYX to have the aha moment. Eventually I’ll get it. Eventually the language and tools and paradigms will fade into the background and I’ll once again be able to solve problems without fighting every step of the way. But right now it’s crushing.</p><p>More importantly, I wanted to share a moment of weakness. We’re an industry weirdly obsessed with genius and ninjas, and it’s ok not to feel like that every day. Or ever. We’re humans here at <a href="http://slytrunk.com/">Sly Trunk</a>, and as such we’re prone to struggling from time to time. It’s only fair that we document the bad with the good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*JSJJhiKuTQToOk2kNPupew.png" /></figure><p>It’s hard for me to remember if I was ever like this with Objective C. It’s easy to forget the bad times when they’re behind you.</p><p>The thing is, it’s worth it.</p><p>It’s a valuable, humbling, challenging experience. There are smart people building these tools and technologies. Whole companies pinning their hopes on this being the future. And so there has to be something to it. Even if this doesn’t wind up being the future for long, at least we’ll have organizational experience with it and it’ll impact and inform countless decisions we make for every future project and client. It’ll make us better at writing code on other stacks and in other languages. It’s good to get out of your comfort zone, start over again, and suffer a little for your art. And if against all my instinct this turns out to be the future, well the struggle will have been all the more worthwhile.</p><p>Cheers!</p><p><em>*I’m planning to start </em><a href="http://slytrunk.com/posts/159/how-running-makes-me-a-better-programmer"><em>running</em></a><em> tomorrow!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ac781485b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/developers-writing/is-it-really-worth-learning-a-modern-web-stack-7ac781485b">Is it really worth learning a modern web stack?</a> was originally published in <a href="https://medium.com/developers-writing">Developers Writing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our 2015 Highlights]]></title>
            <link>https://medium.com/@slytrunk/our-2015-highlights-fca1271b6c79?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/fca1271b6c79</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Mon, 04 Jan 2016 19:02:07 GMT</pubDate>
            <atom:updated>2016-01-04T19:02:07.984Z</atom:updated>
            <content:encoded><![CDATA[<p>2015 was a big year for Sly Trunk. We established some key partners, shipped a LOT of code written in different languages dependent on new technologies, and developed experiences for entirely new platforms. To close out the year, we hired a CEO, so we’re already excited for 2016! Here are some of our highlights:</p><h4>February</h4><p>Shah, Dave and Ben attended Super Bowl XLIX following the successful Fantasy Mobile App rollout in 2014</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9Ar-QzAtO7SCv7Xl-Qwbw.jpeg" /></figure><h4>March</h4><p>The World Surf League (WSL) Mobile Apps Launched on Google Play for Android and in the App Store for iOS</p><p>Partnering with Hubstar Games, we launched <a href="http://slytrunk.com/posts/138/real-time-brackets">Real Time Brackets</a> in time for March Madness, with a website and mobile apps</p><h4>May</h4><p>We launched <a href="http://slytrunk.com/posts/195/fantasy-movie-league">Fantasy Movie League</a> in partnership with ESPN’s Fantasy Football Expert, Matthew Berry</p><h4>July</h4><p>Our co-production Brackify went viral with a <a href="http://slytrunk.com/posts/64/brackify-it">Fan Army Faceoff</a> for Billboard.com</p><p>A <a href="http://slytrunk.com/posts/307/when-the-shark-hits-the-fan">Shark Attack</a> during live WSL event in J-Bay, South Africa, brought world wide attention to pro surfing and their digital offerings</p><p>Wing Stop <a href="https://twitter.com/slytrunk/status/619250423254265856">inception</a></p><h4>August</h4><p>First <a href="http://us10.campaign-archive1.com/home/?u=36926ea84ad90f489accedc29&amp;id=5d904a9e4b">Sly Trunk Insider</a> mailing list sent</p><h4>September</h4><p><a href="https://twitter.com/wsl/status/637307228110778368">500k</a> download milestone reached for WSL Mobile Apps</p><h4>October</h4><p><a href="http://slytrunk.com/posts/344/farewell-adrian">Farewell to Adrian</a>, who took an exciting role at AirBNB</p><p>Started working with Specialized supporting their internal dev team</p><h4>November</h4><p><a href="http://slytrunk.com/posts/350/brainstorm-a-party-game">Brainstorm — a party game</a> launches on Google Play for Android and in the App Store for iOS</p><p><a href="http://slytrunk.com/posts/388/health-outcome">Health Outcome</a> launched</p><h4>December</h4><p><a href="http://slytrunk.com/posts/361/wonderwall-com-redesign">Wonderwall.com</a> redesign launched</p><p><a href="http://slytrunk.com/team/10/cory-mummery">Cory Mummery</a> joins the team as CEO</p><p>We’re already working hard to make 2016 our best yet. What were some of your highlights this year?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fca1271b6c79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Farewell Adrian]]></title>
            <link>https://medium.com/@slytrunk/farewell-adrian-76ddbb491041?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/76ddbb491041</guid>
            <category><![CDATA[leaving]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Mon, 19 Oct 2015 17:19:14 GMT</pubDate>
            <atom:updated>2015-10-19T17:19:14.740Z</atom:updated>
            <content:encoded><![CDATA[<h4>Celebrate the impact of a really good hire</h4><p>Hiring into a small team is risky. When your product is your personnel, like here at Sly Trunk, you take that risk seriously. From the outset, Shawn and Luke’s approach has been to hire the best engineers they know. So when it came to hire our first non-engineer, they naturally hired the best they’d worked with to-date.</p><p>Adrian joined Sly Trunk in May of 2013 during what was an interesting period at Sly Trunk. In addition to growing our client work, we were beginning to tackle our own projects. He parachuted into our first native game, <a href="http://slytrunk.com/posts/67/a-challenging-word-game">Ghost Words</a>, and refined the game dynamic, interface and social interactions. His passion for digital product was infectious, and he built on our native app momentum with <a href="http://slytrunk.com/posts/53/shape-shuffle">Shape Shuffle</a>. Through character creation, level design, marketing, content strategies, UX refinement, etc. Adrian had chance to assume many roles and explore every aspect of digital product, unencumbered by traditional team dynamics. He thrived.</p><p>Behind the scenes, Adrian was also re-branding Sly Trunk, attending WWDC, showing off our work and attracting new clients. He became the sounding board for countless ideas and the safe place to talk through product, UX, marketing, design etc..</p><p>Adrian began refining the breadth of skills for what would be his Magnum opus while at Sly Trunk; the <a href="http://slytrunk.com/posts/122/world-surf-league-apps">World Surf League Apps</a>. Coming off the back of the <a href="http://slytrunk.com/posts/63/nfl-fantasy-football-apps">NFL Fantasy Mobile Apps</a>, we were feeling pretty good about the design/engineering workflow, but Adrian saw opportunity for something better. An early adopter of Slack, Sketch, and later Zeplin, he discovered and introduced us to what is now the modern design and collaboration workflow and toolset. Every prototype would be built in the latest and greatest prototyping tool, which from anyone else would be tedious, but from Adrian was just part of chasing the optimal tools and process. It’s difficult getting an engineering team to evolve and break the status quo, but he did so with such passion and by demonstrating the potential of the next big thing. That passion for what is next is important in software, both as a consumer and as a creator.</p><p>Tackling both iOS and Android, phone and tablet, rankings and events, Fantasy and live video, Adrian designed, refined and iterated tirelessly. From early sketches, through prototypes, to the final product, the WSL Apps were steered and nurtured by Adrian throughout. As the iOS engineer implementing Adrian’s vision, I can comfortably say it remains my best work thanks to how deeply rewarding the collaboration with Adrian was. It’s because of the process he encourages, because of the software used to ease communication of ideas, but ultimately it’s rooted in his talent as a designer and his vision for an incredible product.</p><p>On my daily walks I would sometimes call Adrian to talk about Sly Trunk, or the merits of Tab Bars, or to pitch the Next Big Idea. Other times I would listen to podcasts and one particularly memorable moment came from a New Yorker feature on the <a href="http://www.newyorker.com/podcast/out-loud/the-new-new-york-city-skyline">NYC skyline</a>. In it, Adam Gopnik talks about the three things present in all great creations, from creative writing, to architecture etc. They all have: 1.) an object; 2.) a buried subject; and 3.) a theme that was hidden from the creator. So if Adrian’s time with us was a work of art: 1.) his output — the designs and products — would be the ostensible object. 2.) The buried subject is growth — growing in multiple directions and thriving with nothing more than a passion and freedom. 3.) And the theme invisible to us all, I think in retrospect, would be reinvention. Reinvention both individually and as a whole.</p><p>Hiring is so often focussed on minimizing risk, but as this chapter closes, it’s nice to celebrate the impact of a really good hire. Sly Trunk is better because of Adrian and we’ll continue to grow with the momentum he created.</p><p>Connect with Adrian <a href="https://twitter.com/rustydingo">@rustydingo</a>.</p><p><em>Originally published at </em><a href="http://slytrunk.com/posts/344/farewell-adrian"><em>slytrunk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76ddbb491041" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Achieve a Zero Crash Count in Android]]></title>
            <link>https://medium.com/@slytrunk/how-to-achieve-a-zero-crash-count-in-android-21a820adc8f3?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/21a820adc8f3</guid>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Wed, 10 Jun 2015 23:55:19 GMT</pubDate>
            <atom:updated>2015-06-10T23:55:19.846Z</atom:updated>
            <content:encoded><![CDATA[<p>Pretty compelling post title, huh? Click bait? Maybe, a little.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*0GCSIHO6VQ42hpuOobZyOg.png" /></figure><p>Here at Sly Trunk, we’ve gone through quite a few app deployments on Android. I can remember the first app that we pushed to the Play Store. You upload your APK. Sweet, my app is supported on 3,945 different devices! Wait. 3,945 different devices? But we only tested on a handful. It’s ok. We’ll be ok. I’ve got Crashlytics going and we’ll see stuff as soon as it comes in and take care of it.</p><p>You wait the requisite few hours for the binary to be available everywhere. Awesome, we are starting to get downloads! Various forms of promotion then start to make their way out to the public. Website promotion. Commercials. Featured App Promotion.</p><p>And then, whoosh, a crash email. You look at the stack trace and try to understand what the user was trying to do. It’s not obvious at first what’s going on and then whoosh. Another crash email. Ack! You start looking at this stack trace. WTF! That’s not even in my code!?!</p><p>Based on this experience, here are a few things you can do to make sure to cut down on the frustration on the first day of launch and subsequent launches.</p><h3>Use Crashlytics within<a href="https://fabric.io/"> fabric.io</a></h3><p>There are other providers out there that provide these type of “crash tracking” services. We’ve tried a couple and have found that crashlytics seems to be the best of the best. We use it with all of our projects both on Android and iOS. Their support has been great and they are very responsive.</p><h3>Track or append custom data to any stack trace that is logged</h3><p>Being able to do this will be dependent on which crash framework you decide to use. Custom keys are the way to go. See <a href="http://support.crashlytics.com/knowledgebase/articles/120055-how-do-i-use-custom-keys">how to use custom keys with Crashlytics</a>.</p><p>Track as much as you can and as much as makes sense. What do we track?</p><p><strong>For each major activity/fragment, track the most important values that were used in the bundle that helped create that activity/fragment.</strong></p><p>As an example, in our <a href="http://slytrunk.com/posts/122/world-surf-league-apps">WSL App</a> we have views for athletes and events. For each of these we track the “last event id” or “last athlete id” that was used to create those fragments. The reason for this is that if we get a crash that looks like it’s in the athlete fragment, we can look at the last athlete id and use that as our starting point to start hunting. It’s not always perfect but in the vast majority of cases it lets us pin down the exact location.</p><p><strong>If the user is logged in, use the </strong><a href="http://support.crashlytics.com/knowledgebase/articles/120548-how-do-i-set-user-information"><strong>user identifier tracking</strong></a></p><p>So far, we’ve found it invaluable to use this tracking. If you have a login mechanism inside your app (and I would say this probably applies to a fair number of apps), track the user id and user email address if you can. Be sure to detail this in your privacy policy.</p><p>If you look at app store reviews, you’ll often see reviews such as “It crashed on my [ancient device no one has ever heard of running an ancient OS version]. 1 star! You developers suck. Get a new day job!”. These reviews have a name and/or email address associated with them and it’s sometimes possible to correlate that review and a specific stack trace. Once you have the stack trace, you can possible get additional details about the crash directly from the user and also respond to that user (on their review) once you’ve fixed the problem.</p><p>Having this feedback loop will often help change those 1 star reviews into 5 star reviews. Users really just want to know that someone is listening and cares.</p><p><strong>Current memory usage</strong></p><p>We use this help track down Out Of Memory crashes which will inevitably happen, at some point, in your app.</p><h3>Test on as many devices as you can</h3><p>It’s laborious work but please make sure that if you specified that you support Gingerbread that you actually go back and consistently test that version and every version in between.</p><p>Make use of cloud based testing services that allow you to upload your APK and run tests for you. There are a bunch out there right now and we haven’t landed on a recommendation yet. That being said, I’m having high hopes for the newly announced Google Test Lab. You can get information about this service and sign up for updates by visiting the <a href="https://developers.google.com/cloud-test-lab/">Google Test Lab</a> Hub.</p><h3>If your app uses the network, make sure to test in poor and no network scenarios</h3><p>In a lot of the apps that we have written, we make major use of the network. Asynchronous callbacks have bitten us in the past. A user may decide to navigate away from a view that originally made a network request. When you get that callback on the UI thread, most if not all of the UI that needed that data may be gone. You need to gracefully deal with that.</p><p>Other than just added code guards to check to see if the fragment or activity has gone away, you can make use of annotations that automatically inject that code without you having to write it. You can also make use of a message bus and have fragments subscribe and unsubscribe to messages during their lifecycle callbacks.</p><p>We’ve also started to look into using Reactive Programming and <a href="https://github.com/ReactiveX/RxJava/wiki/The-RxJava-Android-Module">RxJava</a> with our projects. Using RxJava should help alleviate this problem as well. When we have more recommendations and opinions around this, we will be sure to update this post.</p><h3>Make use of <a href="http://www.stackoverflow.com/">Stack Overflow</a></h3><p>This may seem like an obvious one but… the first thing most people probably do is search for the crash on google to see if it’s happened to someone else already. Inevitably the highest hits will be from Stack Overflow. If you haven’t already, and again, this is probably old news, sign up for Stack Overflow. Ask questions. Learn how to properly answer a question. Get your reputation up high enough so you can effectively do stuff on the site.</p><p>In some cases you may not get an answer. But, sometimes, out of the blue, a question that corresponds to an old open issue that was never solved will get answered. And when that happens, you get to do the dance of joy.</p><p>We are constantly learning and evolving our process based on our projects. There are many items that didn’t make this list and I’m sure we will have additional ones in the future. Do you have any hints or tricks you’d like to share with other Android developers? If so, <a href="http://slytrunk.com/contact">hit us up</a>.</p><p><em>Originally published at </em><a href="http://slytrunk.com/posts/225/how-to-achieve-a-zero-crash-count-in-android"><em>slytrunk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21a820adc8f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How iOS 9 Will Get The Apple Watch To Click]]></title>
            <link>https://medium.com/@slytrunk/how-ios-9-will-get-the-apple-watch-to-click-ffb032211052?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffb032211052</guid>
            <category><![CDATA[wwdc]]></category>
            <category><![CDATA[ios-9]]></category>
            <category><![CDATA[apple-watch]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Sat, 06 Jun 2015 02:44:22 GMT</pubDate>
            <atom:updated>2015-06-08T06:07:31.813Z</atom:updated>
            <content:encoded><![CDATA[<p>The Apple Watch is Apple’s most heavily constrained device. A tiny screen, a short battery-life, and limited developer access. Prior to launch, the media framed it within its limitations — depending on an iPhone, lacking a keyboard, missing a web-browser, being a fiddly gaming platform, etc. The developer community, too, is focussed on the limitations — particularly limitations of WatchKit extensions and glances when compared to the rich development environment we’re used to with iOS. Much of the chatter prior to the announcement of iOS 9 on Monday is focussed on hoping the developer constraints will be lessened and we’ll get richer access via a Native Apple Watch SDK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*UWMRJfUE6G6VkCUXgqeiDg.png" /></figure><p>The ever insightful Marco Arment wrote a <a href="http://www.marco.org/2015/05/28/watch-sdk-questions">list of questions</a> about the <a href="http://recode.net/2015/05/27/apple-operations-chief-jeff-williams-takes-the-code-stage-liveblog/">upcoming developer kit</a>. A grounded, incremental view of what iOS 9 might mean for the Apple Watch.</p><p>The problem is, after weeks with the watch, I don’t see ANY value in the existing developer app extensions, and I only ever access the app-grid accidentally. Moreover, I don’t see any more value in more complex or richer apps enabled by native developer access. To put it bluntly, I would be just as happy with the Apple Watch if it was app-less akin to the original iPhone.</p><p>It’s a very nice watch. It’s customizable and “smart” in that is an effective window into the lock screen of the device in my pocket. But first and foremost, it’s a watch. The apps, glances, and interactions with notifications feel disconnected and distant. So an incremental evolution to support native development won’t help much, but instead may exacerbate other limitations; battery life, lack of connectivity etc. Marco’s questions are guarded by those same concerns.</p><p>I don’t see the developer generated content becoming dramatically more usable, (or usable in the first place) with a simple evolution of WatchKit and a move to a native SDK. For that to happen, I’m betting on the introduction of a paradigm shift, and for it to arrive in iOS 9.</p><h3>Making Apple Watch Smart</h3><p>The truth is I think apps, glances and their WatchKit UI are great. How un-used and impractical they are stems from how unnatural it is to navigate a visual, touch based UI to expose functionality whose utility is measured in seconds. But if that functionality were available via the primary, natural input to the Apple watch, things would get interesting. And that input is, of course, <strong>voice</strong>.</p><h3>Voice dispatch</h3><p>Let me explain with something I do every single morning:</p><p>Grind beans, half fill French press with water.</p><p>To Siri: “<strong>Set a timer for 1 minutes</strong>”. <em>Timer goes off</em></p><p>Stir the bloom, and top off with water</p><p>To Siri: “<strong>Set a timer for 3 minutes</strong>”. <em>Timer goes off</em></p><p>Push down plunger and enjoy.</p><p>(Based on Stumptown Coffee Roasters <a href="http://stumptowncoffee.com/brew-guides/press-pot/">brew guide</a>)</p><p>I’ve done this for months with my iPhone and yet every day since I got my watch, which is much more accessible and convenient, it feels cumbersome. I love those moments, where your subconscious raises a little flag saying “well, that didn’t feel quite right”. I have a hard time ignoring my sub conscious, so I’ve been mulling over what the device should do differently.</p><p>My belief is that it boils down to making Siri the entry point to ALL apps on Apple Watch. Siri isn’t going to have OS level support for coffee brewing methods, neither is through extension to Wolfram Alpha, so it’s up to the development community to fill in the missing parts and explore the potential of this established but as-of-yet closed off paradigm, much like when the App Store opened the original iPhone to developer code.</p><p>That is MUCH more exciting than anything promised for iOS 9, or even the watch announcement itself. New development paradigms like I’m imagining don’t come around too often.</p><h3>“What can I help you with?”</h3><p>Since Siri was introduced back in 2011, there has been an expectation that developers would get access to it. Apple has, in regular-Apple-form, defied expectations, but I get a feeling enough stars may have aligned in Cupertino to make it make Apple-sense in the context of the Apple Watch.</p><p>So what would my morning routine look like with developer access to Siri?:</p><p>Grind beans, half fill French press with water.</p><p>To Siri: “<strong>I’m making my morning coffee</strong>”</p><p><em>UI updates to allow user to pick coffee brew method. French press is selected</em></p><p><em>UI updates to show instruction “Half fill French press”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*sJPXS4gRHYkkYqQOXAUqEA.png" /></figure><p>User <strong>taps</strong> accompanying “Next” button</p><p><em>UI updates to show 1:00 timer counting down</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*6b1knSl5Qdd21vqqbISDUw.png" /></figure><p><em>UI updates to show “Stir bloom and top off French press”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*kZwgt36ISOhdtX1hrID0EQ.png" /></figure><p><em>UI shows 3:00 timer counting down</em></p><p><em>Timer goes off</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*xzn27WheDr0qXVC52MfBAg.png" /></figure><p><em>UI updates to say “Enjoy!”</em></p><h3>Supporting the Paradigm Shift in iOS 9</h3><p>So what does this developer access to Siri look like in iOS 9? How do I make this coffee brewing utility a reality? My guess is something like this:</p><ul><li>Apps will be able to declaring instruction patterns they can responds to — optionally parameterized. Perhaps initially you’d have to mention the name of the app in the verbal instruction to Siri</li><li>The instruction would be parsed and dispatched with any parameters, by the OS/Siri. I expect the entry point to the app would be similar to how push notifications work</li><li>The app would run some logic to validate/process the parameters, possibly asking for clarification via another Siri code hook. It would then configure and dispatch to a “glance” extension that serves the action concisely</li><li>The glance would be presented to the user, and stay in the “foreground” for the duration of the task. Screen would still dim etc. Can resume with crown double tap</li><li>The glance would have access to configure and display/embed “OS” type utility functionality (timers, reminders, messages etc.)</li></ul><p>Using the iPhone to manage Apple Watch settings works perfectly for setting up enumerated parameters and configurations — maybe for French press I want an initial 2 minute soak, followed by 5 minutes when topped off. Maybe I can say “Help me make coffee for Madeline”, and based on Family sharing, the watch can help me brew coffee just like my wife has it configured on her phone.</p><p>It’s easy to see the potential here, and see how these interactions would come together:</p><ul><li>Play the latest Game of Thrones episode in the living room</li><li>Make sure my garage door is closed</li><li>Bench Tom Brady from my fantasy team</li><li>What is this song? Create a pandora station based on it</li></ul><h3>Siri as a miniature OS</h3><p>No Apple article has stuck with me more than one about a <a href="http://www.macrumors.com/2013/02/05/apple-job-posting-hints-at-siri-for-macs-in-os-x-10-9/">Siri job posting</a>, in which the description asks potential candidates to do the following:</p><blockquote><em>Consider it an entire miniature OS within the OS, and you get a good idea of the scope</em></blockquote><p>I think big things are coming in this area, and I’m excited to see if Monday will deliver the first steps into developer access.</p><p>Siri has <a href="http://9to5mac.com/2015/04/27/siri-backend-mesos/">matured</a>, is central to <a href="https://www.apple.com/ios/carplay/">CarPlay</a>, and will soon be part of Mac OS and AppleTV. With developer access in iOS 9, it would dramatically change the utility of those nice looking watches, by making apps useful, and their development actually worthwhile. I’d be so excited to see the magic that could be created with that power exposed to the dev community.</p><p>We’re getting closer:</p><p><em>Originally published at </em><a href="http://slytrunk.com/posts/202/how-ios-9-will-make-the-apple-watch-click"><em>slytrunk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffb032211052" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[School for Sly Trunk]]></title>
            <link>https://medium.com/@slytrunk/school-for-sly-trunk-938841d5c350?source=rss-6ecec3503078------2</link>
            <guid isPermaLink="false">https://medium.com/p/938841d5c350</guid>
            <category><![CDATA[college]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[graduation]]></category>
            <dc:creator><![CDATA[Slytrunk]]></dc:creator>
            <pubDate>Tue, 02 Jun 2015 16:31:05 GMT</pubDate>
            <atom:updated>2015-06-02T16:31:05.437Z</atom:updated>
            <content:encoded><![CDATA[<p>In the second part of our series profiling the folks who make up the team here at Sly Trunk, I asked everyone to talk a little bit about their schooling. It is graduation season after all!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*BmvwoC6bkVkYRsUBDKyezg.png" /></figure><h4>Shawn: <a href="http://www.calpoly.edu/">Cal Poly</a>, San Luis Obispo CA</h4><p>At Cal Poly, I studied Computer Engineering which is half EE and half CS. I gravitated towards the software side of the world, but having the EE background has helped me understand the inner workings of a computer. This ultimately leads to better architecture and software design. Playing soccer, volleyball and <a href="http://www.wallyball.com/">wallyball</a> (if you haven’t played, it is a ton of fun) lead me to be a better slacker.</p><h4>Adrian: <a href="http://bond.edu.au/">Bond University</a>, Queensland Australia</h4><p>I began my time at Bond University in noble pursuit of a degree in Information Technology &amp; Law. Full of good intentions I dove right into splitting my course work between riveting criminal law lectures and software engineering labs. It wasn’t until I decided to tackle a combination of equity and constitutional law that when it dawned upon me, I’d be much happier tinkering with software and designing digital products than becoming a champion for the Australian legal system. I bid farewell to my law degree (mother was not happy, but she got over it) and focused on technology, interactive design and building products. I also had more time to make full use of the university’s excellent fitness facilities (squash courts!) and olympic swimming pool.</p><h4>Dave: <a href="http://www.cs.cmu.edu/">Carnegie Mellon University</a>, Pittsburgh PA</h4><p>I have to admit that I was pretty miserable my first year or so. I was getting used to life back in United States. I went to high school in London, England when my dad’s job brought us there in the early nighties. I received my degree in Mathematics and Computer Science. I’m not sure what the highlight would have been (other than meeting my future wife). I tended to prefer graphics related courses more than, say, compilers or programming languages. That being said, I’ve since gone back and found some of those areas incredibly interesting and worthy of spending Coursera time on. Ultimately, I guess my biggest take away was learning how to learn.</p><p>Incidentally, I never painted the fence. I never got up early enough to watch a buggy race. Tartan is not my favorite color. I also despise set and graph theory.</p><h4>Phil: <a href="http://www.usc.edu/">University of Southern California</a>, Los Angeles CA</h4><p>At the University of Southern California, I studied Architecture for a year, then gravitated toward Civil Engineering with an emphasis in building science because I favored the objectivity of engineering to the rather subjective critiques in Architecture school. I was more comfortable, but also terribly bored with Civil Engineering. Luckily, one of my jobs was working on campus at the <a href="http://www.marshall.usc.edu/">Marshall Business School</a> in the computer labs. The opportunity for a modest raise was offered to anyone who could build the lab’s upcoming website, still a novel thing in the mid ‘90s, I jumped at the chance. I learned on the fly and eventually was able to build a website that I would be completely ashamed of today, but I never stopped learning and I found something that I enjoyed.</p><h4>Shah: <a href="http://www.wichita.edu/">Wichita State University</a>, Wichita KA and <a href="http://www.iub.edu/">Indiana University Bloomington</a>, Indianapolis IN</h4><p>I began pursuing an Accounting degree in Bangladesh. On a whim, a couple friends and I applied to Wichita State University. I arrived in Kansas and so began my higher education pursuits in the US of A.</p><p>I was majoring in Business still until I took an intro course in Electrical and Computer Engineering. It came naturally to me, so I switched majors. Through college, I worked at LSI Logic assisting and testing digital circuit designs for RAID controller systems. I also obtained a solid entry-level grasp on network engineering with Cisco routers and switches. Alas, the first dot-com sneeze came right around graduation. The hardware companies caught that cold, and with it, the hiring freezes. This was a predicament, especially as an international student.</p><p>I realized the software side of the technology coin was the answer for me. The versatility, its application across a wide variety of industries and the option to go solo was very appealing. I went on to get a Masters in Information Science at Indiana University. It was an intense and transformative period of retooling. I was a graduate research assistant working on citation analysis and information retrieval systems, while my other coursework delved into user-centered design methodologies and human-computer interaction. It was just the springboard I needed and I’m thankful to be doing what I do now!</p><h4>Luke: <a href="http://ucdavis.edu/">UC Davis</a>, Davis CA</h4><p>I went to UC Davis after graduating high school in 1996 (Can’t believe it’s been almost 20 years). Originally I began studying Electrical Engineering but after completing 2 years of all the pre-requisite engineering courses, all the math, all the science, all the programming, it dawned on my that I didn’t really like any of that. The more CS courses I took, the more I realized that I did not want to spend 8 hours a day looking at code. I always had a good eye for design, so I switched to getting a Design degree. Learned about type, layout, presentation, photography, graphics and actually enjoyed it. I graduated in 2000 and got a job at E.piphany in the Bay Area.</p><p>It was towards the end of that job that I started getting into some basic web programming. I started to realize that I was either too practical or too sensitive for people to tell me that a design “sucks” or that they don’t like it. All while not being able to give any actual helpful criticism as to why it “sucked”. So I dove into front end web development head first and haven’t looked back. Turns out I ended up looking at code 8 hours a day anyway.</p><p>I feel like my engineering and design backgrounds made me into the ideal front-end developer. Somebody that could implement a pixel perfect design while at the same time doing it in a way which wouldn’t make Shawn yell at me.</p><h4>Klaus: <a href="https://www.stanford.edu/">Stanford University</a>, Palo Alto CA</h4><p>I grew up clicking ‘view source’, and learned web development from one of the oldest tutorial sites out there: htmlgoodies.com. When it came time to apply to college, I already knew that I wanted to program for a living. My freshman roommate at Stanford cautioned that a CS degree involved lots of sitting in front of the computer. Though this did not deter me at the time, I was surprised by the amount and richness of the theory behind programming, and I got to learn much of it from the people who wrote the authoritative texts on the subject.</p><p>Programming is still a novelty for me. I keep finding new ways to apply what I know to make computers solve my problems, and I hope to do so as long as I possibly can.</p><h4>Ben: <a href="https://www.dur.ac.uk/">Durham University</a>, Durham England &amp; <a href="http://www.sfsu.edu/">San Francisco State University</a>, San Francisco CA</h4><p>At Durham I was surrounded by incredible people both on the rugby field, where I captained, and in the bar, which I managed. I studied Mathematics and Computer Science but I still have nightmares about being woefully unprepared for exam period. I got through it.</p><p>At San Francisco State, I was able to study without the distractions of a social life, and I thrived. What I thought was going to be a 1 year masters spanned 3. My advisors were <a href="http://tintin.sfsu.edu/RahulSingh.html">Rahul Singh</a> and <a href="http://www.cs.sfsu.edu/~huiyang/">Hui Yang</a>. I graduated with a specialism in Computing for Life Sciences.</p><h4>Clint: <a href="http://www.calpoly.edu/">Cal Poly</a>, San Luis Obispo CA</h4><p>I started attending Cal Poly in Aeronautical Engineering convinced I was going to design the ship for the first manned mission to Mars. In fact I had a secret plan to blackmail NASA that they could only use my fantastical design if I was selected to go on the mission. However, in the mid-nineties NASA budgets were constantly getting hacked and somehow in my head the dream of going to space warped into a fear of being stuck designing bombs and fighter jets. Rather than find a way to still work in space (harder), I turned to the much more comfortable (easier) realm of computers.</p><p>I’d been programming since grade school when my dad said I could play as many computer games as I wanted <strong>IF</strong> I built the game myself. As an <em>experienced</em> programmer, I was quickly shocked by how little I understood of the fundamentals of computer science. Cal Poly took my raw ability to write code and beat into it the design principals that are the cornerstones of everything I design today.</p><p><em>Originally published at </em><a href="http://slytrunk.com/posts/188/school-for-sly-trunk"><em>slytrunk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=938841d5c350" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>