4G- waiting behind 3G

3G mobile services would be starting soon in India, thats late as compared to global availability but for us thats a great news.

1G: Voice Calling

2G Voice Calling + SMS  + Internet

3G Voice Calling + SMS  + Video Calling + High Speed Internet

4G Voice Calling + SMS  + Video Calling + High Speed Internet + IP (Internet Protocol) based services.

Handle with Care I - Maintenance phase of application life cycle

Poorly structured design and programming during application development phase increases the complexity and risk involved in in the maintenance phase.
How to make this phase efficient?
1) Clear vision on what requirement could be implemented, making sure that you does not break the existing functionality.
2) Analyze the change request both functionally as well as technical (create impact analysis document if required).
3) Identify the change type in term of Visual, Logical, and Database before starting development.
4) Reserve some time to analyze the IN-OUT of the box(code) which might be out of your development scope.
5) Maintain the team member for long tenure, since they know the code very well with in course of time devoted on it.

More important assure your client that you are there for maintaining there services at higher level not only the software codes.

Convert your Sentence to Picture

My next Idea is to develop an application/website which accepts a "valid" sentences and draws a picture from it. I know it is a very tough task to accumulate all the possible picture related to words, however we can set some AI(Artificial Intelligence) theory on that to cut-shot the probable combinations.
contd...

:-) Humorous scene :-)

When I was in college, My friend rented a small house with a  very small kitchen, they purchased a new Gas-Stove to cook food and  managed the space smartly.....how?

They kept Stove on the platform and used gas cylinder as .....?????? look below...... :-)

:-)

No Comments !

Achievement vs Frustration

A simple formulate derivate Achievement vs Frustration:

Achievement = Expectation - Execution (If  positive value)
:::::: You are executing more than expectations::::::::

Frustration = Expectation - Execution (If  negative value)
:::::: Expectation is more than you could really execute:::::::::




if Zero? then you are "Meet  Expectation" in your appraisal
:-)

Easy way to derive high level estimates for IT project

Are you stuck every time with a demand from your Manager to provide HLL(High Level Estimates) of a requirement within a limited time frame?Yes.

An easy way to derive/calculate high level estimates for a given development task lies in the historical data sheet.
This "Historical Data Sheet" can be maintained to store WBS(Work Breakdown Structure) of every estimates for all type(small/medium/large) task that has been executed till date on the given project.

This would help both new as well as old resources to grasp an idea about required development scope in terms of files/classes/LOC(Line Of Code) on a higher level.

Example:
On Apr-2009, I have received a business requirement that add an extra field1 to a webpage, I have given the WBS like
================================
i) Changes in XYZ JSP Page
ii) Changes in ABC component class
iii) Changes in LMN EJB class

Total 1 JSP and 2 Class

HLL Effort: 24 hrs
================================
Store this information in "Historical Data Sheet" with appropriate column and upload to shared location and communicate to all team members(Others will do the same).

Next time I got a similar requirement to add another filed2 after 1 year in Apr-2010, now there is 2 approach to provide a HLL, either you again drive inside a code to identify what all changes are there, else you simply refer the "Historical Data Sheet" to have and provide a "quick" HLL for the given task. You could add 10% margin to this accommodate the extra scopes.Thats it.

This could also be termed as "Re-usability" of one person knowledge about a product/area with other team members (At least for estimation).

An IT Team - How it looks alike

An IT Team is a like a good looking car, which has external body  that looks great as well as some internal parts that are not visible. There is no need to highlight about the external parts since its visible to the viewers(spectators) however the internal parts like "Engine" is never visible and its quality/characteristic is only measurable by the way it "sounds/speak outs". Truely speaking out this is the part which is responsible for driving the car through a  road/path.


When we are managing a car(equivalent to IT team) it is important to take care of both parts(External/Internal) to drive a Team/Car in passion for long drive.


I hope you understand this.