• Complain

Dave Hendricksen - 12 More Essential Skills for Software Architects

Here you can read online Dave Hendricksen - 12 More Essential Skills for Software Architects full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. publisher: Addison-Wesley Professional, genre: Home and family. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Dave Hendricksen 12 More Essential Skills for Software Architects
  • Book:
    12 More Essential Skills for Software Architects
  • Author:
  • Publisher:
    Addison-Wesley Professional
  • Genre:
  • Rating:
    5 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 100
    • 1
    • 2
    • 3
    • 4
    • 5

12 More Essential Skills for Software Architects: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "12 More Essential Skills for Software Architects" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Master The Crucial Technical Skills Every
Software Architect Needs!

To succeed as a software architect, you must
master both technical skills and soft skills. Dave Hendricksen
illuminated the soft skills in his highly-regarded 12 Essential
Skills for Software Architects
. Now, in 12 More
Essential Skills for Software Architects
he turns to
the technical side.

Drawing on his decades of experience,
Hendricksen organizes technical skills into three areas.

PROJECT SKILLS: driving projects from
ideation through delivery
TECHNOLOGY SKILLS: building, buying, and/or leveraging the right
technologies
VISIONARY SKILLS: realizing an architectural vision that improves
long-term competitiveness

He helps you develop and sharpen these key
technical skills: from conceptualizing solutions to developing
platforms and governance, and from selecting technology innovations
to infusing architectures with an entrepreneurial spirit.

This guide reveals the technical skills you
need and provides a coherent framework and practical methodology
for mastering them.

Taken together, Hendricksens two
books offer the most complete, practical pathway to excellence in
software architecture. Theyll guide you through every step
of your architecture careerfrom getting the right position
to thriving once you have it.

Essential Architect Skills

Visionary Skills
Entrepreneurial Execution
Technology Innovation
Strategic Roadmapping

Technology Skills
Governance
Platform Development
Know-how
Architectural Perspective

Project Skills
Estimation
Partnership
Discovery
Management
Conceptualization

Dave Hendricksen is a big data
architect for Thomson Reuters, where he works closely with the
firms new product development teams to create innovative
legal products for large-scale online platforms such as
Westlaw.com. Hendricksen presented Designing and Building
Large-Scale Systems in an Agile World at Carnegie Mellon
Universitys influential Software Engineering
Institute.

Dave Hendricksen: author's other books


Who wrote 12 More Essential Skills for Software Architects? Find out the surname, the name of the author of the book and a list of all author's works by series.

12 More Essential Skills for Software Architects — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "12 More Essential Skills for Software Architects" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
12 More Essential Skills for Software Architects

Dave Hendricksen

Addison-Wesley

Upper Saddle River, NJ Boston Indianapolis San Francisco
New York Toronto Montreal London Munich Paris Madrid
Capetown Sydney Tokyo Singapore Mexico City

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals.

The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein.

For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales department at or (800) 382-3419.

For government sales inquiries, please contact .

For questions about sales outside the U.S., please contact .

Visit us on the Web: informit.com/aw

Library of Congress Cataloging-in-Publication Data

Copyright 2015 Pearson Education, Inc.

All rights reserved. Printed in the United States of America. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. To obtain permission to use material from this work, please submit a written request to Pearson Education, Inc., Permissions Department, One Lake Street, Upper Saddle River, New Jersey 07458, or you may fax your request to (201) 236-3290.

ISBN-13: 978-0-133-37705-7
ISBN-10: 0-133-37705-9

Text printed in the United States on recycled paper at ____________________
First printing, August 2014

Preface

Architecture is not a profession for the faint-hearted, the weak-willed, or the short-lived.

Martin Filler

Architecture and building is about how you get around the obstacles that are presented to you. That sometimes determines how successful youll be: How good are you at going around obstacles?

Jeremy Renner

Architecture is a service business. An architect is given a program, budget, place, and schedule. Sometimes the end product rises to artor at least people call it that.

Frank Gehry

Architecture is invention.

Oscar Niemeyer

I loved logic, math, computer programming. I loved systems and logic approaches. And so I just figured architecture is this perfect combination.

Maya Lin

I think about architecture all the time. Thats the problem. But Ive always been like that. I dream it sometimes.

Zaha Hadid

The Internet is probably the most important technological advancement of my lifetime. Its strength lies in its open architecture and its ability to allow a framework where all voices can be heard.

Adam Savage

Book Motivation

This book and my first book (12 Essential Skills for Software Architects) focus on the skills needed to become a successful software architect.

Software architecture is about learning how to relate to people and learning how to think about things with an eye toward architecture. 12 Essential Skills for Software Architects focused on soft skills; without these, the rest of the journey is nearly impossible

Shortly after I completed my first book, I began receiving questions about the assumed technical skills (shown in ) that are referred to but not discussed.

Figure P.1. Twelve essential skills for software architects

This book dives into the details of those assumed skillsthe technical skills - photo 1

This book dives into the details of those assumed skillsthe technical skills you need on a daily basis in the role of an architect. It is the combination of soft and technical skills that will enable you reach your goals.

Book Goals

My goals for this book are to

Enable excellence in software architecture through skills development

Enable architectural success in a business context

Promote an architectural approach to thinking about the enterprise

Book Organization

The format and style of this book are intended to help evoke critical thinking about your specific set of projects, your areas of architectural oversight, and your areas of direction-setting leadership. These take the form of project skills, technology skills, and vision skills.

These three areas are organized as follows:

. These skills enable you to drive projects from early ideation to project delivery through

)

)

)

)

)

. These skills ensure that the right technologies are built, bought, or leveraged through

)

)

)

)

. These skills enable the pursuit of the businesss long-term competitive vision through

)

)

)

The three parts can be thought of as a layered set of skills for software architects (see ). Each layer is the basis for the layer above it.

Figure P.2. Technical skills pyramid

Each of the chapters within the book is written to be read independently of the - photo 2

Each of the chapters within the book is written to be read independently of the other chapters. This independence should enable you read the book in the order of your interests or needs.

I hope you enjoy reading the book and that you learn some new things that will enable you to become an excellent architect and better understand the role of an architect.

If you have any questions or comments, please feel free to contact me at .

Acknowledgments

I would like to say thank you to the excellent staff at Addison-Wesley, specifically Olivia Basegio, Sheri Cain, Chris Guzikowski, Chuti Prasertsith, Kesel Wilson, and Barbara Wood. They have been absolutely fantastic to work with.

I would like to thank Brad Appleton, Kevin Bodie, Robert Maksimchuk, and one reviewer who chose to remain anonymous for reviewing my first draft of the book. They all gave me great feedback.

I would also like to thank the following reviewers from Thomson Reuters: Mick Atton, Dan Bennett, Cary Felbab, Scott Francis, Kevin Hakanson, Jesse Haraldson, James Jarvis, Andrew Lipstein, Andrew Martens, Lynn Meredith, Scott Post, Noah Pruzek, Chris Rowland, Bob Sturm, Bas Vellekoop, and Justin Wright. Each of them reviewed selected chapters in their areas of expertise.

In addition, I would like to say thank you to my wife, Jennifer, and son, Tim, for reviewing the book.

Finally, I would like to say thank you to my family and parents for their patience and support while I wrote this second book.

About the Author

The most complicated skill is to be simple.

Dejan Stojanovi

I strive for an architecture from which nothing can be taken away.

Helmut Jahn

My name is Dave Hendricksen, and I am a software architect for Thomson Reuters. I spend most of my time working on WestLawNext (an online legal research tool), Optimus (a learning platform), and a wide variety of other projects, generally focused on new product developmentI love to innovate. I also help run and organize an architecture mentorship program and a technology forum at Thomson Reuters.

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «12 More Essential Skills for Software Architects»

Look at similar books to 12 More Essential Skills for Software Architects. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «12 More Essential Skills for Software Architects»

Discussion, reviews of the book 12 More Essential Skills for Software Architects and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.