From the programmers end, when one is developing an application we could imagine it to be a process of teaching the user or the customer to achieve something. If we could imagine a 5 year old who is going to use our application then we will design it such that it should be one of the most simplest things in the entire universe. The more simplicity you achieve without loosing functionality, the more your customer will love you. It does not matter that you have every feature ever requested, what is important that you have used power-law to find and implement the most important features in your application.
Simplicity - when you can not remove anything from something without destroying utility.
I believe this simplicity should extend to the backend as well. Simplicity is loved by everyone, though some people will frown at the idea of being treated as six year olds, but in the long run it make the most sense. I am not going to let anyone mess with simplicity for any whimsical shit in anyone's head.
So back to the point - the more simple you keep it the better would be
1) understanding of the code
2) readability of the code
3) changebility
4) fronted customer will be the center not the cryptic coder...... which should be the case , always. As it is the end customer who is going to use and achieve goals using out software.4
5) Simplicity - The process will be close to you teaching your customer. One has to be clear with their intentions and expectations otherwise the user has full right to bug you a gallizzion times in your face and make your life hell... as you were the one who committed the mistake of not looking from the angle of the user and made some shit that only you and you clique could make sense of.
Achieving simplicity in thoughts and actions is one of the most complex task....... BUT that is the minimum requirement around here.
Keep Smiling
Simplicity - when you can not remove anything from something without destroying utility.
I believe this simplicity should extend to the backend as well. Simplicity is loved by everyone, though some people will frown at the idea of being treated as six year olds, but in the long run it make the most sense. I am not going to let anyone mess with simplicity for any whimsical shit in anyone's head.
So back to the point - the more simple you keep it the better would be
1) understanding of the code
2) readability of the code
3) changebility
4) fronted customer will be the center not the cryptic coder...... which should be the case , always. As it is the end customer who is going to use and achieve goals using out software.4
5) Simplicity - The process will be close to you teaching your customer. One has to be clear with their intentions and expectations otherwise the user has full right to bug you a gallizzion times in your face and make your life hell... as you were the one who committed the mistake of not looking from the angle of the user and made some shit that only you and you clique could make sense of.
Achieving simplicity in thoughts and actions is one of the most complex task....... BUT that is the minimum requirement around here.
Keep Smiling
No comments:
Post a Comment