Some years ago I worked for a really big telecom firm shipping POTS telco equipment to almost all countries in the world. We had this really smart guy who was working with a command module (a module that receives the CLI command the operator would type to configure something). During system test, one of our testers saw something in the code which looked really weired. It was not really weired but the code in this particular piece of code did something which wasn't obvious. The tester tried to enter a commad which excercised that particular piece of statements. Nothing happend. After a while he discovered this code was dependant on a specific type of hardware configuration. After this was set up he tried again to fire off the command. The reply was: Perre was here!
(his name was Per, Perre is slang). He was sent to the boss and he had to take it away. But I actually think this code got out to customers. If Per reads this you might wanna fill in what really happend at Ludde's office.
I agree. What I've also found out is that the programming language can help you a lot with the task of writing reliable software. If you haven't looked at Erlang yet, please do.
But one of the problems is that you would probably get 4 programmers from India at the same cost as a US programmer. At my company (in Sweden) we hire programmers from India as well, and we get 2 for 1. And if you compare what you make as a programmer per year here in Sweden compared to in the US, 4 for 1 doesn't sound too wrong in my ears.
Slashdot Mirror
Define "new" please.
Here in Sweden, the amount you have to pay back are based on your current salery so you won't end up in a situation as you describe.
Some years ago I worked for a really big telecom firm shipping POTS telco equipment to almost all countries in the world. We had this really smart guy who was working with a command module (a module that receives the CLI command the operator would type to configure something). During system test, one of our testers saw something in the code which looked really weired. It was not really weired but the code in this particular piece of code did something which wasn't obvious. The tester tried to enter a commad which excercised that particular piece of statements. Nothing happend. After a while he discovered this code was dependant on a specific type of hardware configuration. After this was set up he tried again to fire off the command. The reply was:
Perre was here!
(his name was Per, Perre is slang). He was sent to the boss and he had to take it away. But I actually think this code got out to customers. If Per reads this you might wanna fill in what really happend at Ludde's office.
I agree. What I've also found out is that the programming language can help you a lot with the task of writing reliable software. If you haven't looked at Erlang yet, please do.
Don't think it's a British idea. Most europeean countries have some sort of TV tax.
But one of the problems is that you would probably get 4 programmers from India at the same cost as a US programmer. At my company (in Sweden) we hire programmers from India as well, and we get 2 for 1. And if you compare what you make as a programmer per year here in Sweden compared to in the US, 4 for 1 doesn't sound too wrong in my ears.
It's +3 at the moment. That's not too bad.
Another good paper is Mr.Wiger's Four-Fold Increase in Productivity and Quality which can be found http://ais.gmd.de/~ap/femsys/wiger.pdf