The beauty of return this;

As a beginner I was fascinated by the repeated append calls on the StringBuffer (Java) object. Especially because of the saving in the typing and no more string concatenation.

new StringBuffer("start").append("more").append("more")

Obviously the return statement of the append method should look like

return this;

Later I came across more interesting examples of this in the mock libraries like below.

Expect.Call(someObj.someMethod()).Return(anotherObject).Repeat().Once();

This time more than typing benefit what I liked about it is the readability of thecode. This is very close to the natural language translation of the above.
"Expect a method call someMethod on someObj. someMethod returns anotherObject. someMethod call is expected only once." Isn't that very close to how the code reads itself?

Look at this now.

"Create a new bug on build 45576 with description "this is really bugging ....". 

new Bug("new one").onBuild(45576)

   .withDescription("this is really bugging")

   .WithPriority("medium").reportedBy("QA")

and this

 bug = new Bug("new one");

 bug.setDescription("....");

 bug.setBuild(45576)......

We can improve the readability by adding 'And', 'With', 'To' etc.

Below I have added a creational method and used 'and' method to improve the readability a bit more.

Bug.CreateWithTitle("new one").onBuild(45576)

  .withDescription("this is really bugging")

  .WithPriority("medium").reportedBy("QA").and().assignTo("a dev")...