Isn't this old news? I thought that the Lotes Notes client was available for Linux for ages?
Anyway, Novell has had its groupwise client available in Java for some time now. Running on linux was flawless, and not at all limited to Novell's SuSe (I've got it running here on Debian). And if you don't like Java, there's an excellent web-based client.
I don't think it's all that bad. Remember, slashdot thrives on comments. Often these questions, however nonsensical they are, invite lots of discussion.
I agree with you, however when you turn off the PC, all the cached data from disk is cleared. Your apps now take ages to start et cetera. However, if you leave it on, it'll cost you $20 per month extra on the electricity bill. If you want a snappy but cheap PC, you're served best with an old laptop, which doesn't such that much power, and just leave it on permanently.
In the time you get a CS degree, which will be a couple of years, you'll be doing the same boring work. And besides that, there's no guarantee that the degree will get you more interesting work.
The only thing that will get you more interesting work is another job. I was also doing lots of Java programming in a business environment. I got tired of it and applied for a job at a space/climate research organization. It was a difficult interview, but I was very frank about my abilities and I got the job. We're using Linux (C, Perl) to read out custom made instruments. It's very challenging, but lots of fun.
There are still Jacks-of-All-Trades, except those new Jacks may know a scripting language or two, a bit of database, a bit of graphic design, a bit of apache, etc. And those new Jacks-of-all-Trades just couldn't market themselves under the old label Webmaster
I'm not talking about life and death, but about a future event where I might be brought unconscious into first aid. And I can damn well decide whether I want this data to be available in the future or not.
The situation you describe, sounds to me like a solution to a rather rare case.
What I find ridiculously in this whole affair is that the most important question is never asked. Do you want to join and be entered in our system?. I've worked in a similar project where some twenty-ish GP offices were joined in one network, in the Netherlands. Were the patients ever asked? Noooo, the GP just signed a paper where he agreed for all his patients who could then opt out. But most of the time, they wouldn't know about it.
And there comes the whole point: these medical data-sharing networks are useless if there isn't enough data. So nobody (the IT supplier, the medical organizations) has any incentive to keep patient data from being shared.
I'm not worried about employment application data, but I have been worried about the employment application itself. I mean, the IT industry is a small world, especially if you look for work within the same city. At one time I walked the last part to a company building for an interview, when I passed a current colleague of mine. I just greeted him but I could see the questionmarks in his face.
Actually, this is very environmentally friendly. Burning liquid petroleum gas is very clean, and cheap for the farmer. The grid would be severely loaded if directly tapped into for the scale that the huge greenhouses have.
Also, the generators are thoroughly insulated and because of this particular application (greenhouse), the excess warmth is directly used. This results in an extremely high energy/warmth ratio.
In the Netherlands, farmers who plant crops in greenhouses always have petroleum gases driven generators to warm the greenhouse in the winter. In summer, these generators feed back into the grid.
Concerning point 2: I'm residing in N/W Europe and have succesfully signed up for Google Checkout five minutes ago. Haven't bought anything with it yet.
Since there are quite some incidents occuring on the production environment,
Well, it obviously doesn't matter enough for your customers to have those projects 24/7 online, otherwise things would be different. So why bother?
In a previous job, we had three groups: development, system administration and application management & testing. Development would put the deployment files in a share and then sysadmin would take over, deploying it to acceptance and production if fiated by application management. If something went wrong, development would create new deployment files in a share. Sometimes when deployment was quick 'n' dirty, a developer would walk through the deployment with a sysadmin.
However, it took a very strong head of sysadmin. His manager would try to order quick 'n' dirty things, but the head of sysadmin would take it up higher to the boss. I heard once that when he got refused by the boss, he walked straight out of the door saying he'd quit. Boss ran straight after him:-)
It is extremely offensive that phone companies think they can take away things for which you have paid, without giving anything in return by expiring the minutes. That is one of the many, many consequences of having a corrupt government [futurepower.org].
You get bitten by it once, then move on to a provider who lets you keep your minutes forever, like Orange.
I can't really speak for a physicist since I'm a software engineer. I suspect it also depends a great deal on how many candidates they get for an opening...
I'd like to suggest that you look for a job in a research institute. What you're asking is NEVER going to fly in a business environment. I'm
currently working at SRON, a Dutch space
research institute. My current project involves a supercooled instrument which
receives waves in the 500-620 GHz range and will fly on a balloon somewhere
next year. I'm the software guy for the project and it's great work. You get
to work with very smart physics guys and the project has a bunch of
custom-designed electronics which I'm reading out and controlling.
I'm under some pressure right now because we're going to fly april 2007, but
normally, there is enough time to creatively do your job.
Check my website (for instance here) to see some stuff we're working on.
Yeah, however I'm certain these guys have been figuring that out by themselves. Suppose you only had Windows/DOS-related knowledge -- it could take a while before you have a nice shell script running, called from.xinitrc or something to restore any settings made.
I (used to) see Deepfreeze in action in other libraries. It returned the OS to a known, preset state, including stuff that restricted users can change like backgrounds, font settings et cetera.
Isn't this old news? I thought that the Lotes Notes client was available for Linux for ages?
Anyway, Novell has had its groupwise client available in Java for some time now. Running on linux was flawless, and not at all limited to Novell's SuSe (I've got it running here on Debian). And if you don't like Java, there's an excellent web-based client.
I agree with you, however when you turn off the PC, all the cached data from disk is cleared. Your apps now take ages to start et cetera. However, if you leave it on, it'll cost you $20 per month extra on the electricity bill. If you want a snappy but cheap PC, you're served best with an old laptop, which doesn't such that much power, and just leave it on permanently.
In the time you get a CS degree, which will be a couple of years, you'll be doing the same boring work. And besides that, there's no guarantee that the degree will get you more interesting work.
The only thing that will get you more interesting work is another job. I was also doing lots of Java programming in a business environment. I got tired of it and applied for a job at a space/climate research organization. It was a difficult interview, but I was very frank about my abilities and I got the job. We're using Linux (C, Perl) to read out custom made instruments. It's very challenging, but lots of fun.
Hehheh. Well, I'd stone her. Softly. With plush cows that 'mooo' when they hit her :-)
(j/k)
I'm not talking about life and death, but about a future event where I might be brought unconscious into first aid. And I can damn well decide whether I want this data to be available in the future or not.
The situation you describe, sounds to me like a solution to a rather rare case.
What I find ridiculously in this whole affair is that the most important question is never asked. Do you want to join and be entered in our system?. I've worked in a similar project where some twenty-ish GP offices were joined in one network, in the Netherlands. Were the patients ever asked? Noooo, the GP just signed a paper where he agreed for all his patients who could then opt out. But most of the time, they wouldn't know about it.
And there comes the whole point: these medical data-sharing networks are useless if there isn't enough data. So nobody (the IT supplier, the medical organizations) has any incentive to keep patient data from being shared.
I'm not worried about employment application data, but I have been worried about the employment application itself. I mean, the IT industry is a small world, especially if you look for work within the same city. At one time I walked the last part to a company building for an interview, when I passed a current colleague of mine. I just greeted him but I could see the questionmarks in his face.
Actually, this is very environmentally friendly. Burning liquid petroleum gas is very clean, and cheap for the farmer. The grid would be severely loaded if directly tapped into for the scale that the huge greenhouses have.
Also, the generators are thoroughly insulated and because of this particular application (greenhouse), the excess warmth is directly used. This results in an extremely high energy/warmth ratio.
In the Netherlands, farmers who plant crops in greenhouses always have petroleum gases driven generators to warm the greenhouse in the winter. In summer, these generators feed back into the grid.
Concerning point 2: I'm residing in N/W Europe and have succesfully signed up for Google Checkout five minutes ago. Haven't bought anything with it yet.
In a previous job, we had three groups: development, system administration and application management & testing. Development would put the deployment files in a share and then sysadmin would take over, deploying it to acceptance and production if fiated by application management. If something went wrong, development would create new deployment files in a share. Sometimes when deployment was quick 'n' dirty, a developer would walk through the deployment with a sysadmin.
However, it took a very strong head of sysadmin. His manager would try to order quick 'n' dirty things, but the head of sysadmin would take it up higher to the boss. I heard once that when he got refused by the boss, he walked straight out of the door saying he'd quit. Boss ran straight after him
I can't really speak for a physicist since I'm a software engineer. I suspect it also depends a great deal on how many candidates they get for an opening...
I'd like to suggest that you look for a job in a research institute. What you're asking is NEVER going to fly in a business environment. I'm currently working at SRON, a Dutch space research institute. My current project involves a supercooled instrument which receives waves in the 500-620 GHz range and will fly on a balloon somewhere next year. I'm the software guy for the project and it's great work. You get to work with very smart physics guys and the project has a bunch of custom-designed electronics which I'm reading out and controlling.
I'm under some pressure right now because we're going to fly april 2007, but normally, there is enough time to creatively do your job.
Check my website (for instance here) to see some stuff we're working on.
It's not a bug, it's the future
Yeah, however I'm certain these guys have been figuring that out by themselves. Suppose you only had Windows/DOS-related knowledge -- it could take a while before you have a nice shell script running, called from .xinitrc or something to restore any settings made.
Nice nickname BTW
I (used to) see Deepfreeze in action in other libraries. It returned the OS to a known, preset state, including stuff that restricted users can change like backgrounds, font settings et cetera.