In this hands-on guide, author Ethan Brown teaches you the fundamentals through the development of a fictional application that exposes a public website and a RESTful API. You'll also learn web architecture best practices to help you build single-page, multi-page, and hybrid web apps with Express.Express strikes a balance between a robust framework and no framework at all, allowing you a free hand in your architecture choices. With this book, frontend and backend engineers familiar with JavaScript will discover new ways of looking at web development.Create webpage templating system for rendering dynamic dataDive into request and response objects, middleware, and URL routingSimulate a production environment for testing and developmentFocus on persistence with document databases, particularly MongoDBMake your resources available to other programs with RESTful APIsBuild secure apps with authentication, authorization, and HTTPSIntegrate with social media, geolocation, and other third-party servicesImplement a plan for launching and maintaining your appLearn critical debugging skillsThis book covers Express 4.0.

    Inspired by the work of Peter Drucker and Jim Collins, Justin Menkes set out to isolate the qualities that make for the 'right' people. Drawing on his background in psychology and bolstered by interviews with accomplished CEOs, Menkes paints the portrait of the ideal executive.In a sense, Menkes's work reveals an executive IQ—the cognitive skills necessary in order to excel in senior management positions. Star leaders readily differentiate primary priorities from secondary concerns; they identify flawed assumptions; they anticipate the different needs of various stakeholders and how they might conflict with one another; and they recognise the underlying agendas of individuals in complex exchanges.Weaving together research, interviews and the results of his own proprietary testing, Menkes exposes one of the great fallacies of corporate life, that hiring and promotion are conducted on a systematic or scientific basis that allows the most accomplished to rise to their levels of optimal responsibility.Finally, Menkes is a passionate advocate for finding and employing the most talented people, especially those who may have been held back by external assumptions.

    Their rules of thumb and coaching advice are great blueprints for new and experienced software engineering managers alike." --Tom Conrad, CTO, Pandora "I wish I'd had this material available years ago. I see lots and lots of 'meat' in here that I'll use over and over again as I try to become a better manager. The writing style is right on, and I love the personal anecdotes." --Steve Johnson, VP, Custom Solutions, DigitalFish All too often, software development is deemed unmanageable. The news is filled with stories of projects that have run catastrophically over schedule and budget. Although adding some formal discipline to the development process has improved the situation, it has by no means solved the problem. How can it be, with so much time and money spent to get software development under control, that it remains so unmanageable? In Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams , Mickey W. Mantle and Ron Lichty answer that persistent question with a simple observation: You first must make programmers and software teams manageable. That is, you need to begin by understanding your people--how to hire them, motivate them, and lead them to develop and deliver great products. Drawing on their combined seventy years of software development and management experience, and highlighting the insights and wisdom of other successful managers, Mantle and Lichty provide the guidance you need to manage people and teams in order to deliver software successfully. Whether you are new to software management, or have already been working in that role, you will appreciate the real-world knowledge and practical tools packed into this guide.

    This summary explores the fundamental causes of organizational politics and team failure.

    We need a fresh understanding of the meaning of success. What do Condoleezza Rice, Joe Torre, Bill Gates, Goldie Hawn, Mary Hart, Garry Kasparov, and Jack Welch have in common? All have talked at length with Maria Bartiromo about business, the world and their surprising, inspiring and uncommon ideas about the meaning of success. Their stories, those of an extraordinary range of other people from all walks of life, and Maria Bartiromo’s personal insights are the foundation of The 10 Laws of Enduring Success. It is the guide for the extraordinary times we are living through.  During bullish, optimistic periods, people seem to ride an upward wave with ease and confidence. The tangible evidence is right there for all to see--in their jobs, bank accounts, homes, families, and the admiration of their peers. But it is a fact of life that success, once earned, is not necessarily there to stay. If ever there was a cautionary tale about the fleeting nature of success, it is the events of recent years.     But a funny thing happened. Faced with gut-wrenching realities, many people have started to re-evaluate the meaning of success in less superficial and impermanent ways. They're asking themselves hard questions that havelong been ignored:  about what's really important to them, and where the bedrock of their personal achievement lies.     As Maria Bartiromo watched the financial drama from her front-row seat at the New York Stock Exchange, she began to re-assess the meaning of success--not just as one-off achievements, but as a durable, lifelong pursuit. Is there, she wondered, a definition of success that you can have permanently--in spite of the turmoil in your life, your job, or your bank account? This question is more important than ever, given the unpredictability of the current economy. --What are the intangibles that can't be measured or counted? --What are the qualities that aren't reflected in your title or on your business card?--And more practically, how can you remain successful even when the worst things happen to you? --Is it possible to build success from failure? It's lonely at the bottom of the heap, when your BlackBerry stops buzzing, and the world moves on without you.  Everyone wants to be close to success, and to have success. But what is success? How do you get it, and how do you keep it? As Maria interviewed some of the most successful people in the world, she felt the need to answer these questions: what makes these success stories tick? How did they achieve such leadership and power and how can one hold onto it, once you get it. What are the barriers to success and what is the bedrock to enduring success? From the Hardcover edition.

    It gives you the tools to address a wider range of important VSM issues than any other such book, including the psychology of change, leadership, creating teams, building consensus, and charter development.Karen Martin is principal consultant for Karen Martin & Associates, LLC, instructor for the University of California, San Diego's Lean Enterprise program, and industry advisor to the University of San Diego's Industrial and Systems Engineering program. Mike Osterling provides support and leadership to manufacturing and non-manufacturing organizations on their Lean Transformation Journey. In a continuous improvement leadership role for six years, Mike played a key role in Square D Company's lean transformation in the 1990s.

    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

    His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant—or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a colleague from student days—Jonah—to help him break out of conventional ways of thinking to see what needs to be done.The story of Alex's fight to save his plant is more than compulsive reading. It contains a serious message for all managers in industry and explains the ideas which underline the Theory of Constraints (TOC) developed by Eli Goldratt.

    But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.

    

    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.

    But if one per year is good, how about Seven Languages in Seven Weeks? In this book you'll get a hands-on tour of Clojure, Haskell, Io, Prolog, Scala, Erlang, and Ruby. Whether or not your favorite language is on that list, you'll broaden your perspective of programming by examining these languages side-by-side. You'll learn something new from each, and best of all, you'll learn how to learn a language quickly. Ruby, Io, Prolog, Scala, Erlang, Clojure, Haskell. With Seven Languages in Seven Weeks, by Bruce A. Tate, you'll go beyond the syntax-and beyond the 20-minute tutorial you'll find someplace online. This book has an audacious goal: to present a meaningful exploration of seven languages within a single book. Rather than serve as a complete reference or installation guide, Seven Languages hits what's essential and unique about each language. Moreover, this approach will help teach you how to grok new languages. For each language, you'll solve a nontrivial problem, using techniques that show off the language's most important features. As the book proceeds, you'll discover the strengths and weaknesses of the languages, while dissecting the process of learning languages quickly--for example, finding the typing and programming models, decision structures, and how you interact with them. Among this group of seven, you'll explore the most critical programming models of our time. Learn the dynamic typing that makes Ruby, Python, and Perl so flexible and compelling. Understand the underlying prototype system that's at the heart of JavaScript. See how pattern matching in Prolog shaped the development of Scala and Erlang. Discover how pure functional programming in Haskell is different from the Lisp family of languages, including Clojure. Explore the concurrency techniques that are quickly becoming the backbone of a new generation of Internet applications. Find out how to use Erlang's let-it-crash philosophy for building fault-tolerant systems. Understand the actor model that drives concurrency design in Io and Scala. Learn how Clojure uses versioning to solve some of the most difficult concurrency problems. It's all here, all in one place. Use the concepts from one language to find creative solutions in another-or discover a language that may become one of your favorites.

    With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners.Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time.You'll learn:Fundamental differences between software engineering and programmingHow an organization effectively manages a living codebase and efficiently responds to inevitable changeWhy culture (and recognizing it) is important, and how processes, practices, and tools come into play

    Emphasizes possible, realistic and "best practice" approaches for managers, technical leads and self-managed teams. The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classic mistakes, within the context of software-development fundamentals and risk management. Dissects the core issues of rapid development, lifecycle planning, estimation and scheduling. Contains very good and practical discussions of customer-oriented development, motivation and teamwork. Explains such fundamental requirements as team structure, feature-set control (the dreaded feature creep in every project), availability and use of productivity tools and project recovery options. Relevant case studies are analyzed and discussed within the context of specific software development problems. Over 200 pages in this publication are devoted to a summary of best practices, everything from the daily build and smoke test, through prototyping, model selection, measurement, reuse, and the top-10 risks list. This publication is definitely recommended and will become a classic in the field, just as the author's prior publication, "Code Complete" already is.

    Now you can extend it for personal, corporate and enterprise use with advanced plugins and this professional development guide. Learn how to create plugins using the WordPress plugin API: utilize hooks, store custom settings, craft translation files, secure your plugins, set custom user roles, integrate widgets, work with JavaScript and AJAX, create custom post types. You'll find a practical, solutions-based approach, lots of helpful examples, and plenty of code you can incorporate!Shows you how to develop advanced plugins for the most popular CMS platform today, WordPress Covers plugin fundamentals, how to create and customize hooks, internationalizing your site with translation files, securing plugins, how to create customer users, and ways to lock down specific areas for use in corporate settings Delves into advanced topics, including creating widgets and metaboxes, debugging, using JavaScript and AJAX, Cron integration, custom post types, short codes, multi site functions, and working with the HTTP API Includes pointers on how to debug, profile and optimize your code, and how to market your custom plugin Learn advanced plugin techniques and extend WordPress into the corporate environment.