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 Aug 05, 2009
Spec# is a research language based on C#. It is based contract-first principals where the pre- and post-conditions for functions can be defined declaratively. Other features include class invariants, non-nullable reference types, and enhanced static analysis capabilities.
While key features like Code Contracts have found their way into .NET 4, Spec# itself has languished in research status. Recently Microsoft has announced that it is finally loosening the reins on it, but only by a little bit. The source code for Spec# is now available on CodePlex under the Microsoft Research Shared Source License Agreement. This license restricts its use to non-commercial purposes.
Hand in hand with Spec# is Boogie, an intermediate language for code verification. Boogie isn’t .NET specific, other languages it supports include “the HAVOC and vcc verifiers for C, the Dafny language and verifier, and the concurrent language Chalice”.
Boogie is also the name of a tool. The tool accepts the Boogie language as input, optionally infers some invariants in the given Boogie program, and then generates verification conditions that are passed to an SMT solver. The default SMT solver is Z3.
Boogie has been released under the Microsoft Public License, which conforms to Free/Open Source standards.
Currently Microsoft is positioning Code Contracts as the way forward, meaning Spec# probably won’t see much in the way of future development.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
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