知识卡片
内部雷达定位组织情境
内部雷达应包括自研能力、战略默认、实际版本与遗留,服务本组织的决定;外部雷达则广泛服务行业客户。因情境不同,不能直接把外部点的位置当内部指令。某能力只有在特定负载合适,可按场景拆点并解释不同环位。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Using a Technology Radar · 查看原书依据
First, while Thoughtworks doesn’t list any in-house tooling that their clients might have created (it’s the clients’ intellectual property, not that of Thoughtworks, after all), your internal radar is under no such restriction. Locating internal solutions in all quadrants, strategic or de facto, along with honest assessments of their applicability and current state as blips
参考来源
- 位置:《Facilitating Software Architecture》第11章《Using a Technology Radar》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch11.html)
- 结论依据:原文区分产权范围与context/focus,并在聚焦阶段给Azure Functions不同场景拆点示例。
- 原始内容:First, while Thoughtworks doesn’t list any in-house tooling that their clients might have created (it’s the clients’ intellectual property, not that of Thoughtworks, after all), your internal radar is under no such restriction. Locating internal solutions in all quadrants, strategic or de facto, along with honest assessments of their applicability and current state as blips