This just underlines the engineer's problem with making something secure, yet making sure every moron in the U.S. can plug it in and turn it on and have it basically work.
I'm sick and tired of hearing marketing, human resources, finance and 99% of the world of "business" come cry me a river when they complain system doesn't work as expected because they didn't know what the customer really wanted. Not even the customer knew what he wanted, they all came to me saying " it must be cheap and basically print me money "
Yeah sure and If I had the method I'd be working for you fools would I ?
I'm sick and tired of hearing marketing, human resources, finance and 99% of the world of "business" come cry me a river when they complain system doesn't work as expected because they didn't know what the customer really wanted. Not even the customer knew what he wanted, they all came to me saying " it must be cheap and basically print me money "
A big part of engineering is figuring out what the user wants. The user can't be trusted to automatically know exact
A big part of engineering is figuring out what the user wants.
The customer wants something perfect, that works perfectly, with zero maintenance costs and that he can have for free. There you go, that's all you need to know on what any customer really really wants.
Engineers are not supposed to be work on the discovery phase "ask customer what he realistically wants" neither on the update phase "tell customer he can't have but that" neither concern himself with the very fine legal and psycological details
The customer wants something perfect, that works perfectly, with zero maintenance costs and that he can have for free. There you go, that's all you need to know on what any customer really really wants.
Engineers are not supposed to be work on the discovery phase "ask customer what he realistically wants" neither on the update phase "tell customer he can't have but that" neither concern himself with the very fine legal and psycological details involving a transaction.
As some have mentioned, I was slightly off in saying it was the engineer's job to ask the customer, however for better or worse, the engineer's job and analyst's job often get mixed together.
Either way, whoever's job it is to be the analyst (whether it be a separate or shared job) has to coordinate with the business side as well as the customer. Both sides have their roles, and if the business people are allowed to overstep their bounds and make technical decisions, there is going to be problems. A good analyst will stand up to the business people, as well as the customer, to make sure they know what's going on. It won't work out if they don't have that power, whether by their own fault or the fault of the business's structure.
Security vs. Stupidity (Score:5, Insightful)
Re:Security vs. Stupidity (Score:4, Insightful)
I'm sick and tired of hearing marketing, human resources, finance and 99% of the world of "business" come cry me a river when they complain system doesn't work as expected because they didn't know what the customer really wanted. Not even the customer knew what he wanted, they all came to me saying " it must be cheap and basically print me money "
Yeah sure and If I had the method I'd be working for you fools would I ?
Go ask Alan Greenspan you yahoos !
Re:Security vs. Stupidity (Score:4, Insightful)
I'm sick and tired of hearing marketing, human resources, finance and 99% of the world of "business" come cry me a river when they complain system doesn't work as expected because they didn't know what the customer really wanted. Not even the customer knew what he wanted, they all came to me saying " it must be cheap and basically print me money "
A big part of engineering is figuring out what the user wants. The user can't be trusted to automatically know exact
Re:Security vs. Stupidity (Score:1)
The customer wants something perfect, that works perfectly, with zero maintenance costs and that he can have for free. There you go, that's all you need to know on what any customer really really wants.
Engineers are not supposed to be work on the discovery phase "ask customer what he realistically wants" neither on the update phase "tell customer he can't have but that" neither concern himself with the very fine legal and psycological details
Re:Security vs. Stupidity (Score:2)
Engineers are not supposed to be work on the discovery phase "ask customer what he realistically wants" neither on the update phase "tell customer he can't have but that" neither concern himself with the very fine legal and psycological details involving a transaction.
As some have mentioned, I was slightly off in saying it was the engineer's job to ask the customer, however for better or worse, the engineer's job and analyst's job often get mixed together.
Either way, whoever's job it is to be the analyst (whether it be a separate or shared job) has to coordinate with the business side as well as the customer. Both sides have their roles, and if the business people are allowed to overstep their bounds and make technical decisions, there is going to be problems. A good analyst will stand up to the business people, as well as the customer, to make sure they know what's going on. It won't work out if they don't have that power, whether by their own fault or the fault of the business's structure.