This is the first blog which will be based on Chapter 1.
First of I would like to start with the very first page of Chapter 1. It is so short but so true that it hurts, let me explain why. In my opinion today’s standards are beyond our imagination and being honest we see and interact with products, items and people that we think they are perfect. Therefore, we think that anything that we do in our lives has to perfect. Just like the book says and I quote “Where to start?”. We worry too much about what other people could say that we never focus on what is really important, are we enjoying what we’re doing?
The next thing that comes up to my mind is the exercise of what we would change to a software app in this case Rick’s guitar shop (for example) and what do we think makes a great software so here is my opinion regarding this…
“Every time we try to write a program we never take into consideration what the client wants. I truly believe that good apps require less clicks or less taps. Take for instance an app in which you want to buy something, after searching you finally made a conclusion, you added the item to the shopping cart and all of a sudden you get bombarded by multiple ads from the app or web page that has nothing to do with what you want. Things like this makes the customer annoyed and most likely will never use the app again. But what happens when we ignore all of those ads and we try to pay? “TAP HERE TO PAY IMMEDIATELY !” And of course it only requires one tap or click. Another good practice would be having a base model and what I mean with this is studying what the clients do and search. Based on the results create a software DEDICATED to the customer not to the owner of the company because as we all know the owner and employees know what they have, how much they have and the client knows nothing. Create a software surrounding the customer and what he/she likes and you will succeed. “
Oscar E. Rios Macriz
On page 12 it mentions that a great code is an optimized one. Throughout the semesters as ISC I’ve learned that taking advise from others is actually great and that the software community is a great community. No one hates you but if you are not opened to suggestions and help you will stay with an old code that is not optimized. What I’m trying to say is that no code is perfect and with time new options will arise and then if you don’t fix and optimize your code it would be too late and someone else will do it first and maybe better.
Finally, what I loved about chapter 1 is that it breaks down and gives a definition for four different words which are:
I’m not going to write or mention the definitions of the book because that would be useless… instead I will give those words my own approach.
Flexibility is something that I would like to translate to “do not be close minded instead be open minded. Do not be a I cannot do that but be a I can do that” customers are everywhere, we are customers and even though we do not notice it the owners are looking and studying us; therefore, they are implementing new things to their codes.
Encapsulation is more OO like the book says, try to minimize lines of code by simplifying problems through Objects and other methods.
Functionality, ask yourself the question “Is the customer really getting the results he wants?” Why do you think airlines or other services always ask you for feedback? If something is wrong they completely remove it or rework it.
Design Patten I see it like a brainstorm, settle down your ideas, problems and solutions and do not work twice.
With all of this I would like to close my first blog. Really interesting chapter that shows you not to go crazy when something is not working as you planned it to be. Everything has its own solutions.
Thank you and Best regards,