<?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 Rob Chandhok on Medium]]></title>
        <description><![CDATA[Stories by Rob Chandhok on Medium]]></description>
        <link>https://medium.com/@robchandhok?source=rss-fb1a50133bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uv1kbPubV_z5GfIW.jpeg</url>
            <title>Stories by Rob Chandhok on Medium</title>
            <link>https://medium.com/@robchandhok?source=rss-fb1a50133bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:56:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robchandhok/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[slackjawed]]></title>
            <link>https://medium.com/@robchandhok/slackjawed-82972a453f00?source=rss-fb1a50133bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/82972a453f00</guid>
            <dc:creator><![CDATA[Rob Chandhok]]></dc:creator>
            <pubDate>Mon, 08 Jun 2015 15:57:43 GMT</pubDate>
            <atom:updated>2015-06-08T15:57:43.203Z</atom:updated>
            <content:encoded><![CDATA[<p><em>(or, do we really have to kill email to like chat?)</em></p><p>OK, let me start by saying I really like Slack. For our company, Slack enables a kind of camaraderie that is very difficult to obtain in a distributed team — especially a team that uses about 5 different operating systems from mobile to servers. The features are awesome, the app is designed very well, the experience is really what we wanted in a group messaging platform. And we use APIs and other hooks to make it work better, make our process better, and be more fun.</p><p>But fatigue is setting in. FOMO (fear of missing out) has started to make me feel the need to stay constantly plugged in or I might miss something. Information that people need flies by in a mixture of deeply technical content and playful chatter. Wondering where information lives is starting to nag at the back of my head. Is chat really supposed to be the solution for all kinds of communication?</p><p>I never believed synchronous messaging and chat would completely replace other forms of communication as many people are claiming. Especially ominous claims are being made about email. We&#39;ve been around on this several times before and even though the user experience is very different this time (mobile is mature, cross platform has been done right, etc.) it still can&#39;t fix one problem.</p><p>Chat is synchronous.</p><p>All work is not synchronous.</p><p>It doesn&#39;t matter how clever your searching is, backscroll is still backscroll. If discussions are all day long in chat, when do we focus and work? If we focus and work and design and create, should we not have input in the discussion just because we were not available at the time?</p><p>Usually we are pretty good about important decisions and fall into a cadence where periodic meetings happen, even though they are still group voice or video chats. And we meet as often as we can for that face to face high bandwidth connection.</p><p>It shouldn’t be a surprise to us anymore that the kind of computer-mediated communication we choose influences the style and the tone of any communication. These results have been since the early 1980&#39;s from folks like Allen Newell, Lee Sproul, and Sarah Keisler. Their studies showed great things happening when we started to use email to break down time and distance along with not so great things. Communications were perceived as more aggressive than intended among other things. This effect is so pronounced that when working on the Eudora email client in the early 2000&#39;s we added some smarts to warn the user that their language might be perceived as aggressive.</p><p>Which brings us back to Slack and chat in general. Let’s think about what we use and how that will shape the conversation and the interaction, especially ones of high complexity. Folks like Jeff Bezos reportedly don’t allow discussions without an informed piece of prose so a reasoned argument can be made. While I’m not arguing for that or any other particular style I’m suggesting we consider the kind of process we want and use the right tool. It could be that we should use Slack, Twitter, Trello, Jira, Email, Medium, PowerPoint, YouTube or a scribble on a sticky note. We should use them all. And choose depending on what we are trying to do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82972a453f00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thing Neutrality]]></title>
            <link>https://medium.com/@robchandhok/thing-neutrality-5064b3813803?source=rss-fb1a50133bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/5064b3813803</guid>
            <dc:creator><![CDATA[Rob Chandhok]]></dc:creator>
            <pubDate>Thu, 25 Sep 2014 02:22:24 GMT</pubDate>
            <atom:updated>2014-09-25T02:22:24.699Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><a href="http://en.wikipedia.org/wiki/Balkanization"><strong><em>Balkanization</em></strong></a><em>: to break up (as a region or group) into smaller and often hostile units…The term is also used to describe other forms of disintegration, including, for instance, the subdivision of the Internet into separate enclaves.</em></blockquote><p>We are at a fascinating turning point in the evolution of the Internet. So much of the tech communities’ focus has been on the app ecosystem and the cloud that we have left the messy edges of the Internet to grow up on their own. Different protocols, different radios, different models for security and privacy and trust.</p><p>That design autonomy at the edges is about to be disrupted by the the phenomena we are currently calling the “Internet of Things”. The term started out referring to new kinds devices that we were connecting to the Internet but has morphed into a term describing devices, sensing data, and even data in the large.</p><h4>What’s the problem?</h4><p>Some folks don&#39;t see a problem at all. The Internet is the Internet, after all. Even the phrase “the Internet of Everything” deconstructs to “the Internet” if you really get down to it — the very meaning of INTERnet is that internetworking between heterogeneous devices.</p><p>The core of the Internet kept true to a strongly layered design principle. The protocol layers (IP and upwards) were very separate from the physical layer protocols. I remember when we (at CMU) first got DEC bridges that actually filtered traffic on our Ethernet cables, segregating traffic to increase local capacity. This “new” feature and a host of others all happened without breaking or changing new TCP/IP layers like SMTP or FTP (HTTP wasn&#39;t around yet).</p><p>The problem is that the proximal side of connectivity hasn’t kept true to that design principle. Not because the designers and innovators were lazy, or less smart, but because the initial constraints on the problem (radios, power, chip size, etc.) were so overwhelming that it often required building intertwined systems to satisfy the basic connectivity requirements. These systems were incompatible, not IP based, and not interoperable. So we ended up with fully different solutions in unlicensed bands and even in the same band (the 802.15.4 families, for example).</p><p>The end result is a system that is counter to those original design principles of the Internet. We don&#39;t talk about a cloud server as “ethernet” or “WiFi”. But we talk about “Zigbee” switches and DECT phones and other devices by their radio connectivity. And the radios in these devices are deeply intertwined with the protocols. This would never be successful on the core of the Internet. HTTP would have been a failure if Tim Berners-Lee had said he had a great new hypertext protocol but it only worked on token-ring!</p><h4>A new approach</h4><p>The time has come to bring back those original principles with a recognition that there are new challenges as well. Let’s build systems where the radio folks can innovate without interfering with the networking protocol folks, and vice-versa. Let’s keep the interoperability of the Internet without forgetting that the Internet may need to grow and change topologies at the edges to accommodate new kinds of nodes, new use cases, and different usage requirements.</p><p>We need to stop allowing the excuse of “it’s too hard to do unless we optimize completely”. In my opinion, that is a lazy approach to the problem. We can afford to take the time to rethink now that we have far better radio and compute technology on which to base this.</p><p>This means that the standards bodies responsible for device or peer to peer radios need to stop walking their way up the stack. We shouldn&#39;t have application layer protocols that are specific to a kind of wire or radio. We shouldn&#39;t have radio standards bodies dictating how software developers should implement services.</p><h4><em>We should no longer accept that new application layer services require firmware upgrades.</em></h4><p>Some would argue that we just can&#39;t make IP work at low power, and that without squeezing every last literal bit of efficiency we can&#39;t move forward. That is an example of early optimization. The folks doing Thread appear to have found a balance with efficient radios that implement IP correctly. That means we can layer other platforms and solutions right on top, like Alljoyn or MQTT. That’s the right system partitioning.</p><p>If the Internet of Things industry fails to recognize that the layering that drove innovation and robustness in the Internet has to come to devices then they will simply be left behind by the Internet software posse. Dividing up the pie by physical connectivity type is not what grows ecosystems, so as the Internet of Things grows, the connectivity for things must be neutral and open. Software eats the world, as Marc Andreessen says, and in this case the edges of the Internet are far too tasty to ignore.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5064b3813803" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[System on a Net]]></title>
            <link>https://medium.com/@robchandhok/system-on-a-net-c71459d20c52?source=rss-fb1a50133bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c71459d20c52</guid>
            <dc:creator><![CDATA[Rob Chandhok]]></dc:creator>
            <pubDate>Thu, 24 Jul 2014 00:13:53 GMT</pubDate>
            <atom:updated>2014-07-24T04:14:26.808Z</atom:updated>
            <content:encoded><![CDATA[<h3>Locality of Reference Matters</h3><p>In many ways we have spent the last twenty years building everything into a virtual world. The vast web ecosystems has transformed not only the way that we as consumers interact with services and our friends, it has changed the way business is done. Companies can stitch together experiences and services from building blocks provided by others. Small teams can reach hundreds of millions of subscribers almost overnight. The Internet became the Web became the Cloud.</p><p>Fast forward to now where the device side of the world is becoming more than just a window into the virtual world. We are connecting new kinds of things at the edge of the network. Devices that used to be solely physical are getting computing power and connectivity. The connectivity can be used for media (replacing wires) or control (replacing hard wired systems with software).</p><p>Unfortunately this device connectivity has historically developed in silos. The physical layers (the radios) have often been designed in a fashion where upper layer protocols are intertwined in an inextricable fashion. We describe the connected things by their form of connectivity: Bluetooth headset, Zigbee light switch. We never refer to our Cloud in this way. We don’t exclaim, “that’s a great fiber channel server”. The Internet always kept the physical connectivity out of the way of the developers so that each layer (physical connections and logical services) could innovate at their own pace. Those strong abstraction features need to be brought to the edges of the network.</p><p>So here we are. Working at the transition of what will be the next phase of the Internet and the connection of billions (or trillions) of new devices to the network. What impact will this have on the protocols and basic building blocks such as identity, security and privacy?</p><p>The answer is unclear. There is an enormous amount of interesting research and commercial effort in this area. At one end, there is the approach of extending the design metaphor of the cloud to new devices by creating proxies for each device in the cloud — in this architecture, the connections are now virtual so you can wire each and every thing to anything else. The “IFTT” service is a leading example of this approach that can quickly bring new experiences to consumers by connecting different services via the Cloud.</p><p>The best example I can point to at the other end of the design spectrum is the work around autonomous (usually swarming) robots. Companies like Fluid Robotics and others are making devices that crawl, swim, fly or walk and generally can coordinate with each other. In these intense real-time environments most designers have realized that you can’t go back to the Cloud for all the communication and instead these systems use local communication meshes to share sensor data, route planning, and otherwise drive coordinated behavior.</p><p>I believe that somewhere in the middle of these two design patterns lies the hybrid approach that will come to consumer ecosystem faster than many might predict. By hybrid I mean a blend of local computing and communication that is thoughtfully connected to the Internet through well-defined and secure protocols resulting in a topology that is not unlike a system-on-a-chip (or “SoC”). In this topology, if data and software do not need to leave the local environment, they don’t have to. In a SoC you keep things local for many reasons with the chief ones being low latency access and power savings. In addition, the physical nature of the connection can often affect the security of the overall system. This is true in an SoC and it is true in a local context — something that we could call “system on a net” or “SoN” (even though I know that often means “self organizing network”).</p><p>What are the characteristics of a SoN?</p><ol><li><strong>Locality of reference drives the topology.</strong></li></ol><p>Think about the history of computing processor design. When the first CPUs were built, the access to memory was quickly recognized as a limit to any increase in overall computing speed. Over time, this has turned into incredibly complex and hierarchical caching systems, from the pipelines in the CPU themselves to the level 1 (or 2 or 3 or 4) caches on the chip itself. Multi-core processors have to manage shared caches to drive parallel computing correctly. The same thing is necessary in local device communications. We are going to find ourselves wanting things to happen faster and faster as developers create new services and experience. We will want sensors and lights and media to move quickly and react to new kinds of software command and control. That simply cannot scale without managing the communication and data in a local-first way.</p><p><strong>2. The topology can lead to better security by design.</strong></p><p>A basic principle of security is to reduce the surface area by which an attacker can gain entry. If every device in a home, office, car, or train connects to each other via a connection to the cloud, the surface area of the system becomes so large as to affect any fundamental security design. In the home in particular this is troublesome as consumer devices from around the world are unlikely to maintain a high level of security quality in commodity devices. So a design that bounds the impact of a semi-trusted device would be an important design principle. I don’t want that cool connected toaster to be the infection path for my entire connected home. In addition, keeping communication local as much as possible provides a much better privacy by design baseline. In the same way we sandbox third party applications on our smartphones, we need to sandbox connected devices to reduce the opportunity for exploitation.</p><p><strong>3. The Cloud remains the same useful interconnection point, but isn’t the only one.</strong></p><p>Saying that there is only local connectivity is as ridiculous a design goal as saying there is only Cloud connectivity. Each SoN will have well-defined interfaces to the broader world. These include connections to the Cloud using, most likely, Cloud protocols like HTTP/JSON/REST and WebAPIs in general. This is analogous to the complex connections a system-on-a-chip has to the other components on the board near it. Many of these (if not most) are industry standard interconnections for memory, peripherals, and connectivity. But if you want something to run fast, you keep it local as much as you can. Games want to run in the GPU without touching external memory. The sensor “SoN” of the future will want to do the same as it takes that sensor input and applies deep learning to bring you better and better experiences. This deep learning can be computed locally and used locally.</p><p>Whether the SoN in question is in your office, your home, your car, or on your body the locality of reference is going to matter more and more. The companies that recognize this design pattern is coming and move towards the hybrid (and admittedly more complex) approach will be able to reach past their competitors in this new highly connected world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c71459d20c52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open is unreliable, closed is not innovative?]]></title>
            <link>https://medium.com/@robchandhok/open-is-unreliable-closed-is-not-innovative-7691122efc83?source=rss-fb1a50133bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7691122efc83</guid>
            <dc:creator><![CDATA[Rob Chandhok]]></dc:creator>
            <pubDate>Wed, 11 Jun 2014 20:45:10 GMT</pubDate>
            <atom:updated>2014-06-11T20:45:10.701Z</atom:updated>
            <content:encoded><![CDATA[<h4>Complex ecosystems need both to succeed.</h4><p>Today I came across an <a href="http://readwrite.com/2014/06/11/honeywell-and-vivints-new-smart-home-platforms-openness-is-overrated">article</a> on ReadWrite that surprised me a little bit. The author, Adriana Lee, does an excellent job of explaining two new products entering the home automation market. But what caught my attention is the contrasting approach both new products took to their relationship with the connected world around them: they chose to keep their APIs private, and to give no access (or very limited access) to developers to integrate the devices into a broader ecosystem. Adriana notes:</p><blockquote>It’s not a trendy stance to take these days, but it underscores the biggest underlying battle in the fight to rule our homes: “open and innovative” versus “closed and reliable.”</blockquote><p>Surprise! We are back to this false dichotomy. To many of us working to make the “Internet of Things” happen, this is profoundly troubling trend —but it is not new. We’ve been here before, and we will be here again. New ecosystems develop first by vertical and usually proprietary initial offerings but in most cases the scale comes as horizontal and more open ecosystems are created at a global and mass market scale. For some reason, the fear is that “open” means “unreliable”, and that simply isn’t true in practice. Think of Linux. It powers most of the Internet, and yet despite it being open source it is reliable, secure, and commercial grade. Some very deep thinkers in security believe that open source security is the most secure, because of the peer review involved in the implementation. Where is the example that points to open being less reliable?</p><p>Think back to the early days of the Internet. There was a point where the mass consumer market started moving away from dial-up lines that went to a specific service provider and instead connected to a generic “Internet Service Provider” or ISP. At first, you just used this ISP to connect to your Compuserve or AOL (instead of the old direct connection) but then something happened. The sites on the web grew in scale as more and more content and consumer services became available directly through the browser. The closed ecosytems, which were arguably more reliable than the early web, started losing their position as the leading web sites were able to interoperate to each other to accelerate their own offerings. Need some ads to fund your site? Use the open web protocols to syndicate from someone else. Need to show your data using a map? Get that over the open web API ecosystem. That openness wasn’t just for consumer choice, it changed the face of development forever by making it easy for small and medium companies to aggregate building blocks into experiences. That activity continues to fuel the web economy to this day. And it does it reliably and at scale.</p><p>Now flash forward to the connected home and the internet of things. In my opinion, to get to the same tipping point of scale that made the web what it is today the connected home requires a thoughtful blend of open interfaces/protocols and “closed” proprietary solutions. This will accelerate the ability of developers and hardware vendors to create differentiated experiences that they can use to generate value and revenue. The connected home is not going to be constructed from a single brand of product or service any more than the modern web is driven by a single brand or protocol.</p><p>What we should be discussing in the connected home is not how to connect your toaster to its own connected toaster app, we should be discussing what complex and layered architectures will work to create an ecosystem where connected lights interoperate and consumers don’t have to worry about their brand of connected light being supported on the next smartphone OS (since the lights will last over ten years). We should recognize that the open parts of systems are best used to create platforms for innovation by removing the drudgery of re-inventing the foundations of the platform over and over and allowing innovation and differentiation (and yes even closed systems) to happen on the shoulders of the open and interoperable baseline.</p><p>If we don’t, if we continue to build closed ecosystems where one brand or product only talks to themselves we will end up with what my friend Amir Faintuch calls “The Internet of Thing”. It will be a great demo but it won’t be an ecosystem. The right blend of “open” and “closed” is harder to do but it is worth it.</p><p><em>The opinions in this article are mine and do not reflect my employer’s.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7691122efc83" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>