It’s the latest in a long line of “Are you cool enough to use me?” programming languages, APIs, and toolkits. In that sense, it lands squarely in the tradition of Rails, and Ajax, and Hadoop, and even to some degree iPhone programming and HTML5.Dig a little deeper, and you’ll hear that Node.js (or, as it’s more briefly called by many, simply “Node”) is a server-side solution for JavaScript, and in particular, for receiving and responding to HTTP requests. If that doesn’t completely boggle your mind, by the time the conversation heats up with discussion of ports, sockets, and threads, you’ll tend to glaze over. Is this really JavaScript? In fact, why in the world would anyone want to run JavaScript outside of a browser, let alone the server?The good news is that you’re hearing (and thinking) about the right things. Node really is concerned with network programming and server-side request/response processing. The bad news is that like Rails, Ajax, and Hadoop before it, there’s precious little clear information available. There will be, in time — as there now is for these other “cool” frameworks that have matured — but why wait for a book or tutorial when you might be able to use Node today, and dramatically improve the maintainability.

    Presentation Zen challenges the conventional wisdom of making "slide presentations" in today’s world and encourages you to think differently and more creatively about the preparation, design, and delivery of your presentations. Garr shares lessons and perspectives that draw upon practical advice from the fields of communication and business. Combining solid principles of design with the tenets of Zen simplicity, this book will help you along the path to simpler, more effective presentations.--back cover

    Thankfully, Green does—and in this incredibly helpful book, she tackles the tough discussions you may need to have during your career. You’ll learn what to say when• coworkers push their work on you—then take credit for it• you accidentally trash-talk someone in an email then hit “reply all”• you’re being micromanaged—or not being managed at all• you catch a colleague in a lie• your boss seems unhappy with your work• your cubemate’s loud speakerphone is making you homicidal• you got drunk at the holiday party

    Each idiom comes with a detailed description, example code showing the "wrong" way to do it, and code for the idiomatic, "Pythonic" alternative. *This version of the book is for Python 2.7.3+. There is also a Python 3.3+ version available.* "Writing Idiomatic Python" contains the most common and important Python idioms in a format that maximizes identification and understanding. Each idiom is presented as a recommendation to write some commonly used piece of code. It is followed by an explanation of why the idiom is important. It also contains two code samples: the "Harmful" way to write it and the "Idiomatic" way. * The "Harmful" way helps you identify the idiom in your own code. * The "Idiomatic" way shows you how to easily translate that code into idiomatic Python. This book is perfect for you: * If you're coming to Python from another programming language * If you're learning Python as a first programming language * If you're looking to increase the readability, maintainability, and correctness of your Python code What is "Idiomatic" Python? Every programming language has its own idioms. Programming language idioms are nothing more than the generally accepted way of writing a certain piece of code. Consistently writing idiomatic code has a number of important benefits: * Others can read and understand your code easily * Others can maintain and enhance your code with minimal effort * Your code will contain fewer bugs * Your code will teach others to write correct code without any effort on your part

    Every year, tens of thousands of people embark towards taking the exam via private study, Cisco Academy courses, or online training. The sad truth is most students quit along the way, and for those few who actually do attempt it, only 50% pass. All that time, effort, and money wasted! If there are so many manuals, CBT courses, lab simulators, exam engines, and study resources out there, then what goes wrong? This is the question Cisco trainer Paul Browning wanted to get to the bottom of. After interviewing thousands of students, he discovered that most people quit because they are simply overwhelmed with the sheer volume of material they need to digest and, of course, the large number of hands-on skills they need to be able to demonstrate in the exam. Add to that the day-to-day stresses of commuting to work, bringing up a family, and the distraction of everyday problems and challenges; it's no wonder people quit. This is where Cisco CCNA in 60 Days can help. Devised by two industry experts and countless Cisco students just like you, the 60-day programme breaks down every exam requirement into a daily study task. All you need to do is open the book at the relevant day (from 1 to 60), read the theory, and complete the lab. Every lesson is reviewed several times in the form of exam questions, review sessions, a handy exam cram guide, and, of course, hands-on labs for you to follow. You can choose to take the CCENT after the first 30 days and the ICND2 after the next 30 days, or you can take the CCNA after 60 days of study. Here is what is included in your study guide: 60 daily study tasks Full explanations of theory Real-world tips and advice Over 47 hands-on labs, plus 15 bonus CCENT and ICND2 labs CCENT and ICND2 cram guides Bonus VLSM guide Motivational goal-setting guide Downloadable videos Author Paul Browning is a former police officer who used his CCNA qualification to help him make a career change to IT. He worked for Cisco in the UK for a while, and then went on to start his own Cisco training company, which he ran for 8 years before moving into online Cisco training. He is the author of several Cisco study guides. He has also created the online Cisco certification training sites, including www.howtonetwork.net and www.in60days.net. Technical author Farai Tafa used to work in a shoe shop but decided he wanted more out of life, so he began to study for his Cisco exams. He is now a dual CCIE and one of the leading Cisco consultants in the US. He currently designs, installs, and troubleshoots networks for large companies.

    the only separation between mediocrity and excellence in one's pursuit.

    Recognized and respected throughout the world as the most influential leaders in the data warehousing industry, Ralph Kimball and the Kimball Group have written articles covering more than 250 topics that define the field of data warehousing. For the first time, the Kimball Group's incomparable advice, design tips, and best practices have been gathered in this remarkable collection of articles, which spans a decade of data warehousing innovation.Each group of articles is introduced with original commentaries that explain their role in the overall lifecycle methodology developed by the Kimball Group. These practical, hands-on articles are fully updated to reflect current practices and terminology and cover the complete lifecycle--including project planning, requirements gathering, dimensional modeling, ETL, and business intelligence and analytics.This easily referenced collection is nothing less than vital if you are involved with data warehousing or business intelligence in any capacity.

    Keep Playing. Keep Creating. In his previous books Steal Like an Artist and Show Your Work!, both New York Times bestsellers, Austin Kleon gave readers the keys to unlock their creativity and showed them how to become known. Now he offers his most inspiring work yet, with ten simple rules for how to stay creative, focused, and true to yourself—for life. The creative life is not a linear journey to a finish line, it’s a loop—so find a daily routine, because today is the only day that matters. Disconnect from the world to connect with yourself—sometimes you just have to switch into airplane mode. Keep Going celebrates getting outdoors and taking a walk (as director Ingmar Bergman told his daughter, ”The demons hate fresh air”). Pay attention, and especially pay attention to what you pay attention to. Worry less about getting things done, and more about the worth of what you’re doing. Instead of focusing on making your mark, work to leave things better than you found them.Keep Going and its timeless, practical, and ethical principles are for anyone trying to sustain a meaningful and productive life.

    

    The authors also include examples covering a variety of different integration technologies, such as JMS, MSMQ, TIBCO ActiveEnterprise, Microsoft BizTalk, SOAP, and XSL. A case study describing a bond trading system illustrates the patterns in practice, and the book offers a look at emerging standards, as well as insights into what the future of enterprise integration might hold. This book provides a consistent vocabulary and visual notation framework to describe large-scale integration solutions across many technologies. It also explores in detail the advantages and limitations of asynchronous messaging architectures. The authors present practical advice on designing code that connects an application to a messaging system, and provide extensive information to help you determine when to send a message, how to route it to the proper destination, and how to monitor the health of a messaging system. If you want to know how to manage, monitor, and maintain a messaging system once it is in use, get this book.

    He needed a way to keep track of software development over time – whatever he was thinking about or working on. He researched subjects he found interesting, then documented his research with a public blog post, which he could easily find and refer to later. Over time, increasing numbers of blog visitors found the posts helpful, relevant and interesting. Now, approximately 100,000 readers visit the blog per day and nearly as many comment and interact on the site.Effective Programming: More Than Writing Code is your one-stop shop for all things programming. Jeff writes with humor and understanding, allowing for both seasoned programmers and newbies to appreciate the depth of his research. From such posts as“The Programmer’s Bill of Rights” and “Why Cant Programmers... Program?” to “Working With the Chaos Monkey,” this book introduces the importance of writing responsible code, the logistics involved, and how people should view it more as a lifestyle than a career.

    It discusses cloud concepts and highlights various design patterns and best practices. This documentation is offered for free here as a Kindle book, or you can read it in PDF format at https://aws.amazon.com/whitepapers/.

    In this straightforward how-to, he offers down-to-earth guidance on crafting an effective and meaningful online platform.In Platform, you will learn how to:Extend your influence, monetize it, and build a sustainable career. Get noticed and start earning money in an increasingly noisy world.  Learn to amplify, update, polish, and organize your content for success.Platform goes behind the scenes into the world of social media success. You’ll discover what bestselling authors, public speakers, entrepreneurs, musicians, and other creatives are doing differently to gain contacts, connections, and followers and win customers in today’s crowded marketplace.With proven strategies, easy-to-replicate formulas, and practical tips, this book makes it easier, less expensive, and more possible than ever to stand out from the crowd and launch a business.

    A pocket-sized overview of roles, artifacts and the sprint cycle, adapted from the bestseller The Elements of Scrum by Chris Sims & Hillary Louise Johnson

    Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you're not quite Google's size...yet! Breakthrough Techniques You Can Actually Use Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests...thinking like real users...implementing exploratory, black box, white box, and acceptance testing...getting usable feedback...tracking issues...choosing and creating tools...testing "Docs & Mocks," interfaces, classes, modules, libraries, binaries, services, and infrastructure...reviewing code and refactoring...using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator-and make your whole organization more productive!