This book lays out the key skills and capabilities required to ensure that problems do not remain hidden in your organization. It explains how leaders can become effective problem finders, unearthing problems before they destroy an organization. The book explains how leaders can become an anthropologist, going out and observe how employees, customers, and suppliers actually behave. It then goes on to present how they can circumvent the gatekeepers, so they can go directly to the source to see and hear the raw data; hunt for patterns, including refining your individual and collective pattern recognition capability; "connect the dots" among issues that may initially seem unrelated, but in fact, have a great deal in common; give front-line employees training in a communication technique; encourage useful mistakes, including create a "Red Pencil Award"; and watch the game film, where leaders reflect systematically on their own organization's conduct and performance, as well as on the behavior and performance of competitors.

    As technology companies succeed and grow, so do their engineering departments. In your career, you’ll may suddenly get the opportunity to lead teams: to become a manager. But this is often uncharted territory. How can you decide whether this career move is right for you? And if you do, what do you need to learn to succeed? Where do you start? How do you know that you’re doing it right? What does “it” even mean? And isn’t management a dirty word? This book will share the secrets you need to know to manage engineers successfully.

    

    AWS has been the frontrunner in cloud computing products and services, and the AWS Certified Solutions Architect Official Study Guide for the Associate exam will get you fully prepared through expert content, and real-world knowledge, key exam essentials, chapter review questions, access to Sybex's interactive online learning environment, and much more. This official study guide, written by AWS experts, covers exam concepts, and provides key review on exam topics, including:Mapping Multi-Tier Architectures to AWS Services, such as web/app servers, firewalls, caches and load balancers Understanding managed RDBMS through AWS RDS (MySQL, Oracle, SQL Server, Postgres, Aurora) Understanding Loose Coupling and Stateless Systems Comparing Different Consistency Models in AWS Services Understanding how AWS CloudFront can make your application more cost efficient, faster and secure Implementing Route tables, Access Control Lists, Firewalls, NAT, and DNS Applying AWS Security Features along with traditional Information and Application Security Using Compute, Networking, Storage, and Database AWS services Architecting Large Scale Distributed Systems Understanding of Elasticity and Scalability Concepts Understanding of Network Technologies Relating to AWS Deploying and Managing Services with tools such as CloudFormation, OpsWorks and Elastic Beanstalk. Learn from the AWS subject-matter experts, review with proven study tools, and apply real-world scenarios. If you are looking to take the AWS Certified Solutions Architect Associate exam, this guide is what you need for comprehensive content and robust study tools that will help you gain the edge on exam day and throughout your career.

    The author incudes OOD, UML, Design Patterns, Agile and XP methods with a detailed description of a complete software design for reusable programs in C++ and Java. Using a practical, problem-solving approach, it shows how to develop an object-oriented application -- from the early stages of analysis, through the low-level design and into the implementation. Walks readers through the designer's thoughts -- showing the errors, blind alleys, and creative insights that occur throughout the software design process. KEY TOPICS: Covers: Statics and Dynamics; Principles of Class Design; Complexity Management; Principles of Package Design; Analysis and Design; Patterns and Paradigm Crossings. Explains the principles of OOD, one by one, and then demonstrates them with numerous examples, completely worked-through designs, and case studies. Covers traps, pitfalls, and work arounds in the application of C++ and OOD and then shows how Agile methods can be used. Discusses the methods for designing and developing big software in detail. Features a three-chapter, in-depth, single case study of a building security system. MARKET: For Software Engineers, Programmers, and Analysts who want to understand how to design object oriented software with state of the art methods.

    Why Simple Wins helps leaders and their teams move beyond the feelings of frustration and futility that come with so much unproductive work in today’s corporate world to create a corporate culture where valuable, essential, meaningful work is the norm. By learning how to eliminate redundancies, communicate with clarity, and make simplification a habit, individuals and companies can begin to recognize which activities are time-sucks and which create lasting value.Lisa Bodell’s simplification method has several unique principles:• Simplification is a skill that’s available to us all, yet very few leaders use it.• Simplification is the right thing to do—for our customers, for our company, and for each other. Operating with simplification as our core business model will make it easier to be respectful of each other’s time.• Simplification drives culture, and culture in turn drives employee engagement, customer relations, and overall productivity.This book is inspired by Bodell’s passion for eliminating barriers to innovation and productivity. In it, she explains why change and innovation are so hard to achieve—and it’s not what you might expect. The reality is this: we spend our days drowning in mundane tasks like meetings, emails, and reports. These are often self-created complexities that prevent us from getting to the meaningful work that truly matters.Using simple stories and techniques, Why Simple Wins shows that by using simplicity as an operating principle, we can eliminate the busy work that puts a chokehold on us every day, and instead spend time on the work that we value.

    This book looks at how to deal with the changing consumer and the social media as a marketing specialist.

    Though it may not seem this way for those who have been in the field for most of their careers, in the overall scheme of professions, software builders are relative "newbies." In the short history of the software field, a lot of facts have been identified, and a lot of fallacies promulgated. Those facts and fallacies are what this book is about. There's a problem with those facts-and, as you might imagine, those fallacies. Many of these fundamentally important facts are learned by a software engineer, but over the short lifespan of the software field, all too many of them have been forgotten. While reading Facts and Fallacies of Software Engineering , you may experience moments of "Oh, yes, I had forgotten that," alongside some "Is that really true?" thoughts. The author of this book doesn't shy away from controversy. In fact, each of the facts and fallacies is accompanied by a discussion of whatever controversy envelops it. You may find yourself agreeing with a lot of the facts and fallacies, yet emotionally disturbed by a few of them! Whether you agree or disagree, you will learn why the author has been called "the premier curmudgeon of software practice." These facts and fallacies are fundamental to the software building field-forget or neglect them at your peril!

    In this handy guidebook, the authors contend that you manage your boss for a very good reason: to do your best on the job—and thereby benefit not only yourself but also your supervisor and your entire company. Your boss depends on you for cooperation, reliability, and honesty. And you depend on him or her for links to the rest of the organization, for setting priorities, and for obtaining critical resources. By managing your boss—clarifying your own and your supervisor's strengths, weaknesses, goals, work styles, and needs—you cultivate a relationship based on mutual respect and understanding. The result? A healthy, productive bond that enables you both to excel. Gabarro and Kotter provide valuable guidelines for building this essential relationship—including strategies for determining how your boss prefers to process information and make decisions, tips for communicating mutual expectations, and tactics for negotiating priorities. Thought provoking and practical, Managing Your Boss enables you to lay the groundwork for one of the most crucial working relationships you'll have in your career.

    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.

    Chief of Staff: The Strategic Partner Who Will Revolutionize Your Organization presents the results of his research in a clear and practical way. To help business leaders explore the value that a chief of staff offers as a trusted advisor and “chief get-it-done officer,” Parris presents three “pivots” to consider: Organization dynamics Most commonly reported benefits of the role (for leaders, chiefs of staff, and organizations) Deliverables that chiefs of staff most commonly manage for leaders He also explores the history and current context for the role, provides guidelines for how to find and hire the right candidate, suggests ways to make the most of the first 90–100 days, and offers advice on how to develop the role over time.As several of the CEOs Parris interviewed point out, even if you never hire a chief of staff, the thought process that goes into considering the possibility can be a useful exercise in finding strengths and gaps in your current team or approach—and can help you lead more effectively.

    Many of the difficulties however, are not in the classroom... In The (Un)official Teacher's Manual, Omar Akbar offers direct, humorous and accessible advice on how to deal with the daily issues faced by a teacher- none of which involve teaching! Includes guidance on: lesson observations, emails, promotions, avoiding meaningless extra work, meetings, parents, maintaining a work-life balance, dealing with workplace bullying, and much more. While Omar pulls no punches on the reality of working in a school, a positive streak is maintained throughout. A must read for any teacher or potential teacher. - - - - - - - - - - - - - - Contents: Introduction: Why This Book Was Written 1. How to Get the Most from Observations, Learning Walks, and Book Scrutinies 2. The Don’ts of the School Email System 3. How to Get Promoted and Other Things to Consider 4. How and When to Say No and Yes 5. The Dos and Don’ts of Meetings 6. How to Get Parents on Your Side 7. Guidance for Trainee Teachers 8. Ensuring a Life-Work Balance 9. Bullying: the Problem and the Solution 10. How to Get the Teaching Job You Want 11. Maintaining Good Relationships 12. Why It’s All Worth It

    Extreme market volatility, pandemics, industry change, supply-chain disruption. The list of potential threats and strategic challenges seems to be growing exponentially. At the same time, the laborious processes used by many firms to develop a workable strategy often feel overly bureaucratic and behind the curve. There is no question that strategic decision-making has become more challenging and complex. In fact, many companies seem to have given up on strategy altogether. In Better, Simpler Strategy, Harvard Business School professor Felix Oberholzer-Gee provides executives with a simple tool to cut through technological complexity and market uncertainties. The Value Stick, based on proven economic mechanics, is an extraordinarily powerful tool that helps executives decide where to focus their attention and how to deepen their firm's competitive advantage. How does the Value Stick work? It provides a way of measuring two fundamental forces that lead to value creation and capture-the customer's willingness to pay and the employee's willingness to sell their services to the firm. For example, increasing product quality increases a customer's willingness to pay. And firms can redesign work processes or conditions or integrate other benefits (besides income) to lower employees' willingness to sell their services to firms and still retain them. With many examples across industries (based on Harvard Business School case studies), Oberholzer-Gee shows these value dynamics in action and explains how looking at and adjusting these measures using one tool, the Value Stick, enables firms to gauge and improve their strategies and operations. Based on the author's successful strategy course, Better, Simpler Strategy will become every business strategist's must-have guide for making better strategic decisions and gaining competitive advantage"--

    A real life case study with sample project documents and diagrams is used to more practically explain these international tools, techniques, and lean principles to a broad range of practitioners, including: - Business analysts, systems analysts, developers and project managers - Entrepreneurs, product owners and product managers - Consultants, UX designers and marketing specialists - C-suite executives, investors and managers of companies of all sizes.

    The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.