Archive for August, 2007

WOTD:pedagogy

pedagogy
noun, plural -gies.
1. the function or work of a teacher; teaching.
2. the art or science of teaching; education; instructional methods.
Soruce: http://dictionary.reference.com/browse/pedagogy

Sample Sentences:
“In one speech, the Secretary of Education pretty much dismissed the importance of pedagogy.” Source: http://fno.org/sept03/pedagogy.html
“For example, Paulo Freire referred to his method of teaching adults as ‘critical pedagogy’.” Source: http://en.wikipedia.org/wiki/Pedagogy

Leave a Comment

MySQL to Postgres migration links

I just started looking into MySQL to Postgres migration. One of the differences between the two is LAST_INSERT_ID() for MySQL and CURRVAL('serial_variable') for Postgres. Although there were many pages with examples about these, I found this page useful at explaining how to use the function.

This page appears to be a good resource that lists many differences between the two. More docs are available here.

Leave a Comment

webtest and jWebUnit: first impression

I spent a little bit of time check out both webtest and jWebUnit. Here are my first impression:

webtest is declarative and XML configuration file driven. If you like configuration management more than programming, you might like this format. All you need is edit the test definition and hit the run command, no compilation necessary. If you have well formed HTML and working JavaScript, then you should not have too much trouble running this. My initial simple test case works once I commented out the non-working and irrelevant JavaScript reference in the HTML. I tried to take another mini-step forward by attempting to “configure” a click to select one of the link items in a JavaScript widget. Webtest has 3 ways to click on a link, by ID, label, or xPath. The widget’s link item doesn’t have an ID, so I can’t use that. I tried label and that didn’t work. Then I tried xPath and that didn’t work for me either. So, that second mini-step didn’t go very far for me. Any one know an open source xPath validation tool or web site?

jWebUnit is one of the many unit testing frameworks based on jUnit/HtmlUnit. The interesting aspect of this framework is that it supports both HtmlUnit and Selenium test cases. jWebUnit uses similar programmatic model as jUnit, so you can stay comfortable within your favorite IDE. I was able to create a new project in NetBeans and leverage it’s jUnit feature, by creating an unit test and rewrite that as a jWebUnit test case, while using NetBeans to drive the test execution. jWebUnit, or the underlying HtmlUnit engine appears more picky about JavaScript than Webtest, I had to start tweaking YUI libraries in an attempt to load a page, which shouldn’t be something that I supposed to be doing anyway. Perhaps YUI engineers use a different unit testing framework. The test page actually loads without a major issue in Firefox.

Both frameworks do share one thing in common, both do not use actual browser instances to drive the testing. And that explains why they don’t work as well as some of testing frameworks that built within or on the real browser instance because of behavior differences when processing JavaScript. At the same time, both may have one advantage over browser based testing framework, which is the ability for non-interactive testing through ant and is very useful for continuous integration servers such as CruiseControl. Again, I’ve only looked a few testing frameworks and let me know if you know a browser based unit testing framework that works with ant. Thanks.

Comments (6)

Comments and notes on Wikinomics (part 1)

A person I know urged me to read Wikinomics by Don Tapscott and Anthony D. Williams. So, I started reading. So far I read chapter 1, 4, and 5. I agree with less cheerful reviewers of this book (here and here) that this book probably doesn’t worth my time spent reading it. I actually agree the general theme presented by the book (what). I just wasn’t so thrilled by the way authors presented their ideas (how). One of the reviewers, Timothy Haugh, clearly pointed this flaw out by saying “Wikinomics suffers from a common malady among these ‘cheerleading for the future’-type books; namely, that what they take 300 pages to say could have been more easily and better said in about 60 pages.” Other than a few interesting anecdotes and catchy slogans, I didn’t feel I am learning something new and useful.

Here are a few notes on interesting anecdotes and catchy slogans:

* Low-cost of entry: Page 12: “What’s more, people can contribute to the ‘digital commons’ at very little cost to themselves, which makes collective action much more attractive.”
* Page 12: “A world where only the connected will survive.” This is digital divide and the authors says nothing about how to bring in the un-connected world.
* Globalization: Page 14: “Today 180,000 people work, live, learn, and play on Foxconn’s massive high-tech campus, designing and building consumer electronics for teenagers around the globe.” How this related to the central theme of the book? Did the globalization of FoxConn happened because of wikinomics or could it happen even without wikinomics? This reminded me the following sentence from “What Got You Here Won’t Get You There” by Marshall Goldsmith and Mark Reiter, “I’m talking about the difference between success that happens because of our behavior and the success that comes in spite of our behavior.” (Page 26)
* Page 20: “The new art and science of wikinomics is based on four powerful new ideas: openness, peering, sharing, and acting globally.”
* Page 24: “BiOS (Biological Open Source License)”
* Page 26: “But if your invention can be replicated at no cost, why should anyone pay? And if no one pays, how do you recoup your fixed-cost investment?” Where is the answer?
* Page 27: “The first time Michael Powell, then chairman of the Federal Communications Commission, used Skype, he concluded: ‘It’s over. The world will change now inevitably.’” So what? The world is changing all the time. The old world telcom industry still exists today and are getting bigger. What’s the point here?
* Page 32: Prosumer = “producer consumers” This word has many conflicting meanings according to wikipedia
* Page 104: “In fact, virtually all companies with sizable patent holdings are now busy mining their portfolios, looking for licensing-out opportunities, and taking technologies off the shelf that can bring in revenue.” What’s so wikinomic about this?
* Page 107: “When the company finds those good ideas, Huston says, it brings them inside, where it can capitalize on internal capabilities to enhance or append the offering.” Isn’t this an old concept? i.e. acquisition
* Page 107: ideagoras = “they help link all of these individuals, companies, and organizations together by establishing connections and facilitating transactions between buyers and sellers of ideas and technology.”
* Page 114: “‘Open innovation efforts can die like a flash in the pan,’ says Stern, ‘because some senior executive says, ‘I’m giving you two people and an external budget of ten thousand dollars, and we’d like to see ten deals in the first year.’ It just doesn’t happen. It takes quiet a bit of time for these initiatives to mature.” Many people probably would like to show this to their upper management this statement. However, it convey no potential value and such argument probably won’t go very far without clear communication of value-add.
* Page 114: “Employees should also be rewarded for spotting and acquiring external ideas.” I would love to see this happen. At the same time, I don’t have high hope for this.
* Page 117: “Superior technology alone will not produce competitive advantage.” Next…
* Page 129: “But when it came time to rethink the telematic features for future models(such as GPS navigation), the company released a digital design kit on its Web site to encourage interested customers to design them instead.” We should let our customers design our products too! ;)
* Page 144: “Users exert editorial control by clicking on the digg button for each story they like. Articles that receive the most diggs are promoted to the homepage. And so the community collectively updates the front page. You could say the community is the editor.” We should let our users be the editor too!
* Page 146:

* Give users access to raw content such as interviews as a
means of providing greater transparency and accountability.
* Provide tools and become a platform for user-generated
rather than firm-generated content.
* Redesign all content to be a conversation rather than a
corporation monologue.
* Treat advertising as content too.
* Use new distribution forms, including peer-to-peer networks.
* Adapt content forms and schedules to user demands.

* Page 148: “If you make it profitable for customers to get involved, you will always be able to count on a dynamic and fertile ecosystem for growth and innovation.”

Leave a Comment