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 Oct 03, 2006
The BLINQ demo allows developers to quickly develop CRUD (Create/Read/Update/Delete) style applications. With one command, an entire web site with insert, list, and detail pages is created.
Like most automatic web site generators, this tool creates a site suitable for basic administrative tasks. Though the functionality is limited, the site can be up in running in literally minutes
What makes it different from other CRUD tools is that each page it generates is in the form of declarative C# or VB code in ASPX pages. These pages can then be easily modified or replaced on an as needed basis. Instead of being locked in, developers are merely given a convenient starting point.
Web sites created with BLINQ are more suited to prototypes and back-office users than end-user facing websites. With heavy customization it can be turned into a fully featured site, but it is more likely that developers will grab convenient pages and drop them into existing sites as needed.
BLINQ heavily leverages the LINQ project currently being considered for Visual Studio 2007. This means that BLINQ cannot be used in production code any time soon. On the plus side, there is still plenty of time to comment on the project and request feature changes.
For a walk through of BLINQ, see Patrick Spieler's post.
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Getting Started with Stratos - an Open Source Cloud Platform
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