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.

Mobile with USB port

Do you ever think to attach your USB pen drive with your mobile, if yes then we would have this in market soon. Remember requirement is the mother of all inventions and you will find such product in market very soon.

E-Pen:Write on paper & Store on drive

About: When I note done some of my important meetings notes on a piece of paper or notepad, I always think of some miracle device that will convert/move the hard copy of my notes on paper to an electronic file, so that I can save that file in my laptop/desktop for further use.
You would think of an idea to scan it and store it as an image in my pc/laptop, right? or you might be thinking that am too lazy to type this notes directly on my laptop notepad/wordpad later?

I know you are in touch with latest technologies so you will suggest for "Stylus" pen, but wait it works only over another supporting device a Specific Mouse Pad like device.

I think about a device "Pen", which I can use to write on a paper having "ball-point or Ink" in it, meanwhile it should have some internal mechanism that will store the character while writing on a paper or normal notepad.

How: This pen should have a "compass" like device to sense the direction & distance in which it moves, and store this data in pieces say "a char", then this char should be stored multiple times as I writes a whole sentences.
We can use some memory chip to store this data and finally it could be copied from this pen device to my laptop/pc as a stream of data into a file(.txt).

Internal: Say for example to type/draw A now assuming that your compass is showing north to your sitting position, then when you write A, the pen direction goes toward North-East then South-East (remember don't pick the pen point else you will reset the information) go half back in the Nouth-West direction and then West. See your Char "A" is ready now.
Procedure to write would be very straight if you are writing a char like S,L,I,O etc, however for other you would need little practice, thats it you are master in "E-Pen"
The direction as well as distance information will work on mathematical "X,Y" coordinate system transforming user perspective to a device coordinate system with the help of built in compass. This information could be stored for every character you type/write on a paper, and finally when you want to import it in to your laptop/pc file this data will be processed to form a useful word then to sentence and into a electronic file.

Continued......

SQL Injection

It is a trick to inject SQL query/command as an input possibly via web pages. Many web pages take parameters from web user, and make SQL query to the database. Take for instance when a user login, web page that user name and password and make SQL query to the database to check if a user has valid name and password. With SQL Injection, it is possible for us to send crafted user name and/or password field that will change the SQL query and thus grant us something else.

Every release is an Innovation

In IT every DSR/MITR/Change Request you develop is a invention if you have applied an effort that is different from your previous one.It is different from conventional engineering process where you are 100 percent sure that what is going to be your output (Considering this automated machines era), however in software you are 50/50 sure about your actual outcome untill you have the QA/Business verified product is ready, this is because every step from requirement to delivery is still manual (we could consider QA/Auto-build system exclusively since here we have an automated tools now).

Every developer who develops a single piece of code is an Innovator, independent of the fact whether he/she know about "Innovation".