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 Alex Blewitt on Jun 03, 2009
OSGi's APIs were designed against the Java 1.1 platform, and as such use older classes like Dictionary and lack some of the newer Java language features like Generics. Although this has allowed OSGi to run on anything from a high-end supercomputer to a low-end mobile phone, the sweet spot of application development (combined with Java 1.4's End-of-Life) process) is now focussed on Java 1.5, 1.6 or 1.7 (or whatever marketing monikers they happen to be known by).
To that end, there has been experimental investigation to provide a newer version of the OSGi libraries that will support generics. This has been possible with the advent of a compatibility layer (referred to as thunking) which performs on-the-fly translation between the Java 5 variant and the traditional one.
Peter Kriens and BJ Hargrave gave the TS-4966 talk at JavaOne 2009 with lessons learned from this prototype, including how OSGi can take advantage of the JSR 294 language features due to come out for 1.7. Although this is still at the investigation phase, it will further bolster the widespread adoption of OSGi.
Free Gartner Cloud Service Brokerage Report
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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