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 Floyd Marinescu on May 17, 2006
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Monitor your Production Java App - includes JMX! Low Overhead - Free download
18 agile and lean practices for effective software development governance
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Better IDE support for groovy would be nice !
Hello Horia,
I am totally with you on that; but Groovy has already a nice integration with Eclipse to write, run and debug scripts ( groovy.codehaus.org/Eclipse Plugin ).
One of the hard part about the IDE and Groovy is related to one of the benefits of Groovy: it is a dynamic language. So it makes sometimes hard to support some basic features such as code completion are very challenging... How the IDE would know how/what to complete since you are invoking a dynamic method/property that does not exist in the object..
However, I am very very interested to know the kind of features you would like to see for a Groovy editor...
Regards
Tug blog.grallandco.com
Hello Tug,
I am aware of the dificulties dynamic languages bring to code completion, refactoring ( some say they are even imposible ) but syntax coloring is not enough.
Partial code completion would be nice, code templates, automatic imports, etc.
Regards,
Horia
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