pinxystech’s posterous

pinxystech’s posterous

Sarala  //  

Nov 5 / 1:58am

Test Test Test

I stumbled upon this Joel Test here

The Joel Test

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

No guesses on how my current and my previous project ( at the client location) environments fared . The most annoying issue I had to and still sometimes have to deal with is #8. Not that my workplace is swarming with oh so noisy people all around, but how actually fellow programmers/managers can be a pain in the rear. I remember the days when we had a rather unusual arrangement of  our managers and code monkeys seated in a conf room and we had to churn out code like there was no tomorrow. I used to hide myself in a quiet room only to be bugged by a manager to come back for a status update a few minutes later. WTH?

Infact  I suppose both my current and previous projects would only fare a max of 4 -5. Time for a change eh?

Filed under  //  Management   Test   Work Env  

Comments (0)

Nov 4 / 12:04am

Java Heap Issue: Fork level , simple solution

My new project hasn't been any exciting, I kept wondering what on earth was I doing. I ha dto deal with on-boarding Apps day after day on to Hudson and get the Sonar Metrics up. Lame I thought, it was dreadfullu monotonous , until I hit this one. It was a simple Java Heap size issue and I rather sheepishly , set the Hepa to the maz 1024 , no luck. I then bumped it to 2048, still the issue refused to die down. Huh! I targeted the GC options on a lead's suggestion, 2 days + a gazzillion permutations and combinations, I almost gave up.But I guess I mastered the  GC quite a bit.

One look at the build file, the fork option was set to Yes and we had to set up the heap size for each fork here insteda of the usual way of setting it up in the Hudson console. A simple solution , a simpler problem, I just refused to look at the right place.

fork=”true”
memoryInitialSize="256m"
memoryMaximumSize="1024m"

 

Filed under  //  Fork   Heap   java   java Heap size  

Comments (0)