Empower Developers
来源:互联网 发布:淘宝 卖家客服电话 编辑:程序博客网 时间:2024/06/05 00:17
Empower Developers
Timothy High
Things are usually easier said than done, and software architects are notoriously good at coming up with things to say. To keep your words from becoming a lot of hot air (generally the key ingredient in making vaporware), you need a good team of developers. The role of an architect is usually to impose constraints, but you also have the opportunity to be an enabler. To the extent your responsibilities allow, you should do everything possible to empower your developers.
Make sure developers have the tools they need. Tools shouldn’t be imposed on developers, they should be carefully chosen to make sure they are the right tools for the job at hand. Repetitive and mindless work should be automated wherever possible. Also, it is well worth the investment to make sure developers have top-notch machines to work with, adequate network bandwidth, and access to software, data, and information necessary to carry out their work.
Make sure they have the skills they need. If training is required, make sure they get it. Invest in books and promote active discussions about technology. The work life of a developer should be hands-on and practical, but also should be actively academic. If you have the budget for it, send your team to technical presentations and conferences. If not, get them involved in technical mailing lists and look for free events in your city. As much as possible, participate in the developer selection process as well. Look for developers that are hungry to learn, that have that little “spark” that says they really dig technology (also make sure they can play ball with the team…). It’s hard to get a big bang out of a team of duds.
Let developers make their own decisions wherever it won’t contradict the overall goal of the software design. But put constraints where they count, not only to guarantee quality, but also to further empower developers. Create standards for the sake of consistency, but also to reduce the number of troublesome, insignificant decisions that aren’t part of the essential problem developers are solving. Create a clear roadmap for where to put their source files, what to call them, when to create new ones, and so on. This will save them time.
Lastly, protect developers from nonessential parts of their job. Too much paperwork and too many office chores add overhead and reduce their effectiveness. You (usually) aren’t a manager, but you can have influence on the processes surrounding software development. Whatever processes are used, make sure they are designed to remove obstacles, not increase them.
Timothy High
Things are usually easier said than done, and software architects are notoriously good at coming up with things to say. To keep your words from becoming a lot of hot air (generally the key ingredient in making vaporware), you need a good team of developers. The role of an architect is usually to impose constraints, but you also have the opportunity to be an enabler. To the extent your responsibilities allow, you should do everything possible to empower your developers.
Make sure developers have the tools they need. Tools shouldn’t be imposed on developers, they should be carefully chosen to make sure they are the right tools for the job at hand. Repetitive and mindless work should be automated wherever possible. Also, it is well worth the investment to make sure developers have top-notch machines to work with, adequate network bandwidth, and access to software, data, and information necessary to carry out their work.
Make sure they have the skills they need. If training is required, make sure they get it. Invest in books and promote active discussions about technology. The work life of a developer should be hands-on and practical, but also should be actively academic. If you have the budget for it, send your team to technical presentations and conferences. If not, get them involved in technical mailing lists and look for free events in your city. As much as possible, participate in the developer selection process as well. Look for developers that are hungry to learn, that have that little “spark” that says they really dig technology (also make sure they can play ball with the team…). It’s hard to get a big bang out of a team of duds.
Let developers make their own decisions wherever it won’t contradict the overall goal of the software design. But put constraints where they count, not only to guarantee quality, but also to further empower developers. Create standards for the sake of consistency, but also to reduce the number of troublesome, insignificant decisions that aren’t part of the essential problem developers are solving. Create a clear roadmap for where to put their source files, what to call them, when to create new ones, and so on. This will save them time.
Lastly, protect developers from nonessential parts of their job. Too much paperwork and too many office chores add overhead and reduce their effectiveness. You (usually) aren’t a manager, but you can have influence on the processes surrounding software development. Whatever processes are used, make sure they are designed to remove obstacles, not increase them.
- Empower Developers
- Empower Developers
- Contiki-developers
- Oracle Database developers talking to the developers
- The Java Developers Almanac
- C# for Delphi developers
- Books for Developers
- Debian Developers in China
- Interviewing Enterprise Java Developers
- AI for Game Developers
- Talk: Google for developers
- Cryptography for Developers
- Facebook API Developers Guide
- Rails for PHP Developers
- AutoHotkey scripts for developers
- Windows Vista for Developers
- Illuminations for Developers Keygen
- IOS 5 for Developers
- Storyboard的简单使用
- java多线程初步-原子性可见性hanppens-before原则
- extjs中grid的多表头
- CXF wsdl2Java
- 通过Java反射调用方法的实例,通过这个例子,能明白怎么用反射。
- Empower Developers
- 程序员的八荣八耻(转)
- SQLite: trigger触发器
- VC串口编程
- iphone开发之通过unix系统底层获取和系统相关的硬件信息
- VC++获取程序路径
- Nib文件是如何被加载的?
- 影响 Lucene对文档打分的四种方式
- 如何查看本机开放端口