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 Marcie Jones on Jul 13, 2006
While most .NET developers have heard of reflection, many have not yet implemented reflection in their applications to its fullest potential. Essentially, reflection is the run-time examination of an object's members. Zach Smith's reflection article on TechRepublic provides sample code and a few suggested uses for reflection:
Reflection can be used to implement a wide range of functionality. Most serialization engines use reflection to extract data from the objects that need to be serialized. Reflection can also be used to create customizable application architectures through the use of plug-in modules. Many Object Relation Modeling (ORM) solutions also take advantage of reflection to implement dynamic mapping functionality
A few other suggestions: code generation, accessing private members of 3rd party objects(such as Microsoft controls), and dynamically generating unit tests based on an object's methods. The possible uses of reflection are endless. How many more can you come up with?
In addition, with .NET 2.0 provides a new DynamicMethod class in the System.Reflection.Emit namespace that provides even faster access to an object's properties or fields. This class allows direct access to the Intermediate Language (IL) generated for the object, with much faster execution than traditional reflection techniques in .NET 1.x. Read more about these techniques in Fast Dynamic Property/Field Accessors.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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