The Best Comparison I ever read
Love Marriage vs Arranged Marriage
Love Marriage:-Resemblesprocedural programming language. We have some set of functions like flirting, going to movies together, making long conversations on phone and then try to fit all functions to the candidate we like.
Arranged Marriage:-
Similar toobject oriented programming approach. We first fix the candidate and then try to implement functions on her. The functions are added to supplement the main program. The functions can be added or deleted.
Love Marriage:-Family system hangs because hardware (calledParents) is not responding.
Arranged Marriage:-
Compatible with hardware(Parents).
Love Marriage:-You are the project leader so u are responsible for implementation and execution of PROJECT- married life.
Arranged Marriage:-
You are a team member under project leader (parents) so they are responsible for successful execution of project Married life.
Love Marriage:-Client expectations include exciting feature as spouse cooking food, washing clothes etc.
Arranged Marriage:-
All these features are covered in the SRS (System Req. Specification) as required features.
Love Marriage is likeWindows, beautiful n seductive... . Yet one never knows when it willcrash....if crashes that's the end
Arranged Marriage is likeUnix.... Boring n colorless... but still extremelyreliable n robust. May crash but easy to recover
Saturday, January 16, 2010
Satyam employees fooled to work on fake projects
Satyam employees fooled to work on fake projects
Hyderabad: Satyam ex-chairman Ramalinga Raju's fraud game did not spare even its employees. While it inflated revenue through fake invoices, the company created teams to work on the fake projects. The employees working on these 'projects' were made to believe there were clients waiting for these products to be delivered.
According to the finds of the Central Bureau of Investigations (CBI), the employees were also regularly sent emails about the product and project progress as if they were all coming from the clients abroad. But the emails were fake and were used only to keep the employees engaged, reports DNA.
The fraudulent chairman along with the finance in-charges and the core team created at least seven projects, showing that clients were waiting for these products to be delivered. There was regular exchange of mails from the management to the employees to give an impression of the keen interest of management in execution of these projects.
The investigation also found the invoices do not match with the ledgers of banks with which Satyam had transacted in the U.S. "However, the ledgers maintained by Satyam were dishonestly and fraudulently forged pertaining to these seven customers to incorporate the collections pertaining to all the 63 invoices," the CBI said in its latest chargesheet.
What has caught the investigators by surprise is the way the emails to employees for monitoring the progress of the fake projects were generated. The CBI found that they were all generated from Hyderabad. "Detailed analysis of the emails revealed that the internet protocol addresses from which the emails were sent at the relevant time and date were all from within Hyderabad itself, which clearly shows that such emails have never emanated from these seven foreign customers. Further, it was also established that these emails were relayed by the Rediffmail server which has got a paid service facility called Domain Services, which facilitates its clients to create email IDs at their own domain names.
In this case, it was found that the payments for the said services were made through Bank of Baroda Visa credit card which belongs to D Venkatapathy Raju (one of the accused)," the chargesheet said. These email IDs were freely used by the core team working on fabricating the accounts to give sanctity to the fake projects. "For the purpose of executing the projects, which were never delivered to the customers, the accused have wasted thousands of man hours of the associates of Satyam there by incurring a wasteful expenditure to the tune of Rs65.88 crore towards the salaries of the associates and other overheads," the CBI said.
Hyderabad: Satyam ex-chairman Ramalinga Raju's fraud game did not spare even its employees. While it inflated revenue through fake invoices, the company created teams to work on the fake projects. The employees working on these 'projects' were made to believe there were clients waiting for these products to be delivered.
According to the finds of the Central Bureau of Investigations (CBI), the employees were also regularly sent emails about the product and project progress as if they were all coming from the clients abroad. But the emails were fake and were used only to keep the employees engaged, reports DNA.
The fraudulent chairman along with the finance in-charges and the core team created at least seven projects, showing that clients were waiting for these products to be delivered. There was regular exchange of mails from the management to the employees to give an impression of the keen interest of management in execution of these projects.
The investigation also found the invoices do not match with the ledgers of banks with which Satyam had transacted in the U.S. "However, the ledgers maintained by Satyam were dishonestly and fraudulently forged pertaining to these seven customers to incorporate the collections pertaining to all the 63 invoices," the CBI said in its latest chargesheet.
What has caught the investigators by surprise is the way the emails to employees for monitoring the progress of the fake projects were generated. The CBI found that they were all generated from Hyderabad. "Detailed analysis of the emails revealed that the internet protocol addresses from which the emails were sent at the relevant time and date were all from within Hyderabad itself, which clearly shows that such emails have never emanated from these seven foreign customers. Further, it was also established that these emails were relayed by the Rediffmail server which has got a paid service facility called Domain Services, which facilitates its clients to create email IDs at their own domain names.
In this case, it was found that the payments for the said services were made through Bank of Baroda Visa credit card which belongs to D Venkatapathy Raju (one of the accused)," the chargesheet said. These email IDs were freely used by the core team working on fabricating the accounts to give sanctity to the fake projects. "For the purpose of executing the projects, which were never delivered to the customers, the accused have wasted thousands of man hours of the associates of Satyam there by incurring a wasteful expenditure to the tune of Rs65.88 crore towards the salaries of the associates and other overheads," the CBI said.
Problems in year 2038
Test it now...
steps...
1. login to yahoo messenger
2. send instant message to anyone - fine its working...
3. now, change ur system date to 19-Jan-2038, 03:14:07 AM or above
(as mentioned in mail)
4. Confirm whether ur date is changed
5. again send instant message to anyone...
Your Yahoo Messenger crashes....
* * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * *
Why.....
What is it?
Starting at GMT 03:14:07, Tuesday, January 19, 2038, It is expected to see lots of systems around the world breaking magnificently: satellites falling out of orbit, massive power outages (like the 2003 North American blackout), hospital life support system failures, phone system interruptions, banking errors, etc. One second after this critical second, many of
these systems will have wildly inaccurate date settings, producing all kinds of unpredictable consequences. In short, many of the dire predictions for the year 2000 are much more likely to actually occur in the year 2038!
Consider the year 2000 just a dry run. In case you think we can sit on this issue for another 30 years before addressing it, consider that reports of temporal echoes of the 2038 problem are already starting to appear in future date calculations for mortgages and vital statistics!
In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run. This can result in incorrect and wildly inaccurate dates being reported by the operating system and/or applications. The effect of this bug is hard to predict, because many applications are not prepared for the resulting "skip" in reported time anywhere from 1901 to a "broken record" repeat of the reported time at the second the bug occurs. Also, may make some small adjustment to the actual time the bug expresses itself. This bug to cause serious problems on many platforms, especially Unix and Unix-like platforms, because these systems will "run out of time".
what causes it?
Time_t is a data type used by C and C++ programs to represent dates and times internally. (Windows programmers out there might also recognize it as the basis for the CTime and CTimeSpan classes in MFC.) time_t is actually just an integer, a whole number, that counts the number of seconds since January 1, 1970 at 12:00 AM Greenwich Mean Time. A time_t value of 0 would be 12:00:00 AM (exactly midnight) 1-Jan-1970, a time_t value of 1 would be 12:00:01 AM
(one second after midnight) 1-Jan-1970, etc..
some example times and their exact time_t representations:
Date & time time_t representation
1-Jan-1970, 12:00:00 AM GMT 0
1-Jan-1970, 12:01:00 AM GMT 60
1-Jan-1970, 01:00:00 AM GMT 3 600
2-Jan-1970, 12:00:00 AM GMT 86 400
1-Jan-1971, 12:00:00 AM GMT 31 536 000
1-Jan-1972, 12:00:00 AM GMT 63 072 000
1-Jan-2038, 12:00:00 AM GMT 2 145 916 800
19-Jan-2038, 03:14:07 AM GMT 2 147 483 647
By the year 2038, the time_t representation for the current time will be over 2 140 000 000. And that's the problem. A modern 32-bit computer stores a "signed integer" data type, such as time_t, in 32 bits. The first of these bits is used for the positive/negative sign of the integer, while the remaining 31 bits are used to store the number itself. The highest number these 31 data bits can store works out to exactly 2 147 483 647. A time_t value of this exact number , 2 147 483 647, represents January 19, 2038, at 7 seconds past 3:14 AM Greenwich Mean Time. So, at 3:14:07 AM GMT on that fateful day, every time_t used in a 32-bit C or C++ program will reach its upper limit.
One second later, on 19-January-2038 at 3:14:08 AM GMT, disaster strikes.
When a signed integer reaches its maximum value and then gets incremented, it wraps around to its lowest possible negative value. This means a 32-bit signed integer, such as a time_t, set to its maximum value of 2 147 483 647 and then incremented by 1, will become -2 147 483 648. Note that "-" sign at the beginning of this large number. A time_t value of -2 147 483 648 would represent December 13, 1901 at 8:45:52 PM GMT.
So, if all goes normally, 19-January-2038 will suddenly become
13-December-1901 in every time_t across the globe, and every date
calculation based on this figure will go haywire. And it gets worse. Most of the support functions that use the time_t data type cannot handle negative time_t values at all. They simply fail and return an error code.
A quick check with the following Perl script may help determine if your computers will have problems (this requires Perl to be installed on your system, of course):
#!/usr/bin/perl
# Use POSIX (Portable Operating System Interface) use POSIX;
# Set the Time Zone to GMT (Greenwich Mean Time) for
date calculations.
$ENV{'TZ'} = "GMT";
# Count up in seconds of Epoch time just before and
after the critical event.
for ($clock = 2147483641; $clock < 2147483651; $clock++)
{print ctime($clock);}
For example, the output of this script on Debian GNU/Linux (kernel 2.4.22)
(An affected system) will be
# ./2038.pl
Tue Jan 19 03:14:01 2038
Tue Jan 19 03:14:02 2038
Tue Jan 19 03:14:03 2038
Tue Jan 19 03:14:04 2038
Tue Jan 19 03:14:05 2038
Tue Jan 19 03:14:06 2038
Tue Jan 19 03:14:07 2038
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
Solution
"The best way to predict the future is to engineer it." Consider testing your mission-critical code well ahead of time on a non-production test platform set just before the critical date. For more general applications, just using large types for storing dates will do the trick in most cases. For example, in GNU C, 64-bits (a "long " type) is sufficient to keep the time from rolling over for literally geological eons This just means any executables the operating systems runs will always get the correct time reported to them when queried in the correct manner. It doesn't stop the executables you may still want to be worried about Well-written programs can si mply be recompiled with a new version of the library that uses, for example, 8-byte values for the storage format. This is possible because the library encapsulates the whole time activity with its own time types and functions (unlike most mainframe programs, which did not standardize their date formats or calculations). So the Year 2038 problem should not be nearly
as hard to fix as the Y2K problem was.
Admittedly, some don't feel that this impending disaster will strike too many people. They reason that, by the time 2038 rolls around, most programs will be running on 64-bit or even 128-bit computers. In a 64-bit program, a time_t could represent any date and time in the future out to 292 000 000 000 A.D., which is about 20 times the currently estimated age of the universe. The problem with this kind of optimism is the same root problem behind most of the Year 2000 concerns that plagued the software industry in previous years: Legacy Code. Even if every PC in the year 2038 has a 64-bit CPU, there will be a lot of older 32-bit programs running on them.
The greatest danger with the Year 2038 Problem is its invisibility. The more-famous Year 2000 is a big, round number; it only takes a few seconds of thought, even for a computer-illiterate person, to imagine what might happen when 1999 turns into 2000. But January 19, 2038 is not nearly as obvious. Software companies will probably not think of trying out a Year 2038 scenario before doomsday strikes. Of course, there will be some warning ahead of time. Scheduling software, billing programs, personal reminder calendars, and other such pieces of code that set dates in the near future will fail as soon as one of their target dates exceeds 19-Jan-2038, assuming a time_t is used to store them.
Good luck, and hope no one’s flying car breaks down in 2038
Test it now...
steps...
1. login to yahoo messenger
2. send instant message to anyone - fine its working...
3. now, change ur system date to 19-Jan-2038, 03:14:07 AM or above
(as mentioned in mail)
4. Confirm whether ur date is changed
5. again send instant message to anyone...
Your Yahoo Messenger crashes....
* * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * *
Why.....
What is it?
Starting at GMT 03:14:07, Tuesday, January 19, 2038, It is expected to see lots of systems around the world breaking magnificently: satellites falling out of orbit, massive power outages (like the 2003 North American blackout), hospital life support system failures, phone system interruptions, banking errors, etc. One second after this critical second, many of
these systems will have wildly inaccurate date settings, producing all kinds of unpredictable consequences. In short, many of the dire predictions for the year 2000 are much more likely to actually occur in the year 2038!
Consider the year 2000 just a dry run. In case you think we can sit on this issue for another 30 years before addressing it, consider that reports of temporal echoes of the 2038 problem are already starting to appear in future date calculations for mortgages and vital statistics!
In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run. This can result in incorrect and wildly inaccurate dates being reported by the operating system and/or applications. The effect of this bug is hard to predict, because many applications are not prepared for the resulting "skip" in reported time anywhere from 1901 to a "broken record" repeat of the reported time at the second the bug occurs. Also, may make some small adjustment to the actual time the bug expresses itself. This bug to cause serious problems on many platforms, especially Unix and Unix-like platforms, because these systems will "run out of time".
what causes it?
Time_t is a data type used by C and C++ programs to represent dates and times internally. (Windows programmers out there might also recognize it as the basis for the CTime and CTimeSpan classes in MFC.) time_t is actually just an integer, a whole number, that counts the number of seconds since January 1, 1970 at 12:00 AM Greenwich Mean Time. A time_t value of 0 would be 12:00:00 AM (exactly midnight) 1-Jan-1970, a time_t value of 1 would be 12:00:01 AM
(one second after midnight) 1-Jan-1970, etc..
some example times and their exact time_t representations:
Date & time time_t representation
1-Jan-1970, 12:00:00 AM GMT 0
1-Jan-1970, 12:01:00 AM GMT 60
1-Jan-1970, 01:00:00 AM GMT 3 600
2-Jan-1970, 12:00:00 AM GMT 86 400
1-Jan-1971, 12:00:00 AM GMT 31 536 000
1-Jan-1972, 12:00:00 AM GMT 63 072 000
1-Jan-2038, 12:00:00 AM GMT 2 145 916 800
19-Jan-2038, 03:14:07 AM GMT 2 147 483 647
By the year 2038, the time_t representation for the current time will be over 2 140 000 000. And that's the problem. A modern 32-bit computer stores a "signed integer" data type, such as time_t, in 32 bits. The first of these bits is used for the positive/negative sign of the integer, while the remaining 31 bits are used to store the number itself. The highest number these 31 data bits can store works out to exactly 2 147 483 647. A time_t value of this exact number , 2 147 483 647, represents January 19, 2038, at 7 seconds past 3:14 AM Greenwich Mean Time. So, at 3:14:07 AM GMT on that fateful day, every time_t used in a 32-bit C or C++ program will reach its upper limit.
One second later, on 19-January-2038 at 3:14:08 AM GMT, disaster strikes.
When a signed integer reaches its maximum value and then gets incremented, it wraps around to its lowest possible negative value. This means a 32-bit signed integer, such as a time_t, set to its maximum value of 2 147 483 647 and then incremented by 1, will become -2 147 483 648. Note that "-" sign at the beginning of this large number. A time_t value of -2 147 483 648 would represent December 13, 1901 at 8:45:52 PM GMT.
So, if all goes normally, 19-January-2038 will suddenly become
13-December-1901 in every time_t across the globe, and every date
calculation based on this figure will go haywire. And it gets worse. Most of the support functions that use the time_t data type cannot handle negative time_t values at all. They simply fail and return an error code.
A quick check with the following Perl script may help determine if your computers will have problems (this requires Perl to be installed on your system, of course):
#!/usr/bin/perl
# Use POSIX (Portable Operating System Interface) use POSIX;
# Set the Time Zone to GMT (Greenwich Mean Time) for
date calculations.
$ENV{'TZ'} = "GMT";
# Count up in seconds of Epoch time just before and
after the critical event.
for ($clock = 2147483641; $clock < 2147483651; $clock++)
{print ctime($clock);}
For example, the output of this script on Debian GNU/Linux (kernel 2.4.22)
(An affected system) will be
# ./2038.pl
Tue Jan 19 03:14:01 2038
Tue Jan 19 03:14:02 2038
Tue Jan 19 03:14:03 2038
Tue Jan 19 03:14:04 2038
Tue Jan 19 03:14:05 2038
Tue Jan 19 03:14:06 2038
Tue Jan 19 03:14:07 2038
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
Solution
"The best way to predict the future is to engineer it." Consider testing your mission-critical code well ahead of time on a non-production test platform set just before the critical date. For more general applications, just using large types for storing dates will do the trick in most cases. For example, in GNU C, 64-bits (a "long " type) is sufficient to keep the time from rolling over for literally geological eons This just means any executables the operating systems runs will always get the correct time reported to them when queried in the correct manner. It doesn't stop the executables you may still want to be worried about Well-written programs can si mply be recompiled with a new version of the library that uses, for example, 8-byte values for the storage format. This is possible because the library encapsulates the whole time activity with its own time types and functions (unlike most mainframe programs, which did not standardize their date formats or calculations). So the Year 2038 problem should not be nearly
as hard to fix as the Y2K problem was.
Admittedly, some don't feel that this impending disaster will strike too many people. They reason that, by the time 2038 rolls around, most programs will be running on 64-bit or even 128-bit computers. In a 64-bit program, a time_t could represent any date and time in the future out to 292 000 000 000 A.D., which is about 20 times the currently estimated age of the universe. The problem with this kind of optimism is the same root problem behind most of the Year 2000 concerns that plagued the software industry in previous years: Legacy Code. Even if every PC in the year 2038 has a 64-bit CPU, there will be a lot of older 32-bit programs running on them.
The greatest danger with the Year 2038 Problem is its invisibility. The more-famous Year 2000 is a big, round number; it only takes a few seconds of thought, even for a computer-illiterate person, to imagine what might happen when 1999 turns into 2000. But January 19, 2038 is not nearly as obvious. Software companies will probably not think of trying out a Year 2038 scenario before doomsday strikes. Of course, there will be some warning ahead of time. Scheduling software, billing programs, personal reminder calendars, and other such pieces of code that set dates in the near future will fail as soon as one of their target dates exceeds 19-Jan-2038, assuming a time_t is used to store them.
Good luck, and hope no one’s flying car breaks down in 2038
Bhavik
I once went out to the market wearing my Infosys ID card and did not realize till my friend told me why I was wearing it !!!!
Ashok
few days back I slept at 11:30 in the ni8 and woke up in the morning at 7:00 and suddenly thought that I haven't completed 9.15 hours and laughed at myself when I realised abt that.
Jyotsna
One from me too...
Just after our training completion in Mysore Dc and postings to Pune, me and my friends went out for dinner in one of the best restaurants. .
And as I finished.. I started walking towards the Basin with plates in my hand.. :)
Abhijeet
Jus to add...
Once I was on call with my father and mom was not around. I went on to ask, "why is she not attending the status call?"
Anup
I don't login to orkut, yahoo, gmail, youtube, etc.. at my personal internet connection at home... thinking it will be blocked any way.
Till I realize - I am at home.
Rohit
Yeah sometimes it do happens with me also........ ....while writing personal mails also........ .I jus use the way as if I am writing to onsite or some senior person...... ..
Jus forget that we are jus mailing our friends..... .........
And keeping hands in front of tap for waiting water to drop by itself is very frequent with me.......... .....I jus forget that we have to turn on and off the tap......... ..
Nidhi
Awesome!!
Once after talking to one of my friend. I ended the conversation saying ..." Ok bye...in case of any issues will call u back"
(Hilarious!)
Nisha
Sometimes when I mistakenly delete a message
from my mobile, I hope for a second, maybe its in the recycle bin
Farina
I was about to throw my hanky into the bin after drying my hand.
Bhabani
Once I was flashing my ID card instead of unlocking the door with the keys.
Nisha
Kinda a same experience for me too..
I gave my office mail id and pwd to access Gmail and wondered when did they become invalid???
Sandy
I have a experience to share tooo .. I was earlier working at the back office of an international Bank. We used to 'dispatch' lot of Credit / Debit cards and statements for the customers and track its delivery later.
Once my granma was admitted in a hospital, my team mate once casually asked me " howz ur granma doing now ? still in hospital ? " ... and i replied to her " She is better now , she will dispatched from the hospital tomorrow !"
This was followed by a loud laugh in the entire bay !
Sandeep
Once I went to a pharmacy n asked for a tab....pharmacist asked whr I want 250mg r 500mg.....suddenly I replied as 256mg...lol. ....thank god he didn't noticed tht....
Ashwin
Me getting a thought of doing an Alt+Tab while switching from a news channel to the DVD while watching TV..
Vidyarthi
And I - after a forty hour marathon in Bhubaneshwar with Powerbuilder, decided to take a break and went to a movie. In the middle of the movie, when I wanted to check the time, I kept repeatedly glancing at the bottom right corner of the silver screen!
Venu
Few of my friends and myself decided to go out for dinner. The place wasn't fixed yet. I said we shall decide it "run time"
Krishna
When I went to a movie theatre from office directly.. I showed the guy at the entrance my ID card and walked in... he had to call me back asking the ticket...
Rama
One late night when I went home after work, I was trying to flash my id card to open the lock and only after few secs, I realised what i'm trying to do
Sridhar
Once I went to have juice at the local juice vendor and innocuously asked him whether he had a plain 'version' of lemonade.
Arun
Few years back my shogun engine stopped on Bangalore MG Road as the petrol came to reserve. I told my friend I need to restart my bike!
Satya
The other day I was hearing one guy talking of a "Standalone" house.. when he was actually intending a independent house... Poor broker shud have tuff time trying to find a " Alone house standing in a huge empty area... " don't know what interpretations the guy must have made.
I once went out to the market wearing my Infosys ID card and did not realize till my friend told me why I was wearing it !!!!
Ashok
few days back I slept at 11:30 in the ni8 and woke up in the morning at 7:00 and suddenly thought that I haven't completed 9.15 hours and laughed at myself when I realised abt that.
Jyotsna
One from me too...
Just after our training completion in Mysore Dc and postings to Pune, me and my friends went out for dinner in one of the best restaurants. .
And as I finished.. I started walking towards the Basin with plates in my hand.. :)
Abhijeet
Jus to add...
Once I was on call with my father and mom was not around. I went on to ask, "why is she not attending the status call?"
Anup
I don't login to orkut, yahoo, gmail, youtube, etc.. at my personal internet connection at home... thinking it will be blocked any way.
Till I realize - I am at home.
Rohit
Yeah sometimes it do happens with me also........ ....while writing personal mails also........ .I jus use the way as if I am writing to onsite or some senior person...... ..
Jus forget that we are jus mailing our friends..... .........
And keeping hands in front of tap for waiting water to drop by itself is very frequent with me.......... .....I jus forget that we have to turn on and off the tap......... ..
Nidhi
Awesome!!
Once after talking to one of my friend. I ended the conversation saying ..." Ok bye...in case of any issues will call u back"
(Hilarious!)
Nisha
Sometimes when I mistakenly delete a message
from my mobile, I hope for a second, maybe its in the recycle bin
Farina
I was about to throw my hanky into the bin after drying my hand.
Bhabani
Once I was flashing my ID card instead of unlocking the door with the keys.
Nisha
Kinda a same experience for me too..
I gave my office mail id and pwd to access Gmail and wondered when did they become invalid???
Sandy
I have a experience to share tooo .. I was earlier working at the back office of an international Bank. We used to 'dispatch' lot of Credit / Debit cards and statements for the customers and track its delivery later.
Once my granma was admitted in a hospital, my team mate once casually asked me " howz ur granma doing now ? still in hospital ? " ... and i replied to her " She is better now , she will dispatched from the hospital tomorrow !"
This was followed by a loud laugh in the entire bay !
Sandeep
Once I went to a pharmacy n asked for a tab....pharmacist asked whr I want 250mg r 500mg.....suddenly I replied as 256mg...lol. ....thank god he didn't noticed tht....
Ashwin
Me getting a thought of doing an Alt+Tab while switching from a news channel to the DVD while watching TV..
Vidyarthi
And I - after a forty hour marathon in Bhubaneshwar with Powerbuilder, decided to take a break and went to a movie. In the middle of the movie, when I wanted to check the time, I kept repeatedly glancing at the bottom right corner of the silver screen!
Venu
Few of my friends and myself decided to go out for dinner. The place wasn't fixed yet. I said we shall decide it "run time"
Krishna
When I went to a movie theatre from office directly.. I showed the guy at the entrance my ID card and walked in... he had to call me back asking the ticket...
Rama
One late night when I went home after work, I was trying to flash my id card to open the lock and only after few secs, I realised what i'm trying to do
Sridhar
Once I went to have juice at the local juice vendor and innocuously asked him whether he had a plain 'version' of lemonade.
Arun
Few years back my shogun engine stopped on Bangalore MG Road as the petrol came to reserve. I told my friend I need to restart my bike!
Satya
The other day I was hearing one guy talking of a "Standalone" house.. when he was actually intending a independent house... Poor broker shud have tuff time trying to find a " Alone house standing in a huge empty area... " don't know what interpretations the guy must have made.
Subscribe to:
Posts (Atom)