<?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 Chris Hollander on Medium]]></title>
        <description><![CDATA[Stories by Chris Hollander on Medium]]></description>
        <link>https://medium.com/@chrishollander?source=rss-1769469ac9d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DELLosPk07Gu60cI.jpg</url>
            <title>Stories by Chris Hollander on Medium</title>
            <link>https://medium.com/@chrishollander?source=rss-1769469ac9d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:48:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrishollander/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[Freeze Frame, Record Scratch.]]></title>
            <link>https://medium.com/some-assembly-required/freeze-frame-record-scratch-b9a25b89260c?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9a25b89260c</guid>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[parenting-toddlers]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Thu, 05 Apr 2018 00:01:01 GMT</pubDate>
            <atom:updated>2018-11-14T17:16:43.759Z</atom:updated>
            <content:encoded><![CDATA[<p>You may be wondering, What’s happened (in the 18 or so months…) since the last time something new has been posted here?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JFKlRzdRmDs60Lwf_0k4TQ.jpeg" /></figure><h3>Home.</h3><p>Fiona is a big girl now :) In August of 2016, she had just turned 2, and we were firmly planted in toddler territory. Now, we have a big girl that goes to school 3 days per week, tells great jokes, eats cheeseburgers, has different favorite songs that mommy and daddy sing to her, loves gymnastics, and is doing great in swimming class. She tells me which of her toys are ‘EPIC’, and which are ‘for babies’. We all cook together. On the whole, we’re a happy family that loves to spend time together exploring and learning about the world that we live in.</p><p>We want to make sure that Fiona can experience the wealth that comes from spending time with family outside the contexts of weddings and funerals, so we are doing our best to visit with all of our Aunts and Uncles and Cousins, on any and all sides of the family, whenver we can. Fiona is blessed with her Granddad (whom she sees all the time!), Nanna, and Pop-pop (who travel from Atlanta as often as then can), and her two uncles- who, as of late 2017, actually are living in the same city for the first time in over 20 years.</p><h3>Work.</h3><p>Before August 2016, my professional responsibilities included designing, building, and maintaining technology that directly affected what tens of thousands of students learned in math class. As exciting as that work was, it also came with long stressful hours, late night emergencies, and interrupted weekends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dw1oLAKf7a8qk9jMv8P6tg.png" /><figcaption>Visualizing the projected outcomes for thousands of students.</figcaption></figure><p>Since then, my role has evolved to focus more on research, evaluation, and exploration into how technology can improve educational outcomes. This work is challenging me in new and exciting ways, but more importantly has given me the space that I need to be a better leader at work, and better team member at home.</p><h3>Play.</h3><p>Some of you may remember that I wrote an app, <a href="https://medium.com/some-assembly-required/from-scratch-leaky-abstractions-d2bd1f8baa34">Routinely</a>. The work involved in writing, maintaining, and supporting an app- even a silly, simple little app like mine- is surprisingly substantial, and severely underappreciated. The time that I spent on Routinely has given me a profound appreciation for all of the hard work that must go into so many of the apps that I’ve come to depend on for my livelihood, my happiness, and my day to day operations. Beyond that, working on a real live iOS app has exposed me to an entire ecosystem of amazing tools and technologies that I plan to take advantage of in other endeavors.</p><p>If that were all that Routinely did for me, I would chalk it up as an uncontested win, but the story certainly doesn’t end there. First, actually using the app has helped me expand and improve my day to day and week to week routines. It’s also been invaluable in ‘reality testing’- at times, it may have felt like I was waking up at 5:15AM every day for 6 months, but in reality it was more like 6:37am on average, with about 8 mornings earlier than 6AM. Then, apart from the benefit that I personally acrrued, It’s been amazing to watch dozens (at first), and then (eventually) hundreds of real people across the world incorporate my app into their daily routines.</p><p>Photography continues to be a fun distraction, though more and more, my iPhone has become my camera of choice. So often, the ability to instantly capture moments either as still or live photo outweighs the improvements in optics that come from dedicated cameras. I’m excited, though, at the prospect of having a camera that flies- drone photography looks incredibly fun, interesting, and challenging, and I hope to write more soon about my initial forays into this new (at least, new to me!) realm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpyxVnRhuVwno9kCO4a13Q.jpeg" /><figcaption>Waterfall in Alaska. Long exposure, taken with iPhone 7s.</figcaption></figure><h3>The World.</h3><p>In August of 2016, we had a government that wasn’t embroiled in constant scandal, and who’s policies and practices weren’t thinly veiled attacks based on xenophobia, bigotry, sexism, and greed. Today, we have a front row seat to watch as pillars of our society and our government collapse- entire departments, programs, treaties, and international agreements are being dismantled.</p><p>Fear is pervasive. People of color believe their lives are threatened by systematic injustice exhibited in the very institutions in place to protect them. Many citizens fear their constitutional rights are on the verge of being infringed, while others fear that their lives could be taken in an instant by gun violence. Citizens fear that their jobs and livelihoods are at risk, which others who have fled corners of our world that are literal war zones fear that their amnesty may expire. Some children fear they may be ripped from the only homes they have ever known, while others fear that their own health needs, or the health needs of their family members, will no longer be met.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-dVH1uywduiP42z1GaKoCw.jpeg" /></figure><p>But where there is fear, there is also hope. The next generation has begun to teach all of us how truly powerful the interconnection enabled by the internet can be- we are seeing the birth of a movement that will certainly change the story of our country for decades to come. Our society has also reached a tipping point at which the pervasive misogony that has silenced half of our voices for decades can no longer be tolerated.</p><h3>Writing.</h3><p>Given all of this, writing here has been hard for me. There has been so much to tackle, and so little time- trying to concisely assemble coherent thoughts has been consistently difficult, but I’ve tried today, and I’ll try again soon. hopefully the next time I write here will be less than two years from now, but we’ll let the chips fall where they may.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9a25b89260c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/freeze-frame-record-scratch-b9a25b89260c">Freeze Frame, Record Scratch.</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Scratch: Introducing Routinely!]]></title>
            <link>https://medium.com/some-assembly-required/introducingroutinely-9cfd40b6a3f1?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cfd40b6a3f1</guid>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[from-scratch]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[healthy-habits]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Sun, 21 Aug 2016 03:56:21 GMT</pubDate>
            <atom:updated>2016-08-21T04:03:25.173Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago, I began <a href="https://medium.com/some-assembly-required/from-scratch-2ab1fb1b2243#.ubgcr2zc3">playing with the idea of developing an app</a>. I decided to some of my nights and weekends time towards ramping up the skills, tools, and techniques that go into creating a mobile app, and getting it published on the app store.</p><p>Three months later, I’m proud to introduce <a href="https://itunes.apple.com/us/app/routlinely/id1135990298?ls=1&amp;mt=8">Routinely</a>: an app that helps you establish, track, understand, and be more mindful of your daily routine. You can create goals for each of the tasks or habits that make up your day, and then track how well you accomplish those goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8gABY17p0VwQfSoWwNtgKg.jpeg" /><figcaption>Some of the goals that make up my daily routine, in Routinely.</figcaption></figure><h3>Features</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/1*N3Ekbix8iG_yruZSUogH9A.gif" /><figcaption>Create a set of Goals that make up your daily routine</figcaption></figure><p>Routinely lets you organize the tasks and habits that make up your daily routine as a set of Goals. Each Goal is given a full name and an abbreviation; you can use an emoji as the abbreviation to make your goals more visually distinctive.</p><p>You can create custom goals from scratch, or choose from a library of examples. Your phone will notify you when it’s time to complete each of your goals- and, you can create alternative completion targets for different days of the week.</p><p>You can go back and review how you did on specific days, and get a report of which goals were completed (and when), and which were missed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*gcGxvTnXfNSJMg5_E_A-Rw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*19Q4_EMsrHs8VlLhLgH2Lw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*RU970flYdNcxCQnVdyO3cg.gif" /><figcaption>Creating, Completing, and Editing Goals</figcaption></figure><p>There are a handful of other features: Routinely tracks completion streaks, allows goals to be temporarily disabled, and calculates average completion time. Goals can be marked as completed through notifications, and you can find goals by searching using spotlight. If you have an Apple Watch, notifications will flow to your watch, and allow you to complete or snooze goals from your wrist.</p><p>There’s still a ton of features that I want to add, but I figured this was a good time to get a working application into the hands of users, so that actual usage could help guide the path forward.</p><h3>The road to Routinely</h3><p>It’s been a fun ride, getting to this point. When I took on this effort a few months ago, I expected that learning the details and intricacies of iOS would take up the majority of the few hours that I had available to devote to this; I had also heard horror stories about dealing with App Store submissions and rejections, and had mentally prepared myself for challenges like these.</p><p>After a few weeks, I realized I was barely half right- the iOS APIs and SDKs are wonderfully designed, and a pleasure to work with. Completing features, finding documentation, and finding community examples of approaches, best practices, and solved problems was easy and fun. Given my previous dev experience, choosing Xamarin as a development platform contributed greatly to the ease of this part, but the real value comes from the breadth and depth of the vast community of amateur and professional developers that make up the iOS ecosystem. The aspect of reading examples in Objective-C or Swift and transposing them into working C# code was rarely a problem- however, the lower level obstacles based on deeper technical and philosophical incompatibilities between .Net and iOS were more significant. For example, I originally envisioned an Apple Watch extension providing many of the core interactions, but that will have to be delayed until the next release of Xamarin’s software.</p><p>Further, working with the App Store and Apple’s Developer services has (so far…) been smoother than I had expected. To be fair, there is a significant <em>quantity</em> of things that have to be done (certificates, provisioning profiles, build configurations, archiving, packaging, manifests, etc.); but these tasks are (relatively) well documented, and well supported by a bevy of tools and utilities. Apple’s Test Flight service, which provides a platform and pipeline for distributing and tracking apps for beta services, has been a pleasure to use. When I submitted my app to the final review, it took less than 18 hours total for Apple to review, contact me about a minor metadata issue, validate my response, and approve the app.</p><p>In retrospect, the effort that I most underestimated was the quantity of promotional material and accoutrements required to really support a public customer base. If the code is going to be open source, then it must be properly structured, commented, and factored for public scrutiny and contribution. If the <a href="http://bit.ly/RoutinelySource">code is hosted on github</a>, then it really needs a decent readme file, a clear usage license, and proper attribution for all libraries and tools utilized. There should be a website, with screenshots and demo videos. The App Store submission itself requires descriptions, marketing links, contact links. There needs to be s<a href="http://bit.ly/RoutinelyFeedback">ome mechanism for customers to submit bugs, issues, questions or enhancements requests</a>.</p><p>I’ve been most pleasantly surprised by the ecosystem of available services that support continuous integration. It took just about a morning’s worth of work to transition to code that only ran on my machine to code that was hosted, built, signed, packaged, deployed, and delivered in the cloud- and all of <em>these services are available for free</em>. I have a well managed workflow in which I can author code on my machine and instantly deploy it to testers without ever leaving my dev environment, complete with package management, instrumentation, logging, and (eventually) automated unit testing.</p><h3>Next steps</h3><p>Releasing this app isn’t an end, it’s a beginning. 😉 Now that actual customers might be relying on Routinely, I want to be more public about how the app will evolve over the coming months. Here’s what I have planned:</p><ul><li><strong>Focus on User Experience</strong>: The functionality, look and feel, visual appeal, speed, and responsiveness of the app are my highest priority at this point. I think there is a ton of room for improvement in this area, and look forward to any and all feedback that customers are willing to provide.</li><li><strong>Apple Watch Support</strong>: Today, Routinely (and actually, any app that provides notifications) can send notifications to my Apple Watch, which I can respond to by specify actions; I can mark a goal completed, or record an earlier completion, or snooze the notification. There isn’t a way to browse through my list of goals or add new goals, though, and there isn’t a way to view goals as a complication on the watch face. Due to some recent updates to Xamarin, there is now a way to do this- and i’m looking forward to adding this functionality to Routinely.</li><li><strong>Other types of Goals</strong>: Today, Routinely supports target time based goals; when you create a goal, you can specify a time upon which you would like to complete the goal, and Routinely will help you accomplish that. However, there are plenty of other types of goals; to start, I can imagine goals that target completing an activity either a minimum or maximum number of times per day (e.g., <em>drink at least 8 glasses of water</em>, or <em>smoke less than 2 cigarettes per day</em>). I can also imagine duration goals (eg., <em>spend less than 45 minutes per day commuting</em>). I would also like goals with relative targets (e.g., <em>have breakfast within 30 minutes of waking up</em>). Adding things like this will certainly add value to Routinely, but will also add complexity, and that tradeoff will have to be carefully balanced.</li><li><strong>Location Integration</strong>: Today, when a goal is completed, Routinely saves the timestamp of the completion. If the app captured the exact location upon completion as well, that would open up new use cases and insights. For example, Routinely could come to recognize the restaurants you’re most likely to visit, and then (based on the target time of your goals) ask you if you’re about to have lunch or dinner when you get close to one of your favorites. The app could also provide a map of completions for each goal, and automatically trigger goals when you arrive at certain locations.</li><li><strong>Health Kit Integration</strong>: Many of the goals that I imagine folks will create with this app are related to health and fitness, and Apple already provides a great platform for collecting and sharing this data amongst different apps on your phone. If Routinely were to integrate with Health Kit, then when using any of the dozens of great exercise apps on your phone, goals in Routinely could be automatically completed.</li><li><strong>Sharing</strong>: After talking with a handful of beta testers, the ability to share a goal with friends or partners/spouses has come up consistently. Doing this opens up a whole new realm of uses, and also opens up a whole new world of challenges: web services, synchronization challenges, privacy, security, and encryption.</li></ul><p>Working on Routinely has been a labor of love- I’ve learned a wealth of new skills, and hopefully have created something that will make peoples lives just a tiny bit better. If you would like to track, understand, and establish the goals that make up your daily routine, then please <a href="https://itunes.apple.com/us/app/routlinely/id1135990298?ls=1&amp;mt=8">give Routinely a shot</a>. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cfd40b6a3f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/introducingroutinely-9cfd40b6a3f1">From Scratch: Introducing Routinely!</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Predicting the future]]></title>
            <link>https://medium.com/some-assembly-required/predicting-the-future-b9dcf9f84e0?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9dcf9f84e0</guid>
            <category><![CDATA[wwdc]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[macbook]]></category>
            <category><![CDATA[predictions]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 23:16:02 GMT</pubDate>
            <atom:updated>2016-06-10T15:36:36.896Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMHXMmhy3VAp7qZexEnZWw.jpeg" /><figcaption>a Modern Oracle</figcaption></figure><p>In times of <a href="https://en.wikipedia.org/wiki/Classical_antiquity">classical antiquity</a>, people relied on <a href="https://en.wikipedia.org/wiki/Oracle">oracles</a> for precognition and premonition. If you wanted to understand how the future would unfold, you would seek the counsel of a priest or priestess who had privileged access to commune with the all-knowing, all-powerful Gods. Periodically, after engaging with their Deities, the oracles would offer ambiguously worded proclamations, which you would then interpret and use to guide your actions.</p><p>Today, our oracle is the Tech Conference. Throughout the year, the Titans of Technology (<a href="https://developer.apple.com/wwdc/">Apple</a>, <a href="https://events.google.com/io2016/">Google</a>, <a href="https://www.fbf8.com/">Facebook</a>, <a href="http://build.microsoft.com/">Microsoft</a>, and others) gather thousands of their most devout acolytes in vast convention centers to anoint them with glimpses into their prescribed futures. The prophecies are delivered in vaguely coded hyperbolic language, often indecipherable to the unordained.</p><p>As inaccurate and inadequate as these prophecies may be, they are- to a certain extent- self fulfilling. Through their followers, the Titans can manifest their vision. If the vision painted by a tech company aligns with the hopes and dreams of hackers, builders, developers, and designers, then the makers will materialize it with products, apps, tools, and companies built around the future that they envision.</p><p>This is an important part of how technology evolves; materials research, Moores Law, and physics play a huge role in advancing underlying technology, but the evolutionary path that technology takes in how it impacts our daily lives is guided by the establishment of platforms, communities, and ecosystems, and aligning those organizations towards common visions.</p><h3>My Predictions</h3><p>Apple’s WWDC is about a week away, and the internet is ablaze with theories and predictions. This has been an unusual year for Apple. Apple, which has been the largest public company in the world for the past five years, has just posted the first ever decline in growth of the iPhone, and jackals are lining up, ready to pounce. Further, the other tech titans have already had their annual conventions, and have each laid out bold, grand visions of the future of computing that center around competencies that don’t align well with Apple’s strengths.</p><p>Microsoft, Google, Facebook, and Amazon are all rallying around a future of computing that combines AI, the cloud, services, and either virtual or augmented reality in which technology is invisibly woven into the fabric of our every day lives. Apple is a company that excels at creating incredible, physical products that are prominent in our every day lives, and serve as a gateway to a constellation of individual apps that provide distinct value through their explicit use. The rest of the industry is harvesting ever increasing crops of user data into massive silos to feed Machine Learning algorithms in order to enrich the personality of their digital personas. Apple, on the other hand, is doubling down on their commitments to respecting and protecting the privacy of their customers, and pushing more and more computing power into their pockets.</p><p>I think of this years WWDC as the opening statement in Apple’s defense against the industry. Apple believes in a future that centers around both magnificent products and astounding services, and I hope that this conference highlights the next steps of how they see that future materializing.</p><p>I predict these major themes will be discussed:</p><h4>Siri as a Platform</h4><p>Over the last five years, we’ve seen the rise of ‘personal assistants’- <a href="https://en.wikipedia.org/wiki/Siri">Siri</a>, <a href="https://en.wikipedia.org/wiki/Cortana_(software)">Cortana</a>, <a href="https://en.wikipedia.org/wiki/Google_Now">Google Now</a>, and <a href="https://en.wikipedia.org/wiki/Amazon_Echo">Alexa</a>, among others. They all promise to transform computing into a natural, conversational model instead of a model in which users explicitly interact with apps, but I would argue that none have really made significant progress yet.</p><p>Apple will announce a significant upgrade to Siri, in which developers can tap into a comprehensive platform for creating conversational extensions to their apps. The platform will include:</p><ul><li>Improved multi-modal interaction: you’ll be able to seamlessly interact with Siri using your voice, your fingers, gestures, or a keyboard, and easily switch between them throughout the course of a single interaction.</li><li>The merger of Notifications and Proactive: Siri will intelligently aggregate and organize the stream of notifications that we receive from the swarm of apps and services that we use, combine that information with our current context (working, driving, exercising, relaxing, sleeping, etc), and present smarter, more proactive, more actionable notifications.</li><li>Services for managing multi-actor conversations, dialogs, and tangents. This enables a developer to write an app in which you, your spouse, Siri, OpenTable, Fandango, and Uber have a normal conversation about what to do for dinner tonight, while also considering the possibility of going to movies.</li></ul><h4>New MacBook</h4><p>A new MacBook will be announced, complete with the <a href="http://bgr.com/2016/05/31/macbook-pro-with-oled-panel-spy-shots/">rumored digital replacement of the function key row</a>. I predict a body that is a slightly refined version of the current single-port MacBook, available in 11&quot;,12&quot;, and 13&quot; sizes. Battery life expectations will be beyond 12 hours.</p><h4>MacOS: Allow me to reintroduce myself</h4><p>After fifteen years, OSX will be renamed back to MacOS. As with every major OS release, there will be a bevy of minor upgrades and enhancements, and a handful of major updates. Here’s what I predict:</p><ul><li>MacOS will natively run universal iOS apps alongside native apps. Apps will run either windowed or full screen, and will of course work well with the side-by-side ‘snap’ full screen modes. Force-Touch trackpads will translate relatively well to direct screen interaction, and the mouse pointer will likely morph into a surrogate finger/blob. There is a <em>slim chance</em> that the screen will be touch/pressure sensitive, but I think that it will be relatively unlikely.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kbgK4Z9sy1uPMmTcRxe8eQ.jpeg" /><figcaption>The Function Row showing the Siri user interaction, as imagined by Martin Hajek.</figcaption></figure><ul><li>The new Function screen will serve as a major new platform within the OS; it will be dynamically driven through software, and will serve multiple key user scenarios out of the box: app launching, optionally replacing the Dock, and providing the visual UI for Siri interactions. Developers will be able to write apps and features that are completely contained to the function screen.</li></ul><blockquote>Update: As I thought, others have fleshed this concept out much better than I could have. <a href="http://www.martinhajek.com/macbook-meets-oled/">Martin Hajek has mocked up some great example use cases for the function screen</a>, and this matches exactly what I was thinking.</blockquote><ul><li>Dashboard, Mission Control, Notification Center, Spotlight, and the system tray will be merged into a single, coherent concept. Siri will play a big role in that new space.</li></ul><h4>Shopping</h4><p>Apple will introduce a centralized, streamlined model for buying things, centered around Apple Pay. The App Store, iTunes, and the Apple Store will all be unified into a single app, which will be extensible to other vendors as well, selling physical or digital goods or services.</p><h4>Watch</h4><p>As compared to other products, the Apple Watch has had a rocky start. I understand that might be a controversial statement; any product which has sold millions of units in just over one year has had a respectable start- but compared to other products, the Apple Watch has famously lacked direction. I predict this conference will act as a re-launch, and provide the needed direction for this product.</p><ul><li>Apple watch will be positioned as an expressive fashion device, which provides it’s wearer with important information on demand.</li><li>As such, the main interaction and navigation models will be re-worked as part of WatchOS 3.0. Features will be architected to encourage interaction that aligns with this new direction- priority will be given to Custom Faces, then (in order..) Complications, Siri, Notifications/Glances, Contacts, and finally Apps.</li><li>If there is any discussion of a new Watch, it will be a minor upgrade- improved internal components, new finishes and materials, possibly improved battery life. No new major sensors or antennae, no dramatic form factor changes, no significant size or weight changes. I don’t believe that the current watch experience is limited by hardware.</li><li>I don’t think they will introduce new bands- I think they’ll save that for the more consumer oriented launch event in September. They may, however, formally introduce an SDK that allows for bands to interact with the watch via the service port, either for additional (FDA approved) health sensors or for more mundane uses (extra battery life).</li></ul><h3>Caveats</h3><p>Lets be completely clear: these are probably horrible predictions. 60% them are going to be flat out wrong, and another 60% are completely obvious and already written about ad-nausea across the interwebs. I’m capturing my thoughts here primarily as a reminder to myself, 5 years from now, at how bad I was at predicting the future of technology. Let’s see how that plays out?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9dcf9f84e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/predicting-the-future-b9dcf9f84e0">Predicting the future</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Scratch: Leaky Abstractions]]></title>
            <link>https://medium.com/some-assembly-required/from-scratch-leaky-abstractions-d2bd1f8baa34?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2bd1f8baa34</guid>
            <category><![CDATA[from-scratch]]></category>
            <category><![CDATA[xamarin]]></category>
            <category><![CDATA[abstraction]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Fri, 20 May 2016 21:23:35 GMT</pubDate>
            <atom:updated>2016-08-04T05:03:24.407Z</atom:updated>
            <content:encoded><![CDATA[<p>Software is the ultimate expression of metaphor and simile. Our world is software. We interact with software every hour of every day- our traffic signals, our screens, our cars, our currency. Software is the lifeblood of our society- the mind of our culture. A fraction of us actually write software- but what does that even mean?</p><p>Software is written using<em> programming languages</em>- which, themselves, are metaphors for actual languages. Programming languages represent a harmonic convergence of mathematics and literature: they use syntax and grammar to express algebra and logic. These languages, however, are not really languages- languages are tools that like-minded creatures use to communicate with each other. Programming languages, however, are languages built for translation: people write one language, which is then always translated into another language that machines hear. Language and translation are concepts which are inextricably and imperfectly linked: the existence of multiple languages necessitates translation, but the nature of the differences between languages ensures shortcomings. Something is bound to be lost in translation.</p><p>This is the primordial metaphor of software: a person can express an intent in one language, which a machine can then understand. This, in itself, is an abstraction: we operate under the assumption of this idea, rather than the underlying fact of translation. This primordial metaphor is imperfect in it’s simplification; there is not one language, but thousands of programming languages- and the implicit translation is the work of a “compiler”, which is in and of itself software, written using yet another set of languages. Further, the recipient of this communication is often not <em>a machine</em>, but dozens, or hundreds, or thousands of machines that ultimately contribute to deliver an experience of technology, indistinguishable from magic.</p><p>There are countless layers of metaphor, translation, and abstraction layered upon of each other, but even that if inaccurate- the concepts are not like layers of warmth that we pile on in the winter, or sediment making up the crust of our home world, or cold cuts in a sandwich: but more like the aural layers of sounds in a grand symphony- an eternal symphony with an untold number of players, and no orchestral conductor.</p><h4>App In Progress: A status update</h4><p>This has been my long-winded way of saying that software development is complex 😜 . A few weeks ago, I <a href="https://medium.com/some-assembly-required/from-scratch-2ab1fb1b2243">started sharing the journey that I’m taking from idea to working software application</a>. I’ve started this post with some philosophical background, in order to contextualize the progress that i’ve made in the past few weeks. In the next few paragraphs, I’ll outline that progress, and layout some next steps for the coming weeks.</p><h4>Progress</h4><p>Here’s what I’ve accomplished, an hour or two at a time, during my nights and weekends, since my last post:</p><ul><li>I’ve setup working <strong>software development environments</strong> for both Swift and Xamarin. This involved finding, installing, and configuring at least a dozen programs, tools, and utilities on my laptop. I also had to register for a handful of accounts with various developer programs, in order to gain access to sets of tools, certificates, and credentials that are needed to participate in the modern software development world.</li><li>I’ve<strong> built and deployed an ‘MVP’ version</strong> of the app to my phone! This is kinda a big deal, and honestly happened much faster than I thought it would. MVP stands for ‘Minimum Viable Product’- in short, it means the most basic, simple version of something. Specifically for my app, it means that I can ‘use’ the app, essentially as intended, on my phone. I can see, create, edit, and remove things, and the app looks and feels like it belongs on my phone.</li></ul><h4>Challenges</h4><p>After spending some time in both Swift and Xamarin development environments, it became clear to me that Xamarin would serve the majority of my needs better. Both platforms serve as abstractions, but with different goals: Swift aims to abstract away many of the details of developing iPhone applications by designing an entire new language. Xamarin aims to abstract away the details of developing <em>all</em> mobile apps (not only iPhone apps), by using a well known, existing language <a href="https://medium.com/some-assembly-required/from-scratch-2ab1fb1b2243#.pi3315i0d">I grappled with this choice in my last post</a>, and ultimately chose to pursue Xamarin. The value of this choice was apparent: I’ve been able to get a version of my concept up and running in about two weeks, which I now know would have taken significantly longer using Swift. There are, however, some significant drawbacks as well.</p><p>The primary drawback is that, for all intents and purposes, I’m <em>not actually learning IOS development</em>. Instead, I’m leveraging my .NET skills to write an iPhone application. I’m certainly learning many of the core constructs and concepts involved, but few of the techniques, approaches, and best practices common in the iPhone development community are directly applicable in Xamarin. Basically, the abstraction is too strong. If I were to encounter a ‘native’ iPhone developer, we would barely be able to communicate with each other. We would recognize some of the terms in each others languages, and might be able to get the general gist, but we would have different syntaxes, grammars, phrases, and slang. To add another metaphor to the mix, it would be like the <a href="http://www.switchedonpop.com/24-searching-for-max-martin/">Swedish songwriter effect</a>: the Swedes are well known in the music industry as incredible writers and producers of pop music, but its not uncommon for them to include lyrics and phrasings that just don’t translate well to American sensibilities.</p><p>The secondary drawback that I encountered is more concrete, and potentially more troublesome. As far as abstractions go, Xamarin does a pretty incredible job of abstracting away all of the details of mobile app development; 99% of the time, everything just works, and it feels like I’m doing regular, run of the mill, pedestrian .NET development. The problems come in that last 1%. When an abstraction in software development is almost, but not quite, perfect, we refer to that as a <a href="https://en.wikipedia.org/wiki/Leaky_abstraction">leaky abstraction</a>. In this case, the leaky abstraction is lack of support for a new feature that Apple has recently released, which would allow me to add a certain type of customization to my Apple Watch.</p><p>This is more of an actual blocking issue; as in, I may not be able to actually complete the application, as it was originally conceptualized. I see three potential options:</p><ol><li><strong>Restart with Swift.</strong> Since Swift is made by Apple, and since Swift isn’t trying to abstract away the same things as Xamarin, problems like this essentially wouldn’t exist. The obvious downside is that my velocity will be dramatically reduced.</li><li><strong>Attempt to use both Swift and Xamarin.</strong> So, I might be able to split my efforts, and do the majority of my work in Xamarin, and the absolute minimum amount in Swift, in order to deliver the single piece of functionality that I can’t accomplish in Xamarin. The downside is that there might be other technical roadblocks to accomplish this, and I might not find soon.</li><li><strong>Hope that Xamarin adds support for the feature I need.</strong> Ultimately, I can just wait. the feature that I’m hoping to use is popular, and I’m sure that other developers are anxiously awaiting it’s arrival. So, I’m faced with what’s known to developers as a Race Condition: What’s going to happen first? Will I finish my app, and be waiting for Xamarin to add this feature, or will Xamarin add this feature before I’m done? If Xamarin adds the feature before I’m done, then this is just an order-of-execution problem; I just have to wait to complete that particular portion of my app. If, however, I finish the rest of my app first, then I either have to decide to complete my app without the desired feature, or I have to wait for Xamarin to catch up.</li></ol><p>These are the types of problems that every software company, and by extension, every software developer, face every day. The choice often comes down to an individuals beliefs- these are matters of culture, trust, dependency, and reliance. My natural inclination is to trend towards option 3, trusting that my interests align with the interests of Xamarin.</p><h4>Next Steps</h4><p>Here’s what I’m going to be working on over the next few weeks.</p><ul><li><strong>Continued Development:</strong> The MVP delivers about 80% of the functionality of my idea- I think I can get to the 95% mark in a few weeks. As a professional developer, I’ve come to learn that that last 5% might take me at least another year, assuming it ever gets completed!</li><li><strong>User Testing:</strong> Very soon, it will be time to share my app with some folks. There are some pretty significant hoops to jump through, though, to actually get the app onto other people’s phones- so, if anyone is interested in testing, or has experience with the alpha/beta deployment process, please let me know!</li><li><strong>Code Review:</strong> Now that the code has reached an acceptable point of stability, I would love to share it, and have other developers review, analyze, and critique it. There are some steps to accomplish first; I need to host the code using a public service, enlist some friends, and properly license the code, in order to protect both myself and potential collaborators.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2bd1f8baa34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/from-scratch-leaky-abstractions-d2bd1f8baa34">From Scratch: Leaky Abstractions</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Tools we remember]]></title>
            <link>https://medium.com/some-assembly-required/the-tools-we-remember-535162b2a301?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/535162b2a301</guid>
            <category><![CDATA[macbook]]></category>
            <category><![CDATA[biography]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Fri, 13 May 2016 20:31:35 GMT</pubDate>
            <atom:updated>2016-05-13T20:36:25.641Z</atom:updated>
            <content:encoded><![CDATA[<p>My dad was the type of dad that had a favorite hammer. There wasn’t anything particularly spectacular about it; it was old and worn- made of wood, handle wrapped in rubbery black leather. In the stories I heard growing up, when he would do work around the house, I would follow him around with my own plastic hammer. Apparently, “Daddy’s Bang Bang!” were some of my first words. Dad used his hammer to hang pictures, knock down walls, stand up fences, and build the den in which we spent most of our family time.</p><p>My daughter won’t remember her dad’s favorite hammer, but she’ll likely remember the tools I use every day: my laptop, phone, tablet, and watch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSx_8xmkyv4yHwAr-ef3Ag.png" /><figcaption>My 4 month old daughter helping me with some work, December 2014.</figcaption></figure><p>I’ve had my current laptop for almost five years, or put another way, about 25% of my time as a computer user. It’s hard for me to understate how weird that seems to me- for my first 15 years of using computers, I probably went through 20 different machines.</p><p>At any given time, I likely had at least three active machines: a <em>home</em> computer (which was often a desktop PC), a company issued <em>primary </em>laptop, and an <em>experimental</em> machine. The experimental was either a bleeding-edge new machine, or an <em>anything-goes </em>machine<em> </em>about to implode under the weight of a years worth of software cruft.</p><p>There was a complicated dance in which the <em>primary</em> would begin to show signs of wear and tear, just as a new <em>experimental</em> option presented itself. The <em>experimental</em> would slowly become the <em>primary</em>, and the <em>primary</em> would turn into the <em>anything-goes</em>. The <em>home</em> and <em>primary</em> would be kept in reasonably pristine condition, while the others would be subject to varied torture tests including alternative operating systems, alpha and beta software, the general perils of active software development, and Frankensteinian hardware transplantation and transmogrification.</p><p>My MacBook Air was the end of all of this. This one machine has, for all intents and purposes, replaced the ecosystem of machines that came before it. It has been successfully upgraded through five versions of OSX and three versions of Windows (Running in Parallels). This specific combination of hardware, operating system, virtualization, and maintenance has been reliable enough to be my only computer for home, work and experimentation.</p><p>So, will my daughter remember her dad’s 2011 MacBook Air? Maybe through pictures and videos and this blog, but not from experience. Instead, she’ll likely remember its replacement.</p><h4>My Last Laptop</h4><p>The next laptop I buy will almost certainly be the last laptop I’ll buy. Assuming it’s at least as reliable as what I have now, I’ll be using it until the year 2021. I really hope that in the year 2021, computing will have advanced enough that the anchor of my computing experience will no longer be a clamshell device with a QUERTY keyboard. <a href="http://ben-evans.com/">Benedict Evans</a> recently wrote about how <a href="http://ben-evans.com/benedictevans/2016/4/20/the-best-is-the-last">technologies often reach their ideal platonic state just as they are about to become obsolete</a>; I can think of no better example than the laptop computer.</p><p>What will my next laptop be? It will certainly be from Apple, and I will most likely buy it within the next year. My current laptop is fine, but it’s starting to show signs of aging. Its boot time is just a heartbeat longer than I expect it be- its battery drops from 15% to 0% faster than when it was brand new. Other devices have better trackpads, better connectivity, and better screens. There are a handful of alternatives ranging in price from a little to a lot, with performance that nicely correlates with cost and portability concerns.</p><p>What’s the fate of my current machine? It’s hard to say- I’ve never owned a five year old computer that still works really well, and doesn’t <em>need</em> to be replaced.</p><p>Maybe when my daughter remembers how she first discovered the magic of software and the internet- of learning, discovering, and exploring- she’ll remember my current laptop as her first laptop.</p><p><em>This post is part of a series on </em><a href="https://medium.com/some-assembly-required/how-and-why-i-use-technology-d9ff5a9d7b85#.a7d955yfh"><em>How I (and why) use technology</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=535162b2a301" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/the-tools-we-remember-535162b2a301">The Tools we remember</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Scratch]]></title>
            <link>https://medium.com/some-assembly-required/from-scratch-2ab1fb1b2243?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ab1fb1b2243</guid>
            <category><![CDATA[from-scratch]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[xamarin]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Fri, 06 May 2016 22:04:10 GMT</pubDate>
            <atom:updated>2016-08-21T04:01:32.314Z</atom:updated>
            <content:encoded><![CDATA[<h4>update: <a href="https://medium.com/some-assembly-required/introducingroutinely-9cfd40b6a3f1#.lfgpo94r2">I’ve released Routinely</a>!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XI5zpPnl2GlXYhOG-37CPw.png" /></figure><blockquote>So, I’ve got this idea for an App…</blockquote><p>Its incredible how much dust those eight little words must have kicked up in the last twenty or so years. Ideas are followed by conversations, then arguments, then napkin sketches, then email threads. Eventually, after whiteboards, user stories, code, pizza, coffee, bugs, fixes, deployments, and some more coffee, some ideas spring to life. This is the first of a series of posts that will try to capture the story of how my idea turns into an App, from scratch.</p><h4>Motivation</h4><p>So, this idea that I have… it’s decent. Its not a <em>“change the world”</em> idea- Its barely a <em>“change your day”</em> idea- it’s just something that I came up with that I think will help me be more mindful, more aware, and more successful in my daily routines.</p><p>I’m not going to share too many details about the idea itself, for a couple reasons: first, I want to focus these posts on capturing the journey, not the destination. I want to capture the procedural steps along the way, and focusing on the <em>what</em> instead of the <em>how</em> will be distracting. Second, the idea itself is still only partly baked. Eventually, there will be screen shots and videos that show the app in action- that will do a much better job of showcasing the actual idea.</p><h4>How I Got Here</h4><p>I really can say that I’ve had a wonderful time writing software over the past 20 or so years. I’ve built business applications for small businesses, large corporations, and massive enterprise scale government customers. I’ve written software that has powered social networks with tens of millions of users, and have used voice recognition to help a marketplace of health care professionals. Most recently, I’ve developed cutting edge algorithms that drive personalized learning for thousands of students in schools across our country, every day.</p><p>Everything that I’ve accomplished with software, I’ve done with <a href="https://en.wikipedia.org/wiki/.NET_Framework">Microsoft’s .NET framework</a>. Naturally, I want to leverage as much of that experience and expertise as possible for my app idea.</p><blockquote>Sidebar, for my less technical readers: .NET is basically a language that people can use to describe programs to all sorts of computers, from laptops to mega-clusters of thousands of servers. Early in my career at Microsoft, I was part of a team called “.NET Velocity”, which helped get companies started writing software using .NET.</blockquote><h4>Enter Apple.</h4><p>You maybe have noticed that “App” was significantly missing from my list of software development accomplishments. There is, of course, an obvious reason for this. When the <a href="https://en.wikipedia.org/wiki/IPhone">iPhone was released in 2007</a> (or, more accurately, when the <a href="https://en.wikipedia.org/wiki/IOS_version_history#iPhone_OS_2">App Store was released in 2008</a>, along with version 2 of<a href="https://en.wikipedia.org/wiki/IOS"> iOS</a>), the world of software development was forever changed. Apple introduced the next wave of computing, and we’ve all been swimming in it’s ocean of apps ever since.</p><p>However, making apps for an iPhone has traditionally not been easy. Apple chose a<a href="https://en.wikipedia.org/wiki/Objective-C"> powerful, but relatively obscure language</a> for it’s devices, and that language was not directly compatible with .NET.</p><p>Over the past few years, the options for creating iPhone apps has expanded. A handful of companies presented ‘<a href="https://en.wikipedia.org/wiki/Cross-platform">cross-platform</a>’ <a href="https://en.wikipedia.org/wiki/Xamarin">tools</a> that allowed developers to create apps not just for iPhone, but for Android as well, using a bevy of different languages. Also, in 2014, Apple introduced it’s own new development platform, named <a href="https://en.wikipedia.org/wiki/Swift_(programming_language)">Swift</a>, which took the power and performance of their existing language and combined it with many of the features and conveniences of the cross-platform tools that had been brought to market.</p><h4>Xamarin or Swift?</h4><p>So, I’m faced with a choice:</p><ul><li>On one hand, Swift is an excellent platform for developing iPhone apps: it’s modern, well designed, and has a vibrant development community. Apple has provided excellent, robust documentation for the language, and whenever new features are announced for Apple devices, Swift will have the first and best documentation and samples to learn those features.</li><li>On the other hand, Xamarin (one of the above mentioned cross platform tools) is built around the .NET platform, which means I can more directly apply my decades of experience building software. Xamarin provides access to the same capabilities that swift offers, but will obviously lag behind Apple in it’s support and documentation of new features. Xamarin has been around longer than swift, and also has an active, vocal, vibrant developer community.</li></ul><p>I’m going to experiment with both, but Xamarin seems like the better choice. With Swift, I would be learning both a new language, and a new development paradigm; it would be like learning <a href="https://en.wikipedia.org/wiki/Jujutsu">jujutsu</a> and the Japanese language at the same time. Its certainly possible, but not ideal. Conversely, using Xamarin would allow me to focus on just learning the new development paradigm; then, If i want to learn Swift afterwards, I can focus on just the intricacies of the language, without stumbling through the motions at the same time.</p><h4>Methodology</h4><p>How, exactly, am I going to do this? I may not know exactly how i’m going to get there, but I have an idea of where I want to end up, I know of a general roadmap of how to get there, and I know what next steps I can take to make the best progress towards my destination. This is the right mindset for the practice of <a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile</a> software development. Unlike <a href="https://en.wikipedia.org/wiki/Agile_software_development">traditional software development approaches</a>, Agile focuses on learning along the way, iterating often, and adapting to needs as you discover them, instead of trying to plan for every possible eventuality ahead of time. If Agile has become a positive signal of quality for software development process, <a href="https://en.wikipedia.org/wiki/Open-source_software">Open</a> has become a signal of thoughtfulness and contribution. Though there are many definitions of open, the common thread that weaves them together is the believe that great code should be shared: sharing code allows others to both learn from and improve upon your work.</p><p>My goal is to be as Agile and Open as possible. The code will eventually land on GitHub, and I plan on openly sharing my agile artifacts (tasks, user-stories, epics, sprints, issues, etc).</p><h4>Next Steps:</h4><p>in the spirit of Agility, here are my major next steps (aka, user-stories) that I hope to accomplish in the next few weeks (aka, sprints):</p><ul><li><strong>Environment</strong>: Produce a fully functional Dev environment, that allows for simulated and actual (e.g., device) testing.</li><li><strong>Minimum Viable Product</strong>: develop a functional version of the app, that allows me to test out the most basic user stories/use cases, using my phone.</li><li><strong>Alpha Testing Plan</strong>: identify a group of folks that might want to participate in helping me design, test, and maybe even build the app.</li><li><strong>Agile Tools</strong>: find a good tool that lets me easily share Agile artifacts users and collaborators.</li></ul><p>If anybody out there has any advice or tips, please feel free to reach out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ab1fb1b2243" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/from-scratch-2ab1fb1b2243">From Scratch</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How (and why) I use Technology]]></title>
            <link>https://medium.com/some-assembly-required/how-and-why-i-use-technology-d9ff5a9d7b85?source=rss-1769469ac9d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9ff5a9d7b85</guid>
            <category><![CDATA[biography]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Chris Hollander]]></dc:creator>
            <pubDate>Mon, 02 May 2016 21:57:37 GMT</pubDate>
            <atom:updated>2016-05-13T20:39:31.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*izspE9jMu7D_6WtEGxcp4Q.jpeg" /><figcaption>486 SX2, 66Mhz, along with 4MB of RAM, resting on a heatsink. The case of my first computer is in the mid background, with my most recent MINI Cooper behind it.</figcaption></figure><p>I can still remember my first computer. A sentence like that turns itself into an anachronism as it’s being written; I am certainly among the first and last generations of people who will truly remember their first computer, and from here on out, generations to come will certainly not remember theirs any better than I can remember my first crayon, or first pencil sharpener, or first schoolbag.</p><p>But, there it is: not only can I remember <em>My</em> first computer, but I can also remember my first <em>Computer</em>. My first <em>Computer</em>, as in, the first computer that I used, was an add-on for our family’s <a href="https://en.wikipedia.org/wiki/Intellivision#Keyboard_component">intellivision</a>. It was around 1980. My brother and I wrote a program in Basic that printed “Oh Shit” on the screen. <em>My</em> first computer, as in, the very first computer that I owned, which was bought specifically for me, was a Compaq 486SX2-66 with 4MB ram, a 120mb hard drive, and a 14.4 modem. It was 1994, and I had just graduated high school. My parents offered me an option: used car, or new computer. My teenage brain reasoned that a computer could eventually buy me a car, but a car wasn’t going to get me a computer.</p><p>Saying that I “remember” my first computer is actually somewhat disingenuous, <em>because of course I remember it- I still own it</em>. Like many geeks, I have a technology graveyard, in which most of my computing history has been laid to rest. Perhaps another post will explore that further.</p><p>Fast forward 22 years, dozens of computers, and a couple of cars, and I don’t think a single day has gone by without me using a computer, in some way, shape, or form.</p><p>For me, technology has always been automatic. Until recently, I hadn’t really taken the time to think about the how, what, and why of my computing habits. Over the past few years, however, I’ve been digging into these questions thanks to a certain mix of conditions:</p><ul><li>My computing habits have changed more in the last two years than in the first 20. I’ve re-examined what were essentially life long assumptions on how to accomplish things.</li><li>Computing in the world, at large, is finally starting to truly become invisible. As technology becomes intrinsically woven into the fabric of our lives, our own awareness of how we use that technology will erode as well.</li><li>In 30 years, when my daughter is telling her children how their grandpa used to type on keyboards and plug in USB cables and measure capacity in megabytes, they literally won’t believe her, and this will be her proof.</li></ul><p>There’s going to be a lot to read here, by the time all is said and done. I plan to attack the subject from multiple angles. Optimistically, this will take months- pessimistically, years. Idealistically, this will be the beginning of an endeavor that takes a few months to kick off, but ultimately becomes something interesting, at least to myself, for years to come.</p><p>If all goes well, I’ll cover each of the following topics with a dedicated post, and then keep this post updated with links to all of them.</p><h3>What do I use technology for?</h3><ul><li><strong>Attention Management</strong>: How do I balance my time between family, work, friends, interests, and side projects?</li><li><strong>The Quantified Self</strong>: How do I keep track of myself, and what value can I derive from doing so?</li><li><strong>Memory</strong>: How much of my lifetime can I hold on to, and for how long?</li><li><strong>Communication, Coordination, Collaboration</strong>: How do I interact or work with other people who aren’t in my immediate vicinity?</li><li><strong>Transportation</strong>: How do I move?</li><li><strong>Productivity</strong>: How do I accomplish things for others?</li><li><strong>Socializing and Entertainment</strong>: How do I know what’s going on in the world?</li></ul><h3>What technology do I use?</h3><ul><li><strong>Primary computing devices</strong>: <a href="https://medium.com/some-assembly-required/the-tools-we-remember-535162b2a301?source=user_profile---------1-">My MacBook Air is the anchor of my technology</a>, but ironically, I wouldn’t call it my primary device. My primary devices are a constellation that also includes my phone, tablet, and watch.</li><li><strong>Auxiliary devices</strong>: Alexa, TiVo, etc.</li><li><strong>Services</strong>: social networks, health graphs, etc.</li><li><strong>Infrastructure</strong>: broadband internet, cellular networks, etc.</li></ul><h3>Broader topics that I hope to address:</h3><ul><li>How does the Internet work?</li><li>What is the role of technology in our society?</li><li>How do culture and technology influence each other?</li></ul><p>So, let’s see how this all shakes out. I’m interested in seeing if my own awareness of my use cases ends up influencing them, and how that gets captured here over time. It should be a fun ride!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9ff5a9d7b85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/some-assembly-required/how-and-why-i-use-technology-d9ff5a9d7b85">How (and why) I use Technology</a> was originally published in <a href="https://medium.com/some-assembly-required">Some Assembly Required</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>