Concurrency: Past and Present
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Tracking change and innovation in the enterprise software development community
Posted by Deborah Hartmann on Oct 16, 2006 06:31 AM
During the 2004-2005 academic year, Pam Rostal and Dave West ran a unique work-study degree program at New Mexico Highlands University: 20 students using Agile practices to execute real world projects. The premise: if healthy relationships could be maintained between people, software, systems, craft and agility, teams would exhibit software development superiority, leading to the central promise of the program – development teams capable of delivering 10 times as well as their average counterparts. InfoQ brings you an experience report on this unusual educational approach.Everything we did required a variance of one type or another, from allowing multiple courses to be scheduled at the same time in the same room taught by multiple faculty to the physical space requirements; but the attitudes we hoped to instill would only emerge from applying non-traditional pedagogical patterns emphasizing responsibility, feedback, collaboration, and the invention of new ways to look at a problem.The groundbreaking Software Development Apprenticeship (SDA) program was situated in a prevailing culture that stressed familial obligation, which, coupled with extensive regional poverty, forced students to confront life-work balance issues at a much younger age than many of us. To draw a wider variety of students than the average full-time university program, the program was designed to co-exist with students' other priorities. This six-year program, much of it at a level typically reserved for graduate students, covered the equivalent of a four year bachelor degree and more... and could be executed at each student's own pace, organized around their other obligations each semester, allowing for individualized progress through the program.
Read the InfoQ experience report: Software Development Utopia: Agile Development Apprenticeship at NMHU.Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
The End of Middleware: Freedom from IT Stacks as we know it
Six Free Project Management Certification Training Courses
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
The Agile Business Analyst: Skills and Techniques needed for Agile
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
No comments
Reply