This is the last chapter.. I’m happy to know that this is the last chapter of getting real. Imagine I read the whole book.. hehe.. well.. I’m surprised.. wohoo I made it..Seriously, this chapter 16 is almost a summary of all the topics of getting real. Here, you can see that they explained the point in making or building your own web apps up to introducing it to your customers.

I admit that getting real is a good book. It tells the reader that it’s not just about making web apps. There are certain aspects in making web apps. Getting Real discusses how to build your own web apps.

For me, getting real gives me an idea on how to make a good web apps. Once you read the whole chapters of getting real, you may find the real meaning on how you can make a good apps and how you may introduce and sell your apps to your customers. In making or building your apps, you have to start from knowing the people involved, analyzing the data that you gathered, make a design, code it, and up to the last part which is making updates after you launch your apps to the customers.

Thanks for this book. I’ve learned something..

Chapter 13 is about promotion. It is one of the most important parts after building your apps. If you want your products or apps to be known by any costumer or client, you have to have promotion. Your apps need to be recognized by anyone. By doing this, there’s a big possibility that you may have profit or customers will buy it. Some samples of promotion are teasers and previews.

One way to introduce or promote your apps is BLOGGING. You can blog it so that everyone will know about your new apps. BLOGGING is effective when it comes to promoting your new apps. It’s an easy and convenient way for the developers to promote their apps and for the customer to view what’s new.

Another thing in this chapter is the name of the apps. The name of your apps should be easy to remember. It’s easy for you to sell your apps if the name is easy to remember.

Chapter 12 is about pricing and sign ups. I really love the idea of giving freebies to people. It’s a way of introducing your product and letting people to experience your finished product. Letting them used your product seem to make good moves and advertisements also.
Giving freebies makes your customers or clients become interested on your products. It will help you to make things easier. It will help you sell your product to the market.

Another topic that they’ve discusses in this chapter is the free sign ups and what they’ve called easy on, easy off. Here, customer should login to your apps. Make sure that the user login is working properly and easy to use. In addition to that, it must be easy for the user to sign up, login, and log out to the apps. Then once they’re inside, make sure that they can get and see the data that they needed. On the other hand, companies must not trick people. They don’t have to use contracts, sign-up fees just to earn or make money. Customers don’t like one time set-up fees and a contract to sign. They should be free to choose products and cancel it whenever they want to cancel. Companies must use other way instead of providing contracts and other set-up fees. Customers will not buy your products if you’re like that.

The last topic in chapter 12 is the way on how companies will launch their product or apps. I think it’s a good idea that companies should have their own way in launching their apps. Here, they suggest a way in launching the apps. They can use the so-called Hollywood Launch. They emphasize 3 things; the teaser, which gives an idea on what you’re working. Start doing it earlier; then, after that, give people a preview about your apps. I think it’s like doing a trailer of the movie. Give people time and chance to see your apps. Lastly, time to launch your apps. This is the time for you to launch or introduce your apps to the market. Spread the news about your apps.

Chapter 10 of getting real is about building softwares. Getting Real mentioned that in building a software, try to build less software. Less software means trying to put what’s important and make a solution based on the exisiting problem. Here’s the thing, developers must focus on the problem and try to create a solution for it. By doing that, you will have less work and that’s good to hear.

I agree to this idea. It’s good to know that in making your software, you’ll be able to create less work if you try to focus on the essentials only. In addition to that, programmers and developers will be happy and motivated because they were given such consideration. Because of that, they will be able to work with something that they prefer to work with. If I am a programmer, I will be happy to hear it.

I also agree to the idea that programmer should create his/her own original application without copying source codes on the internet or in other application. Sometimes, there are programmers who tend to copy other source codes. It’s a bad habit. If you are a real programmer, you don’t have to copy others source code. Why not try to create your own piece.

Chapter 9 is about Interface design. It talks about designing an interface. For me, developers must create first  an initial interface before they do the coding part. That interface would be their starting point. When you create an interface, you must consider first what is important and prioritize it. Developers must focus on what really matters. Design an interface that includes important features. You don’t need to make the whole thing in the start. Remember to focus on what’s important. Don’t put all things in just one sitting. If you want the whole thing to be customized, I think it’s better if you do that in the end. In making an interface, you must understand first what functionality you may want to implement.

In this chapter, they mentioned 3 states in making an interface. The three states are the regular, blank, and error. In a regular state, you can see the normal screen. That screen consists of functions and features. Then, in a blank state, i think this is a plain interface. Plain, because the content of the interface is there but it doesn’t have designs. On the other hand, the error state is like a message box that includes the errors of the pages.

In creating an interface, you must take the users’ view. You must understand what the users needs because they’re the one who will use your app. So, your design should be user friendly.

Chapter 8 talks about hiring people. There are certain points why companies hire people. Hiring people is not easy. You must see their resume, interview them properly, then test them for you to know his/her ability. Companies must remember and consider that whenever you hire someone, you don’t hire them easily or you must know the reason why you hire him/her. It’s ok to hire people as long as you really need it. But for me, think first the situation before you hire people. Analyze it. In this way, you will probably know whether you’ll hire people or not. When you’re about to hire people, you must know certain things. Don’t judge them by their resume, their grades in school. Base it with their performance or the quality of their work. Don’t just hire them because of their grades and background. You need to know their ability and capability. Why not test them in order for yo to know that they deserve to work in your company. Give them an test. For the mean time, why don’t you give them a small project. In this way, you will be able to test if they can do it or not. According to getting real, there’s also a way to determine whether the people fit the job. That is the open source. Open source means knowing and judging them based on their actions and not their words. You must know how he/she works and how she/he deliver the works. Then, you have to know if the person knows how to decide for the good, if he/she has passion in doing it, and most especially he/she must know how to communicate to other employees.

Unity

According to the book, companies separate designs, development and other sections in making web apps. I think it’s ok to separate those so they can divide the work and in order for the group or team to finish  and integrate it on time. Separating designs, and others is ok and in fact it can help them but they have to remember that even though they separate those things, there’s a possibility to have lock of communication. For me, one member must work with other members. They must consider communication; member must support other member for them to integrate their finished output.

Alone time

I agree to getting real. Everyone needs to be alone sometimes. They need to find their own “zone”.  The “zone” is where they can do work on their own. Here, they are more focused and don’t think There’s a time that people should be alone to get things done. Once they’re alone, they can do more things properly and do what they have to do. In this way, they become productive and ready to finish their work.

Meetings are toxic

Having a meeting is good as long as it has sense. People conduct meeting because they want clarification regarding to something. But the question here is do they really have go to meeting just because they have to clarify things? I think meting is ok. You can conduct and attend meeting. Meetings are good. I can attend meetings if and only if there’s an agenda. Aside from that meeting should not take long.  30 minutes is enough for meetings. But you know, instead of meetings, why don’t you discuss it via im or emails.

Seek and Celebrate Small Victories

According to getting real, it’s ok to celebrate small things because it increases you motivation. Motivation is really important especially when you’re working. Without motivation, I think you can’t do things properly or the output won’t be good as that. I agree to getting real. You must celebrate small things as long as it motivates your people.