Ten times. You can't afford not to hire them. But if you haven't been reading Joel Spolsky's books or blog, you probably don't know how to find them and make them want to work for you.In this brief book, Joel reveals all his secrets--from his years at Microsoft, and as the co-founder of Fog Creek Software--for recruiting the best developers in the world.If you've ever wondered what you should be looking for in a resume, if you've ever struggled to decide whether to hire someone at the end of an interview, or if you're wondering why you can't find great programmers, stop everything and read this book.

    His blog has garnered a devoted following of millions of readers who have come to rely on him to help them run their businesses. A lifelong rap fan, Horowitz amplifies business lessons with lyrics from his favorite songs and tells it straight about everything from firing friends to poaching competitors, from cultivating and sustaining a CEO mentality to knowing the right time to cash in.His advice is grounded in anecdotes from his own hard-earned rise—from cofounding the early cloud service provider Loudcloud to building the phenomenally successful Andreessen Horowitz venture capital firm, both with fellow tech superstar Marc Andreessen (inventor of Mosaic, the Internet's first popular Web browser). This is no polished victory lap; he analyzes issues with no easy answers through his trials, includingdemoting (or firing) a loyal friend;whether you should incorporate titles and promotions, and how to handle them;if it's OK to hire people from your friend's company;how to manage your own psychology, while the whole company is relying on you;what to do when smart people are bad employees;why Andreessen Horowitz prefers founder CEOs, and how to become one;whether you should sell your company, and how to do it.Filled with Horowitz's trademark humor and straight talk, and drawing from his personal and often humbling experiences, The Hard Thing About Hard Things is invaluable for veteran entrepreneurs as well as those aspiring to their own new ventures.

    We put out fires. We deal with emergencies. We stay downstream, handling one problem after another, but we never make our way upstream to fix the systems that caused the problems ... [This book] probes the psychological forces that push us downstream--including 'problem blindness,' which can leave us oblivious to serious problems in our midst. And Heath introduces us to the thinkers who have overcome these obstacles and scored ... victories by switching to an upstream mindset.

    But many of those failures are preventable. The Lean Startup is a new approach being adopted across the globe, changing the way companies are built and new products are launched. Eric Ries defines a startup as an organization dedicated to creating something new under conditions of extreme uncertainty. This is just as true for one person in a garage or a group of seasoned professionals in a Fortune 500 boardroom. What they have in common is a mission to penetrate that fog of uncertainty to discover a successful path to a sustainable business.The Lean Startup approach fosters companies that are both more capital efficient and that leverage human creativity more effectively. Inspired by lessons from lean manufacturing, it relies on "validated learning," rapid scientific experimentation, as well as a number of counter-intuitive practices that shorten product development cycles, measure actual progress without resorting to vanity metrics, and learn what customers really want. It enables a company to shift directions with agility, altering plans inch by inch, minute by minute.Rather than wasting time creating elaborate business plans, The Lean Startup offers entrepreneurs - in companies of all sizes - a way to test their vision continuously, to adapt and adjust before it's too late. Ries provides a scientific approach to creating and managing successful startups in a age when companies need to innovate more than ever.

     With a foreword by Larry Page, and contributions from Bono and Bill Gates. Measure What Matters is about using Objectives and Key Results (OKRs), a revolutionary approach to goal-setting, to make tough choices in business. In 1999, legendary venture capitalist John Doerr invested nearly $12 million in a startup that had amazing technology, entrepreneurial energy and sky-high ambitions, but no real business plan. Doerr introduced the founders to OKRs and with them at the foundation of their management, the startup grew from forty employees to more than 70,000 with a market cap exceeding $600 billion. The startup was Google. Since then Doerr has introduced OKRs to more than fifty companies, helping tech giants and charities exceed all expectations. In the OKR model objectives define what we seek to achieve and key results are how those top­ priority goals will be attained. OKRs focus effort, foster coordination and enhance workplace satisfaction. They surface an organization's most important work as everyone's goals from entry-level to CEO are transparent to the entire institution. In Measure What Matters, Doerr shares a broad range of first-person, behind-the-scenes case studies, with narrators including Bono and Bill Gates, to demonstrate the focus, agility, and explosive growth that OKRs have spurred at so many great organizations. This book will show you how to collect timely, relevant data to track progress - to measure what matters. It will help any organization or team aim high, move fast, and excel.

    At many companies, being first with a concept and first to market are critical just to survive. In The Art of Innovation, Tom Kelley, general manager of the Silicon Valley based design firm IDEO, takes readers behind the scenes of this wildly imaginative and energized company to reveal the strategies and secrets it uses to turn out hit after hit.IDEO doesn't buy into the myth of the lone genius working away in isolation, waiting for great ideas to strike. Kelley believes everyone can be creative, and the goal at his firm is to tap into that wellspring of creativity in order to make innovation a way of life. How does it do that? IDEO fosters an atmosphere conducive to freely expressing ideas, breaking the rules, and freeing people to design their own work environments. IDEO's focus on teamwork generates countless breakthroughs, fueled by the constant give-and-take among people ready to share ideas and reap the benefits of the group process. IDEO has created an intense, quick-turnaround, brainstorm-and-build process dubbed "the Deep Dive."In entertaining anecdotes, Kelley illustrates some of his firm's own successes (and joyful failures), as well as pioneering efforts at other leading companies. The book reveals how teams research and immerse themselves in every possible aspect of a new product or service, examining it from the perspective of clients, consumers, and other critical audiences.Kelley takes the reader through the IDEO problem-solving method:> Carefully observing the behavior or "anthropology" of the people who will be using a product or service> Brainstorming with high-energy sessions focused on tangible results> Quickly prototyping ideas and designs at every step of the way> Cross-pollinating to find solutions from other fields> Taking risks, and failing your way to success> Building a "Greenhouse" for innovationIDEO has won more awards in the last ten years than any other firm of its kind, and a full half-hour Nightline presentation of its creative process received one of the show's highest ratings. The Art of Innovation will provide business leaders with the insights and tools they need to make their companies the leading-edge, top-rated stars of their industries.From the Hardcover edition.

    Visible Ops is comprised of four prescriptive and self-fueling steps that take an organization from any starting point to a continually improving process. MAKING ITIL ACTIONABLE Although the Information Technology Infrastructure Library (ITIL) provides a wealth of best practices, it lacks prescriptive guidance: What do you implement first, and how do you do it? Moreover, the ITIL books remain relatively expensive to distribute. Other information, publicly available from a variety of sources, is too general and vague to effectively aid organizations that need to start or enhance process improvement efforts. The Visible Ops booklet provides a prescriptive roadmap for organizations beginning or continuing their IT process improvement journey. WHY DO WE NEED VISIBLE OPS? The Visible Ops methodology was developed because there was not a satisfactory answer to the question: "I believe in the need for IT process improvement, but where do I start?" Since 2000, Gene Kim and Kevin Behr have met with hundreds of IT organizations and identified eight high-performing IT organizations with the highest service levels, best security, and best efficiencies. For years, they studied these high-performing organizations to figure out the secrets to their success. Visible Ops codifies how these organizations achieved their transformation from good to great, showing how interested organizations can replicate the key processes of these high-performing organizations in just four steps: 1. Stabilize Patient, Modify First Response - Almost 80% of outages are self-inflicted. The first step is to control risky changes and reduce MTTR by addressing how changes are managed and how problems are resolved. 2. Catch and Release, Find Fragile Artifacts - Often, infrastructure exists that cannot be repeatedly replicated. In this step, we inventory assets, configurations and services, to identify those with the lowest change success rates, highest MTTR and highest business downtime costs. 3. Establish Repeatable Build Library - The highest return on investment is implementing effective release management processes. This step creates repeatable builds for the most critical assets and services, to make it "cheaper to rebuild than to repair." 4. Enable Continuous Improvement - The previous steps have progressively built a closed-loop between the Release, Control and Resolution processes. This step implements metrics to allow continuous improvement of all of these process areas, to best ensure that business objectives are met.

    Cracking the PM Interview is a comprehensive book about landing a product management role in a startup or bigger tech company. Learn how the ambiguously-named "PM" (product manager / program manager) role varies across companies, what experience you need, how to make your existing experience translate, what a great PM resume and cover letter look like, and finally, how to master the interview: estimation questions, behavioral questions, case questions, product questions, technical questions, and the super important "pitch."

    Along the way, they introduce 22 thinking tools that can help you customize the right agile practices for any environment.Better, cheaper, faster software development. You can have all three-if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development.Iterating towards excellence: software development as an exercise in discovery Managing uncertainty: decide as late as possible by building change into the system. Compressing the value stream: rapid development, feedback, and improvement Empowering teams and individuals without compromising coordination Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability How to see the whole-even when your developers are scattered across multiple locations and contractors Simply put, Lean Software Development helps you refocus development on value, flow, and people-so you can achieve breakthrough quality, savings, speed, and business alignment.

    It then identifies and describes the advantages of this system, which needs less of everything including time, human effort, inventories, and investment to produce products with fewer defects in smaller volumes at lower costs for fragmenting markets. The Machine That Changed the World even gave the system its name: lean.In the decade since its launch in the fall of 1990, The Machine That Changed the World has sold more than 600,000 copies in 11 languages and has introduced a whole generation of managers and engineers to lean thinking. No lean library is complete without this groundbreaking book."The fundamentals of this system are applicable to every industry across the globea[and] will have a profound effect on human society. It will truly change the world." - New York TimesPaperback / 1990 / 323 pages

    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.

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    People can use economics and they can use statistics and numbers to get at the truth and there is a real appetite for doing so. This is such a BBC thing to say--there’s almost a public service mission to be fulfilled in educating people about economics. When I wrote The Undercover Economist, it was all about my pure enthusiasm for the subject; the book is full of stuff I wanted to say and that is always the thing with the books: they are always such fun to write. Do you think that people these days are generally more economically literate? People are now aware of economics for various reasons. There are the problems with the economy--there is always more interest in economics when it is all going wrong. Where is the border line in your new book between economics and sociology? I don’t draw a border line, and particularly not with the new book. The Undercover Economist was basically all the cool economics I could think of and The Logic of Life was me investigating a particular part of economics. All of the references in The Logic of Life were academic economics papers that I had related--and hopefully made more fun. This new book, Adapt, is very different. I have started by asking what is wrong with the world, what needs fixing, how does it work--and if economics can tell us something about that (which it can) then I have used it. And if economics is not the tool that you need--if you need to turn to sociology or engineering or biology or psychology--I have, in fact, turned to all of them in this book. If that’s what you need, then that’s where I have gone. So I have written this book in a different way: I started with a problem and tried to figure out how to solve it. What specific subjects do you tackle? To be a bit more specific, the book is about how difficult problems get solved and I look at quick change; the banking crisis; poverty; innovation, as I think there is an innovation slow-down; and the war in Iraq. Also, I look at both problems in business and in everyday life. Those are the big problems that I look at--and my conclusion is that these sorts of problems only ever get solved by trial and error, so when they are being solved, they are being solved through experimentation, which is often a bottom-up process. When they are not being solved it is because we are not willing to experiment, or to use trial and error. Do you think companies will change to be much more experimental, with more decisions placed in the hands of employees? I don’t think that is necessarily a trend, and the reason is that the market itself is highly experimental, so if your company isn’t experimental it may just happen to have a really great, successful idea--and that’s fine; if it doesn’t, it will go bankrupt. But that said, it is very interesting to look at the range of companies who have got very into experimentation--they range from the key-cutting chain Timpson’s to Google; you can’t get more different than those two firms, but actually the language is very similar; the recruitment policies are similar; the way the employees get paid is similar. The “strap line” of the book is that “Success always starts with failure.” You are a successful author… so what was the failure that set you up for success? I was working on a book before The Undercover Economist… it was going to be a sort of Adrian Mole/Bridget Jones’ Diary-styled fictional comedy, in which the hero was this economist and through the hilarious things that happened to him, all these economic principles would be explained--which is a great idea--but the trouble is that I am not actually funny. Another example would be my first job as a management consultant… and I was a terrible management consultant. I crashed out after a few months. Much better that, than to stick with the job for two or three years-- a lot of people say you have got to do that to “show your commitment.” Taking the job was a mistake--why would I need to show my commitment to a mistake? Better to realise you made a mistake, stop and do something else, which I did. That idea that “failure breeds success” is central to most entrepreneurs. Do you think we need more of it in the UK? I think that the real problem is not failure rates in business; the problem is failure rates in politics. We need a much higher failure rate in politics. What actually happens is politicians--and this is true of all political parties--have got some project and they’ll say, “Right, we are going to do this thing,” and it is quite likely that idea is a bad idea--because most ideas fail; the world is complicated and while I don’t have the numbers for this, most ideas are, as it turns out, not good ideas. But they never collect the data, or whatever it is they need to measure, to find out where their idea is failing. So they have this bad idea, roll this bad idea out and the bad idea sticks, costs the country hundreds, millions, or billions of pounds, and then the bad idea is finally reversed by the next party on purely ideological grounds and you never find out whether it really worked or not. So we have this very, very low willingness to collect the data that would be necessary to demonstrate failure, which is the bit we actually need. To give a brief example: Ken Livingstone, as Mayor of London, came along and introduced these long, bendy buses. Boris Johnson came along and said, “If you elect me, I am going to get rid of those big bendy buses and replace them with double-decker buses.” He was elected and he did it, so… which one of them is right? I don’t know. I mean, isn’t that crazy? I know democracy is a wonderful thing and we voted for Ken Livingstone and we voted for Boris Johnson, but it would be nice to actually have the data on passenger injury rates, how quickly people can get on and off these buses, whether disabled people are using these buses… the sort of basic evidence you would want to collect. Based on that, are you a supporter of David Cameron’s “Big Society”, which in a sense favours local experimentation over central government planning? Well, I have some sympathy for the idea of local experimentation, but what worries me is that we have to have some mechanism that is going to tell you what is working and what is not--and there is no proposal for that. Cameron’s Tories seem to have the view that ‘if it is local then it will work.’ In my book, I have all kinds of interesting case studies of situations where localism really would have worked incredibly well, as in, say, the US Army in Iraq. But I have also got examples of where localism did not work well at all--such as a corruption-fighting drive in Indonesia. Is the new book, Adapt, your movement away from economic rationalist to management guru? Are you going to cast your eye over bigger problems? The two changes in Adapt are that I have tried to start with the problem, rather than saying, “I have got a hammer--I’m going to look for a nail.” I started with a nail and said, “Ok, look, I need to get this hammered in.” So I have started with the problem and then looked anywhere for solutions. And the second thing is that I have tried to do is write with more of a narrative. This is not a Malcolm Gladwell book, but I really admire the way that people like Gladwell get quite complex ideas across because they get you interested in the story; that is something that I have tried to do more of here. I am not too worried about it, because I know that I am never going to turn into Malcolm Gladwell--I am always going to be Tim Harford--but it doesn’t hurt to nudge in a certain direction. On Amazon, we recommend new book ideas to people: “If you like Tim Harford you may like…”, but what does Tim Harford also like? I read a lot of books, mostly non-fiction and in two categories: people who I think write a lot better than I do, and people who think about economics more deeply than I do. In the first category I am reading people like Michael Lewis, Kathryn Schulz (I loved her first book, Being Wrong), Malcolm Gladwell and Alain de Botton. In the second category, I read lots of technical economics books, but I enjoy Steven Landsburg, Edward Glaeser (who has a book out now which looks good), Bill Easterly… I don’t necessarily agree with all of these people! When I am not reading non-fiction, I am reading comic books or 1980s fantasy authors like Jack Vance.

    Think about a company. Engineers build the product. Designers make sure it has a great user experience and looks good. Marketing makes sure customers know about the product. Sales get potential customers to open their wallets to buy the product. What more does a company need? What does a product manager do? Based upon Product School’s curriculum, which has helped thousands of students become great product managers, The Product Book answers that question. Filled with practical advice, best practices, and expert tips, this book is here to help you succeed! Product School offers product management classes taught by real-world product managers, working at renowned tech companies like Google, Facebook, Snapchat, Airbnb, LinkedIn, PayPal, Netflix and more. The classes are designed to fit into your work schedule, and the campuses are conveniently located in Silicon Valley, San Francisco, Los Angeles and New York.

    But today, success is increasingly dependent on how we interact with others. It turns out that at work, most people operate as either takers, matchers, or givers. Whereas takers strive to get as much as possible from others and matchers aim to trade evenly, givers are the rare breed of people who contribute to others without expecting anything in return. Using his own pioneering research as Wharton's youngest tenured professor, Grant shows that these styles have a surprising impact on success. Although some givers get exploited and burn out, the rest achieve extraordinary results across a wide range of industries. Combining cutting-edge evidence with captivating stories, this landmark book shows how one of America's best networkers developed his connections, why the creative genius behind one of the most popular shows in television history toiled for years in anonymity, how a basketball executive responsible for multiple draft busts transformed his franchise into a winner, and how we could have anticipated Enron's demise four years before the company collapsed - without ever looking at a single number. Praised by bestselling authors such as Dan Pink, Tony Hsieh, Dan Ariely, Susan Cain, Dan Gilbert, Gretchen Rubin, Bob Sutton, David Allen, Robert Cialdini, and Seth Godin-as well as senior leaders from Google, McKinsey, Merck, Estee Lauder, Nike, and NASA - Give and Take highlights what effective networking, collaboration, influence, negotiation, and leadership skills have in common. This landmark book opens up an approach to success that has the power to transform not just individuals and groups, but entire organizations and communities.