Hello world!

Eventhough, I have many blogs throughout the net. This would be my first time to really experience the  “meaning of blogging”. haha

shopify.com

It was last September 9 that I, convinced by the good weather to start the a brand new day filled with joy and contentment. You know why? Because it is the second day of my 8th term of schooling in the institution of College of St. Benilde. Well so to speak, a brand new term for everyone of us to build the term in a right way. Eventhough that all of our class schedule during the afternoon and a little of evening, but still it’s a half day class it just fine.

Anyway, it was during our first class which is IS-EBIZ that we were told by our professor, Mr. David Quitoriano to create an account for blogging, as an introductory lesson to the course subject that he would teach us. Each of us were required to create an account through wordpress.com as well as establishing an e-commerce/ e-business site through shopify.com, the discussion was really exciting for me, and i guess for all of us too, because our general topic for the whole term would be web application, and thus his class is one of the list to build our foundation about the topic. Then all of a sudden the internet connection in the lab was cut off due to some unknown reasons, therefore the result is that i was not able to create a my account in shopify so I have no choice but to create it at home.

To cut the long story short, my experience about the site is, at first I am having a hard time to figure out what the specific navigation tabs are for, for the fact that it was also my first to create one, but as i explore each of the tabs, I was able to decipher the flow of the site. What I did first was to select my personal template for my site. But going through the functions, I forgot that I still don’t have a business to start with to open the site and since I am a music lover, I have come up to establish the site in a “music like world” at first, I am planning to sell musical instruments but in the end I have decided to put up a music store that features album of any given artist. After choosing who artist to include, my last task was to create the “about section” and the welcome note of the homepage. Well, yes at last! I have finished it though it took me a long time make, still it all of it was worthwhile.

By the way my site —–> harvey29.myshopify.com

Please feel free to visit if you have spare time. Thanks in advance! =)

gettingreal.37signals.com

CHAPTER 1

Basically, the chapter discusses the introduction of all the entities involved behind the construction of the site and moreover, the book that was developed throughout the strategies and techniques presented which is– The Getting Real. Primarily,  Getting Real was designed by its developers with the company name of 37signals to provide practical solutions to address such a specific problem of course by means of solving with some kind of a web application concepts formulated by the company. Their statement ensure its readers and users to eliminate unnecessary steps to come up to your defined output.

The first section: What is Getting Real- concentrates and focuses the intention of publishing that specific book and the is to address directly a problem to its corresponding and best practiced techniques. Also in the section, mentioned the benefits of selecting those “direct to the point” conclusions based from what you have gathered. In short, why make life difficult where in fact there is a way of simplifying it, thus this statement is applicable in all of life’s aspects.

The second section: About 37signals- the company that introduce the book. The section mainly discusses the simplicity and convenience of using their products which is divided into 6 aspects: basecamp, campfire, backpack, writeboard, ta-da list and lastly ruby on rails. The have defined that together with these products are simple instruction and are user friendly applications.

The third section: Caveats, disclaimers and other preemptive strikes- The organization through this section claims and proves that their way of solving such risks and threats are not that of a new idea at all, it is just that they are emphasizing and focuses through because they beleive that these are the ones with good implications and yet, not that of a best practiced in the industry.

CHAPTER 2

After the introduction, the chapter shows the first key steps in building the foundation of a the user that would and could bring him/her in a much competitive world in a much higher sense.

The first section: Build Less- “Too many of anything” is not a good thing for the 37signal as for I have understand this would just lead in bigger risks of related chain of problems.

The second section: What’s your problem- the section encourages everyone to look for new opportunities with that of the statement: explore new things that would uplift condition. Also, try to consider everything concerning for the benefit of all.

The third section: Fund yourself- the section simply tell the importance of prioritization of things, together with a vision of the future scenario based on the present time. When setting up project, regardless of what is it, we cannot prevent risks and obstacles come are way, there expect the unexpected. And this section will also goes to prove the statement: Let’s us consume less and conserve more and money is not always the key answer to every given problem.

The fourth section: Fix time and budget, Flex scope- timeliness is vital factor for every project, therefore learn to budget your time in a deadline that you can beat because by doing such you’ll be able to possess prioritization, reality and versatility.

The fifth section: Have an Enemy- don’t be afraid to compete if you know you can and if you know your on that your on the right track of leveling their status  because with this way, you can learn about your downfalls if ever you fail, but always remember that anything can happen right away in a blink of an eye and lastly learn to persuade your audience.

The sixth section: It shouldn’t be a Chore- the section tell us its audience the importance of passion and enthusiasm of an individual to do what he/she really wants because with this philosophy you are doing what you enjoy doing.

gettingreal (cont.1)

CHAPTER 3

In essence, the chapter talks about the “beauty of change”.

First Section: Less mass- this section talks about the benefits of change in general. For a company to grow and stay longer especially in the IT industry you must embrace the fact that ” the only constant in this world is change” because putting this thought always in your mind will truly let you accept that change is can’t be prevented nor be avoided, therefore you must learn how to welcome them at anytime.

Second Section: Lower your cost of change- the section mainly focuses to develop a creative and emergent solution yet simple and user friendly system. With this we can eliminate and disregard many unnecessary things that are irrelevant. In a project, time is one of the main factor you must consider therefore, don’t choose to make things harder for you such as making it more complicated. If you know you still have an option to come up with, but still presented in the same way you wanted then go for it because in the end you would realize that it is more efficient.

Third Section: The three musketeers- when creating a your first web application projects it is advisable to start with three people only having the jobs of a programmer, designer and a sweeper (someone who can adapt in both the worlds of programming and designing). In other other hand, if unfortunately you can handle with that kind of setting, then this is only time for you to recruit another members. Thus a good communication and delegation of tasks is the keep to accomplish the project.

Fourth Section: Embrace constraints- be aware of the constraints you might encounter in doing the project, and thus if you can identify them then as of the initial stage of the project then go for it and do the corresponding preventative measure. As for the resources available utilize it in an effective and efficient manner.

Fifth Section: Be yourself- customers and clients are the assets of the company if there are none of them existing in the organization alll factors of the company will be affected such as productivity, manpower, revenue and most of all profits, so therefore be true to them with all your responsibilities to them when enganging in a clients in not a joke, so you must pursuade them and transact to them in a clean and honest manner because in turn its for your benefits as well.

gettingreal (cont.2)

CHAPTER 4

To summarize it all, basically the chapter tackles the basic steps (such as requirements and needs) in building your first program in web applications. For the past chapters the site have focused with all of the foundation you must know and much better possess as early for that time, prior for building your own web app. But then, chapter 4 I must say it really the starting line to such particular project, thus you will apply here all of your insights that you have gained within the previous chapters. By the way, parts of the chapter including your objectives, “piece by piece” tasks following the pattern of a “cone shaped” (meaning start from a general down to specifics) system of implementing your actions and analyzing things. Also included in the list is of course, identifying your problem, therefore somethings this may be the success and failure, if ever of your project because if you did come up with a wrong point of defining what is the general purpose of doing your program you have a high risk to be engaged of having hard time in accomplishing the entire application. Making and hiring your “suited” customers as well will help in a lot of ways because in this stage, you are able to distinguish what is it that your customers needs and wants up against what is it that he/she don’t need or of a minimal help with his requested program/project. By this time, you have already stated your target market. Just a reminder that the statement (especially referring to the filipino market we have) that “Customers are always right” is a big mistake to stick unto (you know why?) because every individual have his/her own needs and wants, therefore what you have created is not that relatively the same as with the perception of customer A and customer B, but then customers to intend to abuse their as such so better choose your customers of if you can’t they make it a point to have a alternative option to compensate for his/her wants. Next stop, is to address some recurring problems that could happen just like for example system or website is done because many clients and users are accessing the site, for these kinds of problems don’t you worry and bother that much because always remember that there is always a time to change and address those issues and believe that you can pass it through, be optimistic in fixing such problems! Lastly, the last section of the chapter would discuss about your set up of your some kind of a “vision mission” of your software. It was mentioned that a single consistent vision can really help you to build a better software because you have a path to pattern and follow to.

gettingreal (cont.3)

CHAPTER 5

First of all to discuss the content detail by detail, I would say that this chapter entitled “Feature Selection” is quite long to read but don’t you worry because not only that, luckily per section is just short to tackle and start with, so I will just once again discuss it per sections. Anyway, the chapter in general talks your track to produce your own product web development application.

First Section: It says that to build your product you must set your mind to aim for perfection of the product to conform with the client’s needs and working environment he/she is into. Be factual, in creating such one, Step by step make it a point that every functions are amazingly working. As much as possible, try to build the product in such a way that it is attractive to the client’s point of view meaning unique.

Second Section: Be practical, just include that ones that you would just need in completing the requirements of the product. Always remember that no one will ask for “how did the team of developers create” or “how long did the team create this product”, so just don’t be disappointed but instead be flattered with such comments because you know that you’ve created such factual and real web apps to address the customers mode of need. And make a merit for yourself because you’ve just made a productive application that you’ve just been sometime in the past.

Third Section: As I have understand it, your final software product should be implemented in a “hardcore” manner. As the software is fully implemented that means fully available for the public to use, then the software should speak for itself. It should “self serving” as one of my professors have mentioned. In real world, we must admit that we can’t please everybody, right? Then to apply this with concepts I have learned expect that all people will not embrace and reach for it.

Fourth Section: For this section, prove that your web application is are of innovative  and unique for its cause showing new features that the customers are expecting. Make the customers proud of what are they purchasing by making it worth it.

Fifth Section: Build your strategies in a way that you can manage and handle it on both ends, because when you create your product you can have difficulties if its not manageable for you can’t reach your desired output and then you’ll just try it again and to revise your program.

Sixth Section: Make it a point that just build your product and services especially your formulation and conceptualization of product created in a general purpose. It is because you are trying to create product that of an ideal which can impact each and every customers if possible. Let them set their solutions for a particular problem that they would encounter because here they can learn to how use the program and at the same time explore what are the things that they don’t know yet.

Seventh Section: For the section, it discusses that let your customers define what are the important things that you may include in the program you are creating, because once you’ve finished the programs they are the end users of the programs or simply the users in the end of the day. So, therefore dedicate to them what are you creating and create what are their needs.

Eighth Section: By asking the people what are the things they want, so for it, ask also for what they don’t want for here we can examine and identify more precisely what are the features that are of irrelevant to them. By doing also, you can now have a clear of “do’s and don’t” of the web application program you are creating

gettingreal (cont.4)

CHAPTER 6

The title of the chapter is “Process”, basically the chapter talks about the continuation allow me to say the “part 2″ of enhancing your software before building it. As you would read you’ll come to appreciate that creating and making your onw software is not that of a complex and complicated thing. Developers on the first phase of making such, should allow their selves to capture the basic concepts and foundations in order to have a final web application which is clean, unique and impact to the prefences of the customers. Along with the chapter says that from the day one of making your own software target to debug the software in a best way because this will show to be your big goal in the end. The second section also conveys that everything is not perfect for the first time, thus we have the statement that “practice makes perfect”. But don’t miss the things that always aim for perfection rather than mediocrity or less. Don’t afraid to repeat and do iterations because this are the tools that would make anything better. On the other hand, the third section would present its point that formulate and create your ideas first before the general implementation and put into actions your actual codes. It is advisable to do brainstorming together with your team so that you can exchange and share ideas completely and freely. The fourth section of the chapter thus talks about avoid preferences because these things could lead to a cost such as more additional software that is unnecessary in relation with the bigger picture purpose of the software. Of course, preference would have both advantages and disadvantages but, this seciton suggest that there are more disadvantages upon building preferences to your software. Prefences also connects decision making to show effiency and effectivity of your software, in a way that the users of your program will not need to choose having in fact that they have different preferences. Fifth, always put into consideration that in time everything you do as for the moment are to be finished and accompished in time, so stating build your momentum. After you have done one task then that would be the go signal for you to create the next step and that is what you call the “move on” stage. Execution is one of the best way to prove you know something and so after you’ve accompish it all then alarm yourself to executive in a creative manner. The sixth section features that all of yor resources should be based on reality (such as feedbacks, data and etc). After all, your software are designed and dedicated for them. Test anything that you can because in the long run it will benefit your team that you gained and earned the connection to the people through your newly implemented web application. We all know, that a project is broken down into little pieces called “tasks” and therefore, this is what you want to do for faster development, improvement and upgrade. The advised is that, shrink your time and make a target for each division of your task, then if you finish it in an earlier time you can proceed go to the next and so practicing this system could make you more productive and effecient in all aspects.

gettingreal (cont.5)

CHAPTER 7

Entitled as ” The organization” the chapter discusses the entirety of the team that will build the web application. Choosing and hiring who will be  your teammates, delegation of tasks, transitions of your activities and most especially unity of the team organization are discussed throughout the chapter. By the way it is divided into 4 sections:

It says here in this chapter that everything can be done through the quality of unity in what your doing, therefore understanding what is the your main goal is a vital entity to make a product. As experience by the team of 37 signals it’s not always effective to do your task always together with your colleagues meaning your in the conference room in the front of the monitor makng your codes and your other teammates are constructing the flowchart, use case and actitivity diagram, so on and so forth. Thus set up is not always an effective manner in working out a project. Sometimes you must also prefer to work alone with your team mates away from you, well what i mean here is that work on your product eventhough your teammates are not present at all because in some sense you will realize that make it on your own can make your more productive. Making this out, you’ll not to entertain interruptions because this can worsen your working time, therefore as much as possible focus on your work. Though the third section is quite vague because I myself do disagree at some point to the statement that meetings are toxic. For me, I do believe that meetings are not burden to a team to accomplish such projects but instead meetings are set for a purpose to clear things up. Also, to inform and update your team (some kind of a status report) so that you know what are the things that you are finished with and as well as the ones that you are not done yet. Meetings are places to discuss and settle things and as well, do contribute to the progress of a project. Lastly, meetings are always a part of a project (most of the a business project) so therefore you can’t just eliminate it as simple as it is. Anyway, moving on to the last sections of the chapter discusses about motivation and passion to do your thing, therefore everything single success of accomplishment is a victory for the team, therefore celebrate a little. With this line of thinking, you will soon realize that your on the right track and so you would probably be motivated (and continue to motivate and motivate yourself as well as your team) to finish the product down to its final stage.

gettingreal (cont.6)

CHAPTER 8

Having the title of “Staffing”, the chapter deals with the management of your staff in general. When to hire people and when not? How to hire them? Who to hire? This are some of the questions that would be answered if you read the chapter.

Its not of an advantageous strategy to hire and make many employees for a specific project. You know why? it’s because this could be of a good help to the company or more option would be a “burden” for the projects and also for the company. Having many teammates can not assure to accomplish tasks and activities because it depends on what is the scope of the project. So, make it a point that as you begin a project make your workers not of many number but as necessary that the project would need.

Upon choosing employees to hire, the next procedure would be to test what are their potentials and capabilities as far as the related project is concerned. Giving them a little of work would be a great help to determine who are the one really qualified and best suits each series of task/s.

For technical and specific occupations, it would be better to be an open minded selector as you pick your choice of employee. Resumes, grades and etc are not the only factors you may want to look at, but also their potentials as well.

As much as possible, try to hire and get employees who are well rounded individuals who can make and do other things if needed for a purpose. Versatility is also one of the good qualities a worker can possess.

Enthusiasm and passion– are the magic words for an employee to be hired. If you are able to see this qualities in him/ her. He/she may be the right person you are looking and want to hire for, because having dedication and love for work is the key to finish a quality and high-level projects.

Good writers are of equivalent to any other professions. If you possess this quality I have to say you are lucky because everything will follow. Organized mind, clear thinking and good communication are also with your qualities as a person.

Web designing 101

My site 90 (csszengarden) – http://harvey28.site90.com/

Shopping cart (drop and shop) – http://harvey28.site90.com/cart/cart.php

gettingreal (cont.7)

CHAPTER 9

We are now nearing to the implementation of the web application program that we will create. By the way, the title of the chapter is Inteface design and also it is divided into eight sections.

First thing that a team should consider in creating a web app is the user interface also known as UI. This should always be the first as reccomended. Focus first on what would be your design because this the part of the program that could attract your clients and users. Of course this is would be seen first compared to the other aspect of the whole program (such codes, development and other concerns). First priority should be this aspect.

As far as hierarchy are concerned, build your UI in a way that start in the most important piece of the content of your entire website. Aim to reach your purpose of creating the website, itself. Entirety should be based in your epicenter. The method of making such action are called “epicenter designing”.

When designing your interface there are also others things that you would need to take into consideration. One of the things I am referring to are the three kinds/ states of the screen that you should build: regular, blank and error. Regular states are the ones you should spend your time most, but as much as possible try to balance the three so that you can come up to a effective and user friendly interface for your users.

First impression about everything are the important things that one should consider, that’s why make your blank state page of high quality. Assistance, tutorials and troubleshooting should also be addressed by the state to avoid confusions and complications.

Defense is a great mechanism– the statement is a good thing you may also do in order to track your’s needs, requirements and preferences. You will always be ready for problems, because we don’t know when will it happen. By being defensive a team can minimize risks and problems that can hinder their customers to use their programs of web application that they are introducing.

Context may appeal more than the consistency of the program, therefore make it a point that each and every context you are putting on your site are of relevant and informative ones. Weighing things shoud also be a good strategy to start with.

Language is very important to communicate to others, that’s why choice of words in creating your web app will also put into considerations. Common language instead of jargon are the ones that should be implemented by a team, the reason behind this is to make your information reachable to your audience.

Many interfaces are not always the excellent ones instead these are the ones that give migraine to your users, so as much as possible try to target for a few screens of interfaces that your would construct. Remember that your are the admin of the system, so anytime you can edit and update the application, if needed.

gettingreal (cont.8)

CHAPTER 10

When you are done with your UI, now its the right time to code and manipulate your application in terms of syntax and logic. The chapter is entitled “Code”, as well.

Personally, this chapter is my favorite chapter of the getting real guiding principles and concepts. Eventhough the chapter talks about coding, and to admit it I’m not that of a good programmer, to refer to it directly I’m a not a hardcore programmer, but still I love this chapter. You know why? because in this chapter it doesn’t just tackle coding as well as some life insights and ecouragement to pursue your life each and everyday. Motivation, excitement and happiness are some of the things mentioned to this section. It says that being optimistic is a good way because for that condition you are able to make productive things. Craftmanship and passion are the keys that can make you a better person and professions. Your job defines who you are and your devotion to your job should always bring you motivation and enjoyment. Programming are not just codes you implement and then execute but by doing this also, though be able to express what is that you really want, and so as for the other occupations you want to pursue. And this should be the way it is.

Other discussions that was covered throughout the chapter is to build lesser software because this might save you to any bigger problems that might arise in the future. Also,  let’s code much better because you are able to maintain your web app as simple as it can be. After some time try to re examine and evaluate your codes to remove some of the unnecessary codes. Lastly, just a reminder make it a habit to put up newsfeeds and updates to inform everyone about what’s new to your site and as well as to enchance and develop your features as coming from your customers, clients and users.

gettingreal (cont.9)

CHAPTER 11

The chapter is entitled “Words”. Interface designing and coding are now finished, the next course of action we must do now is the documentation by identifying your functional specifications and requirements. But this is a different approach of documenting your works in the sense that you should aim for a less paperworks by more of the conversational thing. During construction of the program, keep your specs as simple as possible. Specifications by the way should also be of reach at the same time, because when requirements are not of the kind you can often encounter problems upon doing the completion of the entire web application. As I have said earlier, as possible as it may seem try to minimize paperworks especially the things that are of unnecersary ones because this can just ruin your web app. Documents are treated not in the same way as your programs are. On the other hand, engage more of talking and presenting your application Documents are just second priorities to support your program. By talking, you can persuade your customers compared in presenting a bunch of papers that customers are oblige to read. Reading is far more difficulty rather than listening, right? Another fact also is to make stories rather than focusing on to details. Stories are much effective to execute instead of detailing every important facts. As well as, first hand experiences are much better rather than details because the former are much interesting to converse about. Lorem ipsum can also not of a good way is conveying your messages to reach your customers because these are not actual and real words to use. What you need as for the moment is to straight to the point information. Lastly, personify your product meaning depicts your product as a person so that correlation can easily be applied by the customers. And developers should not also forget that products do have voices and thus it is talking and interacting to customers 24/7, it simply means that products are not always constant and so, we must update it from time to time and also being competent to others.

gettingreal (cont.10)

CHAPTER 12

Through this chapter, this is the stage where the team have already accomplished their software, so the next stop now is to distribute it and see for what will be the customer feedback would be. But wait, before doing that we should also make a list of actions to gain customer’s approval out of our product. The chapter discusses more of the customer relation management (CRM) and the quality of the product software you’ve just put into the market.

During the introductory stage, make everything you’ve done to be given to others for free. Let them test the program you have just created. After sometime, you the team can now have a glimpse of what is the impact of their software in the basis of the first hand users. Always try to think of the statement that products are meant to be free for its first level. Other things that we should look at are the registration and cancellation of a user. Erogonomics- are the words that could make your user stick to what you have started. As he/s he enter for making and signing up an account. Please don’t make it a hassle step for him/ her because once they have experience a hard time, the tendency of anyone is to quite and not to contnue the registration process. It that is not a good thing, but of course otherwise. So these are just some of the things that you and your team a preventing to happen. But if it happens though, make the user what he/ she wants to make– even he/ she wants to leave, cancellation process also should not bring them a hard time figuring out. Customers deserve to have a reward not a penalty by using a developer’s web app, and this should alway be a reminders for all of us. Another fact, is that terms of services and condition should be kept in a simple and easy manner, keep it short as it may seem. Lastly, be optimistic as I always say even your news is not of quite bad. Announce it in a way that the user/s can take it not to deeply. As adviced, short notices are not applicable in building your web app but rather advance notices to prepare your customers to can happen.

gettingreal (cont.11)

CHAPTER 13

The chapter is entitled “Promotion” as for its main context serves this would mainly tackle the marketing and advertisement side of the web application program you are creating. It is divided into 9 mini sections that mainly concentrates ways on how to make an impact for the web application you have just created. After sometime talking about month after you have finished your web app. The next thing is the launching of the application per se. To do this you will need to make a notification to the customers you are aiming for to have, you will need to really prepare for this event because in the long this would the first impact and judgement that your customers can make. Also, as much as possible it is reccomended to go for a promo site that features all of your intention, benefits and overview of what you what just created to gian much viewers and audiences to engage in your site. Next thing would comprise the statement that blogging is far more better than advertising and thus a lot more cheaper yet much effecienct and effective therefore make it happen to have a blog because in a split second of time your audience can be notify immediately by sending information through this marketing strategy instead of making it out to the “old school” way of advertising such as television and radio ad but this could a good thing though don’t prioritize it instead. As soon as you have made your way to gain customers you are now ready to notify them in case of need. Make a point also to promote in terms of educating and informing your customers of what your team opt to offer in general. With this way both parties are enjoying and having fun while learning and grasping the whole thing that you want to convey to them. A good thing also to launch your product is to make it in an original and unique meaning having the features and benefits not seen by anybody, here you should really think of a creative manner to start to. Feel free on the other to accept comments whether it is a good or bad comment to improve your product line as a new in the industry you are pursuing to. As well as make it a point each and everything to make an upgrade of your web app because this may open to bigger oppurtunities that are waiting for the team in the future. Lastly, create a domain which is easy to remember for the customer becuase having such can’t be a tendency for a wrong site or even mispelled, in this way also you can minimize the errors of you application.

Web designing 102

Link for Ajax Generator ->http://harvey28.site90.com/ajax_generator/generator/

Link for ajax form using jquery –> http://harvey28.site90.com/jquery_ajax_contact_form/

Web designing 103

Link for lightview –> http://harvey28.site90.com/lightview/

Link for fancybox –> http://harvey28.site90.com/fancybox/

gettingreal (cont.12)

CHAPTER 14

The chapter mainly talks about the support system of your web application that you have just created. Upon initializing to construct the website you have as of the moment your devotion shoud be shown to the efforts you are having now.

When implementing a web app, a developer should always put into mind that all of the needs of the end user are present. Don’t let your users initiate the move of requesting a feature for you program, but the proper way is to make it available immediately as you think that it would a over all feature. But also don’t always grant the request of the user for your product will be hated. Here, a person should know how to weigh things, which is which from which. A web developer should also learn to provide to answers to questions with short notice. It is recommended to put up an interactive station for the customers such as forum and chat rooms, so that in both parties can easily talk with one another. Lastly a support system should always be true, straight to the point and honest with its customers because by being such you customers can understand.

gettingreal (cont.14)

CHAPTER 16

In this chapter, you have just finished you new or for other the first web application. Following all of the principle of gettingreal by 37 signals you are now ready to face your users. Upon finishing your software, you must remember three great advices: execution, people and more than just software.

Personally, I’m happy to finish this particular book for the reason that its ideas and concepts are not that new but easy to implement. All of the chapters have sighted their own point of view in a chronological easy to do manner. Hope that in the future, I can make all of these concepts happen as I go through my endeavors in life.

gettingreal (cont.13)

CHAPTER 15

Generally speaking, the chapter talks about the follow up actions to your web application before the official launching. First, is to make it a habit that upgrade is always present within your product. By doing such as well, you may determine the drawbacks of your system, then in turn you may fix it. Blogging will always be there, use it as tool for your news about your site. Here you must do feed news, faqs and feature (and/ or added features) of the web app. Another point is not to excuse your product for its errors stating the reason that it is only a beta testing because after all you are not launching your product just to become a beta, right? Anyway, be confident with what you have created otherwise don’t if you are not it is a sign for you that deploying your product as of the moment is not yet the right time. Bugs are always there and will never be gone therefore what can you do is not to solve them not by eliminating but to preventing it to happen. With scenarios like this, you should know how to prioritize your bugs. A developer can’t complete a product is he/she do not have news feeds, here you can use a RSS or Feedburner so that results if one would requested can now be easily access. Adding features regularly will not always be the answer but instead provide a valuable ongoing service. In this way, you have reduced cost and as well as customers can still enjoy your developed web application. Lastly, go with the flow. Be open to others that are commenting and suggesting to your products as an upgrade and improvement. Learn how to change paths if needed because this can only just lead to a much bright world of opportunity and innovation.

My site90 wordpress

Link —> http://harvey28.site90.com/wordpress/

Webdevt Final Exam

Click here

Click here

Webdevt Requirements Proj2 (Extra Joss)

Click here

Webdevt Requirements As19 (fbstyle)

Click here

Webdevt Requirements Exercise 6 (Credit Card Validation)

Click here

Webdevt Requirements Exercise 5 (Poly9)

Click here

Webdevt Requirements – As18 (Autocomplete Lookup)

Click here

Click here

Webdevt Requirements – As17 (AmChart)

Click here

Webdevt Requirements – PROJ1 (Fan site)

Click here

Webdevt Requirements – As16 (Creating a Facebook Application)

Click here

Webdevt Requirements – As14 (Simplepie)

Click here