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 James Vastbinder on Jun 05, 2008
Late last month, Jeffery Olson announced BooLangStudio on the Boo Language Users mailing list. Olson’s effort now makes it possible to write Boo code in Visual Studio 2008 and take advantage of Visual Studio IDE features.
The first release of the Visual Studio plugin is primarily a proof of concept and Olson warns developers:
Check it out at: http://www.codeplex.com/BooLangStudio
Please note that it is VERY rough around the edges currently. The Microsoft Visual Studio 2008 SDK is a dependency, also. And lots of other stuff that I didn't mention.
The current release is version 0.1.2 and development on version 0.2 is actively progressing and is intended to feature:
Around the same time, Cedric Vivier announced the latest release of Boo, 0.8.2 with the following enhancements from the Boo web site:
InfoQ has covered Boo in the past providing a primer on the language and highlighted as an ideal host language for creating Domain Specific Languages.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
SCM best practices for multiple processes, releases & distributed teams
A Guide to Branching and Merging Patterns
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
I should have included this in the news post...
Thank you very much for highlighting the project. It should be noted, though, that I'm not at all the sole contributor to this project. James Gregory is doing a great job of working towards a working intellisense implementation. Torkel Ödegaard has pitched in some great bug fixes. Justin Chase and Chris Bilson are working independently towards a working, proper installer for the project.
I want to point out that the "critical path" for BooLangStudio is implemented, that is: You can open SharpDevelop .booproj projects or create new ones, you can edit non-trivial code and have it be compiled within the IDE (including macros and all of that, provided you satisfy dependencies as needed). Syntax-highlighting is in place, but it could quite fairly be described as "incomplete". This is being worked on.
Basically everything else is missing, to include: intellisense, debugging support (breakpoints), and all the other stuff you're used to being pampered with when dev'ing on managed code in VS2008.
thank you guys working on it!
I love boo too.
I wish this IDE too long. Before, I writed boo in SharpDevelop and MonoDevelop.
Who needs another language? Anyone heard about Python?
Boo seems like Python wannabe. Do I care whether it compiles?? I apologize for the sarcarsm but in all honesty, the value proposition is more important than its features.
Good Luck with it! =D
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.
5 comments
Watch Thread Reply