Becoming a Technical Leader


Book Description

Whether you manage people, are managed by people, or just want to change the way you interact with others, this book is about success. How to plan it, how to make it happen--Becoming a Technical Leader shows you how to do it!




The Manager's Path


Book Description

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




Roundtable on Technical Leadership


Book Description

Software Experts Debate Leadership Qualities and the Hazards of Shortcuts and Stupid Tricks Joined by coeditors Marie Benesh and James Bullock, consultant's consultant Gerald M. Weinberg highlights forty experts' secrets for building and sustaining a leadership role in software development. Participants of the SHAPE forum, many of them software consultants and managers at the world's most successful software companies, logged in to help each other identify the "stupid tricks" that developers are tempted to employ in design, code, and documentation--tricks that seem clever in the short term but have damaging longterm effects. Topics include programming, design, documentation, teaching, learning, educating management, being yourself, and much more. Presented in an easy-to-read dialogue format, true to the comments' original appearance on the Web, this is the second stand-alone book drawn from Weinberg's SHAPE forum, following Roundtable on Project Management. Contributors include Jim Batterson, James Bullock, Pat Ferdinandi, Fritz, Phil Fuhrer, Jesse Gordon, Don Gray, Brian Gulino, Peter Harris, Joseph Howard, Kevin Huigens, Steve Jackson, Jim Jarrett, Bob King, Dave Kleist, Henry Knapp, Brian Knopp, Fredric Laurentine, Pat McGee, Nate McNamara, George Olsen, Mark Passolt, Sue Petersen, Dwayne Phillips, Brian Richter, Sharon Marsh Roberts, Brett Schuchert, Stuart Scott, Dave Smith, Steve Smith, Daniel Starr, Wayne Strider, Pete TerMaat, Phil Trice, Bill Trierweiler, Marianne Tromp, Jerry Weinberg, and Kay Wise.




Leader Evolution


Book Description

Most individuals who move into leadership positions expe-rience the modern day version of trial by ordeal. It’s sink or swim. To reduce the learning curve and create a more effec-tive process, this book describes a road map for leadership development, a series of four stages that expand personal competence as well as create a broader impact on the orga-nization or business. Each stage requires unique changes in thinking, perspective taking, and behavior, both those needed to acquire as well as those needed to jettison. The book is a pragmatic approach for self-motived individuals to take con-trol of their professional development by giving them the concepts, tools, techniques, and assignments to develop their leadership effectiveness where it counts the most—on the job. While highly relevant to new and existing managers, the book is ideally suited for technical professionals and leaders in technical organizations looking to develop critical lead-ership skills distinct from technical expertise. The concepts and principles are directed toward the individual for on-the-job application, however, this also serves as an organi-zational and leadership development resource for Executive MBA programs, as well as a blueprint for in-house leadership development programs.




Staff Engineer


Book Description

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.




Leadership on the Line


Book Description

Heifetz and Linsky (both John F. Kennedy School of Government, Harvard U.) discuss how to survive and thrive on the dangers of leadership. They address leadership at all levels, from parents to everyday workers, managers and community activists, presidents of organizations and of countries. They examine why and how leadership is dangerous, how that danger drives some people "out of the game," possible strategies to reduce the risk of getting pushed aside, ways that people contribute to their own demise, ways to manage personal vulnerabilities, and how to keep one's spirit alive in the face of adversity. This text takes a more personal and practical approach to expand on ideas raised in Heifetz's earlier book, Leadership Without Easy Answers. Annotation copyrighted by Book News, Inc., Portland, OR




Keys to Becoming an Effective Worship Leader


Book Description

Practicing untried methods and ideas on your con-gregation or music team often proves discouraging. Trying unsuccessful ventures long term can be devastating. Tom Kraeuter needs and desires of those involved in the ministry of praise and worship.




Technology Strategy Patterns


Book Description

Technologists who want their ideas heard, understood, and funded are often told to speak the language of businessâ??without really knowing what that is. This bookâ??s toolkit provides architects, product managers, technology managers, and executives with a shared languageâ??in the form of repeatable, practical patterns and templatesâ??to produce great technology strategies. Author Eben Hewitt developed 39 patterns over the course of a decade in his work as CTO, CIO, and chief architect for several global tech companies. With these proven tools, you can define, create, elaborate, refine, and communicate your architecture goals, plans, and approach in a way that executives can readily understand, approve, and execute. This book covers: Architecture and strategy: Adopt a strategic architectural mindset to make a meaningful material impact Creating your strategy: Define the components of your technology strategy using proven patterns Communicating the strategy: Convey your technology strategy in a compelling way to a variety of audiences Bringing it all together: Employ patterns individually or in clusters for specific problems; use the complete framework for a comprehensive strategy




Chief Technology Officer


Book Description

Smith describes the role and responsibilities of the Chief Technology Officerand executives with similar titles. He provides a framework for understandingthe many unique flavors the position; identifies key responsibilities that gowith the job; and provides vignettes of successful CTOs.




An Introduction to General Systems Thinking


Book Description

A classic introduction to systems theory, with applications in computer science and beyond. -- Back cover.