Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Oct 17, 2007
When .NET 3.5 is released later this year, it will include several changes to the "red bits" including new types and methods. Scott Hanselman has posted a list of new types and methods with links to the MSDN documentation.
The so-called "red bits" are any libraries that existed in .NET 2.0 or 3.0. As .NET 3.5 is not supposed to be a major release of the .NET framework, changes to red bits were supposed to be minimal. This is in contract to the "green bits" which consist solely of new libraries.
Several of the new methods are in support of the new class DateTimeOffset. This is a date/time type with support for time zone information. This replaces the DateTime class for many scenarios.
New enumerations for the garbage collector suggest that developers are going to be getting more control over how the garbage collector functions. This is a break with earlier .NET designs which, unlike Java, pretty much expect the developer to not need to tune the GC.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A practical guide to choosing the right agile tools
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
At first I thought the title for this article was an error, but no, it seems they really have gone and added new types and methods to SP1 for .NET 2.0. What are they thinking? Java learned from this mistake years ago, so now all update releases for the same major version contain no new classes or methods, just big fixes and performance improvements. And thats the way it should be.
Why?
It's not the same version number?
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
3 comments
Watch Thread Reply