|
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).
|
|
|
|