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 Charlie Martin on Jan 26, 2009
Chef is a new open-source system integration, configuration management and provisioning application, released under the Apache 2.0 license by Opscode, in Seattle, Washington. Chef operates by defining system nodes, cookbooks for performing administrative tasks, and libraries for defining interactions with other tools such as applications, databases, and system administration resources like LDAP directories.
Chef is implemented as a Ruby-based DSL which is interpreted by Chef clients, working under the direction of a Chef server. Clients authenticate themselves to the server using OpenID, then synchronize the needed resources and libraries automatically. These resources are then used by the client to perform steps toward configuring the client node, a process called convergence. The ideal is that the configuration should be completed in one step; if it can't be, then the goal is for the client to make progress with later invocations in order to "converge" on the desired final state.
While Chef has just been announced, and is still an early version, it is being used in production in several installations.
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
A Guide to Branching and Merging Patterns
18 agile and lean practices for effective software development governance
Getting Started with Stratos - an Open Source Cloud Platform
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.
2 comments
Watch Thread Reply