Monster hit again
-
From what I've read they still store their passwords in plain text :confused:
Todd Smith
-
Repost from last week. Keep up.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Repost from last week. Keep up.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John Simmons / outlaw programmer wrote:
Repost from last week.
That's funny.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
As long as these moron companies keep hiring the cheapest developers they can get their hands on and treating us like worthless commodities this will continue to happen. They deserve what they get. I imagine Monster is one of those companies actively engaged in H1-b visa fraud too.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
If you don't ask questions the answers won't stand in your way.
Most of this sig is for Google, not ego.For a company with a big online presence and a lot of user data you'd think developers would have very little to do with it other than following the plan of a person with a dedicated role to security like a security architect or something. I think the problems happen not always from cheap developers but just as easily from expensive and good developers that are arrogant and think they can do everything just as well as they can write code or being overworked and asked to take on too much outside their area of core competency and not having an option of saying no. And in the end a lot more of these situations occur from simple social hacking than anything else. In most cases I read about it is *rarely* a problem with the design or the code itself.
Ennis Ray Lynch, Jr. wrote:
As long as these moron companies keep hiring the cheapest developers they can get their hands on and treating us like worthless commodities
That's the fault of developers in the end though isn't it? In general developers (particularly corporate ones) stupidly and eagerly bought into a myriad of schemes over the last few decades that were precisely designed to turn developers into a commodity. Developers have no one to blame but themselves, they surrendered to the gray men in accounting a *long* time ago.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
For a company with a big online presence and a lot of user data you'd think developers would have very little to do with it other than following the plan of a person with a dedicated role to security like a security architect or something. I think the problems happen not always from cheap developers but just as easily from expensive and good developers that are arrogant and think they can do everything just as well as they can write code or being overworked and asked to take on too much outside their area of core competency and not having an option of saying no. And in the end a lot more of these situations occur from simple social hacking than anything else. In most cases I read about it is *rarely* a problem with the design or the code itself.
Ennis Ray Lynch, Jr. wrote:
As long as these moron companies keep hiring the cheapest developers they can get their hands on and treating us like worthless commodities
That's the fault of developers in the end though isn't it? In general developers (particularly corporate ones) stupidly and eagerly bought into a myriad of schemes over the last few decades that were precisely designed to turn developers into a commodity. Developers have no one to blame but themselves, they surrendered to the gray men in accounting a *long* time ago.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
John C wrote:
In general developers (particularly corporate ones) stupidly and eagerly bought into a myriad of schemes over the last few decades that were precisely designed to turn developers into a commodity.
This statement has caught my interest. Can you give some examples of schemes that have turned us into a commodity?
-
John C wrote:
In general developers (particularly corporate ones) stupidly and eagerly bought into a myriad of schemes over the last few decades that were precisely designed to turn developers into a commodity.
This statement has caught my interest. Can you give some examples of schemes that have turned us into a commodity?
-
Sure: http://www.codeproject.com/Lounge.aspx?msg=2708452#xx2708452xx[^]
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
I appreciate the link, and I read every word. But that post doesn't mention the methodologies of which you speak either. Can you give exact names of technologies and methods?
-
I appreciate the link, and I read every word. But that post doesn't mention the methodologies of which you speak either. Can you give exact names of technologies and methods?
At first I was wondering if you are serious, after all most developers are surrounded by it every day, particularly in a corporate programming environment, then I realized that the concept of water might be inconceivable to a fish as well. ;) Sure it's a fine line between methodologies and technologies that benefit programmers and those that benefit accountants of programmers but they're not hard to find...oh look here's one from todays CodeProject newsletter: http://www.cio.com/article/print/478106[^]
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
A couple of years ago I ran a presentation to our developers about how easy it is to let the hackers steal our secrets if we don't do our job right. Someone asked me yesterday to run it again. Looks like a good opportunity to re-affirm the message to our folks that this sort of media exposure does us developers no good at all, let alone the company we work for.
-
I appreciate the link, and I read every word. But that post doesn't mention the methodologies of which you speak either. Can you give exact names of technologies and methods?
Have you not wondered why we have Java and .NET? They don't substantially reduce development time, and increase system resources required; they are clearly intended to reduce the minimum skills that a programmer should have. There are many such innovations that do not benefit the end user in any way. We have microcode running inside the chip to build its instruction set; then we divide the machines into fragments using virtualization; run an operating system on it; then create another virtual environment using Java or .NET. How many layers do one need to build?
