Archive for December, 2008

h1

My Pre-Finals/ Finals Requirements

December 17, 2008

You could visit my site here.

Make sure you change the theme to WP Coda (my default theme is Masinop)

  • simply click the dropdown located at the middle left portion of WordPress
  • change the theme to WP Coda

Exercise for Week November 4 (make sure it’s on Masinop theme)

  • google analytics
  • google adsense
  • sitemap
  • gravatar
  • feedburner
  • sharethis/addthis,
  • ajax post
  • wordpress contact form

Exercise for Week November 11

AS10 – Make the WordPress FancyBox plugin

AS11 – Setup a style switcher for your WP-Shopping-Cart

AS12Customized NetTuts iGoogle

Some of my works/exercises are here.

Final Exam

1. Fancy name generator

2. Create your lifestream using Yahoo! Pipes

3. Install a favicon (done: installed in WP) Check this site too.

4. Post a screencap of 1 Paypal Sale Transaction in your PayPal account (no transaction: CURL issue)

5. Install WP-PluginsUsed (done: installed in WP)

6. Install WordPress plugin BackupWordpress. (done: installed in WP)

7. Create the most beautiful folio site using the WordPress theme WP Coda

Note: the plugin can be downloaded via WP (Finals)

h1

A Vertical Solutions For Retail Reader

December 16, 2008

made by yours truly.

View this document on Scribd
h1

My First Pipe in Yahoo! Pipes

December 13, 2008

Here is my first pipe made using Yahoo! Pipes

You could view the original source here.

h1

Afterword

December 9, 2008

I would like to highlight what the author wrote in this chapter:

The principle is simple: one battle at a time. My tribe is waging a struggle to raise the quality and reliability expectations of software consumers and overturn the standard operating procedures of the software industry. We face entrenched opposition with a lot of money and mind-share and monopoly power. It’s not an easy fight, but the logic and economics are clear; we can win and we will win. If, that is, we stay focused on that goal.

Indeed, this Open source that we know came from a scratch. But because of the efforts of these hackers, they prove to everybody that they could make something far to imagine. I also believe that it is important to take one step at a time. Learning how to focus and to prioritize what you should do is important.

Just like what 37signals adheres: keep your focus on the GOAL. Once you’ve achieve it, you will soon realize the effort you have made in accomplishing it. PASSION is important in every work. Just like these hackers who have devoted their time, effort, and sacrifices to develop something that could change the humanity forever.

h1

Revenge of the Hackers

December 9, 2008
Revenge of the Hackers
Beyond Brooks’s Law
Memes and Mythmaking
The Road to Mountain View
The Origins of `Open Source’
1. Forget Bottom-Up; Work on Top-Down
2. Linux is Our Best Demonstration Case
3. Capture the Fortune 500
4. Co-opt the Prestige Media that Serve the Fortune 500
5. Educate Hackers in Guerrilla Marketing Tactics
6. Use the Open Source Certification Mark to Keep Things Pure
The Accidental Revolutionary
Phases of the Campaign
The Facts on the Ground
Into the Future

In this chapter, the author explained his thoughts how hackers able to put back things they have started – making a statement that hackers are back to take revenge. I also learned something about Brook’s Law.

Brook’s Law is a principle in software development which says that “adding manpower to a late software project makes it later”. This is how Open source came to be. Projects can be brought back into control if people are added earlier in the process. It’s also important to determine if the project is really late, or if the schedule was originally overly optimistic. Scheduling mistakes account for a large number of late projects. Correcting the schedule is the best way to have a meaningful and reliable time frame for the project’s completion. It have been a drought for hackers and yet, they stood still.

I also realize that communication is important n this hacker culture. Because of effective communication, they were able to develop strategies so that Open Source would once more dignified itself from the world of Internet.

h1

The Magic Cauldron

December 9, 2008

This chapter explains the economic, yet technical side of Open Sources. The author explained something how his developments fundings have started and how it was invest for a long time. He also share his insights how people were amazed to what Open Source is actually offering to them.

To many people, the successes of the open-source community seem like an implausible form of magic. High-quality software materializes “for free”, which is nice while it lasts but hardly seems sustainable in the real world of competition and scarce resources.

Indeed, Open Source is too good to be true and thus must be magic.

Open Source Software developers are evidently motivated by many factors but favoring features over quality is not noticeable amongst them. For many developers, peer review and acclaim is important, so it’s likely that they will prefer to build software that is admired by their peers. Highly prized factors are clean design, reliability and maintainability, with adherence to standards and shared community values preeminent.

So how can we evaluate the payoff from open source? It’s a difficult question in general, but we can approach it as we would any other predictive problem. We can start from observed cases where the open-source approach has succeeded or failed. We can try to generalize to a model that gives at least a qualitative feel for the contexts in which open source is a net win for the investor or business trying to maximize returns. We can then go back to the data and try to refine the model.

There are additional benefits of open source security tools. Most of them are more or less “free”.  The solutions are available to anyone with the time and need to install them.

Perhaps a tool doesn’t do exactly what you need – you can break open the code and fix it yourself. Open source provides a flexibility not available in closed products. Hopefully, if you do make improvements to an open tool you’ll offer them back to the original developer and community at large. The give-and-take of the gift economy benefits everyone.

h1

Homesteading the Noospehere

December 8, 2008

In this chapter, the author examined in detail the property and ownership customs of the open-source culture. And the topic, ‘General Public Licensing’ was brought up.

The term GNU can be found in this chapter. GNU is a computer operating system composed entirely of free software. The acronym means:

GNU’s Not Unix

So what GNU? (I find it funny when they made this such acronym. It really doesn’t make any sense at all.

What we don’t know is that the acronym GNU was chosen because its design is Unix-like, but differs from Unix by being free software and containing no Unix code.

Another thing that the author explained is about the General Public License, GNU GPL or simply GPL. GPL is a widely used free software license. The GPL is said to grant the recipients of a computer program the rights of the free software definition and uses copyleft to ensure the freedoms are preserved, even when the work is changed or added to. This means that it is in distinction to permissive free software licenses, such as open sources.

The widespread availability of source code for UNIX operating systems and programs has been a blast. Good thing that these open source continues to merge into something that these ‘independent sources’ can’t.

Looking forward for this Open Sources.