By jettro, on September 14th, 2009
For a project that I am working on Your-Scrum I need a lot of items in a list that are sortable. One Story is to have a backlog with stories that are sortable to reflect the importance. Using Domain Driven Design, I have created a rich domain model. Using the model, we can execute all stories related to sorting items in a list. At the front-end I want an easy way to handle the sorting. I found a library for jQuery that can do the job for a large part on the client. Still there are some server side components as well.
The following screen gives an idea about the look and feel of the sortable list of stories.
Continue reading Creating a sortable list of items using jQuery
By Ben, on September 13th, 2009
The last few days I’ve been reading BAD Astronomy, a book by astronomer Philip Plait that describes common misconceptions, misuses and scientific abuses of astronomy. Partly written to be funny and partly to debunk the nonsense that arises from people misusing and abusing science, it’s a good and worthwhile read for anybody (especially if you have some spare time on your hands).
Philip C. Plait. Wiley 2002, Paperback, 288 pages, $3.64
Reading through the book I came to chapter 14, which deals with the doomsday advocates who swore up and down that the world was going to come to an end on May 5, 2000 due to a planetary alignment (more or less) of Mercury, Venus, Mars, Jupiter and Saturn. It was quite funny to read Plait’s description of why this neither would nor did cause catastrophe for our planet. But more than that, the chapter got me thinking about how bad science is all around us and affects us in sometimes rather drastic ways.
Continue reading Bad science…
By jettro, on September 1st, 2009
As a programmer you are writing code. As a designer you are creating solid designs and if you are wise, the code is a good reflection of your design. My previous post was about Domain Driven Design. One of the things I want to repeat is the strong relation between the domain, the design and the code. The best way to accomplish this is to combine the role of designer and implementer. That way you get the best representation of the domain in your solution.
Why this introduction, when I promised to write about performance and monitoring? For performance I see the same relationship. A tester creates the test plan, including the performance test. If you are lucky requirements for monitoring are available as well. Ok, I do not want to combine the role of tester and developer. Still they should both have a very good idea about what the other one does and how you can help each other. Real performance testing is hard and should not be taken to light. Monitoring however can be done on a low level during development. How often have you written log statements like: This method X is executed. Sometimes with a start and end time. Some of you might have used there own aspects to be non intrusive and other might have used a framework.
This blog post is about using a framework to do basic performance measurement and monitoring. The framework I am going to discuss is the Beet framework.
Beet records user behavior and performance data for your Spring-based Java application. It can thus help you to analyze usage patterns and research production performance issues.
Read on to learn about my experiences with the framework and why I like it to do some basic monitoring.
Continue reading Using Beet to monitor your (spring framework) application
Popular