nathan_marz_storm nathan_marz_storm-2013 nathan_marz_storm-2013-36 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: There's been a lot of speculation about what my new startup is doing, so I've decided to set the record straight and reveal all. We are working on one of the biggest problems on Earth, a problem that affects nearly every person on this planet. Our products will significantly improve the quality of life for billions of people. We are going to revolutionize the bedsheet industry. Think about it. There's been almost no innovation in bedsheets in thousands of years. There's nothing worse than waking up to discover one of the corners of your Egyptian cotton fitted sheets has slipped off the mattress. How is this not a solved problem yet? Why are we still using sheets with that annoying elastic in it to secure them to our mattresses? They slip all the time – and if you have a deep mattress, good luck finding sheets that even fit. You're just screwed. Consider the impact of solving this problem, of a bedsheet product that never slips, that always stays secure on the mattre
sentIndex sentText sentNum sentScore
1 There's been a lot of speculation about what my new startup is doing, so I've decided to set the record straight and reveal all. [sent-1, score-0.27]
2 We are working on one of the biggest problems on Earth, a problem that affects nearly every person on this planet. [sent-2, score-0.318]
3 Our products will significantly improve the quality of life for billions of people. [sent-3, score-0.306]
4 We are going to revolutionize the bedsheet industry. [sent-4, score-0.305]
5 There's been almost no innovation in bedsheets in thousands of years. [sent-6, score-0.512]
6 There's nothing worse than waking up to discover one of the corners of your Egyptian cotton fitted sheets has slipped off the mattress. [sent-7, score-0.7]
7 Why are we still using sheets with that annoying elastic in it to secure them to our mattresses? [sent-9, score-0.774]
8 They slip all the time – and if you have a deep mattress, good luck finding sheets that even fit. [sent-10, score-0.721]
9 Consider the impact of solving this problem, of a bedsheet product that never slips, that always stays secure on the mattress. [sent-12, score-0.634]
10 This translates to better sleep, to less grogginess in the morning, to feeling more upbeat in the morning. [sent-13, score-0.258]
11 This translates into less morning arguments between husbands and wives that spiral into divorces, child custody battles, and decades of trauma for the children. [sent-14, score-0.569]
12 Not only is this a big problem – it's a big opportunity. [sent-15, score-0.32]
13 We've done extensive market research and discovered that our target market is the entire human population. [sent-16, score-0.348]
14 At 7 billion people and an estimated average sale of $20 per sheet, this is at least a $140,000,000,000 opportunity. [sent-17, score-0.159]
15 We are going to solve this problem using modern, 21st century techniques and take bedsheets out of the Stone Age and into the future. [sent-18, score-0.608]
16 We are going to make it possible to attach your sheets to your bed , completely solving the problem. [sent-19, score-0.751]
17 Solving this problem in a practical and cost-efficient way is not easy and will require significant engineering breakthroughs. [sent-20, score-0.393]
18 If you're a world-class, rock star by day and ninja by night engineer who's as passionate about bedsheets as I am, please get in touch. [sent-21, score-0.635]
19 Bedsheets have been my true passion since I was a child. [sent-23, score-0.09]
20 I'm excited to finally be focused on what I really care about, and I can't wait until the day when untucked sheets are a curious relic of the past. [sent-24, score-0.886]
wordName wordTfidf (topN-words)
[('sheets', 0.553), ('bedsheets', 0.332), ('bedsheet', 0.221), ('morning', 0.221), ('secure', 0.221), ('problem', 0.192), ('translates', 0.18), ('solving', 0.114), ('market', 0.105), ('spiral', 0.09), ('straight', 0.09), ('thousands', 0.09), ('curious', 0.09), ('reveal', 0.09), ('sale', 0.09), ('innovation', 0.09), ('record', 0.09), ('billions', 0.09), ('modern', 0.09), ('passion', 0.09), ('slip', 0.09), ('wait', 0.09), ('going', 0.084), ('day', 0.084), ('impact', 0.078), ('rock', 0.078), ('sleep', 0.078), ('arguments', 0.078), ('products', 0.078), ('engineer', 0.078), ('feeling', 0.078), ('solved', 0.078), ('luck', 0.078), ('worse', 0.078), ('discovered', 0.069), ('human', 0.069), ('significant', 0.069), ('average', 0.069), ('excited', 0.069), ('quality', 0.069), ('significantly', 0.069), ('discover', 0.069), ('require', 0.069), ('big', 0.064), ('age', 0.063), ('biggest', 0.063), ('practical', 0.063), ('night', 0.063), ('nearly', 0.063), ('love', 0.063)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999982 36 nathan marz storm-2013-04-01-My new startup
Introduction: There's been a lot of speculation about what my new startup is doing, so I've decided to set the record straight and reveal all. We are working on one of the biggest problems on Earth, a problem that affects nearly every person on this planet. Our products will significantly improve the quality of life for billions of people. We are going to revolutionize the bedsheet industry. Think about it. There's been almost no innovation in bedsheets in thousands of years. There's nothing worse than waking up to discover one of the corners of your Egyptian cotton fitted sheets has slipped off the mattress. How is this not a solved problem yet? Why are we still using sheets with that annoying elastic in it to secure them to our mattresses? They slip all the time – and if you have a deep mattress, good luck finding sheets that even fit. You're just screwed. Consider the impact of solving this problem, of a bedsheet product that never slips, that always stays secure on the mattre
2 0.079360828 39 nathan marz storm-2014-02-12-Interview with "Programmer Magazine"
Introduction: I was recently interviewed for "Programmer Magazine", a Chinese magazine. The interview was published in Chinese, but a lot of people told me they'd like to see the English version of the interview. Due to the Google translation being, ahem, a little iffy, I decided to just publish the original English version on my blog. Hope you enjoy! What drew you to programming and what was the first interesting program you wrote? I started programming when I was 10 years old on my TI-82 graphing calculator. Initially I started programming because I wanted to make games on my calculator – and also because I was bored in math class :D. The first interesting game I made on my calculator was an archery game where you'd shoot arrows at moving targets. You'd get points for hitting more targets or completing all the targets faster. A couple years later I graduated to programming the TI-89 which was a huge upgrade in power. I remember how the TI-82 only let you have 26 variables (for the character
3 0.079001531 33 nathan marz storm-2012-02-06-Suffering-oriented programming
Introduction: Someone asked me an interesting question the other day: "How did you justify taking such a huge risk on building Storm while working on a startup ?" (Storm is a realtime computation system). I can see how from an outsider's perspective investing in such a massive project seems extremely risky for a startup. From my perspective, though, building Storm wasn't risky at all. It was challenging, but not risky. I follow a style of development that greatly reduces the risk of big projects like Storm. I call this style "suffering-oriented programming." Suffering-oriented programming can be summarized like so: don't build technology unless you feel the pain of not having it. It applies to the big, architectural decisions as well as the smaller everyday programming decisions. Suffering-oriented programming greatly reduces risk by ensuring that you're always working on something important, and it ensures that you are well-versed in a problem space before attempting a large investment. I ha
4 0.06356927 19 nathan marz storm-2010-07-12-My experience as the first employee of a Y Combinator startup
Introduction: I'm the first employee of BackType , a Summer '08 YC company. My joining the company increased the company size by 50%. The experience has been awesome, but I will say up front that being the first employee of a startup is not for everyone. The best part of being the first employee of a startup is the total exposure to all parts of the company. I've learned a ton about product development, customer development, recruiting, and entrepreneurship. Additionally, I've met and connected with lots of other awesome people through the YC network. I've gotten all these benefits at relatively low risk for myself, as I still have a salary and a solid chunk of equity. No Rules There are a lot of rules working at most companies. You don't even realize that some of the rules are rules until you work at a company with no rules. I'm talking about the most basic things like what hours you work, what days of the week you work, what tools you use, and whether you come into the office or not. B
5 0.053880494 22 nathan marz storm-2010-10-05-How to get a job at a kick-ass startup (for programmers)
Introduction: When I finished college, I was incredibly naive when it came to finding a great job. I knew that I wanted to work at a small startup but didn't know how to find that great opportunity. I didn't know what questions to ask to evaluate a company, and I didn't know how I should present myself during the recruitment process. Now I'm a few years out of college and I have that kick-ass job I was looking for. My dual experiences of looking for a job and being on the other side recruiting programmers have taught me quite a bit about what it takes to get a great job at a kick-ass startup. Here are my tips, from preparing for the job search process to finding great startups to applying and getting the job. If you have any tips of your own, be sure to leave them in the comments! Preparing for the job search 1. Make a list of the qualities you're looking for in a job. Be explicit and specific. What are you looking for? Coworkers that are really smart that you can learn from? Coworkers
6 0.050311279 13 nathan marz storm-2010-04-14-Introducing Cascalog: a Clojure-based query language for Hadoop
7 0.046502195 38 nathan marz storm-2013-04-12-Break into Silicon Valley with a blog
8 0.043137752 40 nathan marz storm-2014-02-24-The inexplicable rise of open floor plans in tech companies
9 0.040720455 25 nathan marz storm-2010-12-06-You Are a Product
10 0.040129185 41 nathan marz storm-2014-05-10-Why we in tech must support Lawrence Lessig
11 0.03655231 31 nathan marz storm-2011-10-13-How to beat the CAP theorem
12 0.036372654 37 nathan marz storm-2013-04-02-Principles of Software Engineering, Part 1
13 0.036095873 23 nathan marz storm-2010-10-27-Fastest Viable Product: Investing in Speed at a Startup
14 0.034128644 17 nathan marz storm-2010-05-26-Why your company should have a very permissive open source policy
15 0.033042703 3 nathan marz storm-2010-01-13-Mimi Silbert: the greatest hacker in the world
16 0.0329597 14 nathan marz storm-2010-04-27-New Cascalog features: outer joins, combiners, sorting, and more
17 0.031472422 28 nathan marz storm-2011-01-11-Cascalog workshop
18 0.030514915 8 nathan marz storm-2010-03-08-Follow-up to "The mathematics behind Hadoop-based systems"
19 0.029393036 34 nathan marz storm-2012-09-19-Storm's 1st birthday
20 0.02860532 4 nathan marz storm-2010-01-26-My conversation with the great John McCarthy
topicId topicWeight
[(0, 0.192), (1, 0.02), (2, -0.024), (3, 0.026), (4, -0.081), (5, -0.075), (6, 0.066), (7, 0.054), (8, 0.098), (9, -0.014), (10, -0.008), (11, 0.035), (12, -0.076), (13, -0.051), (14, -0.362), (15, -0.383), (16, -0.296), (17, -0.16), (18, 0.257), (19, -0.001), (20, 0.514), (21, 0.338), (22, -0.105), (23, -0.052), (24, -0.197), (25, 0.129), (26, 0.066), (27, -0.058), (28, -0.033), (29, -0.008), (30, 0.042), (31, 0.033), (32, 0.07), (33, -0.028), (34, 0.003), (35, 0.007), (36, -0.028), (37, 0.02), (38, -0.012), (39, -0.014), (40, -0.013)]
simIndex simValue blogId blogTitle
same-blog 1 0.98900181 36 nathan marz storm-2013-04-01-My new startup
Introduction: There's been a lot of speculation about what my new startup is doing, so I've decided to set the record straight and reveal all. We are working on one of the biggest problems on Earth, a problem that affects nearly every person on this planet. Our products will significantly improve the quality of life for billions of people. We are going to revolutionize the bedsheet industry. Think about it. There's been almost no innovation in bedsheets in thousands of years. There's nothing worse than waking up to discover one of the corners of your Egyptian cotton fitted sheets has slipped off the mattress. How is this not a solved problem yet? Why are we still using sheets with that annoying elastic in it to secure them to our mattresses? They slip all the time – and if you have a deep mattress, good luck finding sheets that even fit. You're just screwed. Consider the impact of solving this problem, of a bedsheet product that never slips, that always stays secure on the mattre
2 0.13155021 33 nathan marz storm-2012-02-06-Suffering-oriented programming
Introduction: Someone asked me an interesting question the other day: "How did you justify taking such a huge risk on building Storm while working on a startup ?" (Storm is a realtime computation system). I can see how from an outsider's perspective investing in such a massive project seems extremely risky for a startup. From my perspective, though, building Storm wasn't risky at all. It was challenging, but not risky. I follow a style of development that greatly reduces the risk of big projects like Storm. I call this style "suffering-oriented programming." Suffering-oriented programming can be summarized like so: don't build technology unless you feel the pain of not having it. It applies to the big, architectural decisions as well as the smaller everyday programming decisions. Suffering-oriented programming greatly reduces risk by ensuring that you're always working on something important, and it ensures that you are well-versed in a problem space before attempting a large investment. I ha
3 0.11451926 39 nathan marz storm-2014-02-12-Interview with "Programmer Magazine"
Introduction: I was recently interviewed for "Programmer Magazine", a Chinese magazine. The interview was published in Chinese, but a lot of people told me they'd like to see the English version of the interview. Due to the Google translation being, ahem, a little iffy, I decided to just publish the original English version on my blog. Hope you enjoy! What drew you to programming and what was the first interesting program you wrote? I started programming when I was 10 years old on my TI-82 graphing calculator. Initially I started programming because I wanted to make games on my calculator – and also because I was bored in math class :D. The first interesting game I made on my calculator was an archery game where you'd shoot arrows at moving targets. You'd get points for hitting more targets or completing all the targets faster. A couple years later I graduated to programming the TI-89 which was a huge upgrade in power. I remember how the TI-82 only let you have 26 variables (for the character
4 0.099265113 19 nathan marz storm-2010-07-12-My experience as the first employee of a Y Combinator startup
Introduction: I'm the first employee of BackType , a Summer '08 YC company. My joining the company increased the company size by 50%. The experience has been awesome, but I will say up front that being the first employee of a startup is not for everyone. The best part of being the first employee of a startup is the total exposure to all parts of the company. I've learned a ton about product development, customer development, recruiting, and entrepreneurship. Additionally, I've met and connected with lots of other awesome people through the YC network. I've gotten all these benefits at relatively low risk for myself, as I still have a salary and a solid chunk of equity. No Rules There are a lot of rules working at most companies. You don't even realize that some of the rules are rules until you work at a company with no rules. I'm talking about the most basic things like what hours you work, what days of the week you work, what tools you use, and whether you come into the office or not. B
5 0.084932283 3 nathan marz storm-2010-01-13-Mimi Silbert: the greatest hacker in the world
Introduction: Here's a problem for you: build an organization that transforms thousands of homeless people, ex-cons, and recovering drug addicts into productive members of society. OK, now do it with no money and no staff. And achieve a >90% success rate. While you're at it, make the organization double as a business that provides valuable services to the community. And make the whole thing self-sustaining. Amazingly, Mimi Silbert accomplished this very feat . She's been at it for 35 years and her organization is called the Delancey Street Foundation . I've been scouring the web for every bit of information I could find about how Delancey Street operates, and simply put, it's the most spectacular and innovative organization I've ever come across. At the highest level, Delancey Street is a stunning example of social entrepreneurship. Residents work in Delancey Street's numerous training schools, such as their moving company and restaurant . These businesses give the residents marketable sk
6 0.081684418 41 nathan marz storm-2014-05-10-Why we in tech must support Lawrence Lessig
7 0.077371538 22 nathan marz storm-2010-10-05-How to get a job at a kick-ass startup (for programmers)
8 0.077319369 40 nathan marz storm-2014-02-24-The inexplicable rise of open floor plans in tech companies
9 0.073069856 38 nathan marz storm-2013-04-12-Break into Silicon Valley with a blog
10 0.064916737 13 nathan marz storm-2010-04-14-Introducing Cascalog: a Clojure-based query language for Hadoop
11 0.063364252 23 nathan marz storm-2010-10-27-Fastest Viable Product: Investing in Speed at a Startup
12 0.062056601 25 nathan marz storm-2010-12-06-You Are a Product
13 0.057815224 31 nathan marz storm-2011-10-13-How to beat the CAP theorem
14 0.055733744 37 nathan marz storm-2013-04-02-Principles of Software Engineering, Part 1
15 0.053447787 9 nathan marz storm-2010-03-10-Thrift + Graphs = Strong, flexible schemas on Hadoop
16 0.053337839 2 nathan marz storm-2010-01-03-Tips for Optimizing Cascading Flows
17 0.0511945 18 nathan marz storm-2010-06-16-Your company has a knowledge debt problem
18 0.048969578 14 nathan marz storm-2010-04-27-New Cascalog features: outer joins, combiners, sorting, and more
19 0.048893277 4 nathan marz storm-2010-01-26-My conversation with the great John McCarthy
20 0.044830333 34 nathan marz storm-2012-09-19-Storm's 1st birthday
topicId topicWeight
[(10, 0.044), (13, 0.635), (26, 0.026), (41, 0.047), (59, 0.047), (76, 0.011), (88, 0.057)]
simIndex simValue blogId blogTitle
same-blog 1 0.97051924 36 nathan marz storm-2013-04-01-My new startup
Introduction: There's been a lot of speculation about what my new startup is doing, so I've decided to set the record straight and reveal all. We are working on one of the biggest problems on Earth, a problem that affects nearly every person on this planet. Our products will significantly improve the quality of life for billions of people. We are going to revolutionize the bedsheet industry. Think about it. There's been almost no innovation in bedsheets in thousands of years. There's nothing worse than waking up to discover one of the corners of your Egyptian cotton fitted sheets has slipped off the mattress. How is this not a solved problem yet? Why are we still using sheets with that annoying elastic in it to secure them to our mattresses? They slip all the time – and if you have a deep mattress, good luck finding sheets that even fit. You're just screwed. Consider the impact of solving this problem, of a bedsheet product that never slips, that always stays secure on the mattre
2 0.11737763 25 nathan marz storm-2010-12-06-You Are a Product
Introduction: I had a revelation the other day. I realized that the terms "programmer" and "employee" are inadequate to describe what I am. What I am is a product, and you are one too. If you want to develop your career, you need to approach your career as a product development problem. You sell yourself for various things: money, status, the opportunity to work on interesting problems, good coworkers, etc. In this post I'll be referring to this as "getting paid", but please keep in mind that "getting paid" means more than just money. Supply and Demand Like any product, you have supply and demand. Your supply is what you can do for a company that hires you. It's your ability to make beautiful websites. It's your ability to scale a database. It's your ability to get the best work out of others. Your supply is the actual value you will provide to a company that hires you. Your demand is what companies think you can do for them. Your demand is your perceived value by others. At the end of
3 0.1123432 19 nathan marz storm-2010-07-12-My experience as the first employee of a Y Combinator startup
Introduction: I'm the first employee of BackType , a Summer '08 YC company. My joining the company increased the company size by 50%. The experience has been awesome, but I will say up front that being the first employee of a startup is not for everyone. The best part of being the first employee of a startup is the total exposure to all parts of the company. I've learned a ton about product development, customer development, recruiting, and entrepreneurship. Additionally, I've met and connected with lots of other awesome people through the YC network. I've gotten all these benefits at relatively low risk for myself, as I still have a salary and a solid chunk of equity. No Rules There are a lot of rules working at most companies. You don't even realize that some of the rules are rules until you work at a company with no rules. I'm talking about the most basic things like what hours you work, what days of the week you work, what tools you use, and whether you come into the office or not. B
4 0.10432529 21 nathan marz storm-2010-08-20-5 Tips for Thinking Under Uncertainty
Introduction: Most people flee uncertainty. Yet being able to think well under uncertainty can be very rewarding, and I've come to realize it's a skill that can be learned. Here are some tips for thinking under uncertainty. 1. Think in terms of ranges of scenarios In many situations, you only have limited information. Our brains are quick to make conclusions and don't consider all the scenarios. Don't let this happen. You have to realize that given the information you have, there is a range of scenarios that could account for it. Talking to someone who seems cold and aloof? Maybe the person is unfriendly, or maybe the person is just shy . Is your boss micromanaging you lately? Maybe he doesn't trust you, maybe he's under increased pressure from his boss, or maybe it's just a random event. You need to avoid tunnel vision. It's easy to become focused on one scenario - because you're afraid of the scenario or really hopeful for it - and ignore information that points to other possibil
5 0.10333958 8 nathan marz storm-2010-03-08-Follow-up to "The mathematics behind Hadoop-based systems"
Introduction: In a previous post , I developed an equation modeling the stable runtime of an iterative, batch-oriented workflow. We saw how the equation explained a number of counter-intuitive behaviors of batch-oriented systems. In this post, we will learn how to measure the amount of overhead versus dynamic time in a workflow, which is the first step in applying the theory to optimize a workflow. Recall that we started with the equation for the runtime of a single iteration of a workflow: Runtime = Overhead + {Time to process one hour of data} * {Hours of Data} T = O + P * H We ended with the equation for the stable runtime of a workflow that runs repeatedly: {Stable Runtime} = Overhead / (1 - {Time to process one hour of data} T = O / (1 - P) Measuring O and P The first step towards utilizing this theory for optimizing your workflow will be to measure the values of O and P for your workflow. This can be difficult if the cluster is shared with lots of other jobs, as the P for each ru
6 0.09943299 23 nathan marz storm-2010-10-27-Fastest Viable Product: Investing in Speed at a Startup
7 0.097938605 22 nathan marz storm-2010-10-05-How to get a job at a kick-ass startup (for programmers)
8 0.092264056 39 nathan marz storm-2014-02-12-Interview with "Programmer Magazine"
9 0.091804199 30 nathan marz storm-2011-03-29-My talks at POSSCON
10 0.090879351 17 nathan marz storm-2010-05-26-Why your company should have a very permissive open source policy
11 0.083194494 34 nathan marz storm-2012-09-19-Storm's 1st birthday
12 0.082942195 6 nathan marz storm-2010-02-21-Why so many research papers are so hard to understand
13 0.082816765 12 nathan marz storm-2010-04-10-Fun with equality in Clojure
14 0.081621021 9 nathan marz storm-2010-03-10-Thrift + Graphs = Strong, flexible schemas on Hadoop
15 0.077790171 18 nathan marz storm-2010-06-16-Your company has a knowledge debt problem
16 0.075765193 28 nathan marz storm-2011-01-11-Cascalog workshop
17 0.074460357 7 nathan marz storm-2010-03-04-Introducing "Nanny" - a really simple dependency management tool
18 0.07238768 26 nathan marz storm-2010-12-09-How to reject a job candidate without being an asshole
19 0.070319362 40 nathan marz storm-2014-02-24-The inexplicable rise of open floor plans in tech companies
20 0.070304602 3 nathan marz storm-2010-01-13-Mimi Silbert: the greatest hacker in the world