Quotessence
Home / Topics / Bottlenecks Quotes

Bottlenecks Quotes

Browse 26 quotes about Bottlenecks.

Bottlenecks Quotes

“I always liked the steel guitar. I also love the guys that play the bottleneck. But I could never do it; I never made it do what I want. So every time I would pick up the guitar, I'd shake my hand and trill it a bit. For some strange reason my ears would say to me that sounds similar to what those guys were doing. I can't pick up the guitar now without doing it. So that's how I got into making my sound. It was nothing pretty. Just trying to please myself. I heard that sound.”

“One of my oldest friends from Kansas, his sister was married to Ben [Folds] and wrote lyrics on his first couple of albums. I got to meet him the first time I saw them in concert at The Bottleneck, a great bar in Lawrence, Kansas. Then, he was the musical guest my first or second week as a writer on SNL. I was like, "I don't know if you remember me?" And he was like, "Oh my god, yeah!" He's a big photography fan, as am I.”

“Plague has hung over human history. The biggest human extinction was after 1492 in North and South America when the mortality rate was 95 per cent, which is enormous. But again, I'm actually giving you grounds for optimism: There were enough to continue. The five per cent who made it through are what you need to survive a bottleneck, which we have been through before.”

“You will launch many projects, but have time to finish only a few. So think, plan, develop, launch and tap good people to be responsible. Give them authority and hold them accountable. Trying to do too much yourself creates a bottleneck.”

“Don't be a bottleneck. If a matter is not a decision for the President or you, delegate it. Force responsibility down and out. Find problem areas, add structure and delegate. The pressure is to do the reverse. Resist it.”

“Rushing to optimize before the bottlenecks are known may be the only error to have ruined more designs than feature creep. From tortured code to incomprehensible data layouts, the results of obsessing about speed or memory or disk usage at the expense of transparency and simplicity are everywhere. They spawn innumerable bugs and cost millions of man-hours - often, just to get marginal gains in the use of some resource much less expensive than debugging time”

“Make the bottlenecks work only on what will contribute to throughput today … not nine months from now. That’s one way to increase capacity at the bottlenecks. The other way you increase bottleneck capacity is to take some of the load off the bottlenecks and give it to non-bottlenecks.”