high_scalability high_scalability-2008 high_scalability-2008-352 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Robert Scoble in an often poignant FriendFeed thread commiserating PodTech's unfortunate end, shared what he learned about creating a successful startup. Here's a summary of a Robert's rules and why Machiavelli just may agree with them: Have a story. Have everyone on board with that story. If anyone goes off of that story, make sure they get on board immediately or fire them. Make sure people are judged by the revenues they bring in. Those that bring in revenues should get to run the place. People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. Work ONLY for a leader who will make the tough decisions. Build a place where excellence is expected, allowed, and is enabled. Fire idiots quickly. If your engineering team can't give a media team good measurements, the entire company is in trouble. Only things that are measured ever get improved. When your stars aren't listened to the company is in trouble. Getting rid of t
sentIndex sentText sentNum sentScore
1 Make sure people are judged by the revenues they bring in. [sent-5, score-0.414]
2 Those that bring in revenues should get to run the place. [sent-6, score-0.276]
3 People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. [sent-7, score-0.43]
4 Build a place where excellence is expected, allowed, and is enabled. [sent-9, score-0.155]
5 An excellent list that meshes with much of my experience, which is why I thought it worth sharing :-) My take-away from Robert's rules can be summarized in one word: focus . [sent-15, score-0.185]
6 When Robert says have "a story" that to me is because a story provides a sort of "decision box" giving a group its organizing principle for determining everything that comes later. [sent-19, score-0.333]
7 Without a management strong enough act in accordance with the story, centripetal forces tear an organization apart. [sent-25, score-0.484]
8 " Princes must exhibit virtue if they are to keep their land. [sent-29, score-0.25]
9 Machiavelli doesn't mean virtue in the modern sense of be good and eat your peas, but in the ancient sense of manliness (sorry ladies, this was long ago). [sent-30, score-0.25]
10 So to act virtuously is to be bold, to act, to take risks, be aggressive, and make the hard unpopular decisions. [sent-32, score-0.187]
11 For Machiavelli that's the only way to reach your goals in accordance with how the world really works, not how it ought to work. [sent-33, score-0.289]
12 Firing people (yes, I've been fired) not contributing to your story is by Machiavelli's definition a virtuous act. [sent-35, score-0.387]
13 And that's why people are often not fired as Robert suggests. [sent-38, score-0.207]
14 Addition by subtraction is such a powerful force precisely because it maintains group focus on excellence and purpose. [sent-40, score-0.234]
15 Keeping people who aren't helping is a vampire on a group's energy. [sent-42, score-0.151]
16 It slowly drains away all vivacity until only a pale corpse remains. [sent-43, score-0.145]
17 Robert's rules may seem excessively ruthless and cruel to many. [sent-44, score-0.344]
18 But in true Machiavellian fashion let's ask what is preferable: a strong secure long-lived state ruled by virtue or a state ruled according to how the world ought to work that is constantly at the mercy of every invader? [sent-46, score-0.767]
19 If you are still hungry for more starter advice, Gordon Ramsay has some unintentionally delicious thoughts on developing software as well. [sent-47, score-0.146]
20 Kevin Burton share's seven deadly sins startups should avoid and makes an inspiring case how his company stronger and better able to compete by not taking VC funds. [sent-51, score-0.213]
wordName wordTfidf (topN-words)
[('machiavelli', 0.329), ('robert', 0.279), ('story', 0.254), ('virtue', 0.25), ('ramsay', 0.247), ('revenues', 0.188), ('accordance', 0.155), ('excellence', 0.155), ('fired', 0.138), ('gordon', 0.138), ('ought', 0.134), ('ruled', 0.125), ('act', 0.116), ('rules', 0.111), ('board', 0.107), ('bring', 0.088), ('forces', 0.086), ('excessively', 0.082), ('ladies', 0.082), ('ruthless', 0.082), ('truer', 0.082), ('vampire', 0.082), ('visionary', 0.082), ('group', 0.079), ('prince', 0.077), ('preferable', 0.077), ('starter', 0.077), ('fewer', 0.077), ('company', 0.077), ('drains', 0.074), ('meshes', 0.074), ('decision', 0.072), ('corpse', 0.071), ('decidedly', 0.071), ('mercy', 0.071), ('unpopular', 0.071), ('judged', 0.069), ('cruel', 0.069), ('delicious', 0.069), ('inspiring', 0.069), ('unfortunate', 0.069), ('people', 0.069), ('deadly', 0.067), ('spoken', 0.067), ('tear', 0.065), ('messy', 0.064), ('virtuous', 0.064), ('listened', 0.063), ('bold', 0.063), ('strong', 0.062)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
Introduction: Robert Scoble in an often poignant FriendFeed thread commiserating PodTech's unfortunate end, shared what he learned about creating a successful startup. Here's a summary of a Robert's rules and why Machiavelli just may agree with them: Have a story. Have everyone on board with that story. If anyone goes off of that story, make sure they get on board immediately or fire them. Make sure people are judged by the revenues they bring in. Those that bring in revenues should get to run the place. People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. Work ONLY for a leader who will make the tough decisions. Build a place where excellence is expected, allowed, and is enabled. Fire idiots quickly. If your engineering team can't give a media team good measurements, the entire company is in trouble. Only things that are measured ever get improved. When your stars aren't listened to the company is in trouble. Getting rid of t
2 0.17604449 1500 high scalability-2013-08-12-100 Curse Free Lessons from Gordon Ramsay on Building Great Software
Introduction: Gordon Ramsay is a world renowned chef with a surprising amount to say on software development. Well, he says it about cooking and running a restaurant, but it applies to software development too. You may have seen Gordon Ramsay on one of his many TV shows. Hell's Kitchen is a competition between chefs trying to win a dream job: head chef of their own high-end restaurant. On this show Ramsay is judge, jury, and executioner. And he chops off more than a few heads. Kitchen Nightmares is a show where Ramsay is called in by restaurant owners to help turn around their failing restaurants. On this show Ramsay is there to help. If you just watch Hell's Kitchen you will likely conclude Ramsay is one of the devil's own helpers ("ram" is the symbol of the devil and "say" means he speaks for the devil: Ramsay). Ramsay screams, yells, cusses, belittles, and throws tantrums even a 7 year old could learn from. Then he does it all over gain just for spite. In Hell's Kitchen there's no evidence a
Introduction: One of the cool things about Mr. Scoble is he doesn't pretend to know everything, which can be an deadly boring affliction in this field. In this case Robert is asking for help in an upcoming interview. Maybe we can help? Here's Robert's plight: I’m really freaked out. I have one of the biggest interviews of my life coming up and I’m way under qualified to host it. It’s on Thursday and it’s about Scalability and Performance of Web Services. Look at who will be on. Matt Mullenweg, founder of Automattic, the company behind WordPress (and behind this blog). Paul Bucheit, one of the founders of FriendFeed and the creator of Gmail (he’s also the guy who gave Google the “don’t be evil” admonishion). Nat Brown, CTO of iLike, which got six million users on Facebook in about 10 days. What would you ask?
4 0.11371995 870 high scalability-2010-08-02-7 Scaling Strategies Facebook Used to Grow to 500 Million Users
Introduction: Robert Johnson, a director of engineering at Facebook, celebrated Facebook's monumental achievement of reaching 500 million users by sharing the scaling principles that helped reach that milestone. In case you weren't suitably impressed by the 500 million user number, Robert ratchets up the numbers game with these impressive figures: 1 million users per engineer 500 million active users 100 billion hits per day 50 billion photos 2 trillion objects cached, with hundreds of millions of requests per second 130TB of logs every day How did Facebook get to this point? People Matter Most . It's people who build and run systems. The best tools for scaling are an engineering and operations teams that can handle anything. Scale Horizontally . Handling exponentially growing traffic requires spreading load arbitrarily across many machines. Using different databases for tables like accounts and profiles only doubles capacity. This approach hurts efficiency, but
5 0.090918735 1344 high scalability-2012-10-19-Stuff The Internet Says On Scalability For October 19, 2012
Introduction: It's HighScalability Time: @davilagrau : Youtube, GitHub,..., Are cloud services facing a entropic limit to scalability? Async all the way down? The Tyranny of the Clock : The cost of logic and memory dominated Turing's thinking, but today, communication rather than logic should dominate our thinking. Clock-free design uses less than half, about 40%, as much energy per addition as its clocked counterpart. We can regain the efficiency of local decision making by revolting against the pervasive beat of an external clock. Why Google Compute Engine for OpenStack . Smart move. Having OpenStack work inside a super charged cloud, in private clouds, and as a bridge between the two ought to be quite attractive to developers looking for some sort of ally for independence. All it will take are a few victories to cement new alliances. 3 Lessons That Startups Can Learn From Facebook’s Failed Credits Experiment . I thought this was a great idea too. So what happened? FACEBOOK DID NOT
6 0.087230727 1430 high scalability-2013-03-27-The Changing Face of Scale - The Downside of Scaling in the Contextual Age
7 0.086068287 107 high scalability-2007-10-02-Some Real Financial Numbers for Your Startup
8 0.085082494 201 high scalability-2008-01-04-For $5 Million You Can Buy Enough Storage to Compete with Google
9 0.082498111 1011 high scalability-2011-03-25-Did the Microsoft Stack Kill MySpace?
11 0.079892509 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
12 0.079328984 919 high scalability-2010-10-14-I, Cloud
13 0.077810474 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
14 0.0755734 1247 high scalability-2012-05-18-Stuff The Internet Says On Scalability For May 18, 2012
15 0.073452689 127 high scalability-2007-10-20-Strategy: Send XHR Request on Lost Focus Instead of For Every Character
16 0.072920792 1635 high scalability-2014-04-21-This is why Microsoft won. And why they lost.
17 0.07186611 1564 high scalability-2013-12-13-Stuff The Internet Says On Scalability For December 13th, 2013
18 0.071243897 988 high scalability-2011-02-11-Stuff The Internet Says On Scalability For February 11, 2011
19 0.069906458 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?
20 0.069450311 1047 high scalability-2011-05-25-Stuff to Watch from Surge 2010
topicId topicWeight
[(0, 0.116), (1, 0.055), (2, 0.009), (3, 0.038), (4, 0.038), (5, -0.066), (6, -0.038), (7, 0.047), (8, -0.002), (9, -0.037), (10, -0.034), (11, 0.014), (12, -0.022), (13, 0.027), (14, 0.033), (15, -0.024), (16, 0.041), (17, -0.017), (18, -0.026), (19, 0.005), (20, 0.011), (21, -0.01), (22, 0.024), (23, 0.008), (24, -0.053), (25, 0.025), (26, 0.02), (27, 0.012), (28, -0.028), (29, 0.002), (30, -0.027), (31, -0.023), (32, -0.002), (33, 0.005), (34, -0.006), (35, 0.009), (36, -0.012), (37, 0.011), (38, 0.047), (39, -0.038), (40, -0.011), (41, 0.032), (42, -0.006), (43, -0.015), (44, 0.048), (45, 0.019), (46, -0.004), (47, -0.028), (48, 0.014), (49, 0.028)]
simIndex simValue blogId blogTitle
same-blog 1 0.9790346 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
Introduction: Robert Scoble in an often poignant FriendFeed thread commiserating PodTech's unfortunate end, shared what he learned about creating a successful startup. Here's a summary of a Robert's rules and why Machiavelli just may agree with them: Have a story. Have everyone on board with that story. If anyone goes off of that story, make sure they get on board immediately or fire them. Make sure people are judged by the revenues they bring in. Those that bring in revenues should get to run the place. People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. Work ONLY for a leader who will make the tough decisions. Build a place where excellence is expected, allowed, and is enabled. Fire idiots quickly. If your engineering team can't give a media team good measurements, the entire company is in trouble. Only things that are measured ever get improved. When your stars aren't listened to the company is in trouble. Getting rid of t
2 0.86142319 1500 high scalability-2013-08-12-100 Curse Free Lessons from Gordon Ramsay on Building Great Software
Introduction: Gordon Ramsay is a world renowned chef with a surprising amount to say on software development. Well, he says it about cooking and running a restaurant, but it applies to software development too. You may have seen Gordon Ramsay on one of his many TV shows. Hell's Kitchen is a competition between chefs trying to win a dream job: head chef of their own high-end restaurant. On this show Ramsay is judge, jury, and executioner. And he chops off more than a few heads. Kitchen Nightmares is a show where Ramsay is called in by restaurant owners to help turn around their failing restaurants. On this show Ramsay is there to help. If you just watch Hell's Kitchen you will likely conclude Ramsay is one of the devil's own helpers ("ram" is the symbol of the devil and "say" means he speaks for the devil: Ramsay). Ramsay screams, yells, cusses, belittles, and throws tantrums even a 7 year old could learn from. Then he does it all over gain just for spite. In Hell's Kitchen there's no evidence a
3 0.82548153 347 high scalability-2008-07-07-Five Ways to Stop Framework Fixation from Crashing Your Scaling Strategy
Introduction: If you've wondered why I haven't been posting lately it's because I've been on an amazing Beach's motorcycle tour of the Alps ( and , and , and , and , and , and , and , and ). My wife (Linda) and I rode two-up on a BMW 1200 GS through the alps in Germany, Austria, Switzerland, Italy, Slovenia, and Lichtenstein. The trip was more beautiful than I ever imagined. We rode challenging mountain pass after mountain pass, froze in the rain, baked in the heat, woke up on excellent Italian coffee, ate slice after slice of tasty apple strudel, drank dazzling local wines, smelled the fresh cut grass as the Swiss en masse cut hay for the winter feeding of their dairy cows, rode the amazing Munich train system, listened as cow bells tinkled like wind chimes throughout small valleys, drank water from a pure alpine spring on a blisteringly hot hike, watched local German folk dancers represent their regions, and had fun in the company of fellow riders. Magical. They say you'll ride more
4 0.82393384 863 high scalability-2010-07-22-How can we spark the movement of research out of the Ivory Tower and into production?
Introduction: Over the years I've read a lot of research papers looking for better ways of doing things. Sometimes I find ideas I can use, but more often than not I come up empty. The problem is there are very few good papers. And by good I mean: can a reasonably intelligent person read a paper and turn it into something useful? Now, clearly I'm not an academic and clearly I'm no genius, I'm just an everyday programmer searching for leverage, and as a common specimen of the species I've often thought how much better our industry would be if we could simply move research from academia into production with some sort of self-conscious professionalism. Currently the process is horribly hit or miss. And this problem extends equally to companies with research divisions that often do very little to help front-line developers succeed. How many ideas break out of academia into industry in computer science? We have many brilliant examples: encryption, microprocessors, compression, transactions, distribu
5 0.82152277 1503 high scalability-2013-08-19-What can the Amazing Race to the South Pole Teach us About Startups?
Introduction: At the heart of every software adventure exists a journey in service of a quest. Melodramatic much? Sorry, but while wandering dazzled through Race to the End of the Earth , a fantastic exhibit at the Royal BC Museum on the 1911-1912 race to the South Pole between Norwegian explorer Roald Amundsen and British naval officer Robert Scott , I couldn’t help but think of the two radically different approaches each team took to the race and it shocked me to see that some of the same principles that lead to success or failure in software development also seem to lead to success or failure in exploration. I wish I could reproduce the experience of walking through the exhibit . Plaque after plaque I remember wondering out loud at Scott’s choices and then nod in agreement with Amundsen’s approach. The core conflict was straight out of any ancient Agile (Amundsen) vs Waterfall (Scott) thread you can find on Usenet. And Waterfall lost. As background here are some sources you may want
6 0.81628609 1635 high scalability-2014-04-21-This is why Microsoft won. And why they lost.
7 0.81243575 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?
9 0.78563976 1526 high scalability-2013-10-02-RFC 1925 - The Twelve (Timeless) Networking Truths
10 0.77706778 363 high scalability-2008-08-12-Strategy: Limit The New, Not The Old
11 0.7708087 1377 high scalability-2012-12-26-Ask HS: What will programming and architecture look like in 2020?
12 0.7666285 1366 high scalability-2012-12-03-Resiliency is the New Normal - A Deep Look at What It Means and How to Build It
13 0.76616031 1388 high scalability-2013-01-16-What if Cars Were Rented Like We Hire Programmers?
15 0.75437897 1410 high scalability-2013-02-20-Smart Companies Fail Because they Do Everything Right - Staying Alive to Scale
16 0.74554479 1379 high scalability-2012-12-31-Designing for Resiliency will be so 2013
17 0.73549318 1012 high scalability-2011-03-28-Aztec Empire Strategy: Use Dual Pipes in Your Aqueduct for High Availability
18 0.73381853 1014 high scalability-2011-03-31-8 Lessons We Can Learn from the MySpace Incident - Balance, Vision, Fearlessness
19 0.73144108 1011 high scalability-2011-03-25-Did the Microsoft Stack Kill MySpace?
20 0.72906226 747 high scalability-2009-11-26-What I'm Thankful For on Thanksgiving
topicId topicWeight
[(1, 0.097), (2, 0.164), (10, 0.014), (40, 0.048), (47, 0.022), (61, 0.089), (79, 0.117), (85, 0.045), (92, 0.273), (94, 0.045)]
simIndex simValue blogId blogTitle
1 0.89396828 839 high scalability-2010-06-09-Paper: Propagation Networks: A Flexible and Expressive Substrate for Computation
Introduction: Alexey Radul in his fascinating 174 page dissertation Propagation Networks: A Flexible and Expressive Substrate for Computation , offers to help us break free of the tyranny of linear time by arranging computation as a network of autonomous but interconnected machines . We can do this by organizing computation as a network of interconnected machines of some kind, each of which is free to run when it pleases, propagating information around the network as proves possible. The consequence of this freedom is that the structure of the aggregate does not impose an order of time. The abstract from his thesis is : In this dissertation I propose a shift in the foundations of computation. Modern programming systems are not expressive enough. The traditional image of a single computer that has global effects on a large memory is too restrictive. The propagation paradigm replaces this with computing by networks of local, independent, stateless machines interconnected with stateful storage
2 0.8914355 1636 high scalability-2014-04-23-Here's a 1300 Year Old Solution to Resilience - Rebuild, Rebuild, Rebuild
Introduction: How is it possible that a wooden Shinto shrine built in the 7th century is still standing? The answer depends on how you answer this philosophical head scratcher: With nearly every cell in your body continually being replaced, are you still the same person? The Ise Grand Shrine has been in continuous existence for over 1300 years because every twenty years an exact replica has been rebuilt on an adjacent footprint. The former temple is then dismantled. Now that's resilience. If you want something to last make it a living part of a culture. It's not so much the building that is remade, what is rebuilt and passed down from generation to generation is the meme that the shrine is important and worth preserving. The rest is an unfolding of that imperative. You can see echoes of this same process in Open Source projects like Linux and the libraries and frameworks that get themselves reconstructed in each new environment. The patterns of recurrence in software are the result of Darw
same-blog 3 0.87333488 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
Introduction: Robert Scoble in an often poignant FriendFeed thread commiserating PodTech's unfortunate end, shared what he learned about creating a successful startup. Here's a summary of a Robert's rules and why Machiavelli just may agree with them: Have a story. Have everyone on board with that story. If anyone goes off of that story, make sure they get on board immediately or fire them. Make sure people are judged by the revenues they bring in. Those that bring in revenues should get to run the place. People who don't bring in revenues should get fewer and fewer responsibilities, not more and more. Work ONLY for a leader who will make the tough decisions. Build a place where excellence is expected, allowed, and is enabled. Fire idiots quickly. If your engineering team can't give a media team good measurements, the entire company is in trouble. Only things that are measured ever get improved. When your stars aren't listened to the company is in trouble. Getting rid of t
4 0.81567961 1234 high scalability-2012-04-26-Akaros - an open source operating system for manycore architectures
Introduction: If you are interested in future foward OS designs then you might find Akaros worth a look. It's an operating system designed for many-core architectures and large-scale SMP systems, with the goals of: Providing better support for parallel and high-performance applications Scaling the operating system to a large number of cores A more indepth explanation of the motiviation behind Akaros can be found in Improving Per-Node Efficiency in the Datacenter with NewOS Abstractions by Barret Rhoden, Kevin Klues, David Zhu, and Eric Brewer. The abstract: We believe datacenters can benefit from more focus on per-node efficiency, performance, and predictability, versus the more common focus so far on scalability to a large number of nodes. Improving per-node efficiency decreases costs and fault recovery because fewer nodes are required for the same amount of work. We believe that the use of complex, general-purpose operating systems is a key contributing factor to these inefficiencies
5 0.78056216 532 high scalability-2009-03-11-Sharding and Connection Pools
Introduction: Hi we are looking at sharding our existing Java/Oracle based application. We are looking to make the app servers able to process requests for multiple (any?) shard. The concern that has come up is the amount of memory that would be consumed by having so many connection pools on one app server. Additionally there is concern about having so many physical connections to the database server coming from all the various app servers that may talk to that particular shard. I was wondering if anyone else has dealt with this issue and how you resolved it? Thanks, Scott
6 0.77298701 528 high scalability-2009-03-06-Product: Lightcloud - Key-Value Database
7 0.74727851 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
8 0.7431882 988 high scalability-2011-02-11-Stuff The Internet Says On Scalability For February 11, 2011
9 0.71381867 357 high scalability-2008-07-26-Google's Paxos Made Live – An Engineering Perspective
10 0.71280444 850 high scalability-2010-06-30-Paper: GraphLab: A New Framework For Parallel Machine Learning
11 0.69730717 928 high scalability-2010-10-26-Scaling DISQUS to 75 Million Comments and 17,000 RPS
12 0.69292331 157 high scalability-2007-11-16-Product: lbpool - Load Balancing JDBC Pool
13 0.684784 1180 high scalability-2012-01-24-The State of NoSQL in 2012
14 0.66290468 1020 high scalability-2011-04-12-Caching and Processing 2TB Mozilla Crash Reports in memory with Hazelcast
15 0.66218251 1559 high scalability-2013-12-06-Stuff The Internet Says On Scalability For December 6th, 2013
16 0.66035819 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014
17 0.66000623 1389 high scalability-2013-01-18-Stuff The Internet Says On Scalability For January 18, 2013
18 0.65997982 517 high scalability-2009-02-21-Google AppEngine - A Second Look
19 0.65981913 301 high scalability-2008-04-08-Google AppEngine - A First Look
20 0.65973061 768 high scalability-2010-02-01-What Will Kill the Cloud?