And it was an astronomer who finally explained what happened to the dinosaurs.Frans Johansson's The Medici Effect shows how breakthrough ideas most often occur when we bring concepts from one field into a new, unfamiliar territory, and offers examples how we can turn the ideas we discover into path-breaking innovations.

    These people are celebrities now. What was it like when they were just a couple friends with an idea? Founders like Steve Wozniak (Apple), Caterina Fake (Flickr), Mitch Kapor (Lotus), Max Levchin (PayPal), and Sabeer Bhatia (Hotmail) tell you in their own words about their surprising and often very funny discoveries as they learned how to build a company.Where did they get the ideas that made them rich? How did they convince investors to back them? What went wrong, and how did they recover?Nearly all technical people have thought of one day starting or working for a startup. For them, this book is the closest you can come to being a fly on the wall at a successful startup, to learn how it's done.But ultimately these interviews are required reading for anyone who wants to understand business, because startups are business reduced to its essence. The reason their founders become rich is that startups do what businesses do--create value--more intensively than almost any other part of the economy. How? What are the secrets that make successful startups so insanely productive? Read this book, and let the founders themselves tell you.

    You'll get several case studies, including Airbnb, along with interviews with UX strategists from different work environments (startup, agency, and enterprise) about their roles and experience.With this book, UX designers, product stakeholders, and startup founders will learn how to: • Conduct a competitive analysis on the online marketplace• Perform guerrilla user research for your MVP• Design for conversion and develop a funnel matrix for understanding customer acquisition• Extract innovative online opportunities from market research• Validate customer research with continuous feedback loops• Adapt traditional and contemporary business approaches (such as Lean Startup) to implement a successful strategy

    This book aims to minimize the complexity of user-centered design for the Web with explanations and illustrations that focus on ideas rather than tools or techniques.

    These principles have revolutionized manufacturing and have been adopted by the most innovative product companies including Toyota and 3M. In 2003 the Poppendieck's published Lean Software Development: An Agile Toolkit which showed how these same lean principles can be successfully applied to software development. Since that publication the authors have increased their understanding of Lean and Agile problems faced by large organizations and have emerged as leading advocates for bringing Lean production techniques to software development. While their first book provides an introduction, theoretical advice and a reference to Lean, this follow-up incorporates their gained knowledge and understanding of what works and goes steps further to provide hands-on guidance for implementing a Lean system. Using historical case studies from prominent companies such as Polaris, Lockheed and Fujistu the authors prove the overall value of Lean practices and shows how to effectively apply these methods to software production.

    Yet successful software businesses like Slack, Dropbox, Atlassian, and HubSpot make millions selling to customers who never once reached out to a sales rep.In Product-Led Growth: How to Build a Product That Sells Itself, growth consultant Wes Bush challenges the traditional SaaS marketing and sales playbook and introduces a completely new way to sell products. Bush reveals how your product—not expensive sales teams—can be the main vehicle to acquire, convert, and retain customers.In this step-by-step guide to Product-Led Growth, Bush explains: Why you should flip the traditional sales process on its head and turn your product into a sales machine; How to decide whether your business should use a free trial, freemium, or hybrid model; How to turn free users into happy, paying customers. History tells us that “how” you sell is just as important as “what” you sell. Blockbuster couldn’t compete with Netflix by selling the same digital content, and you need to decide “when” not “if” you’ll innovate on the way you sell. Are you going to be product-led? Or will you be disrupted, too?

     This book by the team at Intercom, a rapidly growing San Francisco software startup, is designed to help those working in the ever evolving field of product management Since Intercom began in 2011, its team has been writing about how it approaches the product challenges it faces. How do you decide what to build? How do you decide what not to build? What questions should you ask beta users? How do you manage feedback? Intercom on Product Management takes the best product posts from Intercom’s award winning blog, Inside Intercom, and collects them together in actionable lessons for product managers. It’s not the definitive book on product management, but we think it’s a damn good place to start. What you’ll learn: CHAPTER 1 Evaluating your product CHAPTER 2 The thing about new features CHAPTER 3 Which new features to build CHAPTER 4 Getting the feature used Intercom on Product Management was written by Des Traynor, co-founder of Intercom and edited by John Collins, managing editor of Intercom's blog. Des has written extensively on product management and strategy and is a regular speaker on the topic at conferences like Business of Software, Launch and Mind the Product. John has over 20 years journalism experience covering technology and business issues, most recently for The Irish Times. Intercom helps web and mobile businesses to see, engage, learn from, and support their customers in incredibly personal ways. More than 4,000 web and mobile businesses use Intercom to communicate with their customers. Praise for Intercom on Product Management "A valuable resource for anyone who wants to build products that customers will want to use time and time again." - Nir Eyal, author of Hooked: How to Build Habit-Forming Products. "Moves beyond the cliches and platitudes and provides astute, actionable advice on modern product management. I'd put it at the top of the reading list for anyone that has anything to do with building great products." - Dharmesh Shah, co-founder and CTO of HubSpot. "Really, really really good. Even better, easily accessible, so you can spend just a few minutes scanning through it and pick up something of value to use quickly." - John Koetsier, VP of Product at VentureBeat. "While books about design and programming abound, resources for the product manager are scant. Intercom has been filling that void with excellent blog posts and now a book of guidance, Intercom on Product Management." - Ryan Singer, Product Manager at Basecamp

    Topics covered range from the difference between deductive and inductive reasoning, to a discussion of how to highlight the structure of information.

    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.

    Kanban leverages visual management techniques to involve stakeholders and to facilitate understanding of how the work works. Through limiting the amount of work in process, and by focusing on finishing that work as soon as possible, kanban helps you to adjust demand to capacity, to reduce lead times and to create a driver for continuous improvement.Kanban in Action is a down-to-earth, no-frills, get-to-know-the-ropes introduction to kanban. It's based on the real-world experience and observations from two kanban coaches who have introduced this process to dozens of teams. In this book, you'll discover basic but powerful techniques on how to visualize and track work, how to construct a kanban board, how to visualize queues and bottlenecks, and much much more. You'll learn the principles of why kanban works as well as nitty-gritty details like how to use different color stickies to help you organize and track your work items.

    Startups face daunting challenges entering the technology ecosystem, including stiff competition, copycats, and ineffective marketing channels. Teams launching new products must consider the advantages of “the network effect,” where a product or service’s value increases as more users engage with it. Apple, Google, Microsoft, and other tech giants utilize network effects, and most tech products incorporate them, whether they’re messaging apps, workplace collaboration tools, or marketplaces. Network effects provide a path for fledgling products to break through, attracting new users through viral growth and word of mouth.Yet most entrepreneurs lack the vocabulary and context to describe them—much less understand the fundamental principles that drive the effect. What exactly are network effects? How do teams create and build them into their products? How do products compete in a market where every player has them? Andrew Chen draws on his experience and  on interviews with the CEOs and founding teams of LinkedIn, Twitch, Zoom, Dropbox, Tinder, Uber, Airbnb, Pinterest — to provide unique insights in answering these questions. Chen also provides practical frameworks and principles that can be applied across products and industries. The Cold Start Problem reveals what makes winning networks successful, why some startups fail to successfully scale, and most crucially, why products that create and compete using the network effect are vitally important today.

    In High Output Management, Andrew S. Grove, former chairman and CEO (and employee number three) of Intel, shares his perspective on how to build and run a company. Born of Grove’s experiences at one of America’s leading technology companies, this legendary management book is a Silicon Valley staple, equally appropriate for sales managers, accountants, consultants, and teachers, as well as CEOs and startup founders. Grove covers techniques for creating highly productive teams, demonstrating methods of motivation that lead to peak performance—throughout, High Output Management is a practical handbook for navigating real-life business scenarios and a powerful management manifesto with the ability to revolutionize the way we work.

    It happens because VCs are experts in financings and most entrepreneurs are not. Brad and Jason are out to fix that problem with Venture Deals. This book is long overdue and badly needed."—Fred Wilson, Managing Partner, Union Square Ventures"Feld and Mendelson pack a graduate-level course into this energetic and accessible book.?The authors' frank style and incisive insight make this a must-read for high-growth company entrepreneurs, early-stage investors, and graduate students.?Start here if you want to understand venture capital deal structure and strategies.?I enthusiastically recommend."—Brad Bernthal, CU Boulder, Associate Clinical Professor ofLaw, Technology Policy, Entrepreneurial Law"A must-read book for entrepreneurs.?Brad and Jason demystify the overly complex world of term sheets and M&A, cutting through the legalese and focusing on what really matters.?That's a good thing not just for entrepreneurs, but also for venture capitalists, angels, and lawyers.?Having an educated entrepreneur on the other side of the table means you spend your time negotiating the important issues and ultimately get to the right deal faster."—Greg Gottesman, Managing Director, Madrona Venture Group"Venture Deals is a must-read for any entrepreneur contemplating or currently leading a venture-backed company. Brad and Jason are highly respected investors who shoot straight from the hip and tell it like it is, bringing a level of transparency to a process that is rarely well understood. It's like having a venture capitalist as a best friend who is looking out for your best interests and happy to answer all of your questions."—Emily Mendell, Vice President of Communications,National Venture Capital Association"The adventure of starting and growing a company can be exhilarating or excruciating—or both. Feld and Mendelson have done a masterful job of shedding light on what can either become one of the most helpful or dreadful experiences for entrepreneurs—accepting venture capital into their firm. This book takes the lid off the black box and helps entrepreneurs understand the economics and control provisions of working with a venture partner."—Lesa Mitchell, Vice President, Advancing Innovation, Kauffman Foundation

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    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.