Learn the platform before writing production code!
Often people just jump in and start writing their app, and it becomes a mess, the developers learn lots then regret the "noob" stuff they did, but are locked in.
So my theory is take a few spikes and go throughan implement a very very thin feature that goes through all layers of a framework.
ie, say if it was a web mvc / web services..... something that has javascript - > ajax -> html -> web service -> Controller -> Model -> Database.
Get people to review it. Don't spend time building a framework layer when you don't know a lot about the Technology you are dealing with. Spend some time exploring what kind of flexibility your technology has (ie, try a number of different ways you can skin a cat)
假设您拥有一支熟练的开发人员团队，并且新技术在某种程度上相当于该团队历史上所做的事情，那么几乎每次实践学习的努力都会击败 RTFM。例如，我可以看到与一群 Java Web 开发人员一起进行 .NET Web 开发，但我不太愿意与一个专注于 VB Windows 应用程序的团队一起进行 .NET Web 开发。您应该从跨越所有层的基本功能的峰值开始。最佳实践是在团队中添加一两名专家，以通过结对编程来帮助指导和指导开发过程。出于估计目的，我将显着减少允许团队在前几次迭代中进行的故事点的数量。保守地说，我计划在前几次迭代中实现不超过团队历史速度的一半。
Hands-on learning effort will beat RTFM almost every time assuming you have a team of skilled developers and the new technology is somewhat equivalent to what the team has historically done. For example, I could see undertaking .NET web development with a bunch of Java web developers, but I would not be very comfortable undertaking .NET web development with a team that has been focused on VB Windows applications. You should start with spikes of basic functionality that span all layers. Best practice would be to add an expert or two to the team to help mentor and guide the development process via pair programming. For estimating purposes, I would significantly reduce the number of story points I would allow the team to undertake in the first few iterations. Conservatively, I would plan on achieving no more than half the team's historical velocity in the first few iterations.
What about some sort of code-review or related step where some experienced person could glance through and offer suggestions.
RTFM seems like it would just waste time, especially if you are doing agile development.
EDIT: Since you said 'nobody' in the team knows the language... I don't know, but RTFM still seems like a waste of time to try and 'learn the whole language' before you start.
Most of the teams I've been on have had at least one language enthusiast. These guys love to learn everything they can about new languages and are more than happy to share. Figure out who this person is on your team and let them know that you're going to be working with the new language.
Once you start, do code reviews. Lots of them on small, manageable pieces of code. The code enthusiast will be able to point out things that are handled better by the language. The whole team learns this way.
发布评论
评论（5）
在编写生产代码之前先了解平台！
通常人们只是跳进去开始编写他们的应用程序，然后它就变得一团糟，开发人员学到了很多东西，然后后悔他们所做的“菜鸟”东西，但被锁定了。
所以我的理论是采取一些尖峰并通过一个非常好的实现非常薄的功能，贯穿框架的所有层。
即，假设它是一个 Web MVC / Web 服务.....具有 javascript 的东西 - >阿贾克斯-> html->网络服务->控制器->型号->数据库。
让人们审查它。当您对正在处理的技术了解不多时，不要花时间构建框架层。花一些时间探索你的技术具有什么样的灵活性（即，尝试多种不同的方法来给猫剥皮）
Learn the platform before writing production code!
Often people just jump in and start writing their app, and it becomes a mess, the developers learn lots then regret the "noob" stuff they did, but are locked in.
So my theory is take a few spikes and go throughan implement a very very thin feature that goes through all layers of a framework.
ie, say if it was a web mvc / web services..... something that has javascript - > ajax -> html -> web service -> Controller -> Model -> Database.
Get people to review it. Don't spend time building a framework layer when you don't know a lot about the Technology you are dealing with. Spend some time exploring what kind of flexibility your technology has (ie, try a number of different ways you can skin a cat)
我认为，以及其他人一样，拥有一个良好的心智模型并理解您将使用的抽象很重要......但是，有时它并不那么容易，可能是因为时间、经验甚至文档不足。
您可以在这里得到一些想法： http://www.se-radio.net/podcast/2009-06/episode-138-learning-part-development-allan-kelly
还有一种将学习作为其战略部分的敏捷方法：自适应软件开发 (ASD) http:// en.wikipedia.org/wiki/Adaptive_Software_Development
最后，我想提一下测试驱动开发中的探索性测试，它可以帮助学习新框架http:// en.wikipedia.org/wiki/Exploratory_testing。
I think, as well as other, that it is important to have a good mental model and to understand abstractions you will use... However, sometimes it is not as easy, maybe because of insufficient time, experience or even documentation.
You can get some thoughts here: http://www.se-radio.net/podcast/2009-06/episode-138-learning-part-development-allan-kelly
There is also an agile methodology which takes learning as its strategic part: Adaptive Software Development (ASD) http://en.wikipedia.org/wiki/Adaptive_Software_Development
Lastly, I want to mention exploratory tests in Test Driven Development, which can help with learning new frameworks http://en.wikipedia.org/wiki/Exploratory_testing .
假设您拥有一支熟练的开发人员团队，并且新技术在某种程度上相当于该团队历史上所做的事情，那么几乎每次实践学习的努力都会击败 RTFM。例如，我可以看到与一群 Java Web 开发人员一起进行 .NET Web 开发，但我不太愿意与一个专注于 VB Windows 应用程序的团队一起进行 .NET Web 开发。您应该从跨越所有层的基本功能的峰值开始。最佳实践是在团队中添加一两名专家，以通过结对编程来帮助指导和指导开发过程。出于估计目的，我将显着减少允许团队在前几次迭代中进行的故事点的数量。保守地说，我计划在前几次迭代中实现不超过团队历史速度的一半。
Hands-on learning effort will beat RTFM almost every time assuming you have a team of skilled developers and the new technology is somewhat equivalent to what the team has historically done. For example, I could see undertaking .NET web development with a bunch of Java web developers, but I would not be very comfortable undertaking .NET web development with a team that has been focused on VB Windows applications. You should start with spikes of basic functionality that span all layers. Best practice would be to add an expert or two to the team to help mentor and guide the development process via pair programming. For estimating purposes, I would significantly reduce the number of story points I would allow the team to undertake in the first few iterations. Conservatively, I would plan on achieving no more than half the team's historical velocity in the first few iterations.
某种代码审查或相关步骤怎么样，有经验的人可以浏览并提供建议。
RTFM 似乎只会浪费时间，特别是如果您正在进行敏捷开发。
编辑：既然你说团队中“没有人”懂这种语言......我不知道，但在你之前尝试“学习整个语言”似乎仍然是浪费时间开始。
What about some sort of code-review or related step where some experienced person could glance through and offer suggestions.
RTFM seems like it would just waste time, especially if you are doing agile development.
EDIT: Since you said 'nobody' in the team knows the language... I don't know, but RTFM still seems like a waste of time to try and 'learn the whole language' before you start.
我加入过的大多数团队都至少有一名语言爱好者。这些人喜欢学习有关新语言的一切知识，并且非常乐意分享。弄清楚这个人是您团队中的成员，并让他们知道您将使用新语言。
一旦开始，就进行代码审查。其中很多都在小的、可管理的代码片段上。代码爱好者将能够指出该语言可以更好地处理的事情。整个团队都是这样学习的。
Most of the teams I've been on have had at least one language enthusiast. These guys love to learn everything they can about new languages and are more than happy to share. Figure out who this person is on your team and let them know that you're going to be working with the new language.
Once you start, do code reviews. Lots of them on small, manageable pieces of code. The code enthusiast will be able to point out things that are handled better by the language. The whole team learns this way.