I have toes in both the Rails and the Django camps. From what I see, the Rails folks really get testing. They talk about testing in blogs, talk about testing in conferences, and spin off some interesting testing tools (e.g., ScrewUnit) for testing the non-Rails parts of their apps. It's really hard to be part of the Rails community and not test.
The Django community lags behind on the testing front. Django ships with basic support for testing, but you have to look for it. None of current Django books do much more than give testing a footnote, and I rarely see any substantive "how to test" blogs from Django community members. There were no talks on testing at the first DjangoCon.
On the flip side, Rails people are far more likely to get themselves into messes dues to monkeypatching and gem version conflicts (or gems or plugins doing conflicting monkeypatching), so automated testing is essential. The Django projects I've seen have been able to skate by because it's harder to get yourself into the same trouble.
As for other agile practices, it's hard to say without being able to peek inside of a lot of projects on a day-to-day basis.
Alt.Net strikes me as a group where you could bring various Agile practices and get various results as some may like them and some may have had problems with them.
Agile is more about process rather than specific technologies usually, though. If your question is more about what technologies and frameworks do companies using Agile embrace, that is a whole other ball of wax with questionable value to my mind. The companies near me, in Calgary, Alberta, that embrace Agile may be vastly different than others,e.g. what companies in Bangalore, India or London, U.K. or Silicon Valley or New York City, New York or Seattle, Washington to give a few locations where there are some developers working, usually unless you mean companies like Thoughtworks that do Agile if you are near a large city where they have an office.
Another line of thought would be to consider how some technologies may have various sub-communities or size that may cloud things here. For example, there are likely many Java and .Net developers that embrace Agile and many that loathe it. If some companies have a Waterfall methodology that works well for them, why should they switch to Agile? At the same time, some technologies may have really small communities and so they may be viewed in a much different light. There is also how well organized would the people using these new and emerging technologies be if that is a factor to your mind.
Hopefully someone found this brain dump interesting... ;)
I don't think any of these workflows are tied to a specific language, nor do I think any language necessarily lends itself to these workflows. Any deviation from this is largely cultural.
For example, the canonical rails project skeleton has a very low barrier to writing tests or using TDD, but there's nothing stopping you from grabbing NUnit and writing a TDD .NET project.
Here are some .NET tools you might be interested in researching:
From my somewhat limited experience I have found that the Ruby/rail community has been pushing the cutting edge on testing. Introducing new technologies and generally integrating the concept of TDD and BDD into most things. PHP on the other hand is somewhat haphazard. Some groups use it religiously and other seemingly not at all. The toolset in PHP does not seem as robust and deep as it is in the Ruby & Rails communities.
发布评论
评论（4）
我对 Rails 和 Django 阵营都有兴趣。 据我所知，Rails 人员确实进行了测试。 他们在博客中谈论测试，在会议中谈论测试，并衍生出一些有趣的测试工具（例如 ScrewUnit）来测试其应用程序的非 Rails 部分。 成为 Rails 社区的一员而不进行测试真的很难。
Django 社区在测试方面落后了。 Django 附带了对测试的基本支持，但您必须寻找它。 当前的 Django 书籍除了给测试提供脚注之外，没有做更多的事情，而且我很少看到 Django 社区成员发表任何实质性的“如何测试”博客。 第一届 DjangoCon 上没有关于测试的讨论。
另一方面，Rails 人员更有可能因猴子补丁和 gem 版本冲突（或宝石或插件进行冲突的猴子补丁）而陷入混乱，因此自动化测试至关重要。 我见过的 Django 项目都能够顺利通过，因为你很难陷入同样的麻烦。
至于其他敏捷实践，如果不能每天深入了解大量项目的内部情况，就很难说。
I have toes in both the Rails and the Django camps. From what I see, the Rails folks really get testing. They talk about testing in blogs, talk about testing in conferences, and spin off some interesting testing tools (e.g., ScrewUnit) for testing the non-Rails parts of their apps. It's really hard to be part of the Rails community and not test.
The Django community lags behind on the testing front. Django ships with basic support for testing, but you have to look for it. None of current Django books do much more than give testing a footnote, and I rarely see any substantive "how to test" blogs from Django community members. There were no talks on testing at the first DjangoCon.
On the flip side, Rails people are far more likely to get themselves into messes dues to monkeypatching and gem version conflicts (or gems or plugins doing conflicting monkeypatching), so automated testing is essential. The Django projects I've seen have been able to skate by because it's harder to get yourself into the same trouble.
As for other agile practices, it's hard to say without being able to peek inside of a lot of projects on a day-to-day basis.
如果社区是关于人的，那么还有什么才是真正的社区，这里有几个小组：
敏捷项目领导网络 其名称暗示它拥抱敏捷方法。
Alt.Net 给我的印象是，你可以在其中引入各种敏捷实践并获得各种结果，因为有些人可能会喜欢它们，并且有些人可能遇到了问题。
不过，敏捷通常更多的是关于过程而不是特定的技术。 如果您的问题更多是关于使用敏捷的公司采用哪些技术和框架，那么在我看来，这完全是另一个价值值得怀疑的蜡球。 我附近的阿尔伯塔省卡尔加里拥抱敏捷的公司可能与其他公司有很大不同，例如印度班加罗尔或英国伦敦或硅谷或纽约市或华盛顿州西雅图的哪些公司提供一些地点有一些开发人员在工作的地方，通常除非您指的是像 Thoughtworks 这样的公司如果您靠近有办事处的大城市，请进行敏捷开发。
另一种思路是考虑某些技术如何可能具有各种子社区或规模，从而可能使这里的事物变得云彩。 例如，可能有许多 Java 和 .Net 开发人员拥抱敏捷，但也有许多人厌恶它。 如果一些公司的瀑布方法很适合他们，那么他们为什么要转向敏捷呢？ 与此同时，某些技术的社区可能非常小，因此人们可能会以截然不同的角度来看待它们。 如果您考虑到这一点，那么使用这些新兴技术的人们的组织性也会如何。
希望有人觉得这个大脑转储很有趣......;)
If by communitry this is about people, as what else is a community really, here are a few groups:
Agile Project Leadership Network has the implication in its name that it embraces Agile approaches.
Alt.Net strikes me as a group where you could bring various Agile practices and get various results as some may like them and some may have had problems with them.
Agile is more about process rather than specific technologies usually, though. If your question is more about what technologies and frameworks do companies using Agile embrace, that is a whole other ball of wax with questionable value to my mind. The companies near me, in Calgary, Alberta, that embrace Agile may be vastly different than others,e.g. what companies in Bangalore, India or London, U.K. or Silicon Valley or New York City, New York or Seattle, Washington to give a few locations where there are some developers working, usually unless you mean companies like Thoughtworks that do Agile if you are near a large city where they have an office.
Another line of thought would be to consider how some technologies may have various sub-communities or size that may cloud things here. For example, there are likely many Java and .Net developers that embrace Agile and many that loathe it. If some companies have a Waterfall methodology that works well for them, why should they switch to Agile? At the same time, some technologies may have really small communities and so they may be viewed in a much different light. There is also how well organized would the people using these new and emerging technologies be if that is a factor to your mind.
Hopefully someone found this brain dump interesting... ;)
我不认为这些工作流程中的任何一个都与特定语言相关联，也不认为任何语言都一定适合这些工作流程。 任何偏离这一点的行为很大程度上都是文化造成的。
例如，规范的 Rails 项目框架对于编写测试或使用 TDD 的障碍非常低，但是没有什么可以阻止您使用 NUnit 并编写 TDD .NET 项目。
以下是您可能有兴趣研究的一些 .NET 工具：
单元测试：
持续集成：
I don't think any of these workflows are tied to a specific language, nor do I think any language necessarily lends itself to these workflows. Any deviation from this is largely cultural.
For example, the canonical rails project skeleton has a very low barrier to writing tests or using TDD, but there's nothing stopping you from grabbing NUnit and writing a TDD .NET project.
Here are some .NET tools you might be interested in researching:
Unit Testing:
Continuous Integration:
根据我有限的经验，我发现 Ruby/rail 社区一直在推动测试的前沿。 引入新技术，并将TDD和BDD的概念普遍融入到大多数事物中。 另一方面，PHP 则有些随意。 有些团体虔诚地使用它，而另一些团体则似乎根本不使用它。 PHP 中的工具集似乎不像 Ruby 和 PHP 中那样强大和深入。 铁路社区。
YMMV。
From my somewhat limited experience I have found that the Ruby/rail community has been pushing the cutting edge on testing. Introducing new technologies and generally integrating the concept of TDD and BDD into most things. PHP on the other hand is somewhat haphazard. Some groups use it religiously and other seemingly not at all. The toolset in PHP does not seem as robust and deep as it is in the Ruby & Rails communities.
YMMV.