|
Our software is deployed on thousands of seats in banks, the above criteria almost never come into discussions with clients, they care about security and functionality - as in many enterprise solutions our memory usage/cpu etc will never be an issue (unless we do something awful) compared so, say, stored procedure design, query optimisation etc etc.
|
|
|
|
|
I'm in a similar position and network and responsiveness as bloody relevant to us. Someone deploying an unresponsive app is an insult to all developers.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Its a true fact is client don't care about anything that they can suggest...
as example :
if you put a button on the right side of the window instead left side(but it was suppose to be on left), client would think you a bid dumb, in most case they dont know what you do to develop an application.
Once I told my friend that computer works with only 0 and 1 nothing else he suggested me to stop study computer science 
|
|
|
|
|
This is by far the easiest poll I have seen. Where I work none of these items are of any real importance. Personally, I would like all of them to be important. But around here the most important item is one not included in the choices, "Just get it done and get it into production." Don't believe me, check my signature.
Comments from work:
- "Why can't you just do it like everybody else?"
- "Well, we haven't had any complaints yet."
- "I just want to get it into production."
I'm in space!
I know you are mate. Yep, we're both in space.
SPAAAACE!
|
|
|
|
|
Seconded.
We don't care with any of those as long as the "thing" does its job, and is reliable. Of course, the points listed are taken into account as metrics of efficency, but those are not the top priority.
|
|
|
|
|
Responsiveness - you mean this is not an important part of your design, do you pee in your boot as well.
Network is always an issue when a WAN is part of the equation.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I do my best to not pee in my boots. It ruins the leather.  For me, almost all of these are important. And I would also include efficient, maintainable code, decent (prefer excellent) UI design with functionality that the user needs/wants. But that's just me. I'm generally in the minority when it comes to these types of discussions at work.
Comments from work:
- "Why can't you just do it like everybody else?"
- "Well, we haven't had any complaints yet."
- "I just want to get it into production."
I'm in space!
I know you are mate. Yep, we're both in space.
SPAAAACE!
|
|
|
|
|
I find memory, cpu and other hardware based issues to be minor issues. I'm quite happy for the junkyard people (IT) to throw more junk at the problem. The design issues I have strong views on and they get listened to as I set the rules.
One of the great things about age and experience, management tends to take you more seriously the more you have!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I hate when customer says "I don't care how it work, i only care results", and if it fails for memory issue then its my fault. The truth I learned is we can do it easily with computer because we studied it, we studied it because we have the capabilities. So when someone ask "Is this a easy job" I said "no its not, This will be done with the 4 years education and 3 years working experience. Its not an easy job to do".
|
|
|
|
|
... plus number of SQL queries and http requests (yes, I know they can be expressed in terms of CPU and network, but I found it very useful to treat them as a separate metric).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
