Friday, July 10, 2009

Are you jing?

One of the most wonderful free tool I have ever come across – “the Jing”. Capture, Save & Share is what the mantra of Jing team. I am listing few important features that would interest you.

Jing Screen capture:
  • Capture screens and decorate it in one go.
  • Very rich image edit tool will allow you to put text, arrows, boxes, etc.
  • The editing tool is far better than any other including MS paint and it has just required things.
Jing Video capture:
  • Capture screen happening as much as you want
  • Save the entire video and share with your colleagues
  • It saves in SWF format so that you can view the video on any machine.
I would recommend this tool to any QA and Dev who want to communicate anything visually. Many a times, Dev complain about exact steps for any defect reproduction and then QA carry them to their desk to show the steps. This tool can capture your steps so that you the QA or Dev just have to send the SWF and you are done.

I played with the tool for some time today and found that it has all the power to put you in a great comfort. Check the below link.



Wednesday, July 01, 2009

Rich set of .NET services for Rich client

Starting from static web pages (.HTML, .HTM, etc) to dynamism with server scripts (.asp, .jsp, etc) to OO enabled server scripts (ASP.NET) to powerful client applications (ASP.NET + AJAX), THE web has already stepped into rich model of first class web applications delivery to end users.

Making the client rich alone will not work. And that is where .NET RIA services comes into play. There is a nice introductory page released recently, which will clear all your questions and give very good understanding of overall picture.

Getting started with the .NET RIA Services


Refactoring catalog

Refactoring is important part of Agile methodology. As they say no code is ever complete and there is a good scope of improvement. As most of my work experience include traditional SDLC models, I always refrain myself from accepting changes and if it becomes mandatory that goes as Requirement bug or Design bug if not change in requirement.

That was horrible.
That was painful too.

Now with Agile practice, you would say – well, I am open for any changes because my design supports that and importantly my mind too! Does that sound interesting to you?

OK, then there are people (Uncle bob, Martin fowler, etc…) who are ready to solve your problems. Being late in the Agile game, it is glad to see that there are tested patterns and practices that you can follow to ensure success in your software projects.

One of such practice they follow is Refactoring – continuous code improvement. Though it is de-facto in Agile, there is no wrong to practice it in other software execution models.

Definition of Refactoring as per martin fowler’s dedicated site:
Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. Its heart is a series of small behavior preserving transformations. Each transformation (called a 'refactoring') does little, but a sequence of transformations can produce a significant restructuring. Since each refactoring is small, it's less likely to go wrong. The system is also kept fully working after each small refactoring, reducing the chances that a system can get seriously broken during the restructuring.

Click on below links to find well researched articles to dig more.