By analyzing the lives of such past masters as Charles Darwin, Benjamin Franklin, Albert Einstein, and Leonard da Vinci, as well as by interviewing nine contemporary masters, including tech guru Paul Graham and animal rights advocate Temple Grandin, Greene debunks our culture’s many myths about genius and distills the wisdom of the ages to reveal the secret to greatness. With this seminal text as a guide, readers will learn how to unlock the passion within and become masters.

    Thaler, and Cass R. Sunstein: a revelatory look at how we make decisionsNew York Times bestsellerNamed a Best Book of the Year by The Economist and the Financial Times Every day we make choices—about what to buy or eat, about financial investments or our children’s health and education, even about the causes we champion or the planet itself. Unfortunately, we often choose poorly. Nudge is about how we make these choices and how we can make better ones. Using dozens of eye-opening examples and drawing on decades of behavioral science research, Nobel Prize winner Richard H. Thaler and Harvard Law School professor Cass R. Sunstein show that no choice is ever presented to us in a neutral way, and that we are all susceptible to biases that can lead us to make bad decisions. But by knowing how people think, we can use sensible “choice architecture” to nudge people toward the best decisions for ourselves, our families, and our society, without restricting our freedom of choice.

    Drawing on anecdotes from science, economics, history, politics and philosophy, Matt Ridley’s wide-ranging, highly opinionated opus demolishes conventional assumptions that major scientific and social imperatives are dictated by those on high, whether in government, business, academia, or morality. On the contrary, our most important achievements develop from the bottom up. Patterns emerge, trends evolve. Just as skeins of geese form Vs in the sky without meaning to, and termites build mud cathedrals without architects, so brains take shape without brain-makers, learning can happen without teaching and morality changes without a plan.Although we neglect, defy and ignore them, bottom-up trends shape the world. The growth of technology, the sanitation-driven health revolution, the quadrupling of farm yields so that more land can be released for nature—these were largely emergent phenomena, as were the Internet, the mobile phone revolution, and the rise of Asia. Ridley demolishes the arguments for design and effectively makes the case for evolution in the universe, morality, genes, the economy, culture, technology, the mind, personality, population, education, history, government, God, money, and the future.

    As the words "at work" suggest, Peter Seibel focuses on how his interviewees tackle the day–to–day work of programming, while revealing much more, like how they became great programmers, how they recognize programming talent in others, and what kinds of problems they find most interesting. Hundreds of people have suggested names of programmers to interview on the Coders at Work web site: http://www.codersatwork.com. The complete list was 284 names. Having digested everyone’s feedback, we selected 16 folks who’ve been kind enough to agree to be interviewed:- Frances Allen: Pioneer in optimizing compilers, first woman to win the Turing Award (2006) and first female IBM fellow- Joe Armstrong: Inventor of Erlang- Joshua Bloch: Author of the Java collections framework, now at Google- Bernie Cosell: One of the main software guys behind the original ARPANET IMPs and a master debugger- Douglas Crockford: JSON founder, JavaScript architect at Yahoo!- L. Peter Deutsch: Author of Ghostscript, implementer of Smalltalk-80 at Xerox PARC and Lisp 1.5 on PDP-1- Brendan Eich: Inventor of JavaScript, CTO of the Mozilla Corporation - Brad Fitzpatrick: Writer of LiveJournal, OpenID, memcached, and Perlbal - Dan Ingalls: Smalltalk implementor and designer- Simon Peyton Jones: Coinventor of Haskell and lead designer of Glasgow Haskell Compiler- Donald Knuth: Author of The Art of Computer Programming and creator of TeX- Peter Norvig: Director of Research at Google and author of the standard text on AI- Guy Steele: Coinventor of Scheme and part of the Common Lisp Gang of Five, currently working on Fortress- Ken Thompson: Inventor of UNIX- Jamie Zawinski: Author of XEmacs and early Netscape/Mozilla hackerWhat you’ll learn:How the best programmers in the world do their jobWho is this book for?Programmers interested in the point of view of leaders in the field. Programmers looking for approaches that work for some of these outstanding programmers.

    But there are very few books that provide clear how-to information that can actually help you think better.Think Better is about Productive Thinking -- why it's important, how it works, and how to use it at work, at home, and at play. Productive Thinking is a game changer -- a practical, easy-to-learn, repeatable process that helps people understand more clearly, think more creatively, and plan more effectively. It's based on the thinking strategies that people we celebrate for their creativity have been using for centuries. Tim Hurson brings Productive Thinking out of the closet and presents it in a way that makes it easy for anyone to grasp and use -- so you can think better, work better, and do better in every aspect of your life.Think Better demonstrates how you can start with an intractable technical problem, an unmet consumer need, or a gaping chasm in your business strategy and, by following a clearly defined, practical thinking process, arrive at a robust, innovative solution. Many companies use the Productive Thinking model to generate fresh solutions for tough business problems, and many individuals rely on it to solve pressing personal problems.The principles you'll find in Think Better are straight-forward: separate your thinking into creative thinking and critical thinking; stay with the question; strive for the "third third" by generating lots and lots of ideas; and look for unexpected connections.The model consists of six interlocking steps:Step 1: What's Going On? Explore and truly understand the challenge.Step 2: What's Success? Envision the ideal outcome and establish success criteria.Step 3: What's the Question? Pinpoint the real problem or opportunity.Step 4: Generate Answers List many possible solutions.Step 5: Forge the Solution Decide which solution is best. Then make it better.Step 6: Align Resources Create an action plan.Tim Hurson starts by explaining how we all build inner barriers to effective thinking. He identifies our habits of thinking that severely limit our behavior, from "monkey mind" to "gator brain." Then he demonstrates how to overcome these barriers.More than anything, productive thinking is an attitude that will let you look at problems and convert them into opportunities. At the end of this disciplined brainstorming process, you'll have a concrete action plan, complete with timelines and deadlines.The book is filled with many of Hurson's original brainstorming tools that will empower you to generate, organize, and process ideas. For example, you can identify your best ideas using the five C's: Cull, Cluster, Combine, Clarify and Choose. And you can transform an embryonic idea into a robust solution with POWER, which stands for Positives, Objections, What else?, Enhancements and Remedies.To create the future, you first must be able to imagine it. Productive thinking is a way to help you do that.

    More than a series of fascinating case studies, To Engineer Is Human is a work that looks at our deepest notions of progress and perfection, tracing the fine connection between the quantifiable realm of science and the chaotic realities of everyday life."Alert, inquisitive, unspecialized, wholly human...refreshingly eclectic." --The Spectator"Henry Petroski is an ardent engineer, and if he writes more good books like this, he might find himself nominated to become the meistersinger of the guild. [This is] a refreshing plunge into the dynamics of the engineering ethos...as straightforward as an I-beam."--Science

    We have too much email, juggle multiple remotes, and hack through thickets of regulations from phone contracts to health plans. But complexity isn’t destiny. Sull and Eisenhardt argue there’s a better way. By developing a few simple yet effective rules, people can best even the most complex problems.   In Simple Rules, Sull and Eisenhardt masterfully challenge how we think about complexity and offer a new lens on how to cope. They take us on a surprising tour of what simple rules are, where they come from, and why they work. The authors illustrate the six kinds o f rules that really matter - for helping artists find creativity and the Federal Reserve set interest rates, for keeping birds on track and Zipcar members organized, and for how insomniacs can sleep and mountain climbers stay safe.   Drawing on rigorous research and riveting stories, the authors ingeniously find insights in unexpected places, from the way Tina Fey codified her experience at Saturday Night Live into rules for producing 30 Rock (rule five: never tell a crazy person he’s crazy) to burglars’ rules for robbery (“avoid houses with a car parked outside”) to Japanese engineers mimicking the rules of slime molds to optimize Tokyo’s rail system. The authors offer fresh information and practical tips on fixing old rules and learning new ones.   Whether you’re struggling with information overload, pursuing opportunities with limited resources, or just trying to change your bad habits, Simple Rules provides powerful insight into how and why simplicity tames complexity.

    social scientist and consultant examines five professions - engineering, architecture, management, psychotherapy, and town planning - to show how professionals really go about solving problems. The best professionals, Donald Sch�n maintains, know more than they can put into words. To meet the challenges of their work, they rely less on formulas learned in graduate school than on the kind of improvisation learned in practice. This unarticulated, largely unexamined process is the subject of Sch�n's provocatively original book, an effort to show precisely how 'reflection-in-action' works and how this vital creativity might be fostered in future professionals.

    America's leadership expert John C. Maxwell will teach you how to be more creative and when to question popular thinking. You'll learn how to capture the big picture while focusing your thinking. You'll find out how to tap into your creative potential, develop shared ideas, and derive lessons from the past to better understand the future. With these eleven keys to more effective thinking, you'll clearly see the path to personal success.The 11 keys to successful thinking include:Big-Picture Thinking - seeing the world beyond your own needs and how that leads to great ideasFocused Thinking - removing mental clutter and distractions to realize your full potentialCreative Thinking - thinking in unique ways and making breakthroughsShared Thinking - working with others to compound resultsReflective Thinking - looking at the past to gain a better understanding of the future.

    Ideas for new businesses, solutions to the world's problems, and artistic breakthroughs are common, but great execution is rare. According to Scott Belsky, the capacity to make ideas happen can be developed by anyone willing to develop their organizational habits and leadership capability. That's why he founded Behance, a company that helps creative people and teams across industries develop these skills. Belsky has spent six years studying the habits of creative people and teams that are especially productive-the ones who make their ideas happen time and time again. After interviewing hundreds of successful creatives, he has compiled their most powerful-and often counterintuitive-practices, such as: •Generate ideas in moderation and kill ideas liberally •Prioritize through nagging •Encourage fighting within your team While many of us obsess about discovering great new ideas, Belsky shows why it's better to develop the capacity to make ideas happen-a capacity that endures over time.

    I'm going to share that mindset with you — along with hundreds of actionable techniques and proven habits — so you can shortcut those years.Introducing The Effective Engineer — the only book designed specifically for today's software engineers, based on extensive interviews with engineering leaders at top tech companies, and packed with hundreds of techniques to accelerate your career.For two years, I embarked on a quest seeking an answer to one question:How do the most effective engineers make their efforts, their teams, and their careers more successful?I interviewed and collected stories from engineering VPs, directors, managers, and other leaders at today's top software companies: established, household names like Google, Facebook, Twitter, and LinkedIn; rapidly growing mid-sized companies like Dropbox, Square, Box, Airbnb, and Etsy; and startups like Reddit, Stripe, Instagram, and Lyft.These leaders shared stories about the most valuable insights they've learned and the most common and costly mistakes that they've seen engineers — sometimes themselves — make.This is just a small sampling of the hard questions I posed to them:- What engineering qualities correlate with future success?- What have you done that has paid off the highest returns?- What separates the most effective engineers you've worked with from everyone else?- What's the most valuable lesson your team has learned in the past year?- What advice do you give to new engineers on your team? Everyone's story is different, but many of the lessons share common themes.You'll get to hear stories like:- How did Instagram's team of 5 engineers build and support a service that grew to over 40 million users by the time the company was acquired?- How and why did Quora deploy code to production 40 to 50 times per day?- How did the team behind Google Docs become the fastest acquisition to rewrite its software to run on Google's infrastructure?- How does Etsy use continuous experimentation to design features that are guaranteed to increase revenue at launch?- How did Facebook's small infrastructure team effectively operate thousands of database servers?- How did Dropbox go from barely hiring any new engineers to nearly tripling its team size year-over-year? What's more, I've distilled their stories into actionable habits and lessons that you can follow step-by-step to make your career and your team more successful.The skills used by effective engineers are all learnable.And I'll teach them to you. With The Effective Engineer, I'll teach you a unifying framework called leverage — the value produced per unit of time invested — that you can use to identify the activities that produce disproportionate results.Here's a sneak peek at some of the lessons you'll learn. You'll learn how to:- Prioritize the right projects and tasks to increase your impact.- Earn more leeway from your peers and managers on your projects.- Spend less time maintaining and fixing software and more time building and shipping new features.- Produce more accurate software estimates.- Validate your ideas cheaply to reduce wasted work.- Navigate organizational and people-related bottlenecks.- Find the appropriate level of code reviews, testing, abstraction, and technical debt to balance speed and quality.- Shorten your debugging workflow to increase your iteration speed.

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    Creativity, Inc. is a book for managers who want to lead their employees to new heights, a manual for anyone who strives for originality, and the first-ever, all-access trip into the nerve center of Pixar Animation—into the meetings, postmortems, and “Braintrust” sessions where some of the most successful films in history are made. It is, at heart, a book about how to build a creative culture—but it is also, as Pixar co-founder and president Ed Catmull writes, “an expression of the ideas that I believe make the best in us possible.” For nearly twenty years, Pixar has dominated the world of animation, producing such beloved films as the Toy Story trilogy, Monsters, Inc., Finding Nemo, The Incredibles, Up, and WALL-E, which have gone on to set box-office records and garner thirty Academy Awards. The joyousness of the storytelling, the inventive plots, the emotional authenticity: In some ways, Pixar movies are an object lesson in what creativity really is. Here, in this book, Catmull reveals the ideals and techniques that have made Pixar so widely admired—and so profitable.   As a young man, Ed Catmull had a dream: to make the first computer-animated movie. He nurtured that dream as a Ph.D. student at the University of Utah, where many computer science pioneers got their start, and then forged a partnership with George Lucas that led, indirectly, to his founding Pixar with Steve Jobs and John Lasseter in 1986. Nine years later, Toy Story was released, changing animation forever. The essential ingredient in that movie’s success—and in the thirteen movies that followed—was the unique environment that Catmull and his colleagues built at Pixar, based on philosophies that protect the creative process and defy convention, such as:   • Give a good idea to a mediocre team, and they will screw it up. But give a mediocre idea to a great team, and they will either fix it or come up with something better. • If you don’t strive to uncover what is unseen and understand its nature, you will be ill prepared to lead. • It’s not the manager’s job to prevent risks. It’s the manager’s job to make it safe for others to take them. • The cost of preventing errors is often far greater than the cost of fixing them. • A company’s communication structure should not mirror its organizational structure. Everybody should be able to talk to anybody. • Do not assume that general agreement will lead to change—it takes substantial energy to move a group, even when all are on board.

    No other job pulls people in so many directions at once. Users interrupt you constantly with requests, preventing you from getting anything done. Your managers want you to get long-term projects done but flood you with reques ... Available here:readmeaway.com/download?i=0596007833Time Management for System Administrators: Stop Working Late and Start Working Smart PDF by Thomas A. LimoncelliRead Time Management for System Administrators: Stop Working Late and Start Working Smart PDF from O'Reilly Media,Thomas A. LimoncelliDownload Thomas A. Limoncelli’s PDF E-book Time Management for System Administrators: Stop Working Late and Start Working Smart

    Christensen says outstanding companies can do everything right and still lose their market leadership -- or worse, disappear completely. And he not only proves what he says, he tells others how to avoid a similar fate.Focusing on "disruptive technology" -- the Honda Super Cub, Intel's 8088 processor, or the hydraulic excavator, for example -- Christensen shows why most companies miss "the next great wave." Whether in electronics or retailing, a successful company with established products will get pushed aside unless managers know when to abandon traditional business practices. Using the lessons of successes and failures from leading companies, "The Innovator's Dilemma" presents a set of rules for capitalizing on the phenomenon of disruptive innovation.