|
I work to get payed so I can do whatever I like on my own time
I try to work where I like and using the technologies I want but if I get a very good offer on a not so cool technology I will certainly take it!
|
|
|
|
|
There is nothing wrong with getting paid for honest work, but when someone says he is in programming only for money, my first thought is: Programming: Love It or Leave It[^].
|
|
|
|
|
I don't work "only" for money...
But I do in fact jobs for others that I wouldn't do if I wouldn't get well payed for it.
So I can say that if "you" pay me well I'll use whatever language you want me to
|
|
|
|
|
There are only two things I've been paid to do since I started university - shovel horse manure (really!) and code. Coding pays better and there are more job opportunities. And, it's my favorite hobby. So I guess I'm with you on that.
Henry in Ottawa
|
|
|
|
|
I hate it when people do stuff like that. Case in point:
One place where I worked they had a Unix server that was used for training exercises. The system was basically text interface driven with 1000s of users logging in at once and the applications were all written in C++. Some new functionality was added and the next time the system was run up it was reduced to a crawl because it didn't have enough RAM to handle the load. Over time memory was expanded to 32GB, and then more servers were clustered bring the number of servers up to 8 instead of 1. After a year of this a really clued up C++ guy went into the code to see what was going on, turns out that some new guy preferred Java and had converted one of the small apps to Java - each of the 1000s of users that logged in was creating a 70MB+ virtual machine! The C++ guy converted the app back to C++ and then everything was running happily again on 1 machine within 1GB of RAM.
|
|
|
|
|
so you like when refactoring is applied with c++
(so do i)
|
|
|
|
|
One of the main things I like about .NET is that I can call C++ libraries directly from C#. This means that when I get handed some C# GUI app that say does some signal processing and needs to be sped up I can just refactor the part that processes the signal bits and bytes in native C++ and get a 5x speedup! People think I'm doing some kind of magic.
I've read...somewhere... that Windows 7 is much improved over Vista merely because they ported some of the .NET middle layers to native code.
|
|
|
|
|
That means microsoft is certainly going back in time
|
|
|
|
|
Learning from their mistakes.
|
|
|
|
|
Performance always increases the closer the code is to the metal. .NET is a great application platform, as is Java, but system services on which system performance depend deserve the time and care that creation of a native binary can bring.
|
|
|
|
|
Yeah good points, although I'm surprised that they didn't review the code before chucking 7 more servers at it?
The only thing unpredictable about me is just how predictable I'm going to be.
|
|
|
|
|
I once rewrote a program that worked only for a special case but was in assembler into Pascal to make it work for the general case. The next guy along wrote it back into assembler, for a trivial but measurable speedup.
People who rewrite working code have too littel real work to do.
Henry in Ottawa
|
|
|
|