Using Ruby Fibers for Async I/O: NeverBlock and Revactor
Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
Tracking change and innovation in the enterprise software development community
Posted by Vikas Hazrati on Feb 22, 2008 07:45 AM
Consultant and test project manager Fiona Charles recently wrote an interesting article in StickyMinds on leading troubled projects. She says she sometimes seeks out such projects, because they offer tremendous opportunities for creativity and accelerated learning! Though her thoughts are more aligned towards testers, they do give valuable insights into how an agile team can lead a troubled project and try to turn it around.Talk to each other. The hands down number 1 action that can prevent a project from becoming a failure is the free and open exchange of ideas.However, if the project does end up in trouble then the team needs well-defined strategies to try to turn it around.
The strategies I've described can help you maintain the right frame of mind to access your own creativity and devise tactical solutions to project problems. If you can do that, you, too, can enjoy troubled projects and develop your project skills.To turn a project around the team needs to focus heavily on soft skills and inter-personal communication - they can't simply rely on the process. The keys here seem to be positive action and a creative solution-finding attitude** of each team member.
The Agile Business Analyst: Skills and Techniques needed for Agile
Six Free Project Management Certification Training Courses
The End of Middleware: Freedom from IT Stacks as we know it
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
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.
No comments
Reply