Sunday afternoon #APIOpsLive — building API from scratch with Viljami Kuosmanen

At the peak moment, stream had 49 participants. Real working API was built, deployed to Heroku and code was pushed to Github. Some beer, 4 hours time and comments were needed to get all working.

The idea for live coding session came from Viljami. He tossed the idea in Twitter on Saturday afternoon. APIOps community thought that this is worth testing and thus we wrote a blog post about it. Of course one reason to get interested was that focus of the session was building an API from scratch. Longer background story is available on APIOps website.

The date was set to be on the next day! APIOps community was used to get message to hackers as fast as possible. We posted information to APIOps local groups in Finland and Hungary. In addition Twitter was used to spread the word.

On Sunday afternoon at 1pm (EEST) Viljami started the show from Tammerforce (Futurice office). By the way, Futurice is the company behind spice program — open source and social impact program.

Entertaining and educational

For someone who’s not a hard core developer, it was entertaining to follow real professional to “work”. The session reminded me about pair programming. Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently. The differences were that there were dozens of observers and drivers seat was never switched.

Intense and fast paced

The session was really fast paced. For the “driver” it can be exciting but at the same time nerve wrecking. Driver is learning stuff while others are watching and some might feel anxiety and discomfort. But that did not seem to be the case with Viljami!

What was done (code in Github)

Enough talking, take a look at the results from Github!

Recording available

The recording is available in Youtube platform. Be warned that it’s about 4 hours long, contains drinking of beer, geek language and fast paced development.

Next APIOpsLive — become next driver!

At the moment we don’t know when next APIOpsLive will happen. It depends if we find eager “driver” for the session, the person ready to follow the footsteps of Viljami. What could be the topic for next session? Topics which interests community (but is not limited to):

  • From REST to GraphQL
  • GraphQL in general
  • Chatbot

Follow @APIOpsCyc and hashtag #APIOpsLive in Twitter to get the updates. If you are willing to be our next APIOpsLive driver, let us know!

Meetups coming!

You are always welcome to our traditional meetups as well. The next one is in Tampere Sept 5th. Details and RSVP from