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 Abel Avram on Aug 06, 2008
In this interview, John Lam, Program Manager on the Dynamic Language Runtime team at Microsoft, talks about IronRuby, what it means to .NET supporters and how it has been received by the Ruby community.
Watch: Interview: John Lam About IronRuby (17 minutes)
John says that, generally speaking, IronRuby has been well received both by "kids coming out of school", as he likes to call them, and by veterans like David A. Patterson. When he enters into details, he notices that, while some .NET developers easily embrace a dynamic language, others want languages even more statically strong typed than C#. While everybody has his arguments, John remarks that what it mostly matters today is software shipping, software that is done and delivered quickly, and dynamic languages are good at that.
While it seems natural for the .NET developers to have mixed feelings about IronRuby, everybody would expect the Ruby community to eagerly embrace it. But it does not seem to be so according to John: "You would be surprised by that [Ruby community's attitude towards IronRuby], because I wouldn't say that people in Ruby community are hostile towards our efforts: I think it is worse than that." But John does not stop there and explains why IronRuby matters to the Ruby community.
John also talks about Ruby's scalability and the challenges met trying to introduce a dynamic language into the static world of .NET CLR.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A practical guide to choosing the right agile tools
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