Tracking change and innovation in the enterprise software development community
Testing Tools to
Support Agile
Software Delivery
Whitepaper
Posted by Jean-Jacques Dubray on Feb 18, 2008 01:00 AM
In 2006, Nicholas Negroponte explained at the TED conference that he was now heading the One Laptop Per Child (OLPC) initiative after stepping down from the position of Director of the MIT Media Lab. His main driver is about education:
Whatever the solutions are to the big problems they include education, sometimes it is just education, and can never be without elements of education.
He notes that:
As a child, we learn by interacting with the world, it is only later that teaching becomes the primary learning source. Computers have provided a kind of learning that is driven by the learner himself or herself.
The concept of one laptop per child works, he reported that:
In 2002, the governor of Maine legislated one laptop per child. 3.5 years later, truancy dropped to zero, attendance to parent teacher conference is nearly perfect, increase in student participation, kids are asking a lot of things to the teacher via email.
It is not a laptop project, it is an education project.
Walter Bender, President, Software and Content, adds:
[It] is a project about the transformation of education. It's about giving children who don't have the opportunity for learning that opportunity. So it's about access, it's about equity, and it's about giving the next generation of children in the developing world a bright and open future.
In November 2007, the first XO generation started mass production followed by the first deployment from the G1G1 program in Mongolia.
The XO was developed specifically to operate in developing countries, in places where there is no power grid for instance.
The core of the XO human interface is Sugar. Greg DeKoenigsberg, editor at RedHat magazine, explains:
[Sugar] is very different from the desktop environment to which Linux users have become accustomed. The XO was conceived as a tool to allow kids to learn interactively, and Sugar has been designed for that purpose. The first thing that a child sees, therefore, is not a hard disk or a trash can — it’s the other kids in the “neighborhood”. Sugar developers are encouraged to write activities with collaborative elements that are enabled by default.
In particular, Sugar emphasizes the concept of shared activities which happens when several XOs are meshed together in a neighborhood.
Developers contribute new activities to the OLPC project. You can actually setup a complete Sugar based development environment by downloading an XO image or buy building the environment yourself.
The OS is a Linux Kernel (Linux 2.6.22; Fedora 7 base environment) and the programming environments include:
For instance, eToy, is an activity built in Squeak Small Talk System which provides "a full-fledged, general purpose, multimedia ready, integrated development environment". In this sample, the child can draw a shape, say a car and then can use a palette of instructions to move the car.
and here is a very simple way to tell the car to follow an arbitrary path:
If you feel like contributing your skills to a humanitarian cause, here are the instructions to setup and register an OLPC project. Projects can be hosted on SourceForge, GNU Sanannah and Google Code.
In this article, Tim Jones, consultant at Emulex, provided step-by-step instructions to develop new activities on the XO.
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
The Agile Business Analyst: Skills and Techniques needed for Agile
Business Analyst e-Kit: Tutorials, Best Practices, Techniques from IBM
Combine the power of WebSphere sMash with Adobe Flex
The Key to SOA Governance: Understanding the Essence of Business
You forgot to mention that the OLPC's Sugar environment is written in Python - wiki.laptop.org/go/OLPC_Python_Environment.
Just a fun anecdote:
When I arrived for the 2nd day of RoCoCoCamp 2007 there were green and white toys on the tables in the lounge! A gentleman with grey hair was turning one over and over in his hands, trying to figure out how to open it :-)
Maybe they've figured out a way to make OLPC adult-proof?
:-)
flickr.com/photos/ogmaciel/295938580/
flickr.com/photos/bs/2179335243/
Yes, it is a bit disconcerting to open an XO. There are a couple of very small "ears" preventing the screen to open unless you rotate the WiFi antenna first. Took me a while to find these ears...
JJ-
Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library access, library challenges and future plans.
Alois Reitbauer specifies several architectural anti-patterns that one should stay away from and which can downgrade an application’s performance.
Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
John Pampuch discusses the HotSpot compiler, the history of Java performance, HotSpot development philosophies and challenges, optimization, JVM library improvements, and tips for better performance.
In this interview, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.
This article demonstrates how to build and orchestrate highly configurable and extensible yet light-weight embedded process flow using AOP techniques with Spring AOP and Aspect J.
Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.
3 comments
Reply