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 Oct 30, 2008
During PDC 2008, David Langworthy, Architect at Microsoft, and Don Box, Distinguished Engineer at Microsoft, held a presentation about Oslo, focusing especially on the modeling language M, explaining what is and what is not, and also demonstrating using M to create a data model.
According to Don, Oslo is constituted by the following components:
Don explains they chose a modeling language because they wanted to offer a design tool which allows working with models textually. M allows one to create a model by typing like creating a program in other languages.
According to Don, M is:
- “M” is a language for defining domain models and textual domain-specific languages (DSLs)
- M domain models define schema and query over structured data
Values, Constraints, and Views
Natural projection to SQL- M DSLs define projections from Unicode text to structured data
Rule-based transformation
Grammar-driven text editor integration
"M is about capturing, schematizing and transforming data", says Don. M offers only a representation of data, has no data related behavior, so there is no polymorphism. Typing is done by structural typing, the way represented data is structured.
M is not an OOP language. M is not a data access technology. While all the data can be transported to/from a database, M is not an OLTP solution, and it is not a T-SQL replacement.
In a live demonstration, David creates a data model, stores the data to a database and retrieves it later from there. He shows some features of the language like constraints, identity, value types, functions, and others.
The Oslo SDK can be downloaded from MSDN.
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