Beowulf == combining smaller machines for HPC. Virtual Machines == running several machines on a single system. Mainframe == single system with incredibly high data throughput, which can be partitioned into smaller systems (or virtual machines).
If your class is engineer heavy, then you need to use a few of these:
Manuals
Tutorials
Lab reports
Reviews
Internal technical documentation (code comments for programmers, notes for mechanical engineers, etc), which are primarily aimed at people lookiong for information on specific things in a project
Corporate documents
Each of these targets a different audience (or multiple audiences). Try getting people to cover the same topic in different ways (a topic like tying shoelaces can become interesting).
I would avoid the general topics for descriptive, essay type assignments. Create what if scenarios and ask the students to develop those.
A habit of reading books helps a lot. The more you read, the better your vocabulary and the better your judgement of the appropriate language to be used.
Remember that for your students, precision in writing will be important when communicating with their peers, but the form of language used will be more important when communicating with the rest of humanity. They will need to learn both.
Google's *revenue* is in the $2.25 billion range for a single quarter of a year. If they spent $1.65 billion per quarter in expenses, then their income would be around $600 million.
Revenue == cash income. Then there is deprecation and other accounting stuff which gives you total income. Gross profit = Income - Expenditure. Net profit = gross profit - tax.
AOL is rumored to do most of its spam-blocking without notification to the sender or recipient, and that's a big problem and they're hardly alone in this behaviour.
AOL isn't doing that. They have had technical issues with their filtering systems getting overwhelmed, but they have been moving to rejecting invalid addresses at the edge, lowering the load on their content filtering systems so that rejects no longer disappear into thin air.
Construction (and engineering for that matter) are mostly about repetition. Repeating yourself in software construction is bad practice. "Don't repeat yourself" is a standard rule of software development.
Oh, and add to the above link the requirement that the house be buildable in a few weeks/months and we will see how easily construction becomes predicatable.
Spam is a solicitation to contact the advertised party in the hopes that you will give them money. Otherwise known as an advertisement. THEY CONTACT US. It's called the free market. In turn we all have the right to use the communication path they supply to request that they leave us alone.
Spam is unsolicited bulk messaging. The problem with spam is that the recipient pays. In terms of hardware, in terms of time, in terms of network resources.
Sender pays doesn't scale to email.
People who use content filters compound the problem.
Re:My effective, ridiculed way to stop spam....
on
Spam Gets Personal
·
· Score: 1
Since your program basically acts after data is received and dumped in the inbox by the MTA, I don't see it as being much more effective in the fight against spam than a content filter, except for requiring less maintainance.
OTOH, if you could code it up as a proxy for desktops which hijacks connections to port 25, and filters outbound mail, it would actually be useful. Stopping the spam from being sent is a much better way to fight spam.
Meanwhile, all the criminals who really know what they're doing will send messages PGP encrypted, or use even more sophisticated methods of encrypting their files, and hiding who the messages are travelling between.
Actually, they will just lobby for their crime to become legalised. Witness Haliburton, RIAA, MPAA, Bush...
Crime is now legal. As long as you can pay off the crooks in power.
Re:USian snail mail: return receipt requested
on
Spam Gets Personal
·
· Score: 1
A public-key cryptographic system that used hardware level keys (or key generation) could at least ensure authenticity point to point during envelope exchange.It would also mean being able to reject mail from specific hosts, rather than ever shifting IP addresses.
Rejecting based on hostnames used in the HELO/EHLO? You can already do that in the major Unix MTAs. That doesn't stop the spammer from claiming to be something else. The spammer _0wns_ the sending host. The spammer can choose to send you whatever certificates they like for mail, and you have absolutely no control over that. And before you claim that ceritficates cost money, all that it takes is one corrupt PKI vendor to screw with everything. The spammer won't even need to pay with his/her own money, they can just use some of the stolen credit card information to make that payment.
IP addresses change for consumer IP space. You can use a DNSBL to block vast swathes of IP space, block the entire ISP for being a spam sewer, or whitelist the legitimate smarthosts and block everything else.
Spammers have more money than you do. They have more resources than you do. More bandwidth, more sending hosts, more CPU power. Now come up with a solution that works under those circumstances.
Use registered post. Seriously. IP itself is unreliable. The Internet is reliable in the sense that the global network does not go down even if some sites (or backbones) do.
Modern email is pretty much reliable. What is not reliable is the "business" need driven content filters which cause mail to disappear. SMTP is best effort, and that effort is very, very good. End users can make the best efforts of clued administrators fail.
Reject my email if you think it is spam. Don't filter it out, because then I have no feedback (and no, read receipts aren't acceptable).
Nah. Fairly trivial to throttle the protocol. Also, if you start using too much bandwidth, you are likely to be hit by a ToS violation notice and your access terminated.
But if India is anything like North America in this respect [and I can bet it is] a lot of people use these shit jobs as a safety net so they don't have to try hard in life. Like learn real skills, apply themselves, etc.
India isn't like the US.
The deal is basically like this: The tech support job is for a US company, giving you ~ 13K USD/yr if you are a graduate. Your other option is to do a professional course (engineering/postgrad), get employed by an Indian company and make half that money. If you are lucky, you get a MBA and join a finance company and make big bucks on Wall Street.
Alternatively, you could become a software developer and earn 2x of what the tech support person is making after 2 years, in your next job.
A lot of people do the tech support role only to finance further education, or until they can find other jobs.
Slashdot Mirror
Beowulf == combining smaller machines for HPC.
Virtual Machines == running several machines on a single system.
Mainframe == single system with incredibly high data throughput, which can be partitioned into smaller systems (or virtual machines).
Mainframes aren't exactly known for their number crunching abilities. They can, OTOH, kick data around very fast.
So the whole porting issue depends on whether the application is data throughput bound, or CPU bound.
The lack of security _is_ a market decision. People still buy Windows, regardless of security problems. The market is not willing to pay for security.
If your class is engineer heavy, then you need to use a few of these:
Manuals
Tutorials
Lab reports
Reviews
Internal technical documentation (code comments for programmers, notes for mechanical engineers, etc), which are primarily aimed at people lookiong for information on specific things in a project
Corporate documents
Each of these targets a different audience (or multiple audiences). Try getting people to cover the same topic in different ways (a topic like tying shoelaces can become interesting).
I would avoid the general topics for descriptive, essay type assignments. Create what if scenarios and ask the students to develop those.
A habit of reading books helps a lot. The more you read, the better your vocabulary and the better your judgement of the appropriate language to be used.
Remember that for your students, precision in writing will be important when communicating with their peers, but the form of language used will be more important when communicating with the rest of humanity. They will need to learn both.
Google's *revenue* is in the $2.25 billion range for a single quarter of a year. If they spent $1.65 billion per quarter in expenses, then their income would be around $600 million.
Revenue == cash income. Then there is deprecation and other accounting stuff which gives you total income. Gross profit = Income - Expenditure. Net profit = gross profit - tax.
How, exactly, do you intentionally do anything by acting negligently?
Think "drunk driving". The negligence refers to responsibility.
AOL is rumored to do most of its spam-blocking without notification to the sender or recipient, and that's a big problem and they're hardly alone in this behaviour.
AOL isn't doing that. They have had technical issues with their filtering systems getting overwhelmed, but they have been moving to rejecting invalid addresses at the edge, lowering the load on their content filtering systems so that rejects no longer disappear into thin air.
cut out flash, ajax, and everything else that the Google bot can't
And that is a bad thing why?
Construct a Skyscraper and it's no problem to have a time line, but code an app... whoa, that has so many issues.
t ects_h.html is the normal state of the software industry today.
Construction is mostly a repeatable activity with known materials, and hard, fixed requirements.
Software development, on the other hand, oftne does not have the benefit of hard, fixed requirements. http://twasink.net/blog/archives/2004/10/if_archi
Construction (and engineering for that matter) are mostly about repetition. Repeating yourself in software construction is bad practice. "Don't repeat yourself" is a standard rule of software development.
Oh, and add to the above link the requirement that the house be buildable in a few weeks/months and we will see how easily construction becomes predicatable.
A lot of spammer code is in VB/VC++ (toolbars, cursors, viruses, trojans, winodws desktop based proxies for DNS and HTTP and SMTP clients).
Spam is a solicitation to contact the advertised party in the hopes that you will give them money. Otherwise known as an advertisement. THEY CONTACT US. It's called the free market. In turn we all have the right to use the communication path they supply to request that they leave us alone.
Spam is unsolicited bulk messaging. The problem with spam is that the recipient pays. In terms of hardware, in terms of time, in terms of network resources.
Sender pays doesn't scale to email.
People who use content filters compound the problem.
There is Sendmail at http://www.sendmail.org/ .
Since your program basically acts after data is received and dumped in the inbox by the MTA, I don't see it as being much more effective in the fight against spam than a content filter, except for requiring less maintainance.
OTOH, if you could code it up as a proxy for desktops which hijacks connections to port 25, and filters outbound mail, it would actually be useful. Stopping the spam from being sent is a much better way to fight spam.
Meanwhile, all the criminals who really know what they're doing will send messages PGP encrypted, or use even more sophisticated methods of encrypting their files, and hiding who the messages are travelling between.
Actually, they will just lobby for their crime to become legalised. Witness Haliburton, RIAA, MPAA, Bush...
Crime is now legal. As long as you can pay off the crooks in power.
Return your geek card please. GP was referring to the Lensman series, by EE Smith.
http://en.wikipedia.org/wiki/E.E._Doc_Smith
Here you go. You only need to steal a car first though.
Our mail load is here. That is a minute's worth of traffic.
Care to show benchmarks?
A public-key cryptographic system that used hardware level keys (or key generation) could at least ensure authenticity point to point during envelope exchange.It would also mean being able to reject mail from specific hosts, rather than ever shifting IP addresses.
Rejecting based on hostnames used in the HELO/EHLO? You can already do that in the major Unix MTAs. That doesn't stop the spammer from claiming to be something else. The spammer _0wns_ the sending host. The spammer can choose to send you whatever certificates they like for mail, and you have absolutely no control over that. And before you claim that ceritficates cost money, all that it takes is one corrupt PKI vendor to screw with everything. The spammer won't even need to pay with his/her own money, they can just use some of the stolen credit card information to make that payment.
IP addresses change for consumer IP space. You can use a DNSBL to block vast swathes of IP space, block the entire ISP for being a spam sewer, or whitelist the legitimate smarthosts and block everything else.
Spammers have more money than you do. They have more resources than you do. More bandwidth, more sending hosts, more CPU power. Now come up with a solution that works under those circumstances.
Use registered post. Seriously. IP itself is unreliable. The Internet is reliable in the sense that the global network does not go down even if some sites (or backbones) do.
Modern email is pretty much reliable. What is not reliable is the "business" need driven content filters which cause mail to disappear.
SMTP is best effort, and that effort is very, very good. End users can make the best efforts of clued administrators fail.
Reject my email if you think it is spam. Don't filter it out, because then I have no feedback (and no, read receipts aren't acceptable).
Nah. Fairly trivial to throttle the protocol. Also, if you start using too much bandwidth, you are likely to be hit by a ToS violation notice and your access terminated.
Better languages than the PHP disaster? Perl, Python, Ruby. They work _very_ well.
Caffeinated beer is what the marketing people want you to drink. Or perhaps fermented coffee?
But if India is anything like North America in this respect [and I can bet it is] a lot of people use these shit jobs as a safety net so they don't have to try hard in life. Like learn real skills, apply themselves, etc.
India isn't like the US.
The deal is basically like this:
The tech support job is for a US company, giving you ~ 13K USD/yr if you are a graduate.
Your other option is to do a professional course (engineering/postgrad), get employed by an Indian company and make half that money.
If you are lucky, you get a MBA and join a finance company and make big bucks on Wall Street.
Alternatively, you could become a software developer and earn 2x of what the tech support person is making after 2 years, in your next job.
A lot of people do the tech support role only to finance further education, or until they can find other jobs.
A trainee lawyer is a potential source of revenue. A software developer is a cost.
And what kind of qualifications does a sysadmin have to have there?
User: Help, my computer is broken.
Sysadmin: By looking at the entrails of your computer, I know what is wrong.
Which is why you carry a BFG with a silencer. Or poison. Or ....