In this selection, we shall say it points out to one big thing, the essentiality of one’s program or application. They want to give us the fact that, all those small things that need to be supplied in your application should be seen. As what the selection Half, Not Half-Assed was put into words is that, we should stick to what is truly essential, what is truly needed on your application. You don’t need to take all those fancy filigrees just make your application better, it only takes a simple who and ha to give yourself a thing.
A continuation of essential was published in the next selection. Still, essential that was the key point of the topic.
The idea now is, everything that is important should be published and leave all the unnecessary features for later improvements. By this, you will learn how to maximize your resource as well as learn how to value time. The important thing here is, in developing an application, you should accomplish what is needed, manipulate the application in a sense that you know what is needed from the not, learn to value money and resource by this you will know how to live with and lastly it should work.
The lesson perhaps in this chapter is that, when producing an application, the common assumption of building it big to make it successful is not the best choice. Things don’t go that way anymore, there are too many other applications that users can shift to if yours seem insufficient for their needs. Why spend so much money, time, and effort, for a feature request whose costs demeans its benefits? Why do you have to keep your promises to something that would otherwise be misleading on your part? In knowing what to prioritize, in what to implement from that which shouldn’t be, you can create a software that doesn’t need advertising or marketing just to sell it – all you need is simplicity, and through simplicity, you gain not only customer satisfaction or loyalty, but the most rewarding of it all: their word of mouth. Hey, Vista Battery Saver started the same way these guys did their programs, and even with just nimble features, it’s still a hit worldwide.
The lesson in this chapter is that, when producing an application, we are not bound to build big just to satisfy and tell ourselves that we are successful in dealing so. Why spend nths of pesos/dollars dealing with a big scope of project when you can have a simple but powerful one. Time, money, effort in dealing so will be a scrap if we don’t measure what we’ve got. Getting tackles the virtue of simplicity. In getting real, the lesson is not only applicable for building application and alike but in the real view of life it would always be welcome. Being simple in everything would give you a head start of what true to life means.