> Some of these people are zealots for "Y", some of > these people are zealots against "X", some of these people think that using a crossover cable between '386s in the basement makes them some kind of expert in computer systems generally.
> While I value their opinions and their willingness to inform themselves, there are times where they need to stuff a sock in it and do the job, even if it means something against their judgement.
Well if Y = Linux and X = Windows, you've just described most slashdot readers.
I remember the emotions I felt when first hearing of this rescue story -- I was moved. It partly resulted in my feeling better about my (US) country having used military force in Iraq. I have crossed back and forth both for and against the war.
So when I hear that what was not widely reported, that they tried to deliver her to the Americans in an ambulance and American soldiers fired upon the ambulance would have affected me differently at the time.
The link in the signature reminded me of how actively our government manages the news to sway public opinion. I was manipulated by this process.
I find it very hard to believe that the soliders used blanks. But I am very much aware of how our government rushes news that would show them in a favorable light -- many times making statements that are later proven to be factually incorrect. However, they are reticent to comment on anything that would cast them in an unfavorable light. Anything unfavorable will forever remain "unsubstantiated" because our government won't comment on it.
I believe the BBC reporter also overstated his case. But without hearing his report, I would not be aware of how I had been manipulated.
So the goal of creating the "Fake" or rather exagerated story would be to sway public opinion in the US. This government wants to avoid the fate of President Johnson and the first President Bush.
Republican govenor Pete Wilson refered to the electricity deregulation bill, as he was signing it, as:
"landmark legislation [that] is a major step in our efforts to guarantee lower rates, provide consumer choice and offer reliable service, so no one literally is left in the dark."
When you are no longer an employee, you have to sell the stock.
You can't go to a broker and say, "Give me 100 shares of SAIC."
Re:SAIC is Employee-Owned - Employee-Ownership Roc
on
Inside SAIC
·
· Score: 2, Informative
I can answer this from my own experience.
I was an employee there (1988-1993). When you signed up for a 401(k), the first $2000 of your contributions and all of the companies contributions went into company stock.
Once a quarter, you could trade out of company stock, but you had to take the initiative. If you were a high-level manager, I suppose you would have to explain why you kept selling SAIC stock. But I was just a programmer there and I did sell blocks of stock that were in my IRA. I would have made more money if I had left it in SAIC stock though.
The article says that they beat the S&P 500 and I can attest to that during the years I was there.
In 20 years of working in the computer business I have never seen more formal project management -- especially on fixed price contracts.
Do you know how many of them changed it right after you left?
Sometimes you have to give up your password. If you are out sick and one of your co-workers needs to get at your account. That is when it is good not to use the same password everywhere, so they don't have access to your other accounts.
Another possiblity is that the Windows System Admin set up the server, and applied all the patches. He or she was simply laid off 6 months ago.
I once set up a stock RedHat 5.2 server running Apache on the Internet. When I quit, I don't think I was replaced (the server kept running). A few years later, I heard that the web site was defaced.
It sounds like you had a bad experience and want to share your opinion of "how shitty an IT job can be."
Some of us manage to stay programmers for over 20 years. Part of the trick is to quit when they have you work insane hours for more than a short while. I have met a lot of programmers who have worked from 10 to 25 years as programmers. I have also met people who worked 24 to 40 hour shifts for pre-IPO startups, thinking they were going to get rich. I would have a hard time keeping that up for more than 4 years.
You should work with the attitude that with each paycheck, you and your employer are even. Then, if they start to abuse you, you can leave -- you are not leaving behind promises of future riches.
Programming was (and still is) a hobby for me. It is also what I do for a living.
1) Physics (gravity) - It takes a lot of fuel to get a pound of anything into space. Putting a lot of space station up costs a lot of money.
2) Manned is much more expensive than unmanned. If people are going up, you have to be very careful things don't go wrong. Losing life is much worse than losing $10 million satelites. Being careful costs more.
I'm sure many here believe that it is government inefficiency. I would argue that private inefficiency is not much cheaper. What happens when the private company that has done half the work and spent half the money goes out of business?
People who believe that only government is inefficient have never worked for a large company. And small companies are less stable than large ones. It is so much easier to imagine space travel and write books about it than it is to achieve it.
This seems like a chicken and egg thing. How does your userbase grow if your programs are hard to use?
I have been using the GNOME desktop, as it comes with each version of RedHat Linux. The version of GNOME that came with the RedHat 8.0 upgrade completely changed all my menus. I have trouble finding stuff now. I needed to look up someones address in my address book. I found my cards.vcs and found the phone number using the shell and vi, I still haven't found the address book program I used to use. For Linux to "take over the desktop", do we need an army of masochistic users to use Linux and get so frustrated that they get involved and fix the usability?
It seemed to me that the article had a lot of thought and research in it and I think it would be quite a missed opportunity if the Free Sofware/Open Source community did not take it seriously.
That's odd, I don't remember Stastical Mechanics and Thermal Physics in high school. I don't remember a class in operating systems or compiler design in high school either.
Unfortunately, my experience with the commercial J2EE product was from within the company that owned and sold the product.
So even though there was "support", we couldn't get it (the cobler's children has no shoes). We could not use one of the more popular commercial J2EE environments, because they were a competitor.
We would not have needed to get support for Tomcat because we could figure it out for ourselves. Internal politics, however, made it very difficult to build a web app without EJBs.
Other projects that started earlier were finding that they had performance problems with our J2EE plaform and they had to use bigger hardware than what was planned.
A project that implemented using Servlet technology and got into production before J2EE became the "one true way" is stable in production under Tomcat. It is in use world wide. Of course, your mileage may vary. Your choice of J2EE platform may have better support and work better than the one we used.
I think you underestimate the proprotion of production websites that do not use the EJB portion of J2EE.
A web app based on Servlets or JSP but not EJB can handle plenty of traffic. And you avoid the large architecture, large programming staff and long schedules of J2EE based web apps. Not everyone is a yahoo or an amazon.
Also, the J2EE environments are much harder to configure. Unless you have a crew of developers with lots of J2EE experience on your platform, you are going to have developers trying to figure out why there EJB code doesn't work instead of implementing business logic.Your mileage may vary, but I have yet to hear of a J2EE environment that was easy to configure and didn't fight you every step of the way.
I saw a documentary on television where they talked about the challenge of keeping up digital records at the National Archives and Records Administration. The problem there was that the volume of digital data produced every year grew geometrically. And challenge of keeping up with all the formats that have been produced over the last thirty years.
I think they first started having trouble with 9 track digital tapes (which may only last 5 years or so). Then there is the problem of keeping computer hardware and software that reads all the formats.
They face a task of constantly converting an ever increasing amount of data.
Keeping digital copies is only cheaper than paper once you have digitized the paper. A book printed on acid free paper can last a couple of hundred years. Your multiple redundant digital copies made 10 years ago on 1/4 inch tapes would have to be converted from the non-HTML hypertext format they thought was really cool at the time to HTML/SGML/XML or whatever we think is cool now and then stored on to our CDRW/DVD/what have you. Multiply this by every book published in the last 10 years. Then keep the hardware/software around for 10 years too so you can continue to read them. Do this 20 times to get the same results of keeping an archival book on the shelf for 200 years.
I have seen a lot of posts like this. They imply that somehow, if you are out of work, you must be less qualified than those who are working.
But a lot of big companies did large layoffs that were in large part random. Mangers were given targets to meet for headcount.
I know of several qualified programmers who are out of work. There employment status has nothing to do with their ability.
Normally, it would be easy for a qualified candidate to find another job quickly. But now there are lots and lots of qualified un-employed people and very few jobs (in IT). So if you are working, and you think it is because you are hot stuff. Lets hope YOUR bubble doesn't get burst.
Slashdot Mirror
Which integer do you multiply a frequency by to get a lower frequency?
I'm just curious.
> Some of these people are zealots for "Y", some of > these people are zealots against "X", some of these people think that using a crossover cable between '386s in the basement makes them some kind of expert in computer systems generally.
> While I value their opinions and their willingness to inform themselves, there are times where they need to stuff a sock in it and do the job, even if it means something against their judgement.
Well if Y = Linux and X = Windows, you've just described most slashdot readers.
I remember the emotions I felt when first hearing of this rescue story -- I was moved.
It partly resulted in my feeling better about my (US) country having used military force in Iraq.
I have crossed back and forth both for and against the war.
So when I hear that what was not widely reported, that they tried to deliver her to the Americans in an ambulance and American soldiers fired upon the ambulance
would have affected me differently at the time.
The link in the signature reminded me of how actively our government manages the news to sway public opinion.
I was manipulated by this process.
I find it very hard to believe that the soliders used blanks.
But I am very much aware of how our government rushes news that would show them in a favorable light -- many times making statements that are
later proven to be factually incorrect.
However, they are reticent to comment on anything that would cast them in an unfavorable light.
Anything unfavorable will forever remain "unsubstantiated" because our government won't comment on it.
I believe the BBC reporter also overstated his case. But without hearing his report, I would not be aware of how I had been manipulated.
So the goal of creating the "Fake" or rather exagerated story would be to sway public opinion
in the US.
This government wants to avoid the fate of President Johnson and the first President Bush.
Republican govenor Pete Wilson refered to the electricity deregulation bill, as he was signing it, as:
"landmark legislation [that] is a major step in our efforts to guarantee lower rates, provide consumer choice and offer reliable service, so no one literally is left in the dark."
You have to be an employee to buy the stock.
When you are no longer an employee, you have to sell the stock.
You can't go to a broker and say, "Give me 100 shares of SAIC."
I can answer this from my own experience.
I was an employee there (1988-1993). When you signed up for a 401(k), the first $2000 of your contributions and all of the companies contributions
went into company stock.
Once a quarter, you could trade out of company stock, but you had to take the initiative.
If you were a high-level manager, I suppose you would have to explain why you kept selling SAIC stock.
But I was just a programmer there and I did sell blocks of stock that were in my IRA.
I would have made more money if I had left it in SAIC stock though.
The article says that they beat the S&P 500 and I can attest to that during the years I was there.
In 20 years of working in the computer business I have never seen more formal project management -- especially on fixed price contracts.
Open the patio door HAL.
On memorial day weekend.
http://www.kineticsculpturerace.org/
Don't forget transparent client switchover when the primary being replicated goes down.
Replication safeguards the data, the client switchover on the fly provides high availability.
THORVALDS is REAL but LINUS is INTEGER.
To make LINUS REAL by default, I think you need:
IMPLICIT (L)
or
REAL LINUS
About a dozen years ago, I worked on an OS called Trusted Xenix. It was put out by
Trusted Information Systems.
It ran quite nicely on about 15 MB of hard drive space on a 386.
But searching the web today, I don't think it is alive anymore.
It was no where near as nice to work with as Linux is, though.
Do you know how many of them changed it right after you left?
Sometimes you have to give up your password. If you are out sick and one of your co-workers needs to get at your account.
That is when it is good not to use the same password everywhere, so they don't have access to your other accounts.
Another possiblity is that the Windows System Admin set up the server, and applied all the patches.
He or she was simply laid off 6 months ago.
I once set up a stock RedHat 5.2 server running Apache on the Internet.
When I quit, I don't think I was replaced (the server kept running).
A few years later, I heard that the web site was defaced.
The end user may not see this as a problem.
If you tell them "The problem with Access is that it doesn't run on Linux or any other non-Windows operating system."
They will reply "The problem with Linux is that it doesn't run Access."
Your average person doesn't care too much about operating systems.
Computer professionals do.
Yeah, if these guys don't like Linux, why don't they write their own operating system.
Oh, never mind.
It sounds like you had a bad experience and want to share your opinion of "how shitty an IT job can be."
Some of us manage to stay programmers for over 20 years. Part of the trick is to quit when they have you work insane hours for more than a short while.
I have met a lot of programmers who have worked from 10 to 25 years as programmers.
I have also met people who worked 24 to 40 hour shifts for pre-IPO startups, thinking they
were going to get rich.
I would have a hard time keeping that up for more than 4 years.
You should work with the attitude that with each paycheck, you and your employer are even.
Then, if they start to abuse you, you can leave -- you are not leaving behind promises of future riches.
Programming was (and still is) a hobby for me. It is also what I do for a living.
It is still fun.
Two reasons:
1) Physics (gravity) - It takes a lot of fuel to get a pound of anything into space. Putting a lot of space station up costs a lot of money.
2) Manned is much more expensive than unmanned. If people are going up, you have to be very careful things don't go wrong. Losing life is much worse than losing $10 million satelites. Being careful costs more.
I'm sure many here believe that it is government inefficiency. I would argue that private inefficiency is not much cheaper.
What happens when the private company that has done half the work and spent half the money goes out of business?
People who believe that only government is inefficient have never worked for a large company.
And small companies are less stable than large ones.
It is so much easier to imagine space travel and write books about it than it is to
achieve it.
>
> This will change as the userbase grows.
>
This seems like a chicken and egg thing. How does your userbase grow if your programs are hard to use?
I have been using the GNOME desktop, as it comes with each version of RedHat Linux.
The version of GNOME that came with the RedHat 8.0 upgrade completely changed all my menus.
I have trouble finding stuff now.
I needed to look up someones address in my address book.
I found my cards.vcs and found the phone number using the shell and vi, I still haven't found the address book program I used to use.
For Linux to "take over the desktop", do we need an army of masochistic users to use Linux and get so frustrated that they get involved and fix the usability?
It seemed to me that the article had a lot of thought and research in it
and I think it would be quite a missed opportunity if the Free Sofware/Open Source community did not take it seriously.
That's odd, I don't remember Stastical Mechanics and Thermal Physics in high school.
I don't remember a class in operating systems or compiler design in high school either.
Unfortunately, my experience with the commercial J2EE product was from within the company that owned and sold the product.
So even though there was "support", we couldn't get it (the cobler's children has no shoes).
We could not use one of the more popular commercial J2EE environments, because they were a competitor.
We would not have needed to get support for Tomcat because we could figure it out for ourselves.
Internal politics, however, made it very difficult to build a web app without EJBs.
Other projects that started earlier were finding that they had performance problems with our J2EE plaform and they had to
use bigger hardware than what was planned.
A project that implemented using Servlet technology and got into production before J2EE became the "one true way" is stable in production under Tomcat.
It is in use world wide.
Of course, your mileage may vary. Your choice of J2EE platform may have better support and work better than the one we used.
I think you underestimate the proprotion of production websites that do not use the EJB portion of J2EE.
A web app based on Servlets or JSP but not EJB can handle plenty of traffic.
And you avoid the large architecture, large programming staff and long schedules of J2EE
based web apps.
Not everyone is a yahoo or an amazon.
Also, the J2EE environments are much harder to configure.
Unless you have a crew of developers with lots of J2EE experience on your platform,
you are going to have developers trying to figure
out why there EJB code doesn't work
instead of implementing business logic.Your mileage may vary, but I have yet to hear of
a J2EE environment that was easy to configure
and didn't fight you every step of the way.
Tomcat is a breath of fresh air by comparison.
I saw a documentary on television where they talked about the challenge of keeping up digital records at the National Archives and Records Administration.
The problem there was that the volume of digital data produced every year grew geometrically.
And challenge of keeping up with all the formats that have been produced over the last thirty years.
I think they first started having trouble with 9 track digital tapes (which may only last 5 years or so).
Then there is the problem of keeping computer hardware and software that reads all the formats.
They face a task of constantly converting an ever increasing amount of data.
Keeping digital copies is only cheaper than paper once you have digitized the paper.
A book printed on acid free paper can last a couple of hundred years.
Your multiple redundant digital copies made 10 years ago on 1/4 inch tapes would have to be converted from the non-HTML hypertext format they
thought was really cool at the time to HTML/SGML/XML or whatever we think is cool now and then stored on to our CDRW/DVD/what have you.
Multiply this by every book published in the last 10 years.
Then keep the hardware/software around for 10 years too so you can continue to read them.
Do this 20 times to get the same results of keeping an archival book on the shelf for 200 years.
Well, there is nothing to prevent some of your views also being models.
n %2 0Presentation%20Abstra/
Also, as an alternative to MVC, take a look at Presentation Abstraction Control.
Google yielded this site, among others:
http://www.vico.org/pages/PatronsDisseny/Patter
The subtle message is this. BEA Web Logic is the number one J2EE environment.
So they only bothered to document setup for that.
Some time ago, when I was looking for J2EE books, I noticed that most of the vendor specific stuff
in books was for Web Logic.
I was looking for books on HP Bluestone at the time.
I have seen a lot of posts like this. They imply that somehow, if you are out of work, you must be
less qualified than those who are working.
But a lot of big companies did large layoffs that were in large part random.
Mangers were given targets to meet for headcount.
I know of several qualified programmers who are out of work.
There employment status has nothing to do with their ability.
Normally, it would be easy for a qualified candidate to find another job quickly.
But now there are lots and lots of qualified un-employed people and very few jobs (in IT).
So if you are working, and you think it is because you are hot stuff.
Lets hope YOUR bubble doesn't get burst.