Ferlinechua’s Weblog

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.

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!

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!

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.

Getting Real suggests:

·         To integrate the roles/responsibilities as a team

They need to see the whole project, not only their assigned task because they are also part in that project. If they encountered some problem, they can easily contact or talk with the one who is responsible on it. This chapter propose that a company should hire different kind of talents or skills so that they can use it and put together as one.

·         To limit their time to be connected with the team

We all know that when our friends are physically close to us, we can’t easily ignore them. We talk to them and shared some jokes that hinder us to do be productive in class. Based on the example of this chapter, they find it an advantage to be designated in different places at different time. This gives an advantage to the team since they have less time to be connected with each other; they make sure that the time they are connected is for discussions of important things. This helps the team to be organized and to be productive as well. Also, being alone makes us think well because like what I said talking with our friends sometimes gives us destruction.

·         Don’t have meetings

I agree with what Getting Real wants to address to the readers. There are also disadvantages of having meetings. Sometimes, meeting results to having no productive in that whole time. All you do is to chat with your friends. Instead of attending to meetings, you can work alone in your workplace that would have productivity. If the company can’t avoid meetings, getting real propose to limit your meetings instead of one hour make it thirty minutes so that everybody will be attentive and there will be productivity. Also, before you have meetings, there must be an agenda so that you also know what things to be clear up.

·         To have motivation

Being motivated will result to the success of the whole project. The company should give incentives or rewards for their employees who really deserve so that next time he will do the project, he will again do his best. It would be appreciated by the employees. Even in ourselves, we can reward our self by relaxing or eating delicious foods, this will make us our body productive. For those who anticipate their body because of heavy projects, sometimes they get sick because they don’t give themselves reward.

DONE!

We are tasked to make a shopping cart last week. But, the sad part is I was not able to make a shopping cart last week. With the aid of lectures last week, I learned how to make it.:)

I get to try on how to use scriptaculous(drag and drop) on my own. Thank you for the opportunity!

My version of shopping cart is already done and I have posted it already. I change the color, font, pictures and etc that I want. :0 My products are bracelet, earrings, necklace, ring and headband. To view the site click here!

Chapter 8 suggests us to:

·         Hire less people

This chapter suggests us to hire less people. Having many people in an organization would result to clashes of ideas, misunderstanding and higher cost of production. If there is no need for many people in an organization, then don’t hire a person. In a group project, sometimes it is difficult to integrate because you need the cooperation of the group. Also, you need to also ask for their suggestion before implementing it. There would also disagreements that would also happen unlike having an individual project.

·         Have a test basis first

Don’t just hire a person for that project. You need also to see how he really works, and his habits so that you can easily adapt to him. Some people have different kind of habits on making projects so getting real recommend us to have a test basis first. This is to see how he really works and if there would be clashing of ideas.

·         Go for people who know everything

This chapter propose that we need to hire people who generally knows everything rather than a professional in one area because you can also asked that person if you have problems in some other areas not only in his job. He can also suggest things that would be for the success of the project. This is important especially in having a small team. Each of the members must know how to design, program so that if there is problem, they will help each other.

·         Go for people who are enthusiastic

It is not only in the skill what the company really wants. This chapter encourages the companies to better look for the people who are happy and excited in their jobs because in that you will see their efforts. They will strive hard to do their best and eventually will continue learning from the company. And as he continues to learn, he will unknowingly be that skilled person that the company is looking for. I believed that skills can be learned easily, there must be that passion to learn things.

·         Hire good writers

Having a good writing skill means that you have a general and organized mind. Your mind is clear to make decisions for the betterment of the company. Also, a good writer also represents a person who is hard working. Instead of trusting their minds, they write it down because they know that they will eventually forget it.

·         Test your applicants in an open source project

I agree with this because you can only see a skilled person through his works and his being passionate in what he is doing. The grades can also be evidence but you can’t rely much on that. It is not only in being a good and intelligent student that the company must be preferred. They need to see its quality of work or his achievement in that open source. I again agree to what I read that a person with a passion will sit there and try to code. Even though, he knows for a fact that he is not good in coding, at least he have this kind of passion that not all people have.

This is my first ever lightview demo. I changed font, colors, pictures and etc into what I want. My lightview demo shows my pictures with my friends and etc. If you want to see my lightview demo. click here

Getting Real suggest that:

• Interface must be the first before coding

Do first the easy thing before the hardest thing is what this chapter is saying. I agree with this because sometimes when there is a need to change, I can easily change the design but difficult to change the codes. Also, the interfaces are the ones that users or clients will see. They need to be first to make so that you can also asked them if they like the design or some suggestions. If not, change it. If they like it, then proceed with coding. Clients will not care about coding; the important thing for them is to let it run or work.

• Start from the core of the page rather than small details

This means that the unimportant things like font colors, font, sizes, will not be first to do. The first thing what the designers must do is to answer the question ”what needs to be the content of this page?” or “what is the thing that this page cannot live?” or “what this page means?”. The small details like footer, copyrighted and etc must be the last since it is not the focus of the page. You need to focus on the important content of the page because the small details can be easily added to beautify your page.

• Consider the regular, blank and error

Regular means the actual screen you want that people will be seeing (if the data he inputted is correct). Blank means the outlook of the screen when the data he inputted is being processed. Error means the physical appearance when the data he inputted is not correct. As a programmer, you must also spend time in the blank and error state because your user is not perfect. They will commit mistakes even though you tell him the correct data. To avoid this, there must be an error message saying that you have entered incorrect value, as for the blank state you must also say that this page is loading or wait for a moment. That two would let the user know what the system is also doing.

• Make some solutions when blank slate occurs

You must expect that your page is slow because you have added some designs, data and codes in your page. The system is still generating all the designs, codes and etc that you have made. When this occurs, all the programmers knows that the system is still loading, while for the users, they will began to say that the page is not working because they didn’t know that it is still generating. This chapter suggest that you need to make a solution for the users to also help them if Blank slate occurs. This recommends making a help box wherein this includes some tutorials, the outcome when you clicked this or that, and have an answer that is frequently asked by people.

• Have a defensive design

No matter how great we are to program, still we must expect that there would be error. People what I said is not perfect. The question is how to handle the error made by the people in your page. Based on what I understood, there must be labels like what you will input in this textbox for example email address. There would be a chance to lessen the people who commit mistakes. For the programmer, don’t expect that users knows what data they will he put in your page. If you don’t put any defensive designs, this will make your customer not to like you until they will not visit again your page.

• Context is more important than consistency

For a web, the most important thing is the context. The users will not care if it would be consistent, what they want is the context. If the customer click the add button, he expect that this will add the product. That is what the customer wants to see rather than thinking of what is best if box or circle. It all depends on you as a programmer. The important is to have it to show the exact needs of the customers.

• Have a simple and understandable words

As a programmer, they need to have simple and understandable words to put in their page. The customer are not all intelligent as what you think, they have different levels and understanding. If you make a complex sentence, some of the customers still needs to figure out the term you used before clicking it. Your user will not love it because they need first to learn it and remember all the details of your site. If you have simple words, your user can easily visualize what to expect when he clicks it.

• Have a one interface for the administrator and users

The advantage of having this is the admin can easily manage the site or their users. He can do whatever he likes without any restrictions because he is the admin of the site. If the programmer builds a separate site for the admin, it would be difficult to manage the users who used that other site. This suggests having a joined site for the admin and users so that if there are problem, the admin can easily make an action.

Chapter 10 of getting real is about:

Listen to your code

This means that a programmer should be guided by his codes. There are codes that spent many hours to let it work. That means that the programmer should pick codes which will not take a lot of his time. It is better to have a short codes rather than long codes that also acted in the same way.

Lessen your software

It is better to have less software than many because if you want to change something in the code, it will be easier and faster if you check the less software. If there are bugs, you can easily see the errors.  Also, each time you add features in your codes, it makes the software bigger and complicated to understand. This chapter 10 suggest to have less software because of the advantages attached to it.

Think of it as a debt

We need to think of our applications as a debt so that we would minimize a bad software. We will think that they paid us much money so we must in return do our best to remove the errors and make it easy to use by our clients.  In this way, we can easily have a good codes and a good design of our softwares.

To have an open doors

Getting Real recommends to have an open doors in your software. In this way, people will communicate well the problems encountered in your software. They c an easily check the updates and track made by users.

Optimizing Happiness

This means that as a leader, you should pick a person who is always happy and excited so that every time he will do his job, there would be passion in it. Thus, his behaviour will also reflects on his work. Also, let the programmer choose what he preferred language so that he knows what he is doing. We should not forced them on things they hate, but we must guide them with what they love. Because, in that it reflects in his/her performance.

Chapter 11 of Getting Real is about:

Don’t have much paperwork

This means that a team should not do much paperwork rather than make dummy software. Paperwork’s does not actually help the success of applications. It would be a waste of time since you can’t run it unlike making a start up application. Paper works are only for writing your ideas. Thus, the best way is not too have much paperworks.

Give personality to your product

Product is like human, they must have personality. Every feature you add in your software, you must based it with the personality of your software. The software is like the people who will face the users. Thus, you must have a good choice of personality in your software.

Don’t write too detailed

Your users want that your sentences in your software is easy to understand and must be short. Or else, they will not read the sentences of our software. Our software must be based to what the customer wants. Thus, we must follow what they really expects in our software.

Don’t make your spec as a big deal

According to what I read, we must not worry about our spec because it is useless. There are many hardware that has good specs, but even though it has good specs, sometimes your application is not fully functioning.

click here to see my get ajax demo! tnx:)

Note: you can use mozilla firefox not internet explorer

These are my updated summary of exercises in ISEBIZ

AS1 – my css zen garden
AS2 – my customized css
AS3 – myshoppingcart
AS4 – my fancy box
AS5 – my lightview demo
AS6 – my  ajax generator
AS7 – my quotable quotes
AS8 – my contact form

check this out!

Tnx!

Chapter 12 wants to suggest:

Give it free

            A company must give a free sample for their customers in that way customers will know what products and services that offered by the company. They will try to use that since it is free. This gives the customer a way to have an introduction of using that free sample.

Easy to sign in

            This means that whenever a customer wants to log in or sign in in their account, they must face not too much details, but the things he expects. Also, whenever the customer logs out, they must not face with are you sure to log out because they want that they will easily sign out.

Don’t try to have a trick just to earn money

            Don’t have long term contracts because the customer wants that your relationship with them is for short term so that they can pay you what needs to be paid to you. For example instead of a year basis, we need to be practical and it is a month basis.

Don’t harsh your customers

            This means that if you meet increase price, you must first think the best way to say it t your client and not to surprise them. They might get angry for that issue. This will cause not to trusting us.