His goal was to help shift the focus in Japanese education from memorization to critical thinking, by adapting some of the techniques he had learned as an elite McKinsey consultant.He was amazed to discover that adults were hungry for his fun and easy guide to problem solving and decision making. The book became a surprise Japanese bestseller, with more than 370,000 in print after six months. Now American businesspeople can also use it to master some powerful skills.Watanabe uses sample scenarios to illustrate his techniques, which include logic trees and matrixes. A rock band figures out how to drive up concert attendance. An aspiring animator budgets for a new computer purchase. Students decide which high school they will attend.Illustrated with diagrams and quirky drawings, the book is simple enough for a middleschooler to understand but sophisticated enough for business leaders to apply to their most challenging problems.

    Through consecutive “hook cycles,” these products reach their ultimate goal of bringing users back again and again without depending on costly advertising or aggressive messaging.Hooked is based on Eyal’s years of research, consulting, and practical experience. He wrote the book he wished had been available to him as a start-up founder—not abstract theory, but a how-to guide for building better products. Hooked is written for product managers, designers, marketers, start-up founders, and anyone who seeks to understand how products influence our behavior.Eyal provides readers with:• Practical insights to create user habits that stick.• Actionable steps for building products people love.• Fascinating examples from the iPhone to Twitter, Pinterest to the Bible App, and many other habit-forming products.

    This classic book uncovers what interviews are really like at America's top software and computer companies and provides you with the tools to succeed in any situation. The authors take you step-by-step through new problems and complex brainteasers they were asked during recent technical interviews. 50 interview scenarios are presented along with in-depth analysis of the possible solutions. The problem-solving process is clearly illustrated so you'll be able to easily apply what you've learned during crunch time. You'll also find expert tips on what questions to ask, how to approach a problem, and how to recover if you become stuck. All of this will help you ace the interview and get the job you want.What you will learn from this bookTips for effectively completing the job application Ways to prepare for the entire programming interview process How to find the kind of programming job that fits you best Strategies for choosing a solution and what your approach says about you How to improve your interviewing skills so that you can respond to any question or situation Techniques for solving knowledge-based problems, logic puzzles, and programming problems Who this book is for This book is for programmers and developers applying for jobs in the software industry or in IT departments of major corporations.Wrox Beginning guides are crafted to make learning programming languages and technologies easier than you think, providing a structured, tutorial format that will guide you through all the techniques involved.

    But what if you could have your computer do them for you?In "Automate the Boring Stuff with Python," you'll learn how to use Python to write programs that do in minutes what would take you hours to do by hand no prior programming experience required. Once you've mastered the basics of programming, you'll create Python programs that effortlessly perform useful and impressive feats of automation to: Search for text in a file or across multiple filesCreate, update, move, and rename files and foldersSearch the Web and download online contentUpdate and format data in Excel spreadsheets of any sizeSplit, merge, watermark, and encrypt PDFsSend reminder emails and text notificationsFill out online formsStep-by-step instructions walk you through each program, and practice projects at the end of each chapter challenge you to improve those programs and use your newfound skills to automate similar tasks.Don't spend your time doing work a well-trained monkey could do. Even if you've never written a line of code, you can make your computer do the grunt work. Learn how in "Automate the Boring Stuff with Python.""

    The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver!This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking.Who is this book for?The primary audience of this book are senior people involved in building software products or delivering software projects, from both business and delivery sides. This includes business sponsors and those whose responsibilities include product ownership, project oversight or portfolio management, architecture, business analysis, quality improvement and assurance and delivery. - Business people assigned to software projects will learn how to communicate their ideas better.- Senior product or project sponsors will learn how to communicate their assumptions more effectively to delivery teams, how to engage delivery teams to make better strategic decisions, and how to manage their project portfolio more effectively.- Delivery teams that are already working under the umbrella of agile or lean delivery methods, and more recently lean startup ideas, will learn how to better focus deliverables and engage business sponsors and users.- Delivery teams moving to agile or lean delivery methods will get ideas on how to address some common issues with scaling these practices, such as creating a big picture view, splitting work into small chunks that still have business value and reporting progress more meaningfully.About the authorGojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010. To get in touch, write to gojko@neuri.co.uk or visit http://gojko.net.

    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

    Each chapter is relatively self-contained and can be used as a unit of study. The algorithms are described in English and in a pseudocode designed to be readable by anyone who has done a little programming. The explanations have been kept elementary without sacrificing depth of coverage or mathematical rigor.

    Author Patrick Lencioni--noted screenplay writer and sought-after executive coach -- deftly tells the tale of a young CEO who, facing his first annual board review, knows he is failing, but doesn't know why. "This book provides extraordinary insight into the pitfalls that leaders face when they lose sight of the true measure of success: results. This model is required reading for my staff." --Eric Schmidt, chairman of the board and CEO, NovellAny executive can learn how to:recognize the mistakes that leaders can make avoid errors before they occur and much more! Refreshingly original and utterly compelling, the story of this executive (written to be read in one sitting) will be enjoyed, remembered, and reread for years to come. It serves a timeless and potent reminder that success as a leader can come down to practicing a few simple behaviors--behaviors that are painfully difficult for each of us to master."Lencioni delivers a provocative message: CEOs mainly have themselves to blame when things go wrong. If you're a CEO (or any manager for that matter), do you have the courage to face the blame? Doing so could change your future-for the better." --Dr. Jerry Porras, coauthor, Built to Last; professor, Stanford School of BusinessYou won't find any dry management rhetoric in this razor-sharp novelette. Apply these riveting lessons in leadership with the self-assessment at the end of the book. It will change your career!

    We like to think that we are in control of the future of "artificial" intelligence. The reality, though, is that we -- the everyday people whose data powers AI -- aren't actually in control of anything. When, for example, we speak with Alexa, we contribute that data to a system we can't see and have no input into -- one largely free from regulation or oversight. The big nine corporations -- Amazon, Google, Facebook, Tencent, Baidu, Alibaba, Microsoft, IBM and Apple--are the new gods of AI and are short-changing our futures to reap immediate financial gain. In this book, Amy Webb reveals the pervasive, invisible ways in which the foundations of AI -- the people working on the system, their motivations, the technology itself -- is broken. Within our lifetimes, AI will, by design, begin to behave unpredictably, thinking and acting in ways which defy human logic. The big nine corporations may be inadvertently building and enabling vast arrays of intelligent systems that don't share our motivations, desires, or hopes for the future of humanity. Much more than a passionate, human-centered call-to-arms, this book delivers a strategy for changing course, and provides a path for liberating us from algorithmic decision-makers and powerful corporations.

    You might think the problem is your brain. It seems to have a mind of its own, a mind that doesn't always want to take in the dry, technical stuff you're forced to study. The fact is your brain craves novelty. It's constantly searching, scanning, waiting for something unusual to happen. After all, that's the way it was built to help you stay alive. It takes all the routine, ordinary, dull stuff and filters it to the background so it won't interfere with your brain's real work--recording things that matter. How does your brain know what matters? It's like the creators of the Head First approach say, suppose you're out for a hike and a tiger jumps in front of you, what happens in your brain? Neurons fire. Emotions crank up. Chemicals surge. That's how your brain knows.And that's how your brain will learn Java. Head First Java combines puzzles, strong visuals, mysteries, and soul-searching interviews with famous Java objects to engage you in many different ways. It's fast, it's fun, and it's effective. And, despite its playful appearance, Head First Java is serious stuff: a complete introduction to object-oriented programming and Java. You'll learn everything from the fundamentals to advanced topics, including threads, network sockets, and distributed programming with RMI. And the new. second edition focuses on Java 5.0, the latest version of the Java language and development platform. Because Java 5.0 is a major update to the platform, with deep, code-level changes, even more careful study and implementation is required. So learning the Head First way is more important than ever. If you've read a Head First book, you know what to expect--a visually rich format designed for the way your brain works. If you haven't, you're in for a treat. You'll see why people say it's unlike any other Java book you've ever read.By exploiting how your brain works, Head First Java compresses the time it takes to learn and retain--complex information. Its unique approach not only shows you what you need to know about Java syntax, it teaches you to think like a Java programmer. If you want to be bored, buy some other book. But if you want to understand Java, this book's for you.

    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.

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

    Their days are defined by a relentless barrage of incoming messages and back-and-forth digital conversations--a state of constant, anxious chatter in which nobody can disconnect, and so nobody has the cognitive bandwidth to perform substantive work. There was a time when tools like email felt cutting edge, but a thorough review of current evidence reveals that the hyperactive hive mind workflow they helped create has become a productivity disaster, reducing profitability and perhaps even slowing overall economic growth. Equally worrisome, it makes us miserable. Humans are simply not wired for constant digital communication.We have become so used to an inbox-driven workday that it's hard to imagine alternatives. But they do exist. Drawing on years of investigative reporting, author and computer science professor Cal Newport makes the case that our current approach to work is broken, then lays out a series of principles and concrete instructions for fixing it. In A World without Email, he argues for a workplace in which clear processes--not haphazard messaging--define how tasks are identified, assigned and reviewed. Each person works on fewer things (but does them better), and aggressive investment in support reduces the ever-increasing burden of administrative tasks. Above all else, important communication is streamlined, and inboxes and chat channels are no longer central to how work unfolds.The knowledge sector's evolution beyond the hyperactive hive mind is inevitable. The question is not whether a world without email is coming (it is), but whether you'll be ahead of this trend. If you're a CEO seeking a competitive edge, an entrepreneur convinced your productivity could be higher, or an employee exhausted by your inbox, A World Without Email will convince you that the time has come for bold changes, and will walk you through exactly how to make them happen.

    In eight chapters, it provides the most thorough coverage of TCP available. It also covers the newest TCP/IP features, including multicasting, path MTU discovery and long fat pipes. The author describes various protocols, including ARP, ICMP and UDP. He utilizes network diagnostic tools to actually show the protocols in action. He also explains how to avoid silly window syndrome (SWS) by using numerous helpful diagrams. This book gives you a broader understanding of concepts like connection establishment, timeout, retransmission and fragmentation. It is ideal for anyone wanting to gain a greater understanding of how the TCP/IP protocols work.

    To grow professionally, you also need soft skills and effective learning techniques. Honing those skills is what this book is all about. Authors Dave Hoover and Adewale Oshineye have cataloged dozens of behavior patterns to help you perfect essential aspects of your craft. Compiled from years of research, many interviews, and feedback from O'Reilly's online forum, these patterns address difficult situations that programmers, administrators, and DBAs face every day. And it's not just about financial success. Apprenticeship Patterns also approaches software development as a means to personal fulfillment. Discover how this book can help you make the best of both your life and your career. Solutions to some common obstacles that this book explores in-depth include:Burned out at work? "Nurture Your Passion" by finding a pet project to rediscover the joy of problem solving.Feeling overwhelmed by new information? Re-explore familiar territory by building something you've built before, then use "Retreat into Competence" to move forward again.Stuck in your learning? Seek a team of experienced and talented developers with whom you can "Be the Worst" for a while. "Brilliant stuff! Reading this book was like being in a time machine that pulled me back to those key learning moments in my career as a professional software developer and, instead of having to learn best practices the hard way, I had a guru sitting on my shoulder guiding me every step towards master craftsmanship. I'll certainly be recommending this book to clients. I wish I had this book 14 years ago!" -Russ Miles, CEO, OpenCredo