Friend or Foe - by TATU

"Friend Or Foe"

Is it too late
Nothing to salvage
You look away
Clear all the damage

The meaning to
All words of love
Has disappeared
We used to love one another
Give to each other
Lie under covers so,
Are you friend or foe

Love one another
Live for each other
So, are you friend or foe
Cause I used to know

The promises
Hollow concessions
And innocent show of affection
I touch your hand
A hologram
Are you still there
We used to love one another
Give to each other
Lie under covers so,
Are you friend or foe

Love one another
Live for each other
So, are you friend or foe
Cause I used to know
Is it too late
Nothing to salvage
You look away
Clear all the damage
The meaning to
All words of love
Has disappeared
We used to love one another
Give to each other
Lie under covers so,
Are you friend or foe

Love one another
Live for each other
So, are you friend or foe
Cause I used to know

effectiveness & efficiency and the use of them

1. Discuss the difference between effectiveness & efficiency with suitable examples.

In management terms, efficiency is "doing things right" and effectiveness is doing the right things"

Effectiveness relates the input or the output to the final objectives to be achieved (the outcome)

• efficiency=quality/Input quantity
• Effectiveness=objectives/Input Quantity

In management, effectiveness relates to getting the right things done. Peter Drucker reminds us that effectiveness is an important discipline which “can be learned and must be earned.”

The effectiveness is more difficult to assess than efficiency, since the outcome is influenced political choice. The effectiveness shows the success of the resources used in achieving the objectives set.

Example:
When deploying a transport service, efficiency and effectiveness both comes together to complete the task successfully. In this scenario, effectiveness could be identified by "buying/hiring" vehicles. It means the management should understand the use of the vehicles before buy/hire them. If the management buy wrong type of vehicles to use them for transport service, will lead to bankrupt because some vehicles will not meet the requirements well and will not provide the service which has expected. Some vehicles will not enough for passengers and will make to hire more vehicles. Then it will lead to increase the staff and will make more expenses (vehicle expenses/ salaries to the staff)
Then shall we talk about the efficiency. If the transport service provide the services at unneeded times that less number of passengers using the service, the service will not make profits. So, using a timetable is a must when thinking about the efficiency. It means "doing things right".

2. Which is more important for performance? and Can managers improve both simultaneously?

Efficiency and effectiveness both comes together because both of them are connected to each other. We can't think about the effectiveness without efficiency and we can't think about the efficiency without effectiveness.

Efficiency alone will put the company on the fast track to bankrupt .

Effectiveness (efficacy) alone *may * allow the company to survive. How ever the company will not reach it's maximum potential if it is inefficient.

• Low Efficiency / High Effectiveness
• there is a right goal, but less/poor usage of resources. (leads to expansive result)

• High Efficiency / Low Effectiveness
• Inappropriate goals but right usage of resources. (leads to deliver unwanted products at lower price)

• Low Efficiency / Low Effectiveness
• Works on a wrong target and less/poor usage of resources. (leads to deliver expensive, unwanted products)

• High Efficiency /High Effectiveness
• Works on a Right goal using right resources in a right way. (delivers good/useful products at affordable price)

So, effectiveness & efficiency relates to each other by connecting inputs, outputs and outcomes.

Programming best practices

good programming practices 
using best practices when developing a program/project will help to make successful product without bugs. here are some best practices which needs to follow when developing a project.


Omit needless codes

Needless codes will make the codes unreadable and hard to understand. It will make hard to find the errors when any error has occur. Needless codes will add “lines of code” to the project and will support to earn more money to the developer. But when he/she needs to troubleshoot, needless codes will make hard to find the errors. Sometimes the needless codes will make some critical/hard to identify errors.

Identify duplicate codes

Identifying duplicate codes will helps to remove unnecessary “lines of codes” and will ease the debugging process. Editing the same code at several places will waste some time and delays the deployment of the project. So, it's better if the developer could identify duplicate codes and use that particular code at one place and linking that code to everyplace that needed. It will ease the editing/debugging process because developer no need to find everyplace to edit/debug and editing/debugging a single place will affects to the everyplace which the code is linked.

Using less number of “lines of codes”

When lines of code increased , the project will become large/heavy in size and hard to troubleshoot. So,the developer should use less number of “lines of codes”. Then the project will be smaller in size and will ease the troubleshooting process.

Commenting the codes

When developing a project, it's better if the developer could “comment” the every part of the program. It will helps to identify the usage of that particular “lines of code” and will ease the management/troubleshooting/update process of the program at later time.

Plan Development Process/Life-cycle

Planning the development process/life-cycle helps to determine every part of the development according to a structured plan. Then developer will not forget to do something important on his/her development process.

Plan the time line

Planning the time line will help to identify every work which have to do according to the time and developer could identify what should do in particular day and he/she could predict the development process according to the time.

Gathering Requirements.

Gathering requirements helps to develop the exact program which needs to built. If not programmer will end up with missing some requirements and will be unsuccessful. If the programmer didn't develop the program to fulfill the needs/requirements then developing the program will be useless.

Design

Selecting a suitable design will ease to use program by the user.

Coding separate parts and integrate them in to the main program.

It will ease troubleshoot and testing process as well as the coding process.

Testing

Without testing the developer can't identify the errors. If the developer didn't test his/her codes till the end of the development process, when he/she find any error will make him to edit/code many “lines of code” and it will make many errors. Editing many “lines of code” at the last time will make the programmer unsuccessful.

Performance testing

programmer should develop the program to give the actual performance to the user. So, performance testing will help to identify the missing parts and several errors which leads to minimize the performance.

Deployment

This is the last stage of the development process. This is the stage that user gets the project. Sometimes it will be failed due to some reasons and if it failed , user can't use the project as expected. Before deployment, developer should check a “deployment checklist” to ensure that user could use the product as expected.

System operations and support

There should be a method to identify errors when running the program. So, if there is a method to collect/identify the errors/bugs when running the program will be ease the work of “debugging”

Data migration

It's better if the program could support to the files/data which used in older/other programs. It will help to save the time to enter data into the new program because if there is an older program, user could use the data which associated with that old program inside the new program.

Project Management

Project management is the main part of the development process and it ensures that the existence programming best practices and follows the best practices.

Measuring success

checking the final project meets the industry standards.

Source:
Best practices for software development projects
http://www.ibm.com/developerworks/websphere/library/techarticles/0306_perks/perks2.html
Accessed on 02/24/2010 07:16 AM

A new day has come...

Is the world is equal to a Ball? or is it a Plate? Is the world is beautiful? or isn't beautiful? Doesn't a matter if the world is a Ball or a Plate or it's beautiful or isn't beautiful. A new day has come..

Lyrics - Mandy Moore - Cry

I'll always remember
It was late afternoon
It lasted forever
And ended so soon (yea)
You were all by yourself
Staring up at a dark gray sky
I was changed

In places no one will find
All your feelings so deep inside (deep inside)
Was there that I realized
That forever was in your eyes
The moment I saw you cry (cry)

Moment that I saw you cry

It was late in September
And I've seen you before (seen you before)
You were always the cold one
But I was never that sure

You were all by yourself
Staring up at a dark gray sky
I was changed

In places no one will find
All your feelings so deep inside (deep inside)
Was there that I realized
That forever was in your eyes
The moment I saw you cry

I wanted to hold you
I wanted to make it go away
I wanted to know you
I wanted to make your everything, all right....

I'll always remember...
It was late afternoon...
In places no one will find...
(Baby oh no nooooo)

In places no one will find
All your feelings so deep inside
(forever was in your eyes)
It was there that I realized
That forever was in your eyes
The moment I saw you cry
Baby cry
The moment that I saw you cry
I think I saw you cry
The moment I saw you cry

Fade out
I wanted to know you
I wanted to know you
I wanted to know you