Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Oct 09, 2009
IronRuby has posed a significant challenge for the Microsoft team. Ruby is defined primarily by its premiere interpreter Ruby MRI, also known as CRuby. The ongoing RubySpec project intends to document it, but they are a long way from completion. Most teams trying to implementation a Ruby compiler simply look at the CRuby source code, but this isn’t an option for Microsoft. CRuby is licensed under the GPL, which Microsoft is afraid of for numerous legal reasons. This means they have to reverse engineer it, a daunting feat.
Back in March of 2009, IronRuby was only passing 80% of the documented Ruby Specs. And even then it was running 4.5 times slower than CRuby with a startup time of 10 time slower.
By August, IronRuby had made tremendous advances. It now passes 92.5 % of the specification tests and is running twice as fast as CRuby. The startup time is also greatly improved due to the adaptive compiler. A fully compatible version, labeled IronRuby 1.0, is expected to be ready this fall.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Mobile and the New Two-Tiered Web Architecture
SCM best practices for multiple processes, releases & distributed teams
Monitor your Production Java App - includes JMX! Low Overhead - Free download
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
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.
No comments
Watch Thread Reply