Advertisement
| director of engineering vs vp of engineering: Become an Effective Software Engineering Manager James Stanier, 2020-06-09 Software startups make global headlines every day. 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. Going from engineer to manager doesn't have to be intimidating. Engineers can be managers, and fantastic ones at that. Cast aside the rhetoric and focus on practical, hands-on techniques and tools. You'll become an effective and supportive team leader that your staff will look up to. Start with your transition to being a manager and see how that compares to being an engineer. Learn how to better organize information, feel productive, and delegate, but not micromanage. Discover how to manage your own boss, hire and fire, do performance and salary reviews, and build a great team. You'll also learn the psychology: how to ship while keeping staff happy, coach and mentor, deal with deadline pressure, handle sensitive information, and navigate workplace politics. Consider your whole department. How can you work with other teams to ensure best practice? How do you help form guilds and committees and communicate effectively? How can you create career tracks for individual contributors and managers? How can you support flexible and remote working? How can you improve diversity in the industry through your own actions? This book will show you how. Great managers can make the world a better place. Join us. |
| director of engineering vs vp of engineering: The First 90 Days, Updated and Expanded Michael D. Watkins, 2013-04-23 The world’s most trusted guide for leaders in transition Transitions are a critical time for leaders. In fact, most agree that moving into a new role is the biggest challenge a manager will face. While transitions offer a chance to start fresh and make needed changes in an organization, they also place leaders in a position of acute vulnerability. Missteps made during the crucial first three months in a new role can jeopardize or even derail your success. In this updated and expanded version of the international bestseller The First 90 Days, Michael D. Watkins offers proven strategies for conquering the challenges of transitions—no matter where you are in your career. Watkins, a noted expert on leadership transitions and adviser to senior leaders in all types of organizations, also addresses today’s increasingly demanding professional landscape, where managers face not only more frequent transitions but also steeper expectations once they step into their new jobs. By walking you through every aspect of the transition scenario, Watkins identifies the most common pitfalls new leaders encounter and provides the tools and strategies you need to avoid them. You’ll learn how to secure critical early wins, an important first step in establishing yourself in your new role. Each chapter also includes checklists, practical tools, and self-assessments to help you assimilate key lessons and apply them to your own situation. Whether you’re starting a new job, being promoted from within, embarking on an overseas assignment, or being tapped as CEO, how you manage your transition will determine whether you succeed or fail. Use this book as your trusted guide. |
| director of engineering vs vp of engineering: Software Engineering at Google Titus Winters, Tom Manshreck, Hyrum Wright, 2020-02-28 Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the worldâ??s leading practitioners construct and maintain software. This book covers Googleâ??s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. Youâ??ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions |
| director of engineering vs vp of engineering: An Elegant Puzzle Will Larson, 2019-05-20 A human-centric guide to solving complex problems in engineering management, from sizing teams to handling technical debt. There’s a saying that people don’t leave companies, they leave managers. Management is a key part of any organization, yet the discipline is often self-taught and unstructured. Getting to the good solutions for complex management challenges can make the difference between fulfillment and frustration for teams—and, ultimately, between the success and failure of companies. Will Larson’s An Elegant Puzzle focuses on the particular challenges of engineering management—from sizing teams to handling technical debt to performing succession planning—and provides a path to the good solutions. Drawing from his experience at Digg, Uber, and Stripe, Larson has developed a thoughtful approach to engineering management for leaders of all levels at companies of all sizes. An Elegant Puzzle balances structured principles and human-centric thinking to help any leader create more effective and rewarding organizations for engineers to thrive in. |
| director of engineering vs vp of engineering: Staff Engineer Will Larson, 2021-02-28 At most technology companies, you'll reach Senior Software Engineer, the career level for software engineers, in five to eight years. At that career level, you'll no longer be required to work towards the next pro? motion, and being promoted beyond it is exceptional rather than ex? pected. At that point your career path will branch, and you have to decide between remaining at your current level, continuing down the path of technical excellence to become a Staff Engineer, or switching into engineering management. Of course, the specific titles vary by company, and you can replace Senior Engineer and Staff Engineer with whatever titles your company prefers.Over the past few years we've seen a flurry of books unlocking the en? gineering management career path, like Camille Fournier's The Man? ager's Path, Julie Zhuo's The Making of a Manager, Lara Hogan's Re? silient Management and my own, An Elegant Puzzle. The manage? ment career isn't an easy one, but increasingly there are maps avail? able for navigating it.On the other hand, the transition into Staff Engineer, and its further evolutions like Principal and Distinguished Engineer, remains chal? lenging and undocumented. What are the skills you need to develop to reach Staff Engineer? Are technical abilities alone sufficient to reach and succeed in that role? How do most folks reach this role? What is your manager's role in helping you along the way? Will you enjoy being a Staff Engineer or you will toil for years to achieve a role that doesn't suit you?Staff Engineer: Leadership beyond the management track is a pragmatic look at attaining and operate in these Staff-plus roles. |
| director of engineering vs vp of engineering: The Manager's Path Camille Fournier, 2017-03-13 Managing people is difficult wherever you work. But in the tech industry, where management is also a technical discipline, the learning curve can be brutal—especially when there are few tools, texts, and frameworks to help you. In this practical guide, author Camille Fournier (tech lead turned CTO) takes you through each stage in the journey from engineer to technical manager. From mentoring interns to working with senior staff, you’ll get actionable advice for approaching various obstacles in your path. This book is ideal whether you’re a new manager, a mentor, or a more experienced leader looking for fresh advice. Pick up this book and learn how to become a better manager and leader in your organization. Begin by exploring what you expect from a manager Understand what it takes to be a good mentor, and a good tech lead Learn how to manage individual members while remaining focused on the entire team Understand how to manage yourself and avoid common pitfalls that challenge many leaders Manage multiple teams and learn how to manage managers Learn how to build and bootstrap a unifying culture in teams |
| director of engineering vs vp of engineering: Site Reliability Engineering Niall Richard Murphy, Betsy Beyer, Chris Jones, Jennifer Petoff, 2016-03-23 The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. 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 practices Principles—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 systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use |
| director of engineering vs vp of engineering: Startup Engineering Management, 2nd Edition , 2014-07-23 If you're currently an engineer and have been offered a management job at a startup, this book is for you! If you're an engineer wondering what your manager is supposed to do for you, this book is for you as well! Drawing from the author's experience as an engineer and manager, this book explains: When to consider doing management work. How to put together a team. What to consider when interacting with engineers. How to hire top engineers for your startup. How to pick engineering leaders. How to define processes and a process cookbook. When you don't need a process. How to report to your managers. How compensation systems and promotion systems work, and when they fail. Foreword by Harper Reed. This kind of books are nowhere to be found...as an engineer probing in the dark for what's next I have looked very hard for career guidance for the past few years, and yours are the only books to give enlightenment. --- Cindy Zhou Whether experienced or aspiring, this book will be a great manual to help understand and be successful at this mysterious craft. --- Harper Reed, from the Foreword. |
| director of engineering vs vp of engineering: Building Great Software Engineering Teams Joshua Tyler, 2015-07-03 WINNER of Computing Reviews 20th Annual Best Review in the category Management “Tyler’s book is concise, reasonable, and full of interesting practices, including some curious ones you might consider adopting yourself if you become a software engineering manager.” —Fernando Berzal, CR, 10/23/2015 “Josh Tyler crafts a concise, no-nonsense, intensely focused guide for building the workhouse of Silicon Valley—the high-functioning software team.” —Gordon Rios, Summer Book Recommendations from the Smartest People We Know—Summer 2016 Building Great Software Engineering Teams provides engineering leaders, startup founders, and CTOs concrete, industry-proven guidance and techniques for recruiting, hiring, and managing software engineers in a fast-paced, competitive environment. With so much at stake, the challenge of scaling up a team can be intimidating. Engineering leaders in growing companies of all sizes need to know how to find great candidates, create effective interviewing and hiring processes, bring out the best in people and their work, provide meaningful career development, learn to spot warning signs in their team, and manage their people for long-term success. Author Josh Tyler has spent nearly a decade building teams in high-growth startups, experimenting with every aspect of the task to see what works best. He draws on this experience to outline specific, detailed solutions augmented by instructive stories from his own experience. In this book you’ll learn how to build your team, starting with your first hire and continuing through the stages of development as you manage your team for growth and success. Organized to cover each step of the process in the order you’ll likely face them, and highlighted by stories of success and failure, it provides an easy-to-understand recipe for creating your high-powered engineering team. |
| director of engineering vs vp of engineering: Experimentation in Software Engineering Claes Wohlin, Per Runeson, Martin Höst, Magnus C. Ohlsson, Björn Regnell, Anders Wesslén, 2012-06-16 Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors’ book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a “cookbook” when evaluating new methods or techniques before implementing them in their organization. |
| director of engineering vs vp of engineering: The CTO Handbook Mark D. Minevich, 2004 Why spend countless hours searching for relevant thought leadership articles, specific pieces of statistical data, and navigable reference information, when one resource provides it all? In The CTO Handbook, former CTO of IBM Next Generation Group Mark Minevich, guides readers through what need not be a daunting world of IT management addressing such critical issues as: - Fundamentals, Importance of & Background on the CTO/CIO Profession - Strategic Roles & Responsibilities - Current Economic Climate & Changes - The New Generation & Digital Revolution - Outsourcing & Offshoring Implications for the US IT Market - New Market Economy- Creating Value for Customers - CTO Leadership & Coaching - Globalization, Innovation & Commercialization - & Much More Supplemental to Minevich's engaging commentary, this title includes a wealth of CTO/CIO related technology articles written by C-Level (CEO, CTO, CFO, CMO) executives from companies such as BMC, BEA, Novell, IBM, Bowstreet, Harte-Hankes, Reynolds & Reynolds, McAfee, Verisign, Peoplesoft, Boeing, GE, Perot Systems, and over 50 other companies along with a wealth of reference/appendix material including vital industry statistics, forms and interactive worksheets, field-specific resources and profiles of related professional organizations indispensable for any CTO, CIO or other Technology Executive. |
| director of engineering vs vp of engineering: 97 Things Every Engineering Manager Should Know Camille Fournier, 2019-11-21 Tap into the wisdom of experts to learn what every engineering manager should know. With 97 short and extremely useful tips for engineering managers, you'll discover new approaches to old problems, pick up road-tested best practices, and hone your management skills through sound advice. Managing people is hard, and the industry as a whole is bad at it. Many managers lack the experience, training, tools, texts, and frameworks to do it well. From mentoring interns to working in senior management, this book will take you through the stages of management and provide actionable advice on how to approach the obstacles you’ll encounter as a technical manager. A few of the 97 things you should know: Three Ways to Be the Manager Your Report Needs by Duretti Hirpa The First Two Questions to Ask When Your Team Is Struggling by Cate Huston Fire Them! by Mike Fisher The 5 Whys of Organizational Design by Kellan Elliott-McCrea Career Conversations by Raquel Vélez Using 6-Page Documents to Close Decisions by Ian Nowland Ground Rules in Meetings by Lara Hogan |
| director of engineering vs vp of engineering: Managing Humans Michael Lopp, 2007-10-18 Managing Humans is a selection of the best essays from Michael Lopp's popular website Rands in Repose(www.randsinrepose.com). Lopp is one of the most sought-after IT managers in Silicon Valley, and draws on his experiences at Apple, Netscape, Symantec, and Borland. This book reveals a variety of different approaches for creating innovative, happy development teams. It covers handling conflict, managing wildly differing personality types, infusing innovation into insane product schedules, and figuring out how to build lasting and useful engineering culture. The essays are biting, hilarious, and always informative. |
| director of engineering vs vp of engineering: Engineer Your Own Success Anthony Fasano, 2015-01-07 Focusing on basic skills and tips for career enhancement, Engineer Your Own Success is a guide to improving efficiency and performance in any engineering field. It imparts valuable organization tips, communication advice, networking tactics, and practical assistance for preparing for the PE exam—every necessary skill for success. Authored by a highly renowned career coach, this book is a battle plan for climbing the rungs of any engineering ladder. |
| director of engineering vs vp of engineering: Project to Product Mik Kersten, 2018-11-20 As tech giants and startups disrupt every market, those who master large-scale software delivery will define the economic landscape of the 21st century, just as the masters of mass production defined the landscape in the 20th. Unfortunately, business and technology leaders are woefully ill-equipped to solve the problems posed by digital transformation. At the current rate of disruption, half of S&P 500 companies will be replaced in the next ten years. A new approach is needed. In Project to Product, Value Stream Network pioneer and technology business leader Dr. Mik Kersten introduces the Flow Framework—a new way of seeing, measuring, and managing software delivery. The Flow Framework will enable your company’s evolution from project-oriented dinosaur to product-centric innovator that thrives in the Age of Software. If you’re driving your organization’s transformation at any level, this is the book for you. |
| director of engineering vs vp of engineering: Peopleware Tom DeMarco, Tim Lister, 2013-07-15 Few books in computing have had as profound an influence on software management as Peopleware. The unique insight of this longtime best seller is that the major issues of software development are human, not technical. They’re not easy issues; but solve them, and you’ll maximize your chances of success. “Peopleware has long been one of my two favorite books on software engineering. Its underlying strength is its base of immense real experience, much of it quantified. Many, many varied projects have been reflected on and distilled; but what we are given is not just lifeless distillate, but vivid examples from which we share the authors’ inductions. Their premise is right: most software project problems are sociological, not technological. The insights on team jelling and work environment have changed my thinking and teaching. The third edition adds strength to strength.” — Frederick P. Brooks, Jr., Kenan Professor of Computer Science, University of North Carolina at Chapel Hill, Author of The Mythical Man-Month and The Design of Design “Peopleware is the one book that everyone who runs a software team needs to read and reread once a year. In the quarter century since the first edition appeared, it has become more important, not less, to think about the social and human issues in software develop¿ment. This is the only way we’re going to make more humane, productive workplaces. Buy it, read it, and keep a stock on hand in the office supply closet.” —Joel Spolsky, Co-founder, Stack Overflow “When a book about a field as volatile as software design and use extends to a third edition, you can be sure that the authors write of deep principle, of the fundamental causes for what we readers experience, and not of the surface that everyone recognizes. And to bring people, actual human beings, into the mix! How excellent. How rare. The authors have made this third edition, with its additions, entirely terrific.” —Lee Devin and Rob Austin, Co-authors of The Soul of Design and Artful Making For this third edition, the authors have added six new chapters and updated the text throughout, bringing it in line with today’s development environments and challenges. For example, the book now discusses pathologies of leadership that hadn’t previously been judged to be pathological; an evolving culture of meetings; hybrid teams made up of people from seemingly incompatible generations; and a growing awareness that some of our most common tools are more like anchors than propellers. Anyone who needs to manage a software project or software organization will find invaluable advice throughout the book. |
| director of engineering vs vp of engineering: Ask a Manager Alison Green, 2018-05-01 'I'm a HUGE fan of Alison Green's Ask a Manager column. This book is even better' Robert Sutton, author of The No Asshole Rule and The Asshole Survival Guide 'Ask A Manager is the book I wish I'd had in my desk drawer when I was starting out (or even, let's be honest, fifteen years in)' - Sarah Knight, New York Times bestselling author of The Life-Changing Magic of Not Giving a F*ck A witty, practical guide to navigating 200 difficult professional conversations Ten years as a workplace advice columnist has taught Alison Green that people avoid awkward conversations in the office because they don't know what to say. Thankfully, Alison does. In this incredibly helpful book, she takes on the tough discussions you may need to have during your career. You'll learn what to say when: · colleagues push their work on you - then take credit for it · you accidentally trash-talk someone in an email and hit 'reply all' · you're being micromanaged - or not being managed at all · your boss seems unhappy with your work · you got too drunk at the Christmas party With sharp, sage advice and candid letters from real-life readers, Ask a Manager will help you successfully navigate the stormy seas of office life. |
| director of engineering vs vp of engineering: Programming JavaScript Applications Eric Elliott, 2014-06-26 Take advantage of JavaScript’s power to build robust web-scale or enterprise applications that are easy to extend and maintain. By applying the design patterns outlined in this practical book, experienced JavaScript developers will learn how to write flexible and resilient code that’s easier—yes, easier—to work with as your code base grows. JavaScript may be the most essential web programming language, but in the real world, JavaScript applications often break when you make changes. With this book, author Eric Elliott shows you how to add client- and server-side features to a large JavaScript application without negatively affecting the rest of your code. Examine the anatomy of a large-scale JavaScript application Build modern web apps with the capabilities of desktop applications Learn best practices for code organization, modularity, and reuse Separate your application into different layers of responsibility Build efficient, self-describing hypermedia APIs with Node.js Test, integrate, and deploy software updates in rapid cycles Control resource access with user authentication and authorization Expand your application’s reach through internationalization |
| director of engineering vs vp of engineering: Building Mobile Apps at Scale Gergely Orosz, 2021-04-06 While there is a lot of appreciation for backend and distributed systems challenges, there tends to be less empathy for why mobile development is hard when done at scale. This book collects challenges engineers face when building iOS and Android apps at scale, and common ways to tackle these. By scale, we mean having numbers of users in the millions and being built by large engineering teams. For mobile engineers, this book is a blueprint for modern app engineering approaches. For non-mobile engineers and managers, it is a resource with which to build empathy and appreciation for the complexity of world-class mobile engineering. The book covers iOS and Android mobile app challenges on these dimensions: Challenges due to the unique nature of mobile applications compared to the web, and to the backend. App complexity challenges. How do you deal with increasingly complicated navigation patterns? What about non-deterministic event combinations? How do you localize across several languages, and how do you scale your automated and manual tests? Challenges due to large engineering teams. The larger the mobile team, the more challenging it becomes to ensure a consistent architecture. If your company builds multiple apps, how do you balance not rewriting everything from scratch while moving at a fast pace, over waiting on centralized teams? Cross-platform approaches. The tooling to build mobile apps keeps changing. New languages, frameworks, and approaches that all promise to address the pain points of mobile engineering keep appearing. But which approach should you choose? Flutter, React Native, Cordova? Native apps? Reuse business logic written in Kotlin, C#, C++ or other languages? What engineering approaches do world-class mobile engineering teams choose in non-functional aspects like code quality, compliance, privacy, compliance, or with experimentation, performance, or app size? |
| director of engineering vs vp of engineering: Guide to the Software Engineering Body of Knowledge (Swebok(r)) IEEE Computer Society, 2014 In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)). |
| director of engineering vs vp of engineering: Computer Engineering for Babies Chase Roberts, 2021-10-20 An introduction to computer engineering for babies. Learn basic logic gates with hands on examples of buttons and an output LED. |
| director of engineering vs vp of engineering: Team Topologies Matthew Skelton, Manuel Pais, 2019-09-17 Effective software teams are essential for any organization to deliver value continuously and sustainably. 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. |
| director of engineering vs vp of engineering: Optimized C++ Kurt Guntheroth, 2016-04-27 In today’s fast and competitive world, a program’s performance is just as important to customers as the features it provides. This practical guide teaches developers performance-tuning principles that enable optimization in C++. You’ll learn how to make code that already embodies best practices of C++ design run faster and consume fewer resources on any computer—whether it’s a watch, phone, workstation, supercomputer, or globe-spanning network of servers. Author Kurt Guntheroth provides several running examples that demonstrate how to apply these principles incrementally to improve existing code so it meets customer requirements for responsiveness and throughput. The advice in this book will prove itself the first time you hear a colleague exclaim, “Wow, that was fast. Who fixed something?” Locate performance hot spots using the profiler and software timers Learn to perform repeatable experiments to measure performance of code changes Optimize use of dynamically allocated variables Improve performance of hot loops and functions Speed up string handling functions Recognize efficient algorithms and optimization patterns Learn the strengths—and weaknesses—of C++ container classes View searching and sorting through an optimizer’s eye Make efficient use of C++ streaming I/O functions Use C++ thread-based concurrency features effectively |
| director of engineering vs vp of engineering: Architecture Modernization Nick Tune, Jean-Georges Perrin, 2024-02-27 Proven techniques and principles for modernizing legacy systems into new architectures that deliver serious competitive advantage. For a business to thrive, it needs a modern software architecture that is aligned with its corporate architecture. This book presents concrete practices that sync software, product, strategy, team dynamics, and work practices. You’ll evolve your technical and social architecture together, reducing needless dependencies and achieving faster flow of innovation across your organization. In Architecture Modernization: Socio-technical alignment of software, strategy, and structure you’ll learn how to: Identify strategic ambitions and challenges using listening and mapping tours Visualize your business landscape and crucial capabilities with Wardley Mapping Create a product taxonomy as a framework for your architecture Run big picture EventStorming workshops to map business domains Apply Team Topologies patterns to identify and refine value streams Design loosely coupled, domain-aligned software architectures Build internal developer platforms for rapid, reliable evolution Implement data mesh principles and tools to revolutionize data engineering Deliver compelling modernization roadmaps focused on continuous value Architecture Modernization: Socio-technical alignment of software, strategy, and structure shows you how to turn the practice of architecting systems into a transformative process for your entire company. Chapter-by-chapter, you’ll identify the reasons and benefits of modernization, design an architecture that works for your business, and then implement your new approach in a progressive and sustainable manner. Every technique is illustrated with insightful industry examples and an interactive Miro board that lets you dig deeper. Forewords by Matthew Skelton and Xin Yao. About the technology The decisions you make about your software are inherently connected to the decisions you make about your business. Why not turn the mundane task of modernizing legacy systems into a transformative process for your entire company? This book shows you how! It reveals a socio-technical approach to align your software and products with organizational dynamics and ways of working. About the book Architecture Modernization: Socio-technical alignment of software, strategy, and structure presents a clear path for upgrading your entire organization when you re-imagine your software. In it, you’ll learn to combine practices like Domain-Driven Design, Event Storming, and Wardley Mapping to discover user needs, design optimal architecture, and avoid falling back into old habits. Provocative examples from Danske, Salesforce, the UK Government, and others show the real-world result of each approach, identifying techniques you can apply effectively in your own business. About the reader For CTOs, tech leads, and principal engineers who decide on architecture and organization design. About the author Nick Tune helps organizations modernize their architectures through empowered product teams and continuous delivery. Jean-Georges Perrin builds innovative and modern data platforms. The technical editor on this book was Kamil Nicieja. |
| director of engineering vs vp of engineering: Modern Software Engineering David Farley, 2021-11-16 Improve Your Creativity, Effectiveness, and Ultimately, Your Code In Modern Software Engineering, continuous delivery pioneer David Farley helps software professionals think about their work more effectively, manage it more successfully, and genuinely improve the quality of their applications, their lives, and the lives of their colleagues. Writing for programmers, managers, and technical leads at all levels of experience, Farley illuminates durable principles at the heart of effective software development. He distills the discipline into two core exercises: learning and exploration and managing complexity. For each, he defines principles that can help you improve everything from your mindset to the quality of your code, and describes approaches proven to promote success. Farley's ideas and techniques cohere into a unified, scientific, and foundational approach to solving practical software development problems within realistic economic constraints. This general, durable, and pervasive approach to software engineering can help you solve problems you haven't encountered yet, using today's technologies and tomorrow's. It offers you deeper insight into what you do every day, helping you create better software, faster, with more pleasure and personal fulfillment. Clarify what you're trying to accomplish Choose your tools based on sensible criteria Organize work and systems to facilitate continuing incremental progress Evaluate your progress toward thriving systems, not just more legacy code Gain more value from experimentation and empiricism Stay in control as systems grow more complex Achieve rigor without too much rigidity Learn from history and experience Distinguish good new software development ideas from bad ones Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details. |
| director of engineering vs vp of engineering: Work Happy Jill Geisler, 2012-06-05 Management guru Jill Geisler has coached countless men and women who want to build their leadership skills, help employees do their best work, and make workplaces happy and successful. In WORK HAPPY, she provides a practical, step-by-step guide, based on real-world experience, respected research, and lessons that will transform managers and their teams. It's a workshop-in-a-book, designed to produce positive, immediate and lasting results. Whether the reader is an experienced manager, a rookie boss or an aspiring leader, WORK HAPPY will supercharge their skills and celebrate the values that make anyone look forward to going to work. Jill Geisler offers concrete steps for improving each element of management including collaboration, communication, conflict resolution, motivation, coaching, and feedback, so that everyone on the team-whether in the office or working offsite-can do their best. WORK HAPPY takes management skills to the next level and proves that learning, leadership and life at work can (and should) be fun. |
| director of engineering vs vp of engineering: Communication for Engineers Chris Laffra, 2021-02-09 This book was written by a software engineer for software engineers. It provides an overview of various communication skills and techniques that are relevant to people working in the software industry. Some of the communications skills discussed in this book have a generic nature, such as self-awareness. Others are more specific for engineers, such as writing clean code. The result is a comprehensive coverage of communication as it concerns software engineers with many practical and relevant tips to follow. The book sometimes focuses on communication between engineers and at other times, it explores how to interact with others, typically in a business context. When we say engineers in this book, we generalize and refer to software engineers, programmers, developers, designers, engineering managers, PMs, software architects, or anyone else working in software development.In this book, each communication skill will be discussed with specific tips to improve yourself in a well-structured, constructive, and productive fashion. The end goal is to increase your impact as an engineer by focusing on soft skills that complement your existing coding and problem solving skills. |
| director of engineering vs vp of engineering: Understanding the Educational and Career Pathways of Engineers National Academy of Engineering, Committee on Understanding the Engineering Education-Workforce Continuum, 2019-01-26 Engineering skills and knowledge are foundational to technological innovation and development that drive long-term economic growth and help solve societal challenges. Therefore, to ensure national competitiveness and quality of life it is important to understand and to continuously adapt and improve the educational and career pathways of engineers in the United States. To gather this understanding it is necessary to study the people with the engineering skills and knowledge as well as the evolving system of institutions, policies, markets, people, and other resources that together prepare, deploy, and replenish the nation's engineering workforce. This report explores the characteristics and career choices of engineering graduates, particularly those with a BS or MS degree, who constitute the vast majority of degreed engineers, as well as the characteristics of those with non-engineering degrees who are employed as engineers in the United States. It provides insight into their educational and career pathways and related decision making, the forces that influence their decisions, and the implications for major elements of engineering education-to-workforce pathways. |
| director of engineering vs vp of engineering: MITRE Systems Engineering Guide , 2012-06-05 |
| director of engineering vs vp of engineering: The Effective Engineer Edmond Lau, 2015-03-19 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. |
| director of engineering vs vp of engineering: The Software Developer's Career Handbook Michael Lopp, 2023-08-09 At some point in your career, you'll realize there's more to being a software engineer than dealing with code. Is it time to become a manager? Or join a startup? In this insightful and entertaining book, Michael Lopp recalls his own make-or-break moments with Silicon Valley giants such as Apple, Slack, Pinterest, Palantir, Netscape, and Symantec to help you make better, more mindful career decisions. With more than 40 stand-alone stories, Lopp walks through a complete job lifecycle, starting with the interview and ending with the realization that it might be time to move on. You'll learn how to handle baffling circumstances in your job, understand what you want from your career, and discover how to thrive in your workplace. Learn how to navigate areas of your job that don't involve writing code Identify how the aspects you enjoy will affect your next career steps Build and maintain key relationships and interactions within your community Make choices that will help you have a deliberate career Recognize what's important to your manager and work on things that matter |
| director of engineering vs vp of engineering: Engineering Production-grade Shiny Apps Colin Fay, Vincent Guyader, Sebastien Rochette, Girard Cervan, 2021 Presented in full color, Engineering Production-Grade Shiny Apps helps people build production-grade shiny applications, by providing advice, tools, and a methodology to work on web applications with R. This book starts with an overview of the challenges which arise from any big web application project: organizing work, thinking about the user interface, challenges of teamwork & production environment. Then, it moves to a step by step methodology that goes from the idea to the end application. Each part of this process will cover in detail a series of tools and methods to use while building production-ready shiny applications. Finally, the book will end with a series of approaches and advice about optimizations for production-- |
| director of engineering vs vp of engineering: Advanced Optimization for Process Systems Engineering Ignacio E. Grossmann, 2021-03-25 A unique text covering basic and advanced concepts of optimization theory and methods for process systems engineers. With examples illustrating key concepts and algorithms, and exercises involving theoretical derivations, numerical problems and modeling systems, it is ideal for single-semester, graduate courses in process systems engineering. |
| director of engineering vs vp of engineering: 10 Steps to Successful Mentoring Wendy Axelrod, 2019-06-25 Reach New Heights as a Mentor Broaden people’s perspectives. Sustain momentum for development. Drive significant career growth. It doesn’t take a workplace superhero to accomplish all of this. You can do it—when you become a masterful mentor. While mentoring resources typically center on the mentee or the program, 10 Steps to Successful Mentoring is devoted explicitly to helping you excel in the role of mentor. In this book, Wendy Axelrod helps you stretch your mentoring abilities to yield substantial rewards for you and your mentee. Drawing on more than 20 years of work with mentors, she delves into proven approaches to use in your ongoing meetings, such as elevating the power of questions, leveraging experience for learning, and expanding growth using everyday psychology. Come away inspired to take on a fresh challenge. Whether mentoring is a calling or a choice, you’re new to it or a seasoned veteran, or you’re in a formal program or on your own, 10 Steps to Successful Mentoring is the resource you’ll return to again and again. It’s filled with real-life examples and 40 tools to help you master the nuances that drive deliberate development. Woven throughout are Wendy’s seven guiding principles that distinguish the most successful mentors (hint: “Start where your mentee is, not where you think they should be”). Become the best possible mentor, and deliver memorable experiences to your mentees and create a lasting legacy for yourself. |
| director of engineering vs vp of engineering: The Art of Leadership Michael Lopp, 2020-05-13 Many people think leadership is a higher calling that resides exclusively with a select few who practice and preach big, complex leadership philosophies. But as this practical book reveals, what’s most important for leadership is principled consistency. Time and again, small things done well build trust and respect within a team. Using stories from his time at Netscape, Apple, and Slack, Michael Lopp presents a series of small but compelling practices to help you build leadership skills. You’ll learn how to create teams that are highly productive, highly respected, and highly trusted. Lopp has been speaking and writing about this topic for over a decade and now maintains a Slack leadership channel with over 13,000 members. The essays in this book examine the practical skills Lopp learned from exceptional leaders—as a manager at Netscape, a senior manager and director at Apple, and an executive at Slack. You’ll learn how to apply these lessons to your own experience. |
| director of engineering vs vp of engineering: The Product-Led Organization Todd Olson, 2020-09-23 A playbook on product-led strategy for software product teams There's a common strategy used by the fastest growing and most successful businesses of our time. These companies are building their entire customer experience around their digital products, delivering software that is simple, intuitive and delightful, and that anticipates and exceeds the evolving needs of users. Product-led organizations make their products the vehicle for acquiring and retaining customers, driving growth, and influencing organizational priorities. They represent the future of business in a digital-first world. This book is meant to help you transform your company into a product-led organization, helping to drive growth for your business and advance your own career. It provides: A holistic view of the quantitative and qualitative insights teams need to make better decisions and shape better product experiences. A guide to setting goals for product success and measuring progress toward meeting them. A playbook for incorporating sales and marketing activities, service and support, as well as onboarding and education into the product Strategies for soliciting, organizing and prioritizing feedback from customers and other stakeholders; and how to use those inputs to create an effective product roadmap The Product-Led Organization: Drive Growth By Putting Product at the Center of Your Customer Experience was written by the co-founder and CEO of Pendo—a SaaS company and innovator in building software for digital product teams. The book reflects the author’s passion and dedication for sharing what it takes to build great products. |
| director of engineering vs vp of engineering: Lend Me Your Ears Max Atkinson, 2005-11-10 The room darkens and grows hushed, all eyes to the front as the screen comes to life. Eagerly the audience starts to thumb the pages of their handouts, following along breathlessly as the slides go by one after the other...We're not sure what the expected outcome was when PowerPoint first emerged as the industry standard model of presentation, but reality has shown few positive results. Research reveals that there is much about this format that audiences positively dislike, and that the old school rules of classical rhetoric are still as effective as they ever were for maximizing impact. Renowned communications researcher, consultant, and speech coach Max Atkinson presents these findings and more in a groundbreaking and refreshing approach that highlights the secrets of successful communication, and shows how anyone can put these into practice and become an effective speaker or presenter. |
| director of engineering vs vp of engineering: Encyclopedia of Software Engineering Three-Volume Set (Print) Phillip A. Laplante, 2010-11-22 Software engineering requires specialized knowledge of a broad spectrum of topics, including the construction of software and the platforms, applications, and environments in which the software operates as well as an understanding of the people who build and use the software. Offering an authoritative perspective, the two volumes of the Encyclopedia of Software Engineering cover the entire multidisciplinary scope of this important field. More than 200 expert contributors and reviewers from industry and academia across 21 countries provide easy-to-read entries that cover software requirements, design, construction, testing, maintenance, configuration management, quality control, and software engineering management tools and methods. Editor Phillip A. Laplante uses the most universally recognized definition of the areas of relevance to software engineering, the Software Engineering Body of Knowledge (SWEBOK®), as a template for organizing the material. Also available in an electronic format, this encyclopedia supplies software engineering students, IT professionals, researchers, managers, and scholars with unrivaled coverage of the topics that encompass this ever-changing field. Also Available Online This Taylor & Francis encyclopedia is also available through online subscription, offering a variety of extra benefits for researchers, students, and librarians, including: Citation tracking and alerts Active reference linking Saved searches and marked lists HTML and PDF format options Contact Taylor and Francis for more information or to inquire about subscription options and print/online combination packages. US: (Tel) 1.888.318.2367; (E-mail) e-reference@taylorandfrancis.com International: (Tel) +44 (0) 20 7017 6062; (E-mail) online.sales@tandf.co.uk |
| director of engineering vs vp of engineering: Production Engineering , 1977 |
| director of engineering vs vp of engineering: The Complete Software Developer's Career Guide John Z. Sonmez, 2017 Early in his software developer career, John Sonmez discovered that technical knowledge alone isn't enough to break through to the next income level - developers need soft skills like the ability to learn new technologies just in time, communicate clearly with management and consulting clients, negotiate a fair hourly rate, and unite teammates and coworkers in working toward a common goal. Today John helps more than 1.4 million programmers every year to increase their income by developing this unique blend of skills. Who Should Read This Book? Entry-Level Developers - This book will show you how to ensure you have the technical skills your future boss is looking for, create a resume that leaps off a hiring manager's desk, and escape the no work experience trap. Mid-Career Developers - You'll see how to find and fill in gaps in your technical knowledge, position yourself as the one team member your boss can't live without, and turn those dreaded annual reviews into chance to make an iron-clad case for your salary bump. Senior Developers - This book will show you how to become a specialist who can command above-market wages, how building a name for yourself can make opportunities come to you, and how to decide whether consulting or entrepreneurship are paths you should pursue. Brand New Developers - In this book you'll discover what it's like to be a professional software developer, how to go from I know some code to possessing the skills to work on a development team, how to speed along your learning by avoiding common beginner traps, and how to decide whether you should invest in a programming degree or 'bootcamp.'-- |
外企中Managing Director和General Manager有什么区别？
外企特别是金融类外企经常有vice president，director, managing director之类，头衔很大，其实很多只是职级而已，大多不是字面表达的意思，更多是类似国内的职称。比如VP其实就是外企 …
名片中职务的对应英文翻译及欧美企业职务含义及级别？ - 知乎
1. 如果怕误解为中干，建议翻为CEO，这个老外一听就了解。至于Managing Director要看总经理是否董事会成员，如果是，CEO和Managing Director取其一（听你们领导的），不要重复用。 …
对董事长、总经理等职务，最准确常用的商务英语翻译是什么？
中小公司： General Manager 或 Managing Director. 合伙人制公司中负责日常运作的那位合伙人： Managing Partner. 副总经理： 看公司大小. 大公司： Executive Vice President， 下面还有 …
外企职位层级的划分？从低到高，求中英文对照? - 知乎
而对大多数在职场打拼了半辈子的senior director来说，他们的职业生涯也就止步于此了。从director 到VP，是只属于少数职场精英们的最后一个升职（升值）瓶颈。 第八级： 副总 …
GM、VP、FVP、CIO都是什么职位？ - 知乎
知乎，中文互联网高质量的问答社区和创作者聚集的原创内容平台，于 2011 年 1 月正式上线，以「让人们更好的分享知识、经验和见解，找到自己的解答」为品牌使命。知乎凭借认真、专业 …
导演、监制、制片人、出品人的职责和分工是怎么样的？ - 知乎
本题已加入知乎圆桌 »影视职人说 | 青年导演养成记，更多「电影产业」讨论欢迎关注。
如何知道一个期刊是不是sci？ - 知乎
Master Journal List在这个网站能搜到的就是吗？我在web of knowledge 上能搜到文章的杂志就是sci吗？
执行董事和CEO有什么区别？ - 知乎
Nov 13, 2018 · 我的英国公司职位就是Manaing Director，然后中文名片上写“执行董事”，我承认这个名称一般中国客户都不明白，几乎都认为是董事会的什么角色。但实际上，就是CEO，或者 …
研究员为什么是principal investigator而不是researcher？ - 知乎
美国国家科学基金会(National Science Foundation，简称NSF)定义为”由受让入指定、美国国家自然科学基金委同意的负责项目科学技术方向的个体”，同时指出”这一术语一般用于研究领域”， …
PE、PM、PD、PR分别是什么岗位? - 知乎
PD（product designer/product director）：产品设计或产品负责人，多见于互联网等以产品为中心的行业。 PM（product manager/project manager）：产品经理或项目经理，前者多见于互联 …
外企中Managing Director和General Manager有什么区别？
外企特别是金融类外企经常有vice president，director, managing director之类，头衔很大，其实很多只是职级而已，大多不是字面表达的意思，更多是类似国内的职称。比如VP其实就是外企 …
名片中职务的对应英文翻译及欧美企业职务含义及级别？ - 知乎
1. 如果怕误解为中干，建议翻为CEO，这个老外一听就了解。至于Managing Director要看总经理是否董事会成员，如果是，CEO和Managing Director取其一（听你们领导的），不要重复用。 …
对董事长、总经理等职务，最准确常用的商务英语翻译是什么？
中小公司： General Manager 或 Managing Director. 合伙人制公司中负责日常运作的那位合伙人： Managing Partner. 副总经理： 看公司大小. 大公司： Executive Vice President， 下面还有 …
外企职位层级的划分？从低到高，求中英文对照? - 知乎
而对大多数在职场打拼了半辈子的senior director来说，他们的职业生涯也就止步于此了。从director 到VP，是只属于少数职场精英们的最后一个升职（升值）瓶颈。 第八级： 副总 …
GM、VP、FVP、CIO都是什么职位？ - 知乎
知乎，中文互联网高质量的问答社区和创作者聚集的原创内容平台，于 2011 年 1 月正式上线，以「让人们更好的分享知识、经验和见解，找到自己的解答」为品牌使命。知乎凭借认真、专业 …
导演、监制、制片人、出品人的职责和分工是怎么样的？ - 知乎
本题已加入知乎圆桌 »影视职人说 | 青年导演养成记，更多「电影产业」讨论欢迎关注。
如何知道一个期刊是不是sci？ - 知乎
Master Journal List在这个网站能搜到的就是吗？我在web of knowledge 上能搜到文章的杂志就是sci吗？
执行董事和CEO有什么区别？ - 知乎
Nov 13, 2018 · 我的英国公司职位就是Manaing Director，然后中文名片上写“执行董事”，我承认这个名称一般中国客户都不明白，几乎都认为是董事会的什么角色。但实际上，就是CEO，或者 …
研究员为什么是principal investigator而不是researcher？ - 知乎
美国国家科学基金会(National Science Foundation，简称NSF)定义为”由受让入指定、美国国家自然科学基金委同意的负责项目科学技术方向的个体”，同时指出”这一术语一般用于研究领域”， …
PE、PM、PD、PR分别是什么岗位? - 知乎
PD（product designer/product director）：产品设计或产品负责人，多见于互联网等以产品为中心的行业。 PM（product manager/project manager）：产品经理或项目经理，前者多见于互联 …
