The problem is that our rights and freedoms are reduced a little bit again.
You might say, "Only people with something to hide need fear this." That's not true. I guarantee every single person out there breaks a law when he or she gets behind the wheel. "The Man" could take you down at any time.
If it is not the government (which is at least minimally restrained by the Constitution), NOTHING restrains private enterprise. What's to stop them from publishing their "shoplifting list" to other businesses? What if you're falsely accused of shoplifting in another state and you quickly find that you can't even go to your local grocery store because now you're a "bad element"?
Life can't be made "safe." We can't lock up all of the criminals, because we are all criminals. The key is to balance law and provide acceptable risk, not devolve into some damn draconian corporate state where is it illegal to have independent thought.
Raw sockets in windoze is not the end of the world. *nix systems have them, even vxworks
The difference is that real operating systems (i.e., *nix), prevent ordinary user accounts from getting to the really low level / powerful things, like SUID programs or raw sockets. Windoze takes the "What me worry?" approach to segmenting user privileges, and that is where the problem lies.
Seeing as how Zone Alarm is the only darn free/software firewall that appears to work, then why run anything else? I'd like to see Microsoft's crack team of security "experts" come up with something comparable.
By default, under this scenario, your PC becomes a TCP/IP read-only device. By running applications like Gibson's Zone Alarm you can -- right now -- severely limit the use of TCP/IP by applications on your PC
Actually, the varcar2 variable question is a "trick" question -- no one is supposed to know the answer, but the way they answer it (if they BS their way through) and how they answer it (demonstrating their command of English) tells us enough to either decide whether to bring them in for a face-to-face or not.
Trivia is garbage because anyone can look that stuff up (that's what really irks me about the various certification tests -- they don't test your ability to reason things, just to puke up the stock answer).
I got the job, because I proved that I could handle a real problem, not a silly contrived one.
Exactly!! Most interviews are stupid ("What job would you have if this were a circus?"), irrelevant ("How do you find out how to use 'man'?") or clichéd ("Where do you see yourself in five years?"). They offer nothing in the way of testing the candidates ability to do the job.
Good hiring managers know that the best way to insure someone can do the job is to let them do the job in the interview. That is a simple concept, but the most powerful way to weed out the losers.
What we do is fire up our little Sparc 5, give them the root password and tell them to get the box up on the network, add users, mount remote drive nn and set up printer xx. Oh and while you're at it, set up the korn shell with some specific characteristics (alias, PS1=, blah, blah).
Those who know their stuff will have no sweat. Those who are 'paper tigers' will quickly wash themselves out.
The rumors were true! I knew Hollywood was really a government front to prepare the populace! That explains this classic quote: "Nuke 'em from space. That's the only way to be sure" -- Ripley, Aliens
Is Hollywood so starved for ideas that they have to mine for sequels this low? (rhetorical question, of course...)
Not that they are rift of ideas, but rather that they are run by beancounters who want maximum profit for minimal expenditure. One attractive idea (for them) is to despense with the "writer," take a previously hit film and use contract hacks to rework it.
That's why we get drek like:
Planet of the Apes,
Psycho,
Beverly Hillbillies,
Rollerball,
Parent Trap,
Star Wars "digitally remastered", et cetera
Don't worry, there are a plethora of successful, classic films that Hollywood can remake! I'm still waiting for the John Wayne stuff to come up again -- maybe this time by a hot-shot, fit, muscular actor rather than a drunk, overweight womanizer named Francis.
I was a manager during the period in question, and I can tell you, I had a devil of a time filling a couple of positions
I am also a manager, and when I received the directive from management to bring in another PL/SQL contract programmer to help out on our project, I wanted to scream. This caused two problems:
According to Rapid Development (which every DEV manager, director and executive needs to read), one of the classic mistakes of development is to add a new developer in the middle of the project in the hopes that it will speed development time, and
We would have to find a single qualified person that could learn our design and approach quickly...and who was not currently working or who was ready to leave his/her current position.
We were also hampered by the fact that our $#@! company has an exclusive contract with one of the body shops. What this means is that they would push their own people first no matter how incompetent, before they brought in anyone else from other body shops.
Now, there are a lot of database people out there. A lot. I looked at more resumes than I can count. My ear was sore from phone interviews.
Exactly my experience. There are many PL/SQL folks out there -- both H1B and American citizens. 99% of them were weak in either coding skills or couldn't speak/understand English (another requirement). We had one guy who could correctly pass the hardest phone interview question (What is the maximum size of a VARCAR2 variable in PL/SQL?), but when we brought him in and asked him to write a simple select statement, he got as far as "select * from" and then he stopped, because he'd reached the end of his skills.
From the article, the author gives this advice to developers:
The answer is, sad to say, that you should engage in frequent job-hopping. Note that the timing is very delicate, with the windows of opportunity usually being very narrow, as seen below.
I couldn't agree more. Since most companies are no longer willing to train lesser-competent folks and age them into the positions needed (thus indirectly lowering turnover, duh), then it is up to us to train ourselves, then leave when we can get a better/different job. Someone I used to work for told me that I needed to switch jobs every 3 years, because I'd fall behind in the pay raise schedule. He figured about a 20% pay rate increase was acceptable. With HR mandating 3-6% merit increases (maybe <g>), one will fall behind after three years. I also read in one of the trade rags that the average lifespan of an IT worker ranged from 2.5 to 5 years, which matches my experience. That is a LOT of turnover, which companies pay for by the knowledge/skill loss and the cost to replace.
Never mind that the knowledge and experience is lost forever. We keep making the same mistakes over and over again because we keep forgetting things we did in the past. "If we implement this function at the end of the accounting batch run without notifying Ms. Somebody in accounting exactly 4 days prior and Mr. Whomever on the web team exactly 2 weeks prior, but not via email--only in person, then the process will need to be reset manually," et cetera. Well, Coder Bob figured that out by being burned once, and now he left to another company to do KDE extensions; no one knows what he did in that area, just that he coded report statements.
If companies would treat their workers better (by actually acting like "Employees are [their] most valuable asset") then we will see a decrease of H1Bs, of any skilled talent shortage and of this constant ri-goddamn-diculous job hopping.
Until then, let them whine while we job-hop, learning what we can and taking our knowledge and experience with us to the next gig.
We started using these about 4 years ago. In a business setting, they make sense for:
University/training PCs - Need a new OS for a different class? Swap it out! Want to start fresh for the next class? Swap out the current drive with a fresh drive!
Remotely-supported PCs - We kept three drives for remote users. Drives 1 and 2 were in the user's posession; drive 3 stayed at work in a secured area. If the user's OS or apps fried, they were told to swap drives and bring the bad one in. We would reimage the bad one from the one in the office and then hand it back to them.
We should be sending Marines there and oil rig miners...
Pleased to explain what "miners" have any business doing on an oil rig. Last time I checked, miners pulled minerals or stones out of the ground from a mine, not a rig.
Why bother with that Internet thing when we can pull those nasty books off the shelves and burn them to keep such filth out of childrens' minds, eh?
Good idea, Herr Doktor!
Seig Heil!
Microsoft didn't have it either.
When I was on the floor back in '98, there was only _ON_ NT box -- it was used for monitoring the other systems. What did they use? Unix, of course.
>Where's the problem?
The problem is that our rights and freedoms are reduced a little bit again.
You might say, "Only people with something to hide need fear this." That's not true. I guarantee every single person out there breaks a law when he or she gets behind the wheel. "The Man" could take you down at any time.
If it is not the government (which is at least minimally restrained by the Constitution), NOTHING restrains private enterprise. What's to stop them from publishing their "shoplifting list" to other businesses? What if you're falsely accused of shoplifting in another state and you quickly find that you can't even go to your local grocery store because now you're a "bad element"?
Life can't be made "safe." We can't lock up all of the criminals, because we are all criminals. The key is to balance law and provide acceptable risk, not devolve into some damn draconian corporate state where is it illegal to have independent thought.
Even though the first movie sucked (IMHO, the first good one was ST:TUC - don't believe me? Rent 'em and groan!).
At least the re-edit will make for some good Trekker/ie alternative view.
- "It's" does not mean it possessive. It means "it is" -- a contraction.
- Judging from the context of your sentence, I assume you mean the movie's title, not the title of the movie is "title."
- In this case, you need to use "its" -- the proper form of it possessive.
Final Grade:Content - B+
Editing - D
- Paint everything yellow
- Attach to belt
- Grey tights and cape optional
Dork!The difference is that real operating systems (i.e., *nix), prevent ordinary user accounts from getting to the really low level / powerful things, like SUID programs or raw sockets. Windoze takes the "What me worry?" approach to segmenting user privileges, and that is where the problem lies.
Seeing as how Zone Alarm is the only darn free/software firewall that appears to work, then why run anything else? I'd like to see Microsoft's crack team of security "experts" come up with something comparable.
Oh wait, they did.
Hahahahah
I didn't know Steve Gibson wrote Zone Alarm. When did this happen? What happened to Zone Labs?!
Nah, it was both Hicks and Ripley.
Trivia is garbage because anyone can look that stuff up (that's what really irks me about the various certification tests -- they don't test your ability to reason things, just to puke up the stock answer).
Exactly!! Most interviews are stupid ("What job would you have if this were a circus?"), irrelevant ("How do you find out how to use 'man'?") or clichéd ("Where do you see yourself in five years?"). They offer nothing in the way of testing the candidates ability to do the job.
Good hiring managers know that the best way to insure someone can do the job is to let them do the job in the interview. That is a simple concept, but the most powerful way to weed out the losers.
What we do is fire up our little Sparc 5, give them the root password and tell them to get the box up on the network, add users, mount remote drive nn and set up printer xx. Oh and while you're at it, set up the korn shell with some specific characteristics (alias, PS1=, blah, blah).
Those who know their stuff will have no sweat. Those who are 'paper tigers' will quickly wash themselves out.
Yahoo sez: This page is not available.
How do they get it out of the lake? "Apes can't swim."
The rumors were true! I knew Hollywood was really a government front to prepare the populace!
That explains this classic quote: "Nuke 'em from space. That's the only way to be sure" -- Ripley, Aliens
I am also a manager, and when I received the directive from management to bring in another PL/SQL contract programmer to help out on our project, I wanted to scream. This caused two problems:
We were also hampered by the fact that our $#@! company has an exclusive contract with one of the body shops. What this means is that they would push their own people first no matter how incompetent, before they brought in anyone else from other body shops.
Exactly my experience. There are many PL/SQL folks out there -- both H1B and American citizens. 99% of them were weak in either coding skills or couldn't speak/understand English (another requirement). We had one guy who could correctly pass the hardest phone interview question (What is the maximum size of a VARCAR2 variable in PL/SQL?), but when we brought him in and asked him to write a simple select statement, he got as far as "select * from" and then he stopped, because he'd reached the end of his skills.From the article, the author gives this advice to developers:
I couldn't agree more. Since most companies are no longer willing to train lesser-competent folks and age them into the positions needed (thus indirectly lowering turnover, duh), then it is up to us to train ourselves, then leave when we can get a better/different job. Someone I used to work for told me that I needed to switch jobs every 3 years, because I'd fall behind in the pay raise schedule. He figured about a 20% pay rate increase was acceptable. With HR mandating 3-6% merit increases (maybe <g>), one will fall behind after three years. I also read in one of the trade rags that the average lifespan of an IT worker ranged from 2.5 to 5 years, which matches my experience. That is a LOT of turnover, which companies pay for by the knowledge/skill loss and the cost to replace.
Never mind that the knowledge and experience is lost forever. We keep making the same mistakes over and over again because we keep forgetting things we did in the past. "If we implement this function at the end of the accounting batch run without notifying Ms. Somebody in accounting exactly 4 days prior and Mr. Whomever on the web team exactly 2 weeks prior, but not via email--only in person, then the process will need to be reset manually," et cetera. Well, Coder Bob figured that out by being burned once, and now he left to another company to do KDE extensions; no one knows what he did in that area, just that he coded report statements.
If companies would treat their workers better (by actually acting like "Employees are [their] most valuable asset") then we will see a decrease of H1Bs, of any skilled talent shortage and of this constant ri-goddamn-diculous job hopping.
Until then, let them whine while we job-hop, learning what we can and taking our knowledge and experience with us to the next gig.
You are correct. It was Michael Fay, the American who was "convicted" of a crime in Singapore and flogged.
My only beef with them is the small screen. That and the lack of "network" support. Has anyone figured out how to connect one to an ethernet network?
In some ways, it would be nice if stories contained mirrors, so we wouldn't have to go through this exercise in the first place.
Beyond the first post trash comes 'first read.'
Sigh...
I asked the 'Shack lady if I could have more than one and she refused. I guess she doesn't know about Digital Convergence's "restructuring"...
Only if they caught you cutting your face...and you were in the military / product of government research.
:)
Pleased to explain what "miners" have any business doing on an oil rig. Last time I checked, miners pulled minerals or stones out of the ground from a mine, not a rig.
End transmission.
Well, at least the fat lady hasn't sung yet...