项目经理到建筑师过渡？ [英] Program Manager to Architect transition?
问题描述
在担任项目经理3年之前，我已经担任项目经理5年了。这是我职业生涯的全部。我通常的工作日是编写功能规范或解决沟通问题。我没有编写
代码行的经验，除了娱乐目的。但是我目前的角色与开发人员团队密切合作。
我有没有办法成为.Net架构师？如果是这样的话？是否有证书可以获得或者我需要的是什么。
你可能想问我为什么要改变？我在这里面临一个实际问题，在地理上与我的妻子分开。她的国家对项目经理来说市场并不多。但我确实为.Net架构师看到了很多空缺。
提前感谢你的回答。
- Pulped
简短的回答是肯定的，你可以成为一名建筑师，但困难取决于你的意思术语。
首先，让我们澄清一下条款 - 公司称之为"架构师"的工作角色很多，而且它们通常分层工作，从最一般到最具体的。 Enterprise Architect是最通用的，通常管理整个解决方案的
结构（包括硬件，软件，网络组件等）。设计软件解决方案的架构师就在其下方，其中可能包括数据建模，服务端点定义，第三方工具和库
以及与它们的交互等。接下来是技术主管，有时也是叫建筑师。技术主管对应用程序的结构做出较低级别的决策 - 比如使用哪种架构模式，哪些ORMs b $ b适合，日志框架以及其他特定于技术的决策。
我认为您最简单的过渡将属于中间类别。您需要高水平的技术理解 - 特别是，您可能需要了解良好的数据库设计，SOA和其他大型架构，web
对桌面与移动的影响，以及类似的东西。但是，一旦你有了这个基础，很大一部分工作就是考虑业务需求并选择最佳解决方案来完成它们 - 可能与计划/产品和项目经理密切合作。
<企业架构师通常只落后于高管，他们需要相当多的IT经验或作为中级架构师才能获得资格。技术主管必须对他们正在使用的开发平台有一个深入的了解，
并且通常必须拥有该平台的大量经验才能做出他们必须做出的决策。如果您具有管理，组织，项目规划和业务需求经验，那么中级架构师可能是一个可行的角色。
I have been a Program Manager for 5 years now, before that 3 years as a project manager. This is all of my career. My usually work days is made up of writing functional specification, or solving communication issues. I don't have experience of writing a line of code except for recreational purposed. But I work very closely with the developer's team in my current role.
Is there a way I can become a .Net architect? If so how? Is there certificate to gain or what exactly is the things I would need.
You may want to ask me why the change? I am facing a practical issue here, being separated with my wife geographically. There is not much of a market is her country for Program Managers. But I do see a lot of openings for .Net architects.
Thanks in advance for your kind answers.
- Pulped
The short answer is yes, you could make the move to being an architect, but the difficulty will depend on what you mean by the term.
First off, let's clarify terms - there are a lot of different job roles that companies call "architect", and they typically work in layers from the most general to the most specific. The Enterprise Architect is the most general, and typically manages the structure of an entire solution (including hardware, software, networking components, etc.). Just below them is the architect who designs the software solution, which may include data modeling, service endpoint definitions, third party tools and libraries and the interactions with them, etc.. Next is the Technical Lead, who is also sometimes called an architect. The technical lead makes the lower level decisions about the structure of the application - things like which architectural patterns to use, what ORMs will fit, logging frameworks, and other technology-specific decisions.
I think your easiest transition would be into the middle category. You would need a high level of technical understanding - in particular, you'll probably need to understand good database design, SOA and other large-scale architectures, implications of web vs desktop vs mobile, things like that. Once you have that basis, though, a large part of the job is taking business requirements and choosing the best solutions to accomplish them - probably working very closely with Program/Product and Project Managers.
Enterprise Architects typically fall just below executives, and they need quite a bit of experience in either IT or as a mid-level architect to qualify. Technical leads have to have an intimate understanding of the development platforms they're working with, and usually have to have a lot of experience with that platform to be able to make the decisions they have to make. A mid-level architect could be a feasible role if you have management, organizational, project planning, and business requirement experience.
这篇关于项目经理到建筑师过渡？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
