Monday, July 23, 2012

The value of methods in an agile world

Interesting definition of an agile method from this article.

A method is the way a team works to accomplish its goals. It describes how responsibilities are identified and assigned, what techniques are applied, and how success criteria are identified and achieved.

Documented methods enable an organization to:
  • Define clear responsibilities and critical sequences of events
    As teams become highly distributed, it becomes important to have information available at all times and from all places in some documented form. There isn't time to wait for an explanation, and we can't afford to be confused about what needs to be done, by whom, and when.
  • Capture and promote the organization's best practices
    To stay competitive, organizations must use industry-standard best practices and learn from their mistakes and their successes.
  • Baseline and measure the effect of changes
    If you do not establish a baseline method, what do you improve? Documentation helps you implement the agile principle of continuous improvement based on retrospectives.
  • Address compliance and audits
    CMMi, DO-178B, ITIL, COBIT, SOX, for example. Compliance can be a challenge. Documenting the method is typically necessary to achieve compliance and as evidence to demonstrate compliance.
  • Quickly start projects with a method that fits project characteristics

Thursday, July 19, 2012

S.L.I.Q PenDrive

Benchmark for 16G S.L.I.Q PenDrive.
Got it for only RM27.90

CrystalDiskMark 3.0.1 x64 (C) 2007-2010 hiyohiyo
                           Crystal Dew World :
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :    16.521 MB/s
          Sequential Write :    10.884 MB/s
         Random Read 512KB :    15.926 MB/s
        Random Write 512KB :     0.841 MB/s
    Random Read 4KB (QD=1) :     2.411 MB/s [   588.5 IOPS]
   Random Write 4KB (QD=1) :     0.005 MB/s [     1.3 IOPS]
   Random Read 4KB (QD=32) :     2.529 MB/s [   617.4 IOPS]
  Random Write 4KB (QD=32) :     0.007 MB/s [     1.8 IOPS]

  Test : 1000 MB [E: 0.0% (0.0/14.9 GB)] (x5)
  Date : 2012/07/19 12:57:10
    OS : Windows 7  SP1 [6.1 Build 7601] (x64)

Tuesday, May 10, 2011

Remember to shutdown your database

I was working on a project which uses Spring, Jdbc, Jpa and HSQLDB.

It is meant to be executed as a batch program from command line with multi threaded support.

After a while, I noticed that my final few commits to the database is never captured properly by the database. After checking to see if my threads, jpa or spring context is closed properly, I finally figured out it is because I never shutdown my HSQLDB properly. Even though I am using it as a file based database, I must still issue a shutdown command.

For those of you trying to work with embedded database, do remember to shut it down when your program exits.

Hopes this kind reminder will safe you hours of debugging.

Tuesday, October 12, 2010