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 May 14, 2009
Dynamic languages like Python and Ruby seem to be all the rage these days. And with the Iron versions, they are far more accessible to .NET developers. So if you are looking to make the switch from C# or VB to Python, there has never been a better time.
With the guarantees offered by the Common Language System, you should be able to maintain your legacy assets as DLLs while writing new code in IronPython. But sometimes developers need or want to pull everything into one package.
If you find yourself in that situation, SharpDevelop has you covered. SharpDevelop 3.1 if offering a feature that can convert C# and VB code into IronPython code. This can be done at either the file or project level using SharpDevelop's parsing library NRefactory.
This isn’t the first time SharpDevelop offered code conversion support for Python.
Converting code to IronPython was originally supported in SharpDevelop 2.2 and was based on converting code to a Microsoft CodeDOM and then getting IronPython 1.0 to generate the Python code. In IronPython 2.0 this CodeDOM support was removed so the code conversion feature was removed from SharpDevelop 3.0 since that was using IronPython 2.0. In SharpDevelop 3.1 the code conversion has been rewritten to no longer use the CodeDOM support.
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
Agile Maturity Model Applied to Building and Releasing Software
Monitor your Production Java App - includes JMX! Low Overhead - Free download
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