And, yes, if they're going to sell Linux machines then they damn well need to support them. Does that mean they may not make as much on Linux machines in the short term? Perhaps, since they'll need to build a support staff. In the longer run, they'll discover they're getting a lot fewer support calls per Linux machine than they do for Windows.
I think the real reason they don't sell much linux is because it will cut into sales.
The real reason people upgrade is because their machines are too slow. Why are they too slow? Because the Windows registry has grown to 50M+, the machine is all crapped up with viruses and spyware and the half-dozen apps that are supposed to prevent all this are gumming up the works themselves.
How would Dell stay in business selling machines where someone would buy it, and say "thanks, see you later" and not buy another one for 10 years.
One of my customers runs a mixed shop (Windows & Linux). They can't buy the Windows servers fast enough to keep up with the ever-growing software requirements. I get the old machines, which are now handling things like running postfix on 20K inbound emails/day, and generally running at less than 2% utilization.
Most of them don't even know that the reason the Exchange boxes haven't gone down in flames is because there's a 233Mhz P-III, loafing along, guarding the door.
Running Linux on desktops and servers would eliminate the need to buy new machines on an almost annual cycle.
Find another job. Being "promoted" to manager is about the same as when they "promote" a cow to being hamburger.
Your boss will be pressuring you to get things done faster/cheaper/better/different, the customers will be trying to push a never-ending chain of changes on your (with no increase in budget or time) and your developers will never be ready by your deadlines.
Run away! Manager is a completely different job, which you are not prepared for and will not like.
Software means that if you say x:=1, then x==1. Management is where you say "x:=1" and everybody else tries to make it "3" or ".95" or "blue" or "happy meal".
Terry
I've been writing software since "high level language" meant that the assembler understood named labels. Poorly written software had exploitable pointers back then too.
This is just as newsworthy as the discovery that bears crap in the woods.
Who would have thought that invalid pointers and buffer overruns might be exploitable as a security hole?
Quick, someone alert Bill Gates!
Re:Space is what keeps us from screwing other plan
on
Interstellar Ark
·
· Score: 0
Man. you have issues. Seek medical advice. Fast.
Seek medical advice for what?
For having seen a lifetime of man's stupidity, cruelty and disregard for every living entity on the planet, including all the animals and other humans?
For knowing that in less than a couple of hundred years man has dumped so much CO2 into the atmosphere that we have brought the planet past the tipping point and will not be able to stop
catestrophic climate changes and mass extinctions in the near future?
Colonizing uninhabited worlds is OK with me, but I would have deep misgivings about letting humans set foot on another unspoiled planet similar to Earth. If we want a nice place to live, we should fix the one we have right here.
Space is what keeps us from screwing other planets
on
Interstellar Ark
·
· Score: 0
All I can say is "Thank God for the vastness of space".
It's the only thing that keeps us from destroying every other garden spot in the universe.
I firmly believe that it's not accidental that the technology needed to travel great distances is not attainable in the same era that nuclear and biological weapons were invented.
I have no doubt that we would bring massive destruction to any new planet, regardless of our good intentions.
Maybe in another few thousand year we'll begin to be ready.
Yah right. Do you have any idea how few good coders there are? Now add that to the chance they happened to write nothing but open source (yah, cause you can make so much money doing that). See the picture? Reality: Most open source code is written by semi-good coders - which means, oh boy, walking the code is gonna be an exercise in torture (it's only one step below that when it is good code, btw).
No kidding
I've been writing code since the 80's and by the time I get done with the latest stomach-churning panic-inducing gotta-have-it-by-friday design change that will be superceded by one of it's friends next month, the last thing I want to do is start rooting through perfectly functional code looking for potential privacy violations.
It's a free (or cheap) phone call. If anybody doesn't like it, they don't have to use it.
What kind of company won't even let you take a crap without working?
Maybe now call-centers will start haing their employees answer phone calls on the crapper.
"You're allowed 1 3 minute bathroom break between 10:00AM and 10:03AM, but you are required to answer calls during this time.
With a credit card, you need not sue over false billings. Your first stop is to dispute the charge with your credit card company, which usually takes care of the issue. Only after that fails, do you need to worry about your "other options".
But that wasn't really my point. My point is that if you owe a company money (or in your case, if a company thinks (incorrectly) that you owe them money), they are going to attempt to collect it. Your virtual credit card numbers are not going to provide the barrier that you think they provide, that's all I'm saying.
Not to pick fight, but in the case of the long distance company, if they had a real CC, I'd be in the position of trying to sue them for $40. Because it was virtual, they have to sue me to collect, which means that they have to prove I made the calls on their service, which they can't do. It just changes the balance of power in my favor.
n fact, even in the "billing problems" situation, the company will probably still turn you over to collections since according to their (buggy) computer, you owe them money. It's gonna be a hassle for you either way.
The difference is that it will be a "hassle" on my terms. I get to determine who gets to suck how much money out of my credit card.
Without a virtual credit card #, they can do pretty much anything they want, then it's up to me to sue them. As long as I retain control of the money, I retain control of the entire transaction.
Right now, I've got a long distance company trying to bill a Virtual CC# for calls I made with another service. Guess how much I care that they're upset.
why is the rest of the world not keeping up?
Because I have very little use for one of these? My credit card already protects me from fraudulent charges and I'm not worried in the least if someone uses it two states away for gas. If Chase makes me call them when I'm going outside of my "home area" so they don't shut me off, then I'm not concerned if someone steals the card number after I make a purchase online at Newegg.
If someone uses the card locally, big deal. I call Chase and tell them that the card was stolen and the charge wasn't mine. Not many questions asked.
For *most* people, they just aren't paranoid enough to use a one time number for their purchases.
I wouldn't leave home wihout it (through B of A) When I pay for something online with a virtual CC, I can turn it off at any time. So when it comes time to cancel a service that's been billing me for a while, I first turn off the credit card number, then cancel the service.
They can go pound salt if they want any "early termination fees", or plan on charging me for another six months due to "billing problems"
Even if solar becomes cheap enough, what will prevent me is my home owners association. They don't allow solar panels. Move to a neighborhood that doesn't have that rule? I would have to move to a neighborhood that doesn't have a home owners association. Yeah, good luck in finding one! Folks are so afraid of their property values being hurt, they turn into housing fascists.
Don't be a wuss. Move out into the real world.
If you signed on with some group that tells you what color you can paint your house, you have nobody to blame but yourself.
I think you are arguing that investment in resources is more important than technicality (i.e., the more money you pour on a problem, the better it resolves itself). I'm arguing that someone at some point has to actually think about how to resolve it, regardless of cost. That someone is the resource you have paid for. So we're saying the same thing backwards. To me, it is more interesting to see how the resources go about solving the problem efficiently, not that a larger quantity of resources must be allocated to solve a larger problem. I'm going to give up trying to get that across now.
There's no solution for DOS that I'm aware of (other than staggering capacity), except reworking the entire network infrastructure to allow a server to revoke a client's priviledges(along with non-spoofable addresses), or replacing Windows with something that can't be so easily compromised.
Unfortunately, neither is going to happen any time soon.
Pop quiz, hotshot. You are the only network guy on station, your distributed servers are all getting pounded equally hard, everyone on the network is losing money and the traffic doesn't stop. What do you do? What do you do?
If you're the only guy on call for a global network, I'd find another job.
Rarely does anyone care what you can do without resource limitations. This is because there are always resource limitations. Network guys cost, bandwidth costs, smart Cisco boxes costs. Wires cost money. Electricity costs, rackspace costs. Will you minimize the cost of a DOS attack (including the cost of network equipment you paid before the attack started), or are you going to watch it continue over some coffee?
All those costs are irrelevant. If you have something that can't go down, you do whatever is necessary to achieve that.
If you can't afford to do that (hardware, netowrk or staff), then obviously your service isn't as valuable to society as you think it is. Or it's being managed by morons.
Either way, it's nothing for you to have a stroke over. One of the most valuable things you'll eventually learn is that technology is mostly mental masturbation for humans. If 90% of the internet went down, people might be a little more bored than usual, but they wouldn't stop breathing. It just isn't that important.
There's a whole world out there, and mostly it really doesn't matter if you can pay your bills online or gamble or find porn or music or video or get live radar maps of the weather in your area or pretty much anything else that takes up almost all the bandwidth.
If you want to see where the rubber meets the road, sit in on meeting with a big customer and watch what happens when they say "I don't want my site to ever be down" and the sales rep tells them what that would cost. Then you'll see them say either "I don't care. It can never go down", or "OK, what would it cost for it to almost never goe down?"
And you still don't have a clue. I worked for a company that was hit by a DDOS attack. Their Tier I network provider was so swamped that they switched off all traffic to the company (and this was a company whose entire business relied on its website being up). No matter how many redundant pipes you buy, there is always the possibility of being hit with more traffic. Unless you buy 50% of the worldwide bandwidth. I'd like to see you try that.
All that means is that your contract with the hosting provider let them weasel out of their responsibilities, and that they didn't have big enough pipes to enough networks and that they didn't have big enough balls.
With huge pipes, great network guys and globally distributed servers, a DOS attack becomes something interesting to wtch while having some coffee.
It's not necessary to own 1/2 the bandwidth in the world, only more than the botnet, which although way too much for a single server on a 10 Mb ethernet connection, doesn't mean squat to hundreds of servers doing IP Anycast scattered around the world.
A lot of companies don't want to be down, but in reality, if they go down for a while, they won't go out of business and nobody will die. When a site absolutely can't be down (human life or huge fianancial losses are at stake), they simply make sure they can handle whatever happens.
There is nothing you can practically do to prevent someone on the internet from sending a packet addressed to you, nor two packets, nor 1000000. There is nothing you can practically do to prevent the source address on each of those packets to be different. If a DOSer has much bigger pipes than you, you are sunk, unless you can do something very smart. For a start, getting remote access to your server during a DOS attack is tricky unless you have redundancy. Then you need to profile the traffic, find patterns which you can filter.
The defense against this sort of attack is to using a hosting provider with huge pipes.
Real sites that must be up us providers with huge, redundant tier 1 internet connections to multiple networks.
Then a DOS attack becomes something interesting to watch on a router traffic graph instead of a problem.
I worked for one of those providers, and it was always fun watching a DOS attack because it was like a fart in a hurricaine. If you have big enough pipes and great network guys, nothing else matters.
just about the saddest goddamned thing I've ever read on slashdot. The thought of becoming an arthritis-ridden man who can't play video games is just... shocking. *sigh* I am so jumping into an active volcano when I start to get frail...
Getting older has advantages
I'll be turning 50 this coming year, having worked as a software engineer since the days when having your own PC meant learning how to solder.
The best part is when someone tells you to do something stupid, you can call them on it.
For example when the 24 year-old project manager tries to get a table full of people to agree to an impossible development schedule, when they get around to you, you can smile and say "There's absolutely no way you can pull this off unless the phrase "Divine Intervention is in your Project Plan somewhere"
An you'll be right. And the project will fail, and you'll not be part of the disaster because that would have been the last project meeting you were invited to.
Honestly, the whole thread is depressing. I haven't played VR games in quite a while. I've replaced them with AR games (Actual Reality).
I have several that I really like a lot. One involves wearing a special "Alternate Environment Suit" that allows me to breathe underwater and interact with the local creatures, which is quite incredible, since it's in full 3-D WWMTHD (Way Way More Than High Def). Another favorite is exactly like VR sex, except it's in-person and there's no VR. You could also try something called gourmet cooking, which allows you to create wonderful sensory experiences Right Inside Your Own Mouth!
Don't think of it as getting old, think of it as gaining more "Experience Points" and still having close to half your life left.
It is true, after sticking it out working a 75 hour week for 12 months salary in the US, I nearly refuse to even entertain the idea of taking a salary position. I would rather make minimum wage and be paid hourly than ever do that again.
That's easy to fix. When 40 hours rolls around, you get up from your desk, look at your watch and say "Looks like it's time to go home", and leave.
They might fire you eventually, but they'll do that anyway, so there's really no loss.
Heh, remember when we had binary file formats and protocols, fixed-length fields (didn't need delimiters), and there was no parsing or worrying about "escaping" data? We didn't have these problems.
No kidding. I remember when everything in the world didn't need to be an "Application Framework" and code was fast and small and reliable and easy to fix.
Take an interesting job, regardless of what it pays. Stay for a while, suck up all the experience you can get, then go find a job that requires "experience".
Nobody wants an inexperienced recent grad because they're useless. The world is full of messy, poorly defined requirements that involve huge numbers of incompatible systems and people. It is not based on anything learned in college.
I like that a lot!
It could be a SpamAssassin plugin.
If the mail server gets a confirmed phish (verified with a phishing DB), it could go to the website and start filling in the form. Again and Again.
Slashdot Mirror
In the immortal words of Bugs Bunny: "What a marooon!
If it was a Linux laptop with disk encryption enabled, all he would have is a cool paperweight.
When the nerds get out of school and land jobs with good hours, good pay and good benefits, they'll immediately become attractive to girls.
The dating BS from school fades like a fart in a hurricane when exposed to real life.
If you can't do it with an SSH terminal session, it doesn't need doing.
SSH runs beautifully at 9600 and above.
And, yes, if they're going to sell Linux machines then they damn well need to support them. Does that mean they may not make as much on Linux machines in the short term? Perhaps, since they'll need to build a support staff. In the longer run, they'll discover they're getting a lot fewer support calls per Linux machine than they do for Windows.
I think the real reason they don't sell much linux is because it will cut into sales.
The real reason people upgrade is because their machines are too slow. Why are they too slow? Because the Windows registry has grown to 50M+, the machine is all crapped up with viruses and spyware and the half-dozen apps that are supposed to prevent all this are gumming up the works themselves.
How would Dell stay in business selling machines where someone would buy it, and say "thanks, see you later" and not buy another one for 10 years.
One of my customers runs a mixed shop (Windows & Linux). They can't buy the Windows servers fast enough to keep up with the ever-growing software requirements. I get the old machines, which are now handling things like running postfix on 20K inbound emails/day, and generally running at less than 2% utilization.
Most of them don't even know that the reason the Exchange boxes haven't gone down in flames is because there's a 233Mhz P-III, loafing along, guarding the door.
Running Linux on desktops and servers would eliminate the need to buy new machines on an almost annual cycle.
Find another job. Being "promoted" to manager is about the same as when they "promote" a cow to being hamburger. Your boss will be pressuring you to get things done faster/cheaper/better/different, the customers will be trying to push a never-ending chain of changes on your (with no increase in budget or time) and your developers will never be ready by your deadlines. Run away! Manager is a completely different job, which you are not prepared for and will not like. Software means that if you say x:=1, then x==1. Management is where you say "x:=1" and everybody else tries to make it "3" or ".95" or "blue" or "happy meal". Terry
- The earth isn't flat
- Fire is hot
- Poorly written software is exploitable
I've been writing software since "high level language" meant that the assembler understood named labels. Poorly written software had exploitable pointers back then too.This is just as newsworthy as the discovery that bears crap in the woods.
Who would have thought that invalid pointers and buffer overruns might be exploitable as a security hole?
Quick, someone alert Bill Gates!
Man. you have issues. Seek medical advice. Fast.
Seek medical advice for what?
For having seen a lifetime of man's stupidity, cruelty and disregard for every living entity on the planet, including all the animals and other humans?
For knowing that in less than a couple of hundred years man has dumped so much CO2 into the atmosphere that we have brought the planet past the tipping point and will not be able to stop catestrophic climate changes and mass extinctions in the near future?
Colonizing uninhabited worlds is OK with me, but I would have deep misgivings about letting humans set foot on another unspoiled planet similar to Earth. If we want a nice place to live, we should fix the one we have right here.
All I can say is "Thank God for the vastness of space".
It's the only thing that keeps us from destroying every other garden spot in the universe.
I firmly believe that it's not accidental that the technology needed to travel great distances is not attainable in the same era that nuclear and biological weapons were invented.
I have no doubt that we would bring massive destruction to any new planet, regardless of our good intentions.
Maybe in another few thousand year we'll begin to be ready.
Yah right. Do you have any idea how few good coders there are? Now add that to the chance they happened to write nothing but open source (yah, cause you can make so much money doing that). See the picture? Reality: Most open source code is written by semi-good coders - which means, oh boy, walking the code is gonna be an exercise in torture (it's only one step below that when it is good code, btw).
No kidding
I've been writing code since the 80's and by the time I get done with the latest stomach-churning panic-inducing gotta-have-it-by-friday design change that will be superceded by one of it's friends next month, the last thing I want to do is start rooting through perfectly functional code looking for potential privacy violations.
It's a free (or cheap) phone call. If anybody doesn't like it, they don't have to use it.
No shit!
What kind of company won't even let you take a crap without working? Maybe now call-centers will start haing their employees answer phone calls on the crapper.
"You're allowed 1 3 minute bathroom break between 10:00AM and 10:03AM, but you are required to answer calls during this time.
That's the second most amazingly annoying website I've ever seen ("Punch The Monkey" is first).
What the hell were they thinking?
With a credit card, you need not sue over false billings. Your first stop is to dispute the charge with your credit card company, which usually takes care of the issue. Only after that fails, do you need to worry about your "other options". But that wasn't really my point. My point is that if you owe a company money (or in your case, if a company thinks (incorrectly) that you owe them money), they are going to attempt to collect it. Your virtual credit card numbers are not going to provide the barrier that you think they provide, that's all I'm saying.
Not to pick fight, but in the case of the long distance company, if they had a real CC, I'd be in the position of trying to sue them for $40. Because it was virtual, they have to sue me to collect, which means that they have to prove I made the calls on their service, which they can't do. It just changes the balance of power in my favor.
n fact, even in the "billing problems" situation, the company will probably still turn you over to collections since according to their (buggy) computer, you owe them money. It's gonna be a hassle for you either way.
The difference is that it will be a "hassle" on my terms. I get to determine who gets to suck how much money out of my credit card.
Without a virtual credit card #, they can do pretty much anything they want, then it's up to me to sue them. As long as I retain control of the money, I retain control of the entire transaction.
Right now, I've got a long distance company trying to bill a Virtual CC# for calls I made with another service. Guess how much I care that they're upset.
why is the rest of the world not keeping up? Because I have very little use for one of these? My credit card already protects me from fraudulent charges and I'm not worried in the least if someone uses it two states away for gas. If Chase makes me call them when I'm going outside of my "home area" so they don't shut me off, then I'm not concerned if someone steals the card number after I make a purchase online at Newegg. If someone uses the card locally, big deal. I call Chase and tell them that the card was stolen and the charge wasn't mine. Not many questions asked. For *most* people, they just aren't paranoid enough to use a one time number for their purchases.
I wouldn't leave home wihout it (through B of A) When I pay for something online with a virtual CC, I can turn it off at any time. So when it comes time to cancel a service that's been billing me for a while, I first turn off the credit card number, then cancel the service.
They can go pound salt if they want any "early termination fees", or plan on charging me for another six months due to "billing problems"
You can't do that with a real CC number.
Even if solar becomes cheap enough, what will prevent me is my home owners association. They don't allow solar panels. Move to a neighborhood that doesn't have that rule? I would have to move to a neighborhood that doesn't have a home owners association. Yeah, good luck in finding one! Folks are so afraid of their property values being hurt, they turn into housing fascists.
Don't be a wuss. Move out into the real world.
If you signed on with some group that tells you what color you can paint your house, you have nobody to blame but yourself.
I think you are arguing that investment in resources is more important than technicality (i.e., the more money you pour on a problem, the better it resolves itself). I'm arguing that someone at some point has to actually think about how to resolve it, regardless of cost. That someone is the resource you have paid for. So we're saying the same thing backwards. To me, it is more interesting to see how the resources go about solving the problem efficiently, not that a larger quantity of resources must be allocated to solve a larger problem. I'm going to give up trying to get that across now. There's no solution for DOS that I'm aware of (other than staggering capacity), except reworking the entire network infrastructure to allow a server to revoke a client's priviledges(along with non-spoofable addresses), or replacing Windows with something that can't be so easily compromised.
Unfortunately, neither is going to happen any time soon.
Pop quiz, hotshot. You are the only network guy on station, your distributed servers are all getting pounded equally hard, everyone on the network is losing money and the traffic doesn't stop. What do you do? What do you do?
If you're the only guy on call for a global network, I'd find another job.
Rarely does anyone care what you can do without resource limitations. This is because there are always resource limitations. Network guys cost, bandwidth costs, smart Cisco boxes costs. Wires cost money. Electricity costs, rackspace costs. Will you minimize the cost of a DOS attack (including the cost of network equipment you paid before the attack started), or are you going to watch it continue over some coffee? All those costs are irrelevant. If you have something that can't go down, you do whatever is necessary to achieve that.
If you can't afford to do that (hardware, netowrk or staff), then obviously your service isn't as valuable to society as you think it is. Or it's being managed by morons.
Either way, it's nothing for you to have a stroke over. One of the most valuable things you'll eventually learn is that technology is mostly mental masturbation for humans. If 90% of the internet went down, people might be a little more bored than usual, but they wouldn't stop breathing. It just isn't that important.
There's a whole world out there, and mostly it really doesn't matter if you can pay your bills online or gamble or find porn or music or video or get live radar maps of the weather in your area or pretty much anything else that takes up almost all the bandwidth.
If you want to see where the rubber meets the road, sit in on meeting with a big customer and watch what happens when they say "I don't want my site to ever be down" and the sales rep tells them what that would cost. Then you'll see them say either "I don't care. It can never go down", or "OK, what would it cost for it to almost never goe down?"
And you still don't have a clue. I worked for a company that was hit by a DDOS attack. Their Tier I network provider was so swamped that they switched off all traffic to the company (and this was a company whose entire business relied on its website being up). No matter how many redundant pipes you buy, there is always the possibility of being hit with more traffic. Unless you buy 50% of the worldwide bandwidth. I'd like to see you try that.
All that means is that your contract with the hosting provider let them weasel out of their responsibilities, and that they didn't have big enough pipes to enough networks and that they didn't have big enough balls.
With huge pipes, great network guys and globally distributed servers, a DOS attack becomes something interesting to wtch while having some coffee.
It's not necessary to own 1/2 the bandwidth in the world, only more than the botnet, which although way too much for a single server on a 10 Mb ethernet connection, doesn't mean squat to hundreds of servers doing IP Anycast scattered around the world.
A lot of companies don't want to be down, but in reality, if they go down for a while, they won't go out of business and nobody will die. When a site absolutely can't be down (human life or huge fianancial losses are at stake), they simply make sure they can handle whatever happens.
There is nothing you can practically do to prevent someone on the internet from sending a packet addressed to you, nor two packets, nor 1000000. There is nothing you can practically do to prevent the source address on each of those packets to be different. If a DOSer has much bigger pipes than you, you are sunk, unless you can do something very smart. For a start, getting remote access to your server during a DOS attack is tricky unless you have redundancy. Then you need to profile the traffic, find patterns which you can filter. The defense against this sort of attack is to using a hosting provider with huge pipes.
Real sites that must be up us providers with huge, redundant tier 1 internet connections to multiple networks.
Then a DOS attack becomes something interesting to watch on a router traffic graph instead of a problem.
I worked for one of those providers, and it was always fun watching a DOS attack because it was like a fart in a hurricaine. If you have big enough pipes and great network guys, nothing else matters.
just about the saddest goddamned thing I've ever read on slashdot. The thought of becoming an arthritis-ridden man who can't play video games is just... shocking. *sigh* I am so jumping into an active volcano when I start to get frail...
Getting older has advantages
I'll be turning 50 this coming year, having worked as a software engineer since the days when having your own PC meant learning how to solder.
The best part is when someone tells you to do something stupid, you can call them on it.
For example when the 24 year-old project manager tries to get a table full of people to agree to an impossible development schedule, when they get around to you, you can smile and say "There's absolutely no way you can pull this off unless the phrase "Divine Intervention is in your Project Plan somewhere"
An you'll be right. And the project will fail, and you'll not be part of the disaster because that would have been the last project meeting you were invited to.
Honestly, the whole thread is depressing. I haven't played VR games in quite a while. I've replaced them with AR games (Actual Reality).
I have several that I really like a lot. One involves wearing a special "Alternate Environment Suit" that allows me to breathe underwater and interact with the local creatures, which is quite incredible, since it's in full 3-D WWMTHD (Way Way More Than High Def). Another favorite is exactly like VR sex, except it's in-person and there's no VR. You could also try something called gourmet cooking, which allows you to create wonderful sensory experiences Right Inside Your Own Mouth!
Don't think of it as getting old, think of it as gaining more "Experience Points" and still having close to half your life left.
It is true, after sticking it out working a 75 hour week for 12 months salary in the US, I nearly refuse to even entertain the idea of taking a salary position. I would rather make minimum wage and be paid hourly than ever do that again.
That's easy to fix. When 40 hours rolls around, you get up from your desk, look at your watch and say "Looks like it's time to go home", and leave.
They might fire you eventually, but they'll do that anyway, so there's really no loss.
Heh, remember when we had binary file formats and protocols, fixed-length fields (didn't need delimiters), and there was no parsing or worrying about "escaping" data? We didn't have these problems.
No kidding. I remember when everything in the world didn't need to be an "Application Framework" and code was fast and small and reliable and easy to fix.
Take an interesting job, regardless of what it pays. Stay for a while, suck up all the experience you can get, then go find a job that requires "experience".
Nobody wants an inexperienced recent grad because they're useless. The world is full of messy, poorly defined requirements that involve huge numbers of incompatible systems and people. It is not based on anything learned in college.
I like that a lot! It could be a SpamAssassin plugin. If the mail server gets a confirmed phish (verified with a phishing DB), it could go to the website and start filling in the form. Again and Again.