<?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[Engineering Serendipity - Medium]]></title>
        <description><![CDATA[On forging relationships &amp; creating opportunities. - Medium]]></description>
        <link>https://medium.com/engineering-serendipity?source=rss----2e302f1ee18---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2P4ZKmKXwy3MKEpL.jpeg</url>
            <title>Engineering Serendipity - Medium</title>
            <link>https://medium.com/engineering-serendipity?source=rss----2e302f1ee18---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:57:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/engineering-serendipity" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Engineering Serendipity]]></title>
            <link>https://zmh.medium.com/engineering-serendipity-ee75070a3448?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee75070a3448</guid>
            <dc:creator><![CDATA[Zach Hamed]]></dc:creator>
            <pubDate>Mon, 15 Aug 2016 01:11:26 GMT</pubDate>
            <atom:updated>2014-07-12T21:38:52.797Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PEOBX3J95tdJ1oEMHLtAuw.jpeg" /></figure><h4>The art and science of creating chance.</h4><p>Today I was lucky enough to speak at <a href="http://memorialchurch.harvard.edu/morning-prayers-0">Morning Prayers</a>, a secular Harvard tradition that has existed since its founding in 1636. Below is a copy of my remarks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Fvisual%3Dtrue%26url%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F147242760%26show_artwork%3Dtrue&amp;url=http%3A%2F%2Fsoundcloud.com%2Fharvard%2Fsenior-talks-zachary-hamed-14&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000042877229-l41or1-t500x500.jpg%3F61e8f21&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/205951a33733071d250533718202994c/href">https://medium.com/media/205951a33733071d250533718202994c/href</a></iframe><p>Good morning. My name is Zachary Hamed, and I am a senior in Leverett House studying computer science. I’d like to begin with a reading from Ecclesiastes:</p><blockquote>The race is not to the swift or the battle to the strong, nor does food come to the wise or wealth to the brilliant or favor to the learned; but time and chance happen to them all.</blockquote><p>Chance—and its sister, serendipity—are the under-appreciated forces that drive the twists and turns in life. Serendipity is defined as the “the occurrence and development of events by chance in a happy or beneficial way.” It was first penned by Horace Walpole in a letter to Horace Mann in 1754, who said he was inspired by an old Persian fairy tale called “The Three Princes of Serendip.”</p><p>As the story goes, the King of Serendip had three sons, whom he had educated with the best tutors in the land. After several years, the king felt his sons had mastered all the knowledge of the arts and sciences, but feared they had been too sheltered and privileged in their education. He sent his sons to the desert, where they wandered for days.</p><p>Late in their trip, they met a farmer who asked if they had seen his missing camel. The princes asked the farmer if his camel was blind in one eye, had a gap in its teeth, and was injured in one leg. When the farmer heard this, he accused the princes of stealing his camel and took them to the king.</p><p>When the king asked how his sons knew such intimate details of a stranger’s camel, they explained that their days of wandering had led them to notice small details in the environment. An animal had eaten the tougher and browner grass on the left side of the road, leading them to believe the animal was blind in one eye. There were lumps of chewed grass along the road that were the size of a camel’s tooth. And there were only 3 camel footprints on the road with the fourth being dragged, leading them to believe the camel was disabled in one leg. As soon as they finished, a traveller entered and reported he had found a lost camel in the desert. The princes were rewarded handsomely and their intuition trusted for years to come.</p><p>The story hits close to home because Cambridge resembles Serendip all too often. It is easy for us to be so ensconced in our research, our work, our meetings and our routine that we don’t make time for productive and creative wandering.</p><p>In the 1950s, a pair of medical researchers—one at NYU and one at Cornell—accidentally injected rabbits with a certain enzyme and noticed that the rabbits’ ears folded over. Neither had the time or funding to pursue the anomaly, so they buried it away in their lab notebooks. Several years later, only one of the professors decided to review his research notes when he realized the flopping ears were actually more important than his initial research was. <a href="http://www.nap.edu/readingroom.php?book=biomems&amp;page=lthomas.html">His work</a> led to a Nobel Prize, and a <a href="http://www.psyking.net/HTMLobj-3475/The_Case_of_the_Floppy-Eared_Rabbits.pdf">subsequent sociology paper</a> on the topic coined the terms serendipity gained (for example, reviewing your notes and deciding to pursue a question further) and serendipity lost—making the same discovery but never following up.</p><p>In short, serendipity enters our lives several times a day. We can gain it or lose it. But the best part is—we can engineer it. MIT Professor Ethan Zuckerman covers this phenomenon of creating luck. “Engineering serendipity,” he says, “is this idea that we can help people come across unexpected but helpful connections at a better than random rate. And in some ways it’s based on trying to reassess this notion of serendipitous as lucky — to think of serendipitous as smart.”</p><p>Harvard engineers serendipity at every point it can. You’re placed with a random group of your classmates when you enter as a freshman. Even when you’re allowed to choose your roommates in sophomore year, you’re placed randomly into houses and a lottery randomly places you into rooms. The lectures in your general education class could help you on a completely unrelated assignment in a different class. And have you noticed how many walking paths there are outside this very church? Walking through Harvard Yard is a case study in serendipity—it’s almost impossible to avoid seeing someone you know.</p><p>We meet best friends at events in Ticknor Lounge, significant others in early morning sections in Sever, mentors over lunch in Leverett dining hall, and overhear job opportunities in Lamont Cafe. Every minute on Harvard’s campus is a chance encounter waiting to happen.</p><p>Harvard’s secret is it takes a diverse group of people and squeezes them into a small, confined space. But the real world is a big place. And the scariest part is that serendipity will no longer be engineered for us. In fact, New York City, where I’ve been living for the past 4 months, seems to be engineered against serendipity. Have you ever tried meeting someone new on a New York City subway train? In a city of 8 million people, how do you find your new best friend? Your new job opportunity?</p><p>As always, Ralph Waldo Emerson provides the answer. “Shallow men,” he says, “believe in luck or in circumstance. Strong men believe in cause and effect.” It is up to us to engineer serendipity once we leave Harvard’s gates. So talk to the person behind you in line at the coffee shop. Knock on your neighbor’s door in the otherwise anonymous apartment building you live in. Ask your friends to introduce you to someone new and go to lunch with them.</p><p>Be open to the unexpected today. Relish the uncertain. And embrace serendipity.</p><p>Like this post? <a href="http://zhamed.com/">Visit my website</a> or <a href="http://twitter.com/zmh">follow me on Twitter at @zmh</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee75070a3448" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creative People Say No]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kevin_ashton/creative-people-say-no-bad7c34842a2?source=rss----2e302f1ee18---4"><img src="https://cdn-images-1.medium.com/max/700/1*9Hu-U8R3CEyRgkji0C1v1Q.png" width="700"></a></p><p class="medium-feed-link"><a href="https://medium.com/@kevin_ashton/creative-people-say-no-bad7c34842a2?source=rss----2e302f1ee18---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kevin_ashton/creative-people-say-no-bad7c34842a2?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/bad7c34842a2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Kevin Ashton]]></dc:creator>
            <pubDate>Mon, 18 Mar 2013 16:42:10 GMT</pubDate>
            <atom:updated>2015-03-26T00:16:28.565Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Collaborating Asynchronously to Get More Done]]></title>
            <link>https://medium.com/@bendrucker/collaborating-asynchronously-to-get-more-done-691a0e979223?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/691a0e979223</guid>
            <dc:creator><![CDATA[Ben Drucker]]></dc:creator>
            <pubDate>Wed, 06 Nov 2013 12:03:43 GMT</pubDate>
            <atom:updated>2013-11-06T17:45:22.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*mbzyWKz305t-sc1ZpTbKYw.jpeg" /></figure><h4>How applying a software design principle made work meaningful again</h4><p>I’ve been thinking a lot lately about remote work and building a distributed team. Not having a class or work schedule is a new experience for me. Without any clue how to cope with that, I ended up adopting a nine-to-five-style routine, despite total freedom to do otherwise. That became a serious bottleneck for a team that hails from four cities and three time zones, so I started from scratch in search of a better way to work.</p><p>Tim Ferris’s <a href="http://amzn.com/B002WE46UW">The Four Hour Workweek</a> emphasizes blocking—using long chunks of interrupted time for important tasks to minimize the costly mental inefficiency of switching from one task to another. The term <em>blocking </em>caught my eye, as it has an similar definition in software development. Blocking, in programming, refers to operations that prevent anything else from executing until they finish. It usually comes with a negative connotation, for the same reason it’s so important for <em>mental</em>computation. More on that later.</p><p>Programming as a metaphor for collaborative work came up again in <a href="http://amzn.com/B00C0ALZ0W">Remote</a>, written by Jason and David of 37signals, a pioneer of the software as a service industry and the creator of Ruby on Rails. Remote prescribes asynchronous communication as the key to replacing the feeling of “business” with a steady stream of accomplished work. <strong>That was it. </strong>I already understood how to teach a computer how to work efficiently—all I had to do was adopt the same practices for myself. This isn’t just for geeks—these habits are for <em>everyone</em>, programmer or non-programmer, remote worker or nine to five corporate employee.</p><h3><strong>Programming Concepts for Non-Programmers</strong></h3><p><strong>Seasoned developers, please skip ahead. </strong>In order for the programming metaphor to make a shred of sense, I want to offer a quick primer on synchronous versus asynchronous computing. Synchronous patterns (per the prefix) are predictable and chronological. If you execute operations <em>A </em>and <em>B</em>, <em>A </em>will run to completion before <em>B </em>can start. While this makes it easy to understand the flow of operations in your program, it also introduces a serious bottleneck (<em>blocking</em>). When <em>A </em>runs, it blocks the rest of the program from proceeding. Let’s add some detail about what <em>A </em>and <em>B </em>actually do:</p><ul><li><em>B</em>: a very simple, nearly instantaneous (10 milliseconds) operation</li><li><em>A</em>: a complex and length query to a different server for information on a database (1 second)</li></ul><p><em>B</em>, while itself imperceptibly fast, takes a full 1.01 seconds to return, since it had to wait for <em>A </em>to finish before it could run.</p><p>How serious of a problem can synchronous architecture pose? <a href="http://talkingpointsmemo.com/cafe/a-programmer-s-perspective-on-healthcare-gov-and-aca-marketplaces">Just look at Healthcare.gov</a>. If <em>A </em>occasionally fails completely or sometimes takes ten seconds instead of one, the entire system implodes, no matter how robust <em>B </em>is in isolation. Like our brains, web applications don’t receive simple sets of instructions that require one component. They have multiple pieces that handle different kinds of information and operations, all of which have to work together. And like our brains, the components that process information are more numerous and complex than the the ones that simply perceive it and pass it along to the right destination.</p><p>Asynchronous patterns (non-blocking) are a good deal more complicated, but <em>scale</em>much more smoothly. Asynchronous design allows <em>A </em>and <em>B </em>to run simultaneously, while introducing a challenge of its own: unless we specifically tell <em>B </em>to wait for <em>A</em>, <em>B</em>will not know about the results of <em>A. </em>If you make every operation wait for the previous one, you’ve just constructed a synchronous system with more overhead. To reap the benefits of asynchronous design, you need to embrace the fact that the order in which you farm out tasks is not necessarily the order in which they will finish.</p><h3><strong>Asynchronous in the Real World</strong></h3><p><strong>Programmers, you can rejoin us here. </strong>As powerful as asynchronous design may seem, computers have constraints too. We can’t just press the asynchronous button and magically run 1,000 different operations in parallel. Building that level of parallelism on a computer is no easy task, and our brains are certainly not capable of it. Node.js, a popular framework for building web applications, actually mirrors our brains quite nicely. Node.js won’t automatically run any operation in parallel. Calculating Pi to 100 digits, for example, would block and force the program to wait. Node.js gives the developer asynchronous superpowers without the usual complexity because it manages asynchronous <em>I/O</em>, (input/output). Node runs your application in one thread and handles I/O in one or more others. So while your app is still synchronous and ticks along line by line, retrieving data from a database, receiving a request from a user’s browser, or saving a file to a disk doesn’t make the program wait. This is called the<em>event loop.</em></p><p>The event loop, per its name, is essentially looping through a list of all the pending I/O requests your application made, checking each to see if it’s finished, and handing the result back to the app when it finds a completed request.</p><h3><strong>Asynchronous Productivity</strong></h3><p>What does all this technical jargon mean when it comes to working effectively and getting things done?</p><p>Software implementations like Node and our brains are unified by a single overarching principle of work: <strong>multitasking is impossible. </strong>Working on multiple things at once requires some sort of external device to separate the work and queue it until it can be processed. Interleaving disparate tasks without that external structure is difficult for a computer, let alone a human. Unlike a computer, we <em>want </em>to block as much as possible. The brain is a machine designed to execute one task at a time and incurs steep costs each time it switches to a different task.</p><p>Constant communication between members of a team breaks the blocking model. How do you preserve your blocks without moving to some far-off location without the distractions of Internet or phone? Enforce an asynchronous communication policy wherever possible. The dreaded email, when used properly, is the fundamental unit of asynchronous messaging. It sits in a queue and the expected response time is indefinite, though usually within twenty four hours. A project management tool like <a href="http://asana.com/">Asana</a> is a more advanced queue, but still fundamentally follows the same asynchronous pattern.</p><p>Phone calls and meetings are inherently synchronous. Phone calls block all other work until they are complete. Meetings are even more costly—you might spend just as much time traveling and waiting as you do engaged in discussion. While most people could consciously cut down on unnecessary phone calls and meetings, not all communication can or should happen asynchronously. Just as a programmer carefully polices costly synchronous operations, you should set aggressively short meeting and call times, carefully define expectations in advance, and save blocking communication for critical contacts.</p><p>These techniques will fall flat if you try to hide from the inherent tradeoffs of asynchronous design (responses are not immediate and order is not guaranteed). Don’t just acknowledge them—embrace them.</p><p>No tool will cure you of the temptation to work synchronously. For me, asynchronous email means checking no more than twice a day and anticipating a <em>minimum </em>response time of 12 hours for any email I send. All of a sudden the much maligned email became my second (behind Asana) favorite way to communicate for work.</p><p>The key is to limit each mode of communication to strictly asynchronous or synchronous at all times. I’m so fanatical about preserving that line that I disabled voicemail (asynchronous) on my phone entirely—call your carrier if you want to do the same.</p><p>A pleasant side effect of separating synchronous communication (calls and meetings) is that you’ll be able to easily defer communication that isn’t important enough to block work—shift it to an asynchronous channel. Taking a day off becomes infinitely more enjoyable when the majority of your communication is asynchronous. You can actually take time off, not just thumb your phone from somewhere that’s not your office. You can build your schedule around family, travel, or whatever real-life, blocking pursuits are important to you.</p><p>Unless you’re in sales, you’re not getting paid to communicate. You’re getting paid to get work done, and you have more freedom than you realize when it comes to defining where and when that work happens. You’re not Node—don’t try to work as if you have its event loop to manage your communication. If you spend your day looping back to your inbox every five minutes, 5 o’clock will roll around and you’ll have accomplished little. Instead, dramatically lengthen the time between loops and use the savings for longer blocks of work. You’ll accomplish more while working less.</p><p><em>Republished — </em><a href="http://www.bendrucker.me/posts/collaborating-asynchronously-to-get-more-done/"><em>Original Post</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=691a0e979223" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accelerating serendipity]]></title>
            <link>https://medium.com/@stef/accelerating-serendipity-1d03b0d4da2b?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/1d03b0d4da2b</guid>
            <dc:creator><![CDATA[Stef Lewandowski]]></dc:creator>
            <pubDate>Tue, 13 Aug 2013 07:45:48 GMT</pubDate>
            <atom:updated>2014-06-28T21:16:31.627Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NijdekbOdy9rztCg.jpeg" /></figure><h4>Can you make happy accidents happen more often?</h4><p>Luck plays an unusually large part in any success story—just skimming through a few bestselling biographies will reveal how much people attribute their success to a “break”, a “chance meeting” or a “bumping-into” encounter. That’s serendipity:</p><blockquote>An unsought, unintended, and/or unexpected, but fortunate, discovery and/or learning experience that happens by accident.</blockquote><blockquote>A combination of events which are not individually beneficial, but occurring together produce a good or wonderful outcome.</blockquote><p>Serendipity is often portrayed as <em>just luck—</em>a happy accident that occurs at random. There is a case however, that by having a prepared mind, you will be likely to find more of it. Let’s explore that a little.</p><h3>Sagacity</h3><p>The word “serendipity” was first coined by <a href="http://en.wikipedia.org/wiki/Horace_Walpole">Horace Walpole</a>, an 18th Century British diarist, who wrote about the Persian story of The Three Princes of Serendip (now Sri Lanka), in which three princes went on a journey <em>“making discoveries, by accidents and sagacity, of things they were not in quest of…”</em></p><p>His explanation in his original letter is a little difficult to grasp and is oddly ambiguous. It was only some time later, after his writings were published in the mid 19th Century, that the meaning we now attribute to the word began to be applied.</p><p>In the process one thing seems to have been lost in translation from his original observation, that I think still stands true. And that’s that <em>sagacity</em> was involved—a word that has roots in seeking, being observant, wise and keen. And because luck is just random, it’s this side of serendipity that I want to discuss: <em>chance favours the prepared mind</em>. Serendipity isn’t luck.</p><h3>Can you accelerate serendipity?</h3><p>Is it possible to increase the chances of beneficial, happy accidents to occur? Can you <em>accelerate serendipity</em>? For the last few years, I’ve been trying, and I’ve bumped into a few principles along the way.</p><h4>Just turn up</h4><p>We all get invited to things. When I receive an invitation there’s always a temptation to say “oh gosh, it’s going to be so much effort to get there, I think I have to decline”, or “I’m not really sure what the benefit of attending this is—I think I’ll pass”.</p><p>A couple of years ago I was awarded a place in one of those <em>Important List of Young People Who’ll Probably Be More Important in the Future </em>lists—you know the kind of thing.The thing is, I was broke. My bank account was empty and I was down to my last handful of cash. To get to the event I’d be using it to pay for a train ticket.</p><p>It was probably slightly crazy but I spent my last penny to go to a party where a bunch of the other people from the list would be. I didn’t know what I would find there, but I was determined that it would be a room full of opportunity. It was. On the way out I briefly chatted to someone who I would go on to found a company with. If I hadn’t gone to that party that wouldn’t have happened. <em>Just turn up </em>became a rule, and it can be applied to any kind of event or invitation—even things you’re not invited to.</p><h4>Put yourself in the right place</h4><p>Location, location, location. If you want to bump into people who are relevant to what you want to achieve, put yourself right in the middle. For <a href="http://makeshift.io/">my new company</a> we wanted to be right in the middle of the London startup scene, so that meant being as close as possible to the famous Silicon Roundabout of <a href="http://techcity.io/">Tech City</a>, East London. The bumping-into-ness factor around our studio is way higher than anywhere else in London for the kind of thing we’re doing.</p><p>For you, it might be basing yourself at a research park, or taking a desk at a co-working space, or moving to a different city where there’s a higher density of people doing the thing you want to do. Whatever it is, pay attention to the serendipity factor.</p><h4>Avoid zemblanity</h4><p>When you’re working, take a break occasionally and try not to lock yourself away for periods that are too long. You can’t work all hours of the day, and bumping into other people is an important factor in making whatever it is that you’re doing a success. Step away from the desk occasionally, get out and speak to people and <em>just turn up</em>.</p><p>Zemblanity, a word coined by <a href="http://en.wikipedia.org/wiki/Armadillo_%28novel%29">William Boyd in his book Armadillo</a> in the 1980s, is the polar opposite of serendipity. It’s named after the cold, barren serendipity-less island of <a href="http://wikimapia.org/12145959/Nova-Zembla-Island">Zembla</a>:</p><blockquote>“So what is the opposite of Serendip, a southern land of spice and warmth, lush greenery and hummingbirds, seawashed, sunbasted? Think of another world in the far north, barren, icebound, cold, a world of flint and stone. Call it Zembla. Ergo: zemblanity, the opposite of serendipity, the faculty of making unhappy, unlucky and expected discoveries by design.”</blockquote><p>I pretty much locked myself away for a few years to build something a few years back and experienced a little too much zemblanity. If there were one thing I could change about that time it would be to have done more to get out and meet people.</p><h4>Say “Yes, and…” instead of “Yes, but…”</h4><p>This is such a simple thing to try. Any time someone gives you a suggestion, and you feel yourself thinking of playing the devils’ advocate, stop. Starting a sentence with “yes, but” is a surefire way to close down an opportunity—try to think about the other person’s idea or statement and see what you could add. Start with “yes, and…” and go from there! It’s a principle from the world of improv, and I’m often surprised by the happy accidents that result from a simple suggestion to someone.</p><p>Indeed, I’m writing this because of <a href="http://twitter.com/aexmo">Alex Morris</a>. I’d pulled over to the service station because the road was gridlocked on my journey home. I tweeted that I’d probably not manage my <a href="http://attending.io/events/sunday-post">Sunday Post</a>, and he replied, “<a href="https://twitter.com/stef">@stef</a><strong> </strong>dictate it into Phone and publish unedited. <a href="https://twitter.com/search?q=%23doubledare&amp;src=hash">#doubledare</a>”. Sadly that wasn’t possible, but my “yes, and” was to write it in my head on my way home instead.</p><h4>Keep your eyes open for opportunity</h4><p>To paraphrase that famous <a href="http://quoteinvestigator.com/2012/08/13/overalls-work/">mis-attributed</a> saying, <em>it’s easy to miss an opportunity if it sounds like hard work</em>. Pay attention to things around you, and you just might find something that,yes, would be hard work, but then whoever made anything of any impact that wasn’t?</p><h4>Use serendipity engines</h4><p>Twitter, blogging, all of those social media things that people always talk about, when you frame them as serendipity engines are things that have to go into the mix. I’m not great at using that stuff—I’m mainly just on Twitter, but the rate of bumping-into-ness is radically increased the more you use these things, or so I’ve found.</p><p>I’ve certainly found that since starting writing on <a href="http://sketchingwithcode.com/">Sketching with Code</a>, and <a href="http://medium.com/@stef">here on Medium</a> people seem to bump into me more often. By sharing your thoughts online you become more bump-into-able. Because these things are running all day long, I think of them as engines of serendipity that generate a background hum of opportunity.</p><h4>Don’t be too precious with your ideas</h4><p>A <em>zemblanitous</em> trend is, when meeting someone, to ask them to sign a non-disclosure agreement about what it is you’re about to discuss. It’s by design, a tool that people use to keep a lid on their idea. If you’ve really got something great, and a patent in the pipeline then, sure, I can understand why you want to keep it private. But I’ve <a href="http://helpmewrite.co/people/stef/ideas/1012">decided not to sign NDAs any more</a>—it’s hard to remember what you’re supposed to know about, and after operating under one for over a year (!) I’ve seen the zemblanitous effect it has on you and the people around you.</p><h4>Help other people to have serendipity</h4><p>I tried an experiment—publishing my “free/busy” diary using <a href="http://doodle.com/stefl">Doodle</a>. The idea was that people could request a coffee and suggest a time, and reduce the friction in the process. The trouble is, that I found that my days were getting a bit chopped up by having coffee with people. It was impacting on my other work, so I’ve had to reduce that. Instead, I’ve started hosting dinners where I invite the people I would have liked to have had coffee with recently.</p><p>It’s useful for the people who attend and fun for me—we all get to meet a bunch of interesting people, as well as having a cocktail or two afterwards. By building in some time into my diary for serendipity I’m hoping to make interesting connections happen. For me and for others. There’s much more you could do here—hosting a regular meetup for your peers, for instance.</p><h4>Get good at introductions</h4><p>And while I’m on that <em>help other people have serendipity</em> point, I’ve been trying to get better at the fine art of making introductions. Every week I probably make a couple of introductions between people I think should know each-other. It’s a simple format:</p><blockquote>Intro: Anne, meet Bob</blockquote><blockquote>Hi guys, I thought I’d make an introduction because (reason).</blockquote><blockquote>Anne, Bob is (reason for relevance) and (how I know him / he’s amazing).</blockquote><blockquote>Bob, Anne is (reason for relevance) and (how I know her / she’s ace).</blockquote><blockquote>I hope something good happens because of this intro! (Etc.)</blockquote><blockquote>Stef</blockquote><h4>Answer “But why?” with “I don’t know yet”</h4><p>A couple of weeks ago I went to <a href="http://thedigitalsizzle.com/">an art hack</a> with the theme of making things out of data in a weekend. I made something called <a href="http://cryptographics.io/">Cryptographics</a>, that lets you encrypt text and represent it as a graphic that you can wear on a t-shirt, sew into a quilt, make into a print for your wall, and much more. A few people asked me <em>“but why”</em>? And I could flippantly reply “because art”, but more accurate would be to say “I don’t know yet”.</p><p>Undirected play and experimentation is something we tend to lose as we become adults. I’ve made my rule “<a href="https://medium.com/thoughts-on-creativity/723d7e73b9bd">create something every day</a>”, and one of the side effects of that is that I’ve been doing lots of little experiments as a result. From each of them I end up having interesting conversations, and that’s possibly a way of rationalizing doing playful things. You get to meet people, and in my opinion, the best networking is done whilst talking about things other than work.</p><h3>Goldilocks serendipity</h3><p>There is an obvious danger that you can get distracted from your work by trying too hard to do open-ended things that don’t have an immediate benefit. But also, if you have too little opportunity for serendipity — that zemblanitous state—then you’ll end up stuck in a rut. The answer, is of course, to find a <a href="http://en.wikipedia.org/wiki/Goldilocks_planet">goldilocks zone</a> where it’s not too much and not too little.</p><p>These are all just examples of things I’ve been doing around being <em>sagacious. </em>The big thing for me has been in considering serendipity in making decisions about things, I’m trying to make it so that as we build <a href="http://makeshift.io/">Makeshift</a>, we’re enabling happy accidents to occur for us and for those around us. You might want to try adding a little bumping-into-ness to your work life too.</p><p>If you enjoyed this, I have a very infrequent email list for when I write similar things. <a href="http://stef.io/subscribe">Subscribe</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d03b0d4da2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working for the Weekend]]></title>
            <link>https://medium.com/engineering-serendipity/working-for-the-weekend-c37b05b1f2ed?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/c37b05b1f2ed</guid>
            <dc:creator><![CDATA[Peter Boyce]]></dc:creator>
            <pubDate>Sun, 03 Nov 2013 18:16:15 GMT</pubDate>
            <atom:updated>2013-11-03T19:29:11.995Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*NwqF2Miink34S073qPJraQ.jpeg" /><figcaption>The Noun Project (‘Coworking’)</figcaption></figure><p>I’ve said I was going to start this for a while, so without all the answers, here it goes. What works for MVPs / ‘lean’ principles in startup world should apply here as well: it’s often better to kick things out the door sooner than later, get feedback / critiques, and iterate from there. I’d like to share this as a work-in-progress.</p><p>Working around other people is something special: there’s a certain intangible element that seems hard to pinpoint. It might just come down to the simple fact that <strong><em>people are social creatures</em></strong>, and that working by yourself / isolated from others just isn’t that fun sometimes. In tandem with the fact that we’re all increasingly busy and trying to make the most of our personal and work lives. I propose:</p><blockquote><strong><em>Working for the Weekend (#WFTW)</em></strong>: a movement to set aside time Saturday/Sunday mornings to get work done amongst friends.</blockquote><p><em>The (open) parameters</em>:</p><ul><li><strong>Who</strong>: friends / coworkers / peers / open community invite. Can imagine group sizes of 3-15.</li><li><strong>Time</strong>: 9am -1pm? Saturdays and/or Sundays.</li><li><strong>Venue</strong>: solid wifi + outlets + desk space. Same spot every weekend or can rotate through cafes or the offices of attendees (I’ve been hosting friends at the <a href="http://4sq.com/1cCNrj7">General Catalyst office in NYC</a>, will try out in our Cambridge office as well).</li><li><strong>Fuel</strong>: coffee + morning snack items (suggestions?)</li><li><strong>Online product</strong>: Tumblr / Strikingly / Squarespace? Something to help with invitations, sharing photos, perhaps facilitating communication between the group. Should we design a logo to symbolize this? Or can be as simple as a landing page with this info on it. Or nothing at all…</li><li><strong>Post-session</strong>: optional brunch together, or everyone go separate ways to enjoy the rest of day having gotten their work done!</li></ul><p><em>A first take at a ‘manifesto’</em>:</p><ul><li><strong>Do great things</strong>: much like the <a href="http://tcrn.ch/Hvimnv">mantra of Asana</a>.</li><li><strong>Surround yourself with amazing people</strong>: diverse, interesting, and passionate folks that you enjoy spending time with.</li><li><strong>Collaborate</strong>: as opposed to competition or isolation (though there’s of course a time and a place for those things). Share learnings &amp; be helpful to others.</li><li><strong>Engineer serendipity</strong>: forging a mix of people, products and conversations can lead to unexpected awesome.</li><li><strong>Time is our most scarce resource</strong>: my friend <a href="http://bit.ly/19qp2xw">Hugo</a>’s words of advice have always resonated with me. “What people wish for on their deathbed isn’t more money or fame: it’s that they had more <em>time</em> with friends and loved ones.” This sits in the back of my mind each day, I think they’re words to live by.</li></ul><p><em>Related cool stuff</em>:</p><ul><li><strong>Peopleware</strong>: this <a href="http://bit.ly/19qn2W6">book</a> is a great compilation of insights around teams, project management, and work culture. When reading, keep it mind it was first published in 1987 (you’ll likely come across concepts</li><li><strong>New York Nightowls</strong>: when I first read this <a href="http://nyti.ms/19qlagb">article in the NYTimes</a>, a light went off. It was so exciting to see this type of community gathering in NYC, and sparked the thought: why don’t we have something like this at Harvard?</li><li><strong>HackNights</strong>: at <a href="http://www.hackharvard.org/">HackHarvard</a>, we started a weekly Tuesday gathering called ‘hacknights,’ a gathering of technologists to work on side-projects together.</li><li><strong>Keeping Saturdays Sacred</strong>: <a href="http://bit.ly/18C82Sk">Steve Klabnik</a> has the right idea ;)</li></ul><p><strong>I’d love your questions / comments / feedback</strong>: any ideas on what we can do to make this a productive &amp; worthwhile way to spend part of your weekend would be awesome. For example, <a href="http://bit.ly/1cxR8e5">this may or may not be our soundtrack</a>…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c37b05b1f2ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-serendipity/working-for-the-weekend-c37b05b1f2ed">Working for the Weekend</a> was originally published in <a href="https://medium.com/engineering-serendipity">Engineering Serendipity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘Going West’ (pt.1)]]></title>
            <link>https://medium.com/engineering-serendipity/going-west-pt-1-5a6729612743?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/5a6729612743</guid>
            <dc:creator><![CDATA[Peter Boyce]]></dc:creator>
            <pubDate>Wed, 28 Aug 2013 13:26:35 GMT</pubDate>
            <atom:updated>2013-08-28T13:26:35.169Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*NyNad-D4xAN1YtW9.jpeg" /></figure><h4>Friends, startups &amp; venture for a week in SF + Palo Alto</h4><h4>TC Disrupt</h4><p>Given enough time, things have a tendency to come full-circle in ways you’d least expect. My first trip to SF was to attend <a href="http://techcrunch.com/tag/techcrunch-disrupt-2010/">TechCrunch Disrupt 2010</a>. At the time, I was working to help launch <a href="http://gogirlfinance.com/">GoGirl Finance</a>, and made the trip to learn about social games (Zynga was very much in-vogue at the time) and how we might leverage gamification &amp; the Facebook platform to teach financial literacy.</p><p>I also happened to be in school—and making the trip meant taking a full week off from school. My Spanish teacher was in dismay: we were two weeks into the semester, it was clear Spanish was not my forte, and here I was jetting to a ‘conferencia de tecnología para mi empresa’.</p><p>Fast forward three years: <a href="https://twitter.com/williamhockey">Will Hockey</a>, who I describe then &amp; now as my ‘tech man crush I made in the valley’, is now co-founder of payments startup <a href="https://plaid.io/">Plaid.io</a>. And here we are on the roof deck of the General Catalyst — Palo Alto office, reunited having come quite a ways since our early days in tech. The last time we were together in California, we were nervously debating approaching Ron Conway &amp; dreaming up elaborate plans to build ‘the Levi’s of the tech gold rush’. Funny: that’s what Will might be building…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hU920jnZJArPcE-s.jpeg" /><figcaption>Doppelgangers right out of a Gap / Levi’s ad.</figcaption></figure><h4>CloudFlare</h4><p>I’ll also never forget the conversation Will &amp; I had about CloudFlare at TC Disrupt: by far our favorite company. In spite of coming runner-up, the company has been on a tear since that very day. I <a href="http://techcrunch.com/2011/02/24/disrupt-cloudflare-omfg/">love this post</a> on the topic from co-founder Matt Prince. And I’m luck to have had the chance to visit <a href="https://twitter.com/zatlyn">Michelle Zatlyn</a>, CloudFlare cofounder, to hear how things are going, catchup on life, and get her advice as I collect learnings for my role in venture. Michelle is building something amazing, and I couldn’t be happier for her &amp; the team. Not to mention the awesome CloudFlare t-shirts I snagged and have been wearing since.</p><p>This trip to SF was for both personal &amp; work purposes I realize now, and if I’ve learned anything in my first weeks here at GC, it’s that for me: the two are interwoven. Some of my best friends work at startups &amp; in VC; I love getting fired up debating companies I’m passionate about; and I really can’t imagine a scenario I’m not constantly in the mix of new technology &amp; opportunities I make a part of my life. I’m excited for what this means for my enthusiasm for tech, but also anxious for when things may (read: will) turn complicated or emotional now that I’ve joined the industry.</p><p>My plan: make decisions for the <strong>long-term</strong>, put <strong>people first</strong>, provide <strong>help</strong> where I can, <strong>always be learning</strong>, and prepare for the <strong>ups &amp; downs</strong> that come with doing work you’re passionate about.</p><p>Next post: my <a href="https://foursquare.com/badboyboyce/list/sf">SF itinerary</a> &amp; thoughts on the ‘tech mecca’.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a6729612743" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-serendipity/going-west-pt-1-5a6729612743">‘Going West’ (pt.1)</a> was originally published in <a href="https://medium.com/engineering-serendipity">Engineering Serendipity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Opportunities are Manufactured]]></title>
            <link>https://stirman.medium.com/opportunities-are-manufactured-ed6230a9ddce?source=rss----2e302f1ee18---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed6230a9ddce</guid>
            <dc:creator><![CDATA[Jason Stirman]]></dc:creator>
            <pubDate>Thu, 21 Feb 2013 23:39:51 GMT</pubDate>
            <atom:updated>2026-08-31T18:51:32.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W14pwQkByjZBHT86YGEANQ.jpeg" /></figure><h4>Don’t wait for opportunities to present themselves.</h4><p>I can’t count the number of times someone has told me how lucky I am in my career. According to many, I am lucky to be working with <a href="https://medium.com/@ev">Ev</a>, lucky to have worked at Twitter, lucky to be working on Medium, lucky to be able to work in San Francisco, lucky to work with leading edge technology, etc.</p><p>This isn’t where I say “It’s not luck, it’s all skill”, because that’s not true. Attributing career or personal achievements to only luck or skill is a short-sighted perspective on past successes. Luck and skill play a big part, but so does timing, people, intelligence, past experience, trends, and a multitude of other factors.</p><p>This <a href="http://www.fastcompany.com/46732/how-make-your-own-luck">Fast Company article</a> explains some of the science behind the concept of luck. People that consider themselves lucky are more open to new experiences, which often result in new opportunities. Also, maybe not surprising, lucky people often reflect on and learn from past experiences whereas unlucky people attribute past events to being a victim of chance.</p><blockquote>As it turns out, there’s truth to notion that you can make your own luck, science says so!</blockquote><p>My career is <a href="https://medium.com/what-i-learned-building/6972e9e7c15b">littered with failures</a>, but also has had a few pivotal moments that resulted in big wins. In hindsight, almost all of those moments were initiated by an action I took. In every case, the action didn’t produce the win, it produced an opportunity to win. I capitalized on some of those opportunities, but failed to meet many others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39etkRcV_3pICi29M8R1Tw.jpeg" /></figure><p>The story of how I ended up living in California and working at Medium starts with an email I sent to <a href="http://en.wikipedia.org/wiki/Odeo">Odeo</a> in 2007. I was living in Texas had launched <a href="http://ohdontforget.com/">a product</a> that allowed companies to programmatically send text messages before SMS was a ubiquitous technology. My email was a sales pitch for an Odeo integration with my product, which was a horrible idea. It didn’t make sense for Odeo, but the CEO, Evan Williams, took notice and replied with some questions about who I was and what I was up to. That conversation resulted in an opportunity to prove myself, via contracting, to land a job with Obvious and Twitter.</p><p>That was a big win for my career, but there’s another part to that story that I don’t usually tell. After contracting with Ev and Obvious for a while, I had earned the opportunity to become a very early full-time employee at Twitter. I didn’t take it. I left Obvious. I created an opportunity for myself, and then failed to capitalize on it. It was the right decision at that time for my family, but it was a missed career opportunity.</p><p>Fortunately, my previous work for Obvious earned me another chance to join Twitter a year later, which I accepted. It all started with an action, an idea sent in an email.</p><p><strong>It was a bad idea, a stupid action, but it was action.</strong></p><p>I now have the opportunity to help make Medium amazing. I also have the opportunity to advise awesome companies and mentor entrepreneurs. The number one piece of advice I always give is…</p><blockquote>Don’t wait for opportunities to present themselves. Do something. Do something today. Do something now.</blockquote><blockquote><strong>Opportunities are manufactured.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed6230a9ddce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>