Contributor

Collaborative work in the cloud: What I learned teaching my 9-year-old how to code

opinion
Feb 9, 20164 mins

The power of the cloud lies in collaborative work. Sharing amplifies both productivity and learning.

school kids rasing hands
Credit: Thinkstock

A couple of weeks ago my third grader daughter expressed renewed interest in learning how to program. She had already experimented with MIT Scratch over the past couple of years, so I tried to teach her Python using the Python for Kids book. Somehow, Python did not click — she didn’t see the point.

So I decided to move on to JavaScript. In my last post I pointed out the importance of JavaScript as the language of the cloud. Everybody has a Web browser on their computer, phone or tablet. All commonly used Web browsers support JavaScript. Anybody can run apps in JavaScript without having to install anything. Anybody can write apps in JavaScript without having to install anything other than a text editor.

A little background: My daughter uses a Chromebook that I got her a year ago. She has a Google account through her school. The Chrome OS has amazing parental controls. The device itself is cheap, has incredible battery life, and I have no concerns about my kids using it. Given the fact that I paid $120 for it, abuse from a kid is the risk I am willing to take.

I ordered her a copy of JavaScript for Kids and set out to look for JavaScript development tools that she can use on her Chromebook. After trying out a dozen tools, I ended up settling on Cloud9 IDE — and it was at that point when I realized the true power of the cloud.

With Cloud9 IDE I was able to setup a basic Node workspace serving static files. I shared the workspace with my daughter and showed her how to use the editor and how to preview her work in the browser. She then set out on her own to build herself a website. That process, in and of itself, was easier and more productive than using the text editors the book recommended. Auto-completion and auto indentation helped her to understand JavaScript, HTML and CSS. Instant highlighting of errors and warnings nudged her in the right direction.

An evening later, she was ready to publish her website. She wanted her own domain name and she wanted to share her website with her friends. I set out to do some homework. If this was 1996, I would have recommended a hosting account with SFTP access. But this is 2016 and we need to think outside the box.

It just so happens that Cloud9 IDE workspaces come with Heroku toolchain and Git. It took less than five minutes to set my daughter up with her own Heroku account. Cloud9 workspaces come with an Ubuntu Docker container with the workspace. The challenge for me was to explain Linux command line to a 3rd grader. It is a good thing that a nine-year-old has no pre-conceived biases towards any particular user interfaces. Within minutes, her website was up and running. She now knows how to make changes and push them to the cloud on her own.

The most important motivator for my daughter is the ability to share her work with her friends at school. This type of sharing works when her friends do not have to install anything, much less any command line tools. MIT Scratch lets her do that. Cloud9 IDE does as well. She is able to not just publish and share her website, but she can create and share workspaces with her friends. By working together with her peers, she can learn faster and she can share her knowledge. This greatly amplifies the educational value of the tool.

Whether my third grader becomes a software engineer when she grows up remains to be seen. The ability to customize and extend the behavior of a computer is a skill that is going to remain with her for the lifetime. If she wants to be an educator she can make educational apps. If she becomes a business person or a scientist she will be able to use computers to her advantage. This is what being a citizen developer is all about.

Oleg Dulin is a Big Data software engineer and consultant in the New York City area.

In 1997 Oleg co-founded Clarkson University Linux Users Group. This group was influential in bringing awareness of open-source to Clarkson, and later morphed into what now is a dedicated lab and curriculum called Clarkson Open Source Institute. While at Clarkson, Oleg advocated on behalf of open-source and Linux and community and helped with construction of Clarkson’s first open-source high-performance computing cluster called “The North Country.”

While at IBM T. J. Watson Research Center in 1999-2000 Oleg co-authored a paper on federated information systems that was presented at Engineering of Federated Information Systems (EFIS) conference in 2000. This R&D project involved building a proof-of-concept federated IS that integrated structured (SQL) and unstructured (multi-media) data under a single set of API and user interfaces.

From 2001 to 2003 Oleg worked as a data integration consultant at a major investment bank in NYC on a web portal for private banking. This project involved aggregation of secure financial data from multiple legacy databases and presenting it in a customizable web portal.

In 2004, while working at a startup called ConfigureCode, Oleg contributed to two patent applications involving construction and semantic validation of mixed-schema XML documents. This technology was utilized in a Data Capture and Tracking System for Human Resources data integration.

From 2005 to 2011 Oleg worked at a Wall St. company (see Oleg’s LinkedIn Profile for more details) where he was instrumental in improving data quality, reducing trading errors, implementing analytics and reporting within the context of an equities order management system. The system was a 24/7 high performance computing platform that processed billions of dollars worth of trade executions daily.

From fall of 2011 to end of 2016, Oleg worked at Liquid Analytics as Cloud Platform Architect, where he was a thought leader in the implemention of a cloud-based PaaS for mobile Business Intelligence.

Presently, Oleg works at ADP Innovation Lab as Chief Architect.

The opinions expressed in this blog are those of Oleg Dulin and do not necessarily represent those of IDG Communications, Inc., its parent, subsidiary or affiliated companies.

More from this author