適当に予言しておくと2020年に翻訳書が出ると思う。
"The first is to help architects, product managers, and executives at technology companies or in technology organizations who are charged with producing technology strategies."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/preface01.html
"The second aim is to help you in your career. "
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/preface01.html
この本の目的。
"A hammer doesn’t exist to be a hammer. It’s a tool to construct something else. Technology is one tool with which businesses are constructed, rise, and fall."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/introduction01.html
技術とビジネスのこと。
"I have known many smart people, wonderful technologists, who do not get their ideas heard by upper management. They state what the problems are and where the problems are going to be, write that up, and put it on the wiki—and nothing changes."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/introduction01.html
見たことある。
"I’m sorry to repeat an old saw, but it’s true: increasingly, it is impossible to distinguish between business and technology."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/introduction01.html
技術とビジネスは不可分。
"There are two jobs in the world that people want to do the most while knowing the least about: architect and strategist. "
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
私もアーキテクトが何かわからないので本を読んでいる。
"Likewise, the term “architect” didn’t enter popular usage to describe a role in the software field until the late 1990s."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
20年ほどの歴史しかない。
"The product management team states what must be done to solve the problem, and the architect describes how to realize that vision in a system."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
whatとhowの関係はよく聞く。
"I hope once you’re done with this book, you’ll have some ideas for how to enable and reveal the three facets of firmitas, utilitas, and venustas in your own work."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
日本語では「強・用・美」というらしい。
"Whereas developers are typically focused on delivering working code for a user story within the next two weeks for one system within their one team, architects are concerned with how technology can fulfill business goals given a long-term outlook across a variety of interrelated systems across many teams."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
lean architectureにおけるleanとagileの関係に近いかも。
"Here’s my definition of an architect’s work: it comprises the set of strategic and technical models that create a context for position (capabilities), velocity (directedness, ability to adjust), and potential (relations) to harmonize strategic business and technology goals. "
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
全然わからない。特にカッコの意味がわからない。
"Over my 20 years in this field, I’ve come to conclude that there are three primary concerns of the architect:
Contain entropy.
Specify the nonfunctional requirements.
Determine trade-offs."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
2番目の非機能要件を指定するというのは、意外かつわかりやすい。プロダクトマネージャーの役割ではないというのが興味深い。
"As we mature, we realize that picking one tool or framework or language or platform is not a matter of personal taste, but rather a choice with broad ramifications for future flexibility, mergers and acquisitions, training, our ability to hire future supporting teams, and our future ability to directly support—or subvert—the business strategy."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
技術選定は単なる好みの問題ではない。
"One cannot be successful as an architect without thinking of not only what to do, but how to get it done within an organization, which requires knowing why it should matter to someone who isn’t a technologist."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
いいセリフですわ。
"The nonfunctional requirements are properties of the system that do not necessarily appear directly to the user. They are typically described as the “-ilities.” The ones I focus on most are scalability, availability, maintainability, manageability, monitorability, extensibility, interoperability, portability, security, and performance."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
非機能要件の短い説明として良い。
ちなみに、共通フレーム2013では下記プロセスがアーキテクチャに関係する。
- 2.1.1 システム化構想の立案プロセス
- 2.1.2.2.7 システム化機能の整理とシステム方式の策定
- 2.3.3 システム方式設計プロセス
- 2.4.3 ソフトウェア方式設計プロセス
"This document, the architecture definition, serves as the technologist’s answer to the blueprint. It should be structured in four broad categories to include business, application, data, and infrastructure perspectives, and expressed with clarity and decisiveness, using primarily testable statements as valid propositions (which we’ll examine in the next chapter) and math."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
アーキテクチャ定義書に書かれるべき内容。勉強になる。
"Keeping the design “simple” often defers the interests of flexibility until later, where it becomes very expensive."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
simplicityですら銀の弾丸ではない。
"But to ensure that your technology and architecture decisions are truly supportive of the business—that is, give it the best chance to create competitive advantage—they need to be not shopping lists of shiny objects, but squarely strategic."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
ここすごい良い。「ただし、テクノロジとアーキテクチャの決定がビジネスを本当に支えていること、つまり競争上の優位性を生み出すための最良の機会を与えることを確実にするためには、光沢のあるオブジェクトのリストを買うのではなく、戦略的に戦略を立てる必要があります。」
"Many companies have a Chief Strategy Officer or VP of Corporate Strategy. Strategy season frequently begins in the spring, giving this person and her team a couple of months to prepare a deck to present to the executive leadership team in the late summer. This will be discussed, revised, and eventually approved and used as input for budget season, which begins in the fall and continues until the budget for the following year is approved. We in technology tend to like to see our ideas realized moments after we have them. Being aware of this calendar and corporate planning process will help you plan for adding any big-ticket items to the slate in time for them to receive the necessary attention, support, and budget allocations."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
全く考えたことなかった。
"One assertion of this book is that the roles of Chief Architect and Chief Strategist are more blurred, and more aligned, than ever, and that their mutual understanding of each other’s concerns and methods will be an increasingly important driver for winning organizations."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch01.html
「この本の主張の1つは、チーフアーキテクトとチーフストラテジストの役割がこれまで以上にぼやけていて、一致していること、そして互いの懸念や方法についての相互理解が、優勝する組織にとってますます重要な原動力になるということです。」
自分は戦略に興味があったが、アーキテクチャにも興味を持つべきらしい。
"In these cases, you need to ask clarifying questions about the concerns she expects you to address, and the scope of the recommendations she expects, so that you aim at the right level."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/part02.html
戦略の適切なスコープを上司と握ることが必要。
"Because there is not unlimited money and time to invest in everything, strategy is about making the right recommendations to minimize organizational damage and positional disadvantage, and maximize advantage, profit, and benefit."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch02.html
やはり戦略はトレードオフだな。
"The single most important thing you can do to improve your chances of making a winning technology is to become quite good at making lists."
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch02.html
「あなたが勝つ技術を作る可能性を改善するためにあなたがすることができるただ一つの最も重要なことはリストを作ることでかなりよくなることです。」
リストを1番最初のスキルに持ってくるのはなかなか面白い。
"This formula is MECE:
Profit = Revenue – Cost"
via Check out this quote from Technology Strategy Patterns - https://learning.oreilly.com/library/view/technology-strategy-patterns/9781492040866/ch02.html
式はMECEなのか！結構感動。
