Ferlinechua’s Weblog

I did this in bullets to have a better understanding of chapter 6.

Chapter 6 tackles the following:

• We must avoid the so-called “PREFERENCE”

Based on what I understood, preference means something preferred by the user. As a programmer, you should do the decision for the customer because people are busy. They don’t want to encounter the details; they want “the no complexity part”. The example that they give is the programmer to make an option on having 25, 50 or 100 messages. The customer does not want the detailed like having 20 or any number messages. We believed that the programmer will do it for us. They must know what the customer wants. Actually this preference is not good for the part of the programmer because this creates more code or features to make.

• Say the magic word “DONE” and move on

Done means that you have accomplish the project or assigned task given to you. The problem with this is what if what the tasks that you make have a problem and you need to add features. That would be a problem because you already implement it. Getting real suggests that there would be no problem if you make an application is a web because you can revert back what you write. Also, we must not make a big deal on the mistakes that we did because we are not perfect. So just move on with the mistake that you have

• Have a good and simple process rather than a complex process

Basecamp has a good process that’s why they succeed. First is, they brainstorm their ideas. Because they are the ones who experience the problem, they know absolutely their needs. They tried to let it happen. The needs that they want to have in an application; they collected it and have in the software. Brainstorming is the foundation of their software. Second is, paper sketches. Since they have brainstormed, they tried to design the interface that they will make. This would be good for the team so that they will have the same thoughts to clarify things up. Third is they create html codes. Because they know their design and needed in the application, they will have the web design. After this, then we can code what we want. Like doing a program, we first make the UI (user interface) before we code. Doing the design is easy rather than doing code. The process they have is very simple, but can lead to success of one’s project. We don’t need to have many processes that can also lead to the same output having the simple process.

• Let the program runs

Running software means the software that actually runs. It is better to have a software that runs rather than softwares that has many codes but doesn’t work. As a programmer, you will be rewarded if you let it run because the user will not look at your codes, but if it is running. We first prioritize if it is working and after that the features that it gives to the users.

• It is alright to repeat it again and again

We don’t need to have it perfect at the start because we can change it in the second, third, fourth….time. No one is perfect so it’s alright to make mistakes. If we want to add features or edit something, we can revisit it again. Because the more you have edited it, it means that it leads to perfection. It makes you think what is good for the application you make. Thus, it beautifies your application.

• Breaking down our problems

We need to break the time we will make the program because it will make the software happen. It is impossible to have 30 hours of doing coding; the truth is the 30 hours consists of eating, relaxing, talking and etc. Because of this, getting real suggests that it is better to break it down at least 6 hours. This hour is the reality. This will result to have the software on time and meet the deadline.

• Test your application to your real users

We need to test this to have a feedback if the software that we make is already good or bad for them. We can’t see if our program is good or bad since we make it. For us, it would be good because we are the ones who make it. Also, the ideas they have will make our program better because we have different ideas in a web application. It is better to have 2 minds than one mind.

We have reported script.aculo.us with my groupmates namely Marielle, Mary and Mike. It provides visual effects, user interface and DOM utilities. To know what I am talking about, click the script.aculo. I am so happy that I have learned in that report that can apply in my future career as a developer

I learned many sites that are so cool from my is-ebiz subject. One of these is 280 slides. I have imported a microsoft office powerpoint to the site  because we were on a rush.  I find it cool! I am so sad that we don’t use it for our reporting.  But I learned that it is slow, but when it comes to its effects, I think it is more better than microsoftpowerpoint.

Next time, I will try to use it. Click this site 280slides :D

Just try it!

We are given an opportunity to view e a css and design it in our own way. We download CSS and html in csszengarden. Click the csszengarden to see what I mean

I find it cool because in css, I can make my own website based on my likes. I can make it attractive due to the pictures available. I hope that after this term, I can make my own site

I am so happy that I learned how to transfer a file through filezilla. This is actually good. If you like, you can download it through their site. click here

You can also check my site in 000.webhost . hehehe. mycss

That’s it!

Chapter four is about deciding on things which is really important in having a successful program. First, this chapter also converse about knowing first the vision or the purpose of the software that you will implement because sometimes your program contradicts the vision. You need to know this to have a good direction in the group.

                Second, this chapter tackles about knowing who your market is. We must know their age, likes, dislikes, and etc for us to adjust with what we will program. I have learned that you can’t please everyone. So, as a programmer, we must not care with those people who really don’t like our software but the people who evangelize our products. You can’t change the opinions of other people in you. We must focus on them because they will be the one who will use it.

                Third, this chapter discusses about prioritizing problems which is present. This author suggests not to focus on the problems that will come in the future. According to getting real, the example of this is having 100,000 users in the future, this will eventually create problem because if this things happen, you will have slow connection to the server. I believed that in this situation, you need first to know who your users are at present.Instead of this, try to know if you have hidden problems at present.

                Fourth, this chapter want to confer that we as a programmer needs to decide on increasing the features of the software or not.  We need to know, if it is really necessary then do the action. It is said that you need to limit your features, but what if it really needs in the business procedure. Some said that it is arrogant to limit the features of the system. These two statements is very ironic, but what getting real suggests for the programmers is to judge it and must be supported with the vision of the company. Also, before adding features, you need to have it approve by your client because they will be the one to use it.

                Fifth, this chapter advice us not to measure our users in the future. We must first measure the people who really use our application, but don’t make a prediction of what if it would be successful and many users would use it. Actually that is really a problem. I think there is a maintenance phase in the Rational Unified Procedure because the implementation is not really the end of the process. Programmers need to maintain an application because change is not constant in the real world. Don’t make a prediction because we are not sure if it will really happen

Last, don’t focus much on details. I agree on this statement because we’re not yet professionals who is used in programming. Sometimes, even them, they made mistakes. For example, it is stated in this chapter that the details is about thinking to have four liner codes from a seven liner code. I think the important thing is to let it run because seven liner codes are not that bad.

The chapter is all about the advantages of being small company. Getting real wants us to realize the advantage of being small and to be a small company in the future. I agree with what getting real addressing us. For me, being ambitious is not a bad thing but what Getting Real is addressing it is the most practical thing to do in our competing industry. For especially the beginner in industry like us who is dreaming to have someday a company, you need to start small because there are lot of companies that are big. Practically speaking, it is difficult to compete against them because of their long years in the industry and their knowledge. We don’t realize that being small sometimes takes an advantage of being flexible, adaptable to new changes and easily to integrate or implement. In real life, there are lot of small companies’ succeeding than bigger companies. In this chapter, I have learned that it is good if our business is small, small group of people, smaller focused smaller features and etc. It means that we can easily succeed as one company. As for the cost, the small company has an advantage with it because they would have invested less capital compare to the bigger ones. It is harder to be with the same level with the bigger companies and start to compete. It is much easier to compete against the small companies with the same level as with your small company. The markets will just see where is the good software, excellent designs, quality and lesser price in I.T. companies in the country. Many people chose to have bigger companies thus there are many competitors that are waiting, if we want to have big company. Sometimes, they only realized that in a big company there would be more income but they don’t realize the pressure of being a big company, thus it will not make you succeed. It does not mean that if you are a small company, it means there is less profit, for me it means that you have plenty of clients that will pay you less amount. The clients or markets if they knew that you were as good as with the big companies, then they will stay at your service and might refer you to the other clients. I really believe that markets are conversations. Thus, because markets do converse, you will be known by people and there will be more customers. They will not longer get the service of those big companies because of the higher price that they want; it is like thrice as price of the small company. Getting real is actually just getting real or saying the truth about industry. We thought that having big companies means that you are with good software and excellent in service. That is the challenge for us as a small company that we would also can compete with bigger companies even we are lean. Also, I also learned that setting limitations in your group is a good thing. For example, you are limited in number of functions of the system you are making; it means that it is in your advantage because if changes happen you can easily go back to it and change. You don’t need to think of the number of functions that you will need to put in order to have good interface, you just follow what is required and needed by the user. As for the time, if you limit yourself in time, it just mean that you want to be organized so that you can finish what you are doing. If you limit your time then you will easily accomplish your project as soon as with the others who does not limit themselves with the time.

CHOOSE BEING A SMALL COMPANY.