<?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 Daniel Spinosa on Medium]]></title>
        <description><![CDATA[Stories by Daniel Spinosa on Medium]]></description>
        <link>https://medium.com/@spinosa?source=rss-190a392793ac------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cSYK5V3j3mf9L2Fe.gif</url>
            <title>Stories by Daniel Spinosa on Medium</title>
            <link>https://medium.com/@spinosa?source=rss-190a392793ac------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:35:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@spinosa/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[2014: Welcome to the Year of Apple TV… not.]]></title>
            <link>https://medium.com/engineering-on-a-startup/2014-welcome-to-the-year-of-apple-tv-not-8768ded04257?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/8768ded04257</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Thu, 09 Jan 2014 13:55:34 GMT</pubDate>
            <atom:updated>2014-01-09T13:55:34.224Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unless and until video consumption is made simple and fun again, stick with BitTorrent + VLC + AirPlay.</h4><p>I’m a pretty simple consumer. I have two consumption modes: push and pull. It’s rare for me to sit down in front of the TV, turn it on, and just let the crap flow over me. With the exception of live sports, I generally avoid push and the advertisments that come with it. Pull, on the other hand, is wonderful. Give me what I ask for and take my money. Please.</p><p>Problem is, there’s no <a href="https://www.google.com/search?q=jesus+phone&amp;tbm=isch">Jesus TV</a> service that can give me what I ask for. If there was, I wouldn’t think twice about the money they’re taking from me. Maybe I’d think twice, but after that I could relax.</p><h4>YouTube</h4><p>The <strong>UX</strong> is awful. If you want to discuss that point, let’s take it outside: <a href="http://twitter.com/@spinosa">@spinosa</a>. <strong>Payments</strong> — ads — are fair. Annoying, but fair. The availability of traditional content, like TV shows and movies, is weak, but the <strong>breadth</strong> of short/<a href="https://medium.com/p/531a719bc507">new-form internet video</a> is sufficiently close to perfect.</p><h4>Netflix</h4><p>My mom can use Netflix; that’s pretty good <strong>UX</strong>. The <strong>price</strong> for reliable HD streaming content seems reasonable. The biggest problem with Netflix is <strong>breadth</strong>. Although they are the best player out there when it comes to traditional video, they are not sufficiently close to perfect. The final half-season of Breaking Bad is missing. That detail, as small as it may be, is a deal breaker. Unfortunately, a service like Netflix needs to give me what I want 99.9% of the time lest I start digging for the tiny red cancel link.</p><h4>BTV (BitTorrent + VLC + AppleTV AirPlay)</h4><p>The manual option. Download with BitTorrent, play with VLC, and AirPlay it to the big screen in the living room.</p><p>The <strong>UX</strong> is just fine… if you’re a nerd like me. The <strong>price</strong> is right… unless we care about more great stories getting told with video. And the <strong>breadth</strong> is sufficiently close to perfect. Every episode of Breaking Bad? Ready and waiting. Game of Thrones? Where would it be without BitTorrent?! This is impressive value. Unsustainable but impressive.</p><h3>INTERNET, 2017</h3><p>I’d like to see the simplicity of Netflix combined with the breadth of BitTorrent, including a fair payment system to keep the game alive. Then, for the coup de grace, bake in a little push — the stuff my friends (ie. people and algorithms who know me) already tell me to watch — and commercial-free YouTube access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*a2Gu37SqtCuu1XEmfw7kqQ.jpeg" /><figcaption>(Not) Coming Soon!</figcaption></figure><p>But I won’t see it any time soon. Not because of technical problems, those have been pretty much solved already. Because of rights issues. Fat, slow, rich incumbents do not have the same interests I do. This, by the way, is the reason we don’t have a <em>true</em> Apple TV.</p><p>PS: History has a way of turning specific predictions into embarrassing statements. I’m not privy to any conversations Apple may be having with the incumbents. But I sincerely hope they’re progressing well enough to prove me wrong. I’d happily (try to) place my foot in my mouth, sitting at WWDC, basking in the glow of the just-unveiled Apple TV.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8768ded04257" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-on-a-startup/2014-welcome-to-the-year-of-apple-tv-not-8768ded04257">2014: Welcome to the Year of Apple TV… not.</a> was originally published in <a href="https://medium.com/engineering-on-a-startup">Engineering on a Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productive Procrastination FTW]]></title>
            <link>https://medium.com/engineering-on-a-startup/productive-procrastination-ftw-e6d7515a2ce6?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6d7515a2ce6</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Fri, 13 Dec 2013 14:02:47 GMT</pubDate>
            <atom:updated>2013-12-13T14:02:47.315Z</atom:updated>
            <content:encoded><![CDATA[<h4>Procrastination is not a bad thing. It’s a natural tendency that you can take advantage of. Don’t waste it.</h4><p>When I put off the things I <em>have</em> to do, I still do stuff that pushes me forward (usually learning or creating). This morning I realized why that is. I’m not special. I happened into a fairly simple system that sets the stage for routinely productive procrastination.</p><p>If you don’t want to eat shitty food, don’t have shitty food sitting around. Urges will strike, and you won’t always have the willpower to fight them. (You may want to save that willpower for more important things, anyways.) But not doing something bad is a double negative. Even better than not surrounding yourself with shitty food: surround yourself with good snacks that keep you healthy and energized when you reach for them.</p><p>I don’t diet, per se. I follow processes (like keeping good food around) that are simple and sustainable. It keeps me happy and in pretty good shape. And it helps keep my life simple.</p><h3>Productive Procrastination</h3><p>This morning I realized that I follow a similar pattern when it comes to my creative/productive output. I surround myself with good things to do. To some outsiders this looks like a lot of ‘unfinished projects’. So be it. I’m improving and expanding my skills and knowledge.</p><p>I’d bet that when a lot of folks procrastinate, they feel bad/guilty. And rightfully so. The solution is not fighting procrastination! It’s a waste of energy to fight the tides. Let them take you places.</p><p>Start reading a book, researching a new topic, learning to code, appreciating art, improving your handwriting, riding a unicycle, laughing louder, tuning a guitar, engineering better (paper) airplanes, sketching innovating products, writing a business plan, 3D printing, daydreaming about a different world, whatever. You don’t need a goal and you don’t need to be good. Have interesting things just lying around, waiting. Don’t worry if you pick them up again. Let them sit.</p><p>In a few weeks, or months, do some reflection. Did you do anything different when you procrastinated? Did any of these new interesting things collect less dust than you expected? If you read a little less gossip and wrote half a blog post, you succeeded. Maybe one of those <em>interesting idle things</em> will turn into something big. Maybe not. Either way, it’s good. Keep going.</p><p>This has been a product of my productive procrastination process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6d7515a2ce6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-on-a-startup/productive-procrastination-ftw-e6d7515a2ce6">Productive Procrastination FTW</a> was originally published in <a href="https://medium.com/engineering-on-a-startup">Engineering on a Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[tl;dr; “Multipeer Connectivity  — NSHipster”]]></title>
            <link>https://medium.com/tl-dr/tl-dr-multipeer-connectivity-nshipster-d8773c18da1f?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8773c18da1f</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Tue, 10 Dec 2013 22:27:37 GMT</pubDate>
            <atom:updated>2013-12-16T19:07:01.828Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using the cloud is great if you have an Internet connection... what if you don’t? New iOS devices can network without it! &lt;br/&gt; Nearby users running your app can discover each other. Nearby users running *different* apps could also discover each other! &lt;br/&gt; DEV: advertise/discover peers; send messages; transfer  files;  open streams; encryption optional. &lt;br/&gt; Games, communication, entertainment, utils… the innovation made possible will be eye opening. &lt;br/&gt; #internetofthings</h4><p><a href="http://nshipster.com/multipeer-connectivity/">Multipeer Connectivity at NSHipster.com</a></p><p>Kudos, <a href="http://twitter.com/mattt">Mattt</a>. Big fan.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8773c18da1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tl-dr/tl-dr-multipeer-connectivity-nshipster-d8773c18da1f">tl;dr; “Multipeer Connectivity  — NSHipster”</a> was originally published in <a href="https://medium.com/tl-dr"> tl; dr; </a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shipped is Better than Perfect]]></title>
            <link>https://medium.com/engineering-on-a-startup/shipped-is-better-than-perfect-bd1b92d19382?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd1b92d19382</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Tue, 03 Dec 2013 14:15:25 GMT</pubDate>
            <atom:updated>2013-12-03T14:15:25.783Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYxtnsdB0s_HeRO9PuUAUw.jpeg" /><figcaption>hic svnt dracones</figcaption></figure><h4>You can’t score from the sidelines. I’d like to help you get out there, mix things up, and ship your product.</h4><p>Changing the world isn’t easy. I won’t be satisfied until I do, and even then, I won’t stop trying. To change the world, you must ship your product. But the idea of “just ship it” is deceptively simple.</p><p>You put your heart and soul into your creation, it’s right that you want it to be as great as possible before letting your baby out into the world. I’ve been through it; <a href="https://medium.com/on-startups/c9ee6ca77e03">building</a>, iterating, <a href="https://medium.com/on-startups/8350168e1e1d">throwing it away</a>, holding back for too long, and releasing too soon. Deciding when you’re ready to ship is a nuanced process with many inputs where it’s difficult to analyze the result.</p><p>Perfection is no guarantee of success, but failure is certain if you never ship. And ship, you must. <strong>I’ve got a few tips for <em>Getting to Shipped</em>…</strong></p><h3>Address Common Reasons for Stalling</h3><p>Whatever your role — from CEO, engineer, or designer to caring outsider like mentors and family/friends — the final decision to ship may not lie with you, but you can still affect the decision. It may be your product team, investors, cofounder, or even the voice in your head; you’re going to debate <em>when</em> you should ship. In that discussion, there’s a good chance you hear one or more of these lines:</p><h4>“Good is the enemy of great”</h4><p>This is true. When the market thinks a product is good, the creator has less incentive to push themselves. They may settle for good instead of striving for greatness. This applies to companies with some amount of success. It does not apply when you’ve yet to ship.</p><p>If you hear this objection — implying that your<em> unshipped product isn’t good enough</em> because it’s not perfect — you ought to point out that “perfect is the enemy of good”. You face the law of diminishing returns, the 80/20 rule. Additionally, <strong>your perception of great will be much harsher than that of your customers</strong>. Those are the opinions that really matter. Get your product in front of them. <a href="http://www.youtube.com/watch?v=NflTOYuVJ0E">Do it now!</a></p><h4>“We need more UX testing first”</h4><p>Mockups, hallway tests, UXTestingWhatever.com, iOS Enterprise Program, strangers in Starbucks, and any other way to get feedback are indispensable.They’re also insufficient. Proxies for real world usage are both lacking (because they’re approximations) and disengeneous (situation and context are contrived). While you can make marked improvements, find and fix bugs, and test on users without the curse of knowledge, it’s simply not the same as being exposed in the wild.</p><h4>“We have a reputation to worry about”</h4><p>True, you only have one chance to make a first impression. When Apple launches a piece of hardware, they have one chance to nail it or embarrass themselves. <strong>You’re not Apple and the world is not watching you</strong>. Worrying about reputation assumes that (1) you already know who you customer is and (2) you’re able to distribute to them. Your first users will be early adopters, willing to overlook imperfections and quick to tell friends they “always knew” your product was great.</p><h3>Inspire “<em>Getting to Shipped”</em></h3><p>Getting your product shipped, or convincing others that it’s time to ship, is a marathon, not a sprint. Sometimes, it’s not direct debate that gets you there. It’s the culture, the mindframe of the decision maker, or a combination of so many little things you can’t put your finger on. It may seem cheesy on the surface, but I’ve found quotes like these useful for myself and for others. They don’t have to be on a poster or in your email signature, post-it notes work just fine for me.</p><blockquote>A ship in port is safe, but that is not what ships are built for. Sail out to see and do new things. — <em>Grace Hopper</em></blockquote><blockquote>Give them the third best to go on with; the second best comes too late, the best never comes. — <em>Watson-Watt</em></blockquote><blockquote>No plan survives contact with the enemy — <em>Helmuth von Moltke the Elder</em></blockquote><blockquote>The question isn’t who is going to let me, it’s who is going to stop me — <em>Ayn Rand</em></blockquote><blockquote>Don’t sweat the petty things and don’t pet the sweaty things — <em>George Carlin</em></blockquote><h3>It’s Good, Keep Going</h3><p>In time you’ll look on your product, compare it to what you first shipped, and feel embarassed. We should all be so lucky.</p><p><strong><em>Remember, shipped is better than perfect. It’s never done.</em></strong></p><p>Did you find this interesting or useful? Would you like to sign up for our monthly newsletter, where we talk about building startups and lessons learned? <a href="http://eepurl.com/HLr1T">Subscribe to the Shelby TV newsletter here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd1b92d19382" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-on-a-startup/shipped-is-better-than-perfect-bd1b92d19382">Shipped is Better than Perfect</a> was originally published in <a href="https://medium.com/engineering-on-a-startup">Engineering on a Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple ❤ Zombies]]></title>
            <link>https://medium.com/engineering-in-a-startup/apple-zombies-c7b348d8014d?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7b348d8014d</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Thu, 07 Nov 2013 17:56:55 GMT</pubDate>
            <atom:updated>2013-11-07T18:12:14.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*2XFNjZR_C8Iv-9FBF9he-g.jpeg" /></figure><h4>or How I learned to stop worrying about EXC_BAD_ACCESS and work around Apple’s bug.</h4><p>When your app crashes, it’s your fault. Normally that means you did something dumb. But sometimes it means Apple did something dumb and <em>you forgot to work around it</em>. That happens to be the case with <strong>UIScrollView</strong>’s delegate and me.</p><p>The situation was all too familiar: occasional crash reports without useful stack information providing no help reproducing or fixing the crash. Fortunatley, I stepped in shit while debugging something else and could reproduce the <strong>EXC_BAD_ACCESS</strong> on command.</p><blockquote>Zombies, like farts, are often silent but deadly. Thankfully Xcode has <strong>NSZombieEnabled</strong> to help clear the air.</blockquote><p>Turning on <strong>NSZombieEnabled</strong> made it obvious: the delegate of my scroll view was being sent a message from<em> </em>the scroll view <em>after</em> it was deallocated. This is, of course, impossible with ARC; weak refernces to the delegate are set to <strong>nil</strong> when the delegate is deallocated. Only, it was possible. I was watching it happen.</p><p>Somewhere in the depths of the framework, Apple is holding an <strong>__unsafe_unretained</strong> reference to the delegate. Those don’t get set to <strong>nil</strong> when the object is deallocated, hence the <em>unsafe</em> part. The <strong>delegate</strong> property of <strong>UIScrollView</strong> is certainly <strong>weak</strong>, or this would blow up all the time. So, where is the problem? I don’t know for sure, but I have some idea where this pointer is dangling…</p><blockquote><em>Dan: 1 — Zombies: 1 (a tie goes to the coder) </em><a href="https://github.com/spinosa/DSZombieScroll"><em>https://github.com/spinosa/DSZombieScroll</em></a></blockquote><p>Calling <strong>[someScrollView setContentOffset:offset animated:YES]</strong> and then immediately deallocating the delegate (ie. before the animation is complete) produces the crash. To see it in action for yourself, check out my little example: <a href="https://github.com/spinosa/DSZombieScroll">DSZombieScroll</a>. It seems that Apple hangs on to the <strong>__unsafe_unretained</strong> pointer during the animation.</p><p>The workaround depends on your situation,but it’s probably simple. For my fix in the <a href="http://shelby.tv/">Shelby</a> codebase, I just rearranged the order of deallocation.</p><p>My relationship status with Apple remains love/hate. Which is usually a pretty big number.</p><p>Radar # 15403528</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*ZQdxaVOtMjyO0FnQeqRlqw.png" /><figcaption>Dan ♥ XKCD</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7b348d8014d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-in-a-startup/apple-zombies-c7b348d8014d">Apple ❤ Zombies</a> was originally published in <a href="https://medium.com/engineering-in-a-startup">Engineering in a startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code as Crutch]]></title>
            <link>https://medium.com/engineering-on-a-startup/code-as-crutch-59b07771d524?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/59b07771d524</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Thu, 07 Nov 2013 14:03:21 GMT</pubDate>
            <atom:updated>2013-11-07T14:03:21.411Z</atom:updated>
            <content:encoded><![CDATA[<h4>From programmer to manager to mentor — this CTO learned the hard way that code isn’t the answer to every problem.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*6vW5RFWUkGPWyez0N9JYIQ.jpeg" /><figcaption>image credit giantfreakinrobot.com</figcaption></figure><p>“Addiction is the continued repetition of a behavior despite adverse consequences” — Wikipedia. Although some engineers put on a bit of weight and lose a bit of muscle, coding won’t exactly turn your eyes yellow and make your teeth fall out. While coding can most ceratinly be addictive, it’s a different type of addiction. If you’re not a coder, let me try to pull back the curtains.</p><p>I was 10 or 11 when I wrote my first lines of code. I copied some BASIC directly from the pages of the excellent magazine “3 2 1 Contact”. Then I hit F5, the keystroke to execute your program in MS-DOS QBasic. Running that program was a serious rush. The computer was doing what I programmed it do. I could go back to my code, make a little change, and the machine responded. The power of creation, in my hands. So rapid and so rewarding. (I wish I had a picture of how goofy-excited I must have looked)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*gs-pBa9Z7Lb1nsCed1_1VA.png" /><figcaption>“3 2 1 Contact” + QBasic was my <a href="http://codecademy.com/">Codecademy</a></figcaption></figure><p>I’m not a stereotypical computer prodigy; it wasn’t until college that I really got into coding. But once I was hooked, holy shit was I hooked.</p><p>Ten years later I’m running my own venture backed startup (which I co-founded with my good college buddy <a href="http://medium.com/@reece">@reece</a>) and completely addicted. Write a little code, run it, feel the rush when you see your new creation take shape. That was my routine. But just like any other drug, it never feels quite the same as it did the first time. So I wrote increasing amounts of code which drove me to write even more code. This was great, because we had a ton to build. And unlike a drug, I thought everybody around <em>wanted</em> me to write more code. I thought it was <em>expected</em>.</p><blockquote>crutch /krəCH/ noun. “a thing used for support or reassurance.”</blockquote><p>Indeed, writing code was required. We had a lot to build, and <a href="http://shelby.tv/">we built it</a>. We executed. <a href="http://shelbytv.tumblr.com/post/58356637838/oh-memories-when-we-won-tnw2012-startup-rally">We launched</a>. And like most startups, we needed to <a href="http://shelbytv.tumblr.com/post/60197824397/introducing-the-featured-section-and-more">iterate</a>. So we went to the whiteboards and brainstormed. Then we walked away, put the <a href="http://reecepacheco.com/post/6452490294/the-headphone-rule">headphones</a> right back on, and started coding the ideas we dreamed up. I was working hard, but I was only working <em>in</em> the company. What I didn’t yet appreciate is that a cofounder/ CTO needs to be working <em>on</em> the company as much as they work <em>in</em> it.</p><h4>maker :: manager — an evolution</h4><p>We’re a smart and creative group of individuals; we get shit done. It didn’t occur to me that we might need more direction and structure to continue executing at the same level. As the product and team grew, it was no longer eficient for me to simply hold the entire plan in my head. I couldn’t expect our team (engineers or otherwise) to get by on the occasional ad hoc conversations.</p><p>I didn’t realize this because, while I was coding away and indulging my addiction, my team needed me. In one-on-one reviews with myself and Reece, they made it clear that we needed more structure and guidance. Realizing there was a leadership vacuum, I committed to evolve from “maker only” to a balance of “maker/manager.” After all, I owned product, it seemed natural that I needed to be the project manager that helps us get things done.</p><p>But, as the story often goes, there were false starts. We were a dynamic and highly effective team that didn’t need a full time project manager. Accordingly, that role didn’t fully occupy my time. The rest of my time was spent coding. And the coding time quickly ate into the management time… which I was fine with. :-]</p><p>I don’t like management (from either side of the table). And I’m not particularly good at it (very little practice). Coding, on the other hand; I like it and I’m good at it. Whenever I encountered some non-coding shit I didn’t want to do, it was easy to substitute a bit of engineering: bug fixing instead of organizing Trello; refactoring instead of reviewing deadlines; system planning instead of project planning; code was still my crutch. I had not become our project manager. Hashtag fail.</p><p>Not being one to give up, I searched for another way to lead the team (other than traditional management). We were working on our iOS product and it was the one git repo I hadn’t pushed to. So I jumped on the iOS team, trying to lead from the front. It should have been obvious at the time that I was just leaning on the same old crutch. But I was able to frame it internally as a leadership opportunity.</p><p>We built a great product (which I’m excited to be launching very soon) but this didn’t solve my “maker/manager” balance. It only exacerbated my use of code as crutch. The company didn’t need incremental product features, but that was the path I was on. Critically, I had to change course without a clear new heading.</p><h4>what’s my problem?</h4><p>Accepting that you have a problem is never easy. It was even more difficult in my case because nobody — myself included — identified my problem. Self reflection revealed that something was wrong, but I honestly had no idea what. I accepted that I had a problem without knowing was it was, and set off in search of it.</p><p>Identifying my problem — using code as a crutch — was much like a bug hunt. There was no eureka moment. I systematically explored options, eliminated the weakest theories, and cast a net as wide as I could. During one of my many conversations, Reece mentioned the idea of a crutch. Something in my brain connected that to the idea of code and I ran with it.</p><h4>not exactly cold turkey</h4><p>It’s been several weeks since I’ve gone heads-down in the code for more than half a day at a time. In fact, I’ve completely flipped my code to non-code ratio. It feels good. I’ve been reflecting on my role at Shelby and focusing more <em>on</em> the company. Compare that to the prior six months where my focus was nearly 100% in the code. It was the right thing to do; I built something great with my team. But while my head was down it was almost impossible for me to see anything else that was going on. That’s dangerous for a founder.</p><p>I still think I do an exceptional job of deleting email, turning off all notifications, and focusing on my work. The difference is, my work no longer consists of pure code. I spend a more appropriate amount of time thinking at a high level about the big picture, writing, and discussing these important ideas. Ironically, by not isolating myself coding on a focused area of the product, I’m able to stay more involved with the rest of team and what they’re building.</p><h4>maker :: mentor — a work in progress</h4><p>It’s an ongoing process. I’m working to become more of a teacher, which is incredibly rewarding. I’m allocating more of my time to design review, code review, pair programming, whiteboard sessions, and collaborative deep dives into bugs and/or curious technical events. For a while I was trying to find the proper “maker/manager” balance. That’s been replaced with a drive to find the “maker/mentor” balance (still has a nice ring to it).</p><p>I always start my days by attacking the highest value task. Although I’m most proficient with technical problems, they’re not always the highest value targets (and it’s easy for them to suck in the rest of my day). Some high value tasks lie outside of my engineering domain. So I work to eliminate tunnel vision and find a higher energy state beyond my local maxima.</p><p>Code still is my crutch, and probably always will be. I can live with that. Hopefully, by discussing it openly and remaining vigilant, I can prevent the next relapse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*MERRXzfJis1pfI-ebSBuYg.jpeg" /><figcaption>Bonus picutre of me. This is probably how goofy I looked when I started programming.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b07771d524" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-on-a-startup/code-as-crutch-59b07771d524">Code as Crutch</a> was originally published in <a href="https://medium.com/engineering-on-a-startup">Engineering on a Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your App is Cheaper than a Cup of Coffee?]]></title>
            <link>https://medium.com/engineering-on-a-startup/your-app-is-cheaper-than-a-cup-of-coffee-d5479475d87?source=rss-190a392793ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5479475d87</guid>
            <dc:creator><![CDATA[Daniel Spinosa]]></dc:creator>
            <pubDate>Mon, 21 Oct 2013 18:19:10 GMT</pubDate>
            <atom:updated>2013-10-22T16:42:40.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*UajPywKJybJKVhnU.png" /><figcaption>Candy Crush is Coffee</figcaption></figure><h4>App developers are short changing themselves by anchoring low, but we can fix that.</h4><p>If I can afford to spend $3 every freaking day to buy a cup of coffee — something that I use once and it’s gone — can I not afford $2.99 for an iPhone application? Of course I can. Or so the logic goes…</p><p>When you talk to me about a cup of coffee, my brain automatically and easily pulls up a bunch of connections. A cup of coffee costs a couple of dollars. It lasts for a good little while during which I enjoy the aroma and the delicious flavor. My mood improves and I feel alert and energized for some time afterward. Those all seem like pretty nice things, especially if they were associated with your app. No? No.</p><blockquote>I’d be a fool not to load my $600 iPhone with equally valuable and beautiful apps.</blockquote><p>Coffee is cheap and effective. Your app is just cheap. I have no idea if it’s effective. Or enjoyable. Will it make me feel good, like any crappy coffee can? Or will I regret wasting my $ on your app? I did not wake up thinking “shit man, I need that app.” But that’s exactly how I felt about coffee, so I went out and bought some. Unlike coffee, my loss aversion subsystem kicks in when I consider purchasing your app.</p><p>There are two Apple-sanctioned ways for you to get into my wallet directly through the App Store. One, quickly growing in popularity, <em>In App Purchases (IAP)</em>. The other, a classic, <em>Up Front Pricing</em>. Coffee can teach us lessons about both.</p><h4>In App Purchases</h4><p>Candy Crush is an excellent example of effective IAP for one main reason: <strong>Candy Crush is coffee</strong>. The same could be said for Words with Friends, FarmVille, Letterpress and more. Folks get their first taste for free. They know the product works, they start craving the endorphins, and now they’re addicted. They want more and they’re willing to pay $.99. Not a big deal for another delicious hit.</p><p>If your app can be delivered like coffee, please do so. It’s not a gimmick. It’s a nice way for you to build trust and earn my dollar. Some apps don’t fit that mold; please don’t force it.</p><h4>Up Front Pricing</h4><p>You’ve built something that is well worth a few bucks. I’ve bought an iPhone, yet I won’t spend $2.99 on your app? Bullshit, I’ve got $2.99. But my loss aversion subsystem has kicked in and I’m taking time to evaluate the price of your app so I don’t feel the sting of buyers remorse. Worse yet, your marketing says something like “for the price of your daily coffee yadda yadda yadda.” You’ve just anchored my thinking at $3, making it <em>more</em> difficult to justify the price of your app. I <strong>love</strong> coffee at $3, why would I spend the same on <strong>something I don’t even know?</strong> Can you set a different anchor so it’s easier for me to just buy your app?</p><p>Maybe you can remind me that the iPhone 5s costs over $600. That might set a good anchor. It’s a beautiful piece of engineering and it’s worth every penny. I love my iPhone. I don’t want to fill it with cheap crap. If it costs $600, I’d be a fool not to spend $2.99 on the best apps available, with beautiful design, elegance, and without ugly ads.</p><p>I’m not sure what would work as the best anchor. But I would love to see some trials in the real world and hear about the results.</p><p>There are other business models, of course. Some are more annoying or ugly than others. But for small startups and lone developers, revenue direct from the App Store is convenient and simple.</p><p>If you’re making something people want, you can figure out a way to turn it into cash (or BitCoin). Whatever you do, don’t start by anchoring with the price of coffee. As logical as it may seem, it does you more harm than good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5479475d87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-on-a-startup/your-app-is-cheaper-than-a-cup-of-coffee-d5479475d87">Your App is Cheaper than a Cup of Coffee?</a> was originally published in <a href="https://medium.com/engineering-on-a-startup">Engineering on a Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>