Become a fan of Slashdot on Facebook


Forgot your password?
Slashdot Deals: Get The Fastest VPN For Your Internet Security Lifetime Subscription Of PureVPN at 88% off. ×

Comment Re:A tough one (Score 1) 285

You mention "Window NT and bugs" and that brings back some bad memories.

I was writing a program in MS Visual C++ on Window NT, and encountered a place in my code where the program would always crash. No compiler errors. The syntax was all correct. I then started walking through the assembly code with a debugger. In the middle of my function some system call was erroneously throwing an exception and crashing my program. Thank you Microsoft. So in the middle of my code, I added this try/catch block, empty brackets and all....


That caught the Windows NT system error and allowed my program to continue. Whoa to the future programmer that removes it because is "obviously" does nothing.

Comment ** Spoiler ** (Score 2) 285

It is the anonymous CORBAConnection variable that is create in the function call. Programmers create this anonymous variables all the time and never thing that it will bite them is the ass. Well, this one did and nearly took down the company too. Here is the explanation behind it.

CORBA communication is asynchronous, and thus COBRA connect object lives past the function that created it. When the communication thread that was using the connection is finished the original calling function that created it, has passed out of scope so there is no destructor called implicitly. And since there is no explicit variable, we cannot call the destructor explicitly either. With no way to call a destructor, there is no way to reclaim the memory, used thus the memory leak.

The solution was to explicitly declare a variable for the CORBA connection object and then call the destructor when it finished.

Comment Still haunts me (Score 1) 285

I was a young programmer working at my first startup company back in 1999. We had an communication app that talked using CORBA much as today you would used Web Services. We knew we had a memory leak and back then you only had a few megabytes of RAM so a memory leak could chew through all your memory pretty quickly. This bug was causing our servers to crash at least once a day and was in danger of taking down the whole company.

I didn't write the code, it was written by one of our senior engineers. He has insisted his code was right but I found the memory leak in his code using a debugger.

/*code snippet*/

returncode = CallCORBA( new CORBAConnect( /*Connection parameters*/), &header, &message);

if (returncode != ERROR)
/* continue processing other event */
/* handle error */

Comment Re:Must be Silicon Valley (Score 1) 264

Even if the house costs $1-1.5M, if you are making the salary to afford that house, you end up ahead. The higher cost of living results in higher salaries and in the end, the person making the higher salary accumulates more assets.

Here is a simpler example, Alex and Bob both buy a car for $500/mo and both have student loans for $1000/mo. For Alex, that is only 18% of his salary. For Bob, it is 36% of his. In the end, Alex will accumulate more assets in his working life.

Comment Re:Must be Silicon Valley (Score 1) 264

I agree with you. If the salary doesn't make up for the difference in housing prices, it is not worth it. The housing prices in San Francisco have just gone insane. Same thing for the housing prices in Manhattan. More than outstripping the salaries that they are now paying IT workers.

The best of both worlds is to do contract work in SV but live elsewhere. You get paid like the locals but then get to go home to a house with yard.

Comment Re:Must be Silicon Valley (Score 4, Interesting) 264

I always thought that the cost of living argument (SV vs non-SV) was bullsh*t. Let take two recent CS grads, Call them Alex and Bob.

Alex takes a job in San Francisco and is making $100K. He buys a house at 5x his salary ($500K) and lives in it for 30 years until the mortgage is paid off.
Bob takes a job in the midwest and is making $50K. He buys a house at 5x his salary ($250K) and lives in it for 30 years until the mortgage is paid off.

After 30 years, both Alex and Bob sell their houses and move to Florida. Both houses have doubled twice in those 30 years (look at the price of houses in 1985 and don't you wish had bought back then). Alex comes to Florida with $2M, Bob comes to Florida with $1M. So who is the winner, the one that lived in the low cost area or the one in a high cost area.

My point is that those in high cost of living areas are compensated for it and win in the long run.

Comment Work remote? Easy. (Score 1) 318

If you want to work remote, buy an expensive house. Seriously, that is the secret. I am lucky that I have a highly in demand skills and so have some leverage when it comes to negotiating salary and benefits.

The conversation usually goes something like this.

Mr. Employer: We loved your resume and the interviews when really well. We would like to offer you a job.
Me: Thank you. I would like to work for you.
Mr. Employer: We want to move you to our office in (somewhere not close)
Me: Thank you. I own my own home and would need a relocation package of £200,000 (US$300,000).
(long pause)
Mr. Employer: How would like to work remote...

Comment Re:Another diploma mill with a marketing team (Score 1) 85

I have applied to plenty of Wall Street jobs. Yes, what college you went to comes up, and even gets used as a filter at some places. It can get you in the door for the interview but reputation is not going to get you to the executive suite.

Elites are elite for a reason, they give you the knowledge, tools and connections to be successful.

Comment Re:Another diploma mill with a marketing team (Score 1) 85

You are the one that need to retake logic 101.

My assertion is the at elite colleges are elite because they produce more successful graduates. If that assertion is false, then elite colleges have nothing to do with the success their graduates and other non-elite colleges would produce equally as successful graduates. We reject the negative assertion is false.

ASHes to ASHes, DOS to DOS.