Archive for October, 2008

h1

My List of Exercises and Assignments are here!

October 18, 2008

To Sir Dave,

You could access my  list of Exercises and assignments here.

h1

Getting Real – Chapter 12

October 17, 2008

This chapter talks about how to manage and control your cost when it comes to your building your application and project – pricing and sign in the web developer way. The author suggested that developers must learn to budget – know how to price their projects, especially those deployable in the web.

Another thing that the author mentioned is about free samples. Then I remember what I’ve learned from one of my class, about FREEMIUM. This kind of what we call ‘samplers’ are great way to promote your application, in the same way, they allow users to test out your web application. Another advantage using this process is that your potential clients will help them determine the quality and accuracy of the developer’s product. This kind of approach would also give developers and clients to build relationship, thus, giving loyalty and confidence that they will ensure customer satisfaction and quality service.

One thing that the authors highlighted in this chapter is the proper way of signing up accounts. Customers will look for applications that have easy navigation. On the same way, customers must find ease if they want to cancel their accounts as well. By doing this, developers show their importance for customers. Avoiding hassles for customers make things considerate for them.

h1

Getting Real – Chapter 11

October 13, 2008

In general, this chapter discussed about Words. It explains and illustrates everything from documentation and specifications that should be processed in making web applications.

In paperwork, developers who develop web application should learn this – and the end, most customers won’t read a thing with that documentation. So, it is more important for them to know exactly what the products they are buying. Too much organized works would make your client confused and indecisive. What matters most is how well the application should run smoothly.

Authors suggested that developers should learn to explain customers that are comprehendible for them. Avoid too much ‘geekish’ talk. Instead, talk with them in a common language. Too much technical stuffs could eventually drained up their minds. As a developer, you present your features that can be easily detect by your clients. Be normal and stay normal. You don’t present specifications that are not feasible enough to make. Make your program work at its finest – not to impress your customers from your ‘written’ works.

Lorem Ipsum. It’s been a common thing for almost centuries now, yet it is infamous. Funny thing is that developers are too lazy to change that ‘default’ information. The chapter explains that developers should utilize ‘real’ words than using Lorem Ipsum. Web developers should learn, not to copy-paste the information, but they should learn to acquire information from their clients or customers. Developers should learn to think – think of what customers would think on their applications. Interaction between the client and the developer is important to come up with a better and pleasing interface for the end-users like them.

Web developer must learn how to personify their products. Their application represents themselves. It reflects their attitude and character. Each developer must learn something deeply about their product – making it a subject, not a mere object. They must seek this ‘inner’ information so that developers could come up a better strategy to build their application. Knowing more about your product means learning more. Through proper learning and guidance, developers can create their web applications effectively and productively. What people see is what you get. Developers must understand and reflect from the features they’ll be using – designs, functionality or whatsoever.

h1

Getting Real – Chapter 10

October 11, 2008

This chapter tells us how we should manage our codes – on how we should implement it and making it simpler for us to understand. There are different ways and techniques to utilize your codes efficiently. Just make sure, that every time you code, you remember this quote:

“The palest ink is better than the best memory.”

As human beings, our memories are not precise and can fade without notice. Memories could die eventually. Sometimes, best memory could still lack some elements, which is something unavoidable. It is more reliable to write something, which could remain intact for a long time.

Something that written down is far more accurate. It is something that will be firm and will stand the test of time – something that would last a lifetime.

To write it down is to record it. Just like our history, some facts were written down and not easily forgotten. You have taken the big picture – it is something that you could still recall for a long time. However, some information may not be accurate; the contents written down will be remaining unaffected. Unlike facts that were just stored in memories, they can’t be preserved for a long time.

Just like in any business transaction – you need to write everything down. You don’t just take anybody’s word for a fact. You need to write it down.

Good programmers always document their codes in a way that they are understandable. This would also help you to track down your progress – whether your program/apps is working fine or not.

Knowing your codes would help you lessen time to overdo managing time. As long as you write information that is helpful for your projects, you don’t have to worry so much in making them.

h1

Getting Real – Chapter 9

October 9, 2008

In this chapter, the author discussed how we should design our interfaces. It is ALWAYS a GOOD PRACTICE to know first what is the BIG PICTURE of the project/application you are going to make. Determining how your program will look like would give you already the idea on what will be your scope – whether you need a full-blown project or a simple app to make.

Keeping the idea of knowing what will be the outcome of your design would help you focused more on the functions that you will be adding or creating. The designing of your program would also limit yourself – avoiding the idea of making projects that are not feasible to make. In designing, start first to what is really INSIDE your application. At this stage, you may eventually have the knowledge of what will be the primary purpose of your program/application.

What people see at your application/proect is what you get. Always start a good impression in making designs/layouts for your project. These designs would serve as blueprints for your work. As for the impression you’ll be getting from others, there are three ways, or should I say, three types of first impression – 1. regular, 2. blank, and 3. error. Having a ‘blank’ impression from your viewers would serve as an advantage, since it would help you more to motivate or to convince your viewers that your project/application is one of the best they could even see. Talk about marketing your apps to people for the first time!

Always remember that changes, even problems, are inevitable. Now, it is up to you whether you want to change you app – good or bad – which will eventually reflect you character as a developer of that program/app. Know what are your real capabilities and skills to develop and create an application. In every program/application you make, you learn more and you became mature – you now understand and experience what it feels like to create your own apps.

The author suggest that in making web sites, it is more advisable to focus on what customers or users REALLY NEED. Avoid DESIGNING too much on your website/s – thinking that compelling stuffs would help you. As you can see, too much design means too much maintenace to managed. The author recommends to use small-scale websites, which will help you and your customers navigate websites/links smoothly and efficiently.

Think before you act. To avoid too much cost or breakdown of your project/app, learn to analyze first what would help you as an individual – and what others can benefit with. By understanding what are ‘real conversations’ coming from your customers, this would aid you plan ahead to make and to design the specific needs of your customers. By managing what probable risk/s might happened, you can assure yourself that you are ready and prepared for it.

h1

Getting Real – Chapter 8

October 2, 2008

Chapter 8 talks about staffing – on finding the right and suitable person to do the job for you. In staffing, you hire people which has the best standards for the job. You choose people – at the right time and at the right place. Finding the right people is not an easy task. You must know how to pick out people who are potential for the job.

I remember what I’ve learned during our PERMANA (Personnel Management or Human Resource Management). In hiring an employee, two processes or steps must be consider – recruiting phase and selection phase. In recruitment, employers would find people who would meet their requirements, such as the character, skills, and attitude of the person. On the other hand, selection phase seeks for picking out the right person. You have to break down the list of potential employees. In this process, proper decision making is vital.

Hire less and Hire later. The author explains that we must hire less people when it comes to starting out a project. Finding less people to work the job but being good enough for it would be fine. In this way, your company you’re working with will reduce its cost.

It is important for people to know everyone else – more. In this way, you cannot afford to lose people who are deserving for the job. You interact with them and you participate with them. Communication between two people make them healthy – especially in social aspect. In conversing, you stay connected with your peers- you know more about them.

Get well rounded individuals. You should learn to adapt with new people around your organization. You show them your experience and let it inspire them. Be a role model for them. You must learn to connect with them. Connect. Connect.

Passion. It is important for everyone who will make a project. Without passion in work, you cannot appreciate the works you’ve done. Passion makes thinkgs spiced up. It gives more meaningful to your project. By staying commited at your work and prioritize things you should prioritize, you can finish your project smoothly – without hesitations or worries. By staying optimistic, you would surely enjoy working with your apps, and in the same way, you build healthy relationship with the team.

h1

My Shopping Cart

October 2, 2008

Finally! My very first shopping cart in Site90.

You could vew this site here.

Have a nice stay. God bless.