The call went out weeks before attendees started arriving in Burlingame for the event:
“If you enjoy a challenge, competition, spending time with your NonStop community members, beer, pizza, chip and dip, AND taking home cash prizes, sign up now!”
Since the word ‘Hackathon’ has ‘Hack’ as a root, some attendees immediately wondered if we were encouraging people to break into a NonStop Server. Instead, the word comes from “hack” and “marathon,” where “hack” is used in the sense of exploratory programming. Dating well before the origins of computing all the way back to the 1200s, where it meant “cut with heavy blows in an irregular or random fashion,” not to its scarier meaning as a reference to computer security. In the spirit of the 1960s at MIT and at TBC, the word is intended to encourage a design-sprint that creates a functioning product by the end of the event. (If you want to know more, here is Wikipedia’s take on it.
No hackathon would be complete without a fair number of technical challenges. It was entirely appropriate that everyone pulled together in a spirit of cooperation to overcome the first obstacles. In the end, with a smoothness that embodied the spirit of the hack, the event was considered a success. The official goal was to build a web server that answers HTTP requests with a web page or REST API response, while being unique, inventive, and open. We hoped to demonstrate how easy it is to port an app over to the NonStop for its benefits (fault tolerance, scalability, etc.).
The teams were:
- Team ‘NoName,’ with Jonathon Ziegler and Vuk PetrovicFrom Vuk Petrovic: Our team struggled to get up and running between getting on the proper Wi-Fi, the download and installation of the correct VPN software, connecting to the NonStop, etc. At one point, Jonathan’s computer hit the (Microsoft) “Blue Screen of Death” and then failed to start. We basically just gave up on Jonathan’s PC at that point. (It eventually made a comeback.)
I found myself in a pickle at this point:
- I could not use Python to create the web server, since I could not install anything with Pip on this NonStop. (I could not install the Python web server package.)
- We could not find a simple, dependency-free C/C++ web server library that we could port to the NonStop, build, and run within three hours.
- We could not download, install, configure, and run Eclipse for Java, Spring, and the Spring Boot framework all within three hours, AND have enough time to re-learn Java, learn Spring Boot from scratch, and know enough to build a server that does anything useful.
We had almost finished, when I ran into an issue where my SimpleHTTPServer command started hanging badly, making my terminal unresponsive. We could not debug that in time, and the Hackathon ended. We won the “Best Teamwork” category.
- Team ‘Can’t-tell-ya,’ with Rob Lesan and Anthony Duffus
We recruited a duo of seasoned NonStop architects, (Randall Becker and Bill Honaker), to mentor and judge the competition, and ultimately choose the winners. Each team left with a cash prize, and all of the participants received amazing commemorative Hackathon t-shirts!
The NonStop Under 40 SIG, which conceived and hosted the Hackathon, considered the event a great success, and is already planning an improved event at next year’s TBC. Please send us your suggestions and ideas for 2020!
How useful was this post?
Click on a star to rate it!
Average rating / 5. Vote count:
No votes so far! Be the first to rate this post.