Sampath's Blog

Difference between Scrum, XP

2009-03-24T07:11:00.002-07:00

1. Scrum iterations are 2-4 week long, XP- 1-2 weeks long
2. Scrum do not allow changes into their sprints, XP Allows
3. Scrum tasks prioritised by team, XP- by customer and stricter
4. Scrum does not follow engring practices unlike XP follows TDD, pair programming, simple design, refactoring, and so on

2009-03-24T07:11:00.000-07:00

Great Indian Developer Summit

2008-05-22T02:07:00.000-07:00

It is really a great summit. i think 120 presentations.. spread for 5 days.. amazing summit sponsored by some great companies like Oracle, msdn , Nokia, SAP, Amazon, Adobe etc.. I could see the over helming response to the summit.

I will post more on the sessions i attended in detail later as still i am creating writeup on the same.

There are a lot of stalls open to know more about recent developments in the IT and many offers are on the way.

simply great.

Called from

2006-03-02T05:55:00.000-08:00

public class CalledFrom { public static String getCaller() { StackTraceElement[] stackTrace = Thread.currentThread().getStackTrace(); int i = Math.min(3, stackTrace.length - 1); return stackTrace[i].getClassName() + "." + stackTrace[i].getMethodName() + "()"; }

public static void printCaller() { System.out.println(getCaller()); }

public static void main(String[] args) { CalledFrom.printCaller(); }}

Log4j - Real performer

2006-01-24T03:40:00.000-08:00

I tried to find out the different scenarios with/out log4j... Really great output

consider the following code snippet,

import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.BasicConfigurator;

public class MyApp {

static Logger logger = Logger.getLogger(MyApp.class);

public static void main(String[] args) {
long start = System.currentTimeMillis();
// BasicConfigurator.configure();
//logger.setLevel(Level.DEBUG);
for (int i = 0; i <>
// logger.info("Entering application.");
// logger.info("Exiting application.");

System.out.println("Entering application.");
System.out.println("Exiting application.");
}
long end = System.currentTimeMillis();
System.out.println(end - start);
}
}

with this.. program ends in around 6500 milli secs
disable SOP and enable log and run in ERROR level - ends in around 40 milli secs
disable SOP and enable log and run in DEBUG level - ends in around 13000 milli secs

About Junit Test

2005-12-15T02:56:00.000-08:00

A test suite may contain any class that implements the Test interface, including other suites.

Test Case. A test case, such as AmountTest, collects a set of one or more related test methods and is usually a subclass of the framework class TestCase. Each test method name must start with “test” and has no arguments, e.g., testSetCurrency().
Test Suite. A test suite is a collection of tests that are run at the same time. A test suite is often constructed dynamically from selected test cases or may contain only a single test method.
Test Runner. A test runner is a utility used to run a suite of tests. The runner may provide a graphical presentation, such as an Eclipse view, or a command-line execution that is incorporated into automated build files.

Code that creates the objects used by the tests. This testing context is
referred to as a test’s fixture. The setUp() and tearDown() methods are
part of the fixture.