Look at him! 3 years old baby which is growing and growing and growing! Celebrating birthdays of such tools is a good idea in general. Why? Because attendees of such events are usually students or people not familiar (much) with technology. I have participated at Docker Birthday #3 at RMIT (Ho Chi Minh City, Vietnam) as mentor and what I’d say: local students need MOAR Docker. Students are smart and eager to learn.
Finally got somewhere big and IT. Welcome to FOSS Asia IT conference that took place at Singapore at 18-20th of March. What did I see there? Well, a lot of people willing to learn. Some of the talks were really mindblowing, but majority of them were average. It doesn’t mean they were bad, they were not hardcore, meaning no crazy hacks or benchmarks or extremely low-level code surgery. But they were educating and very useful for students and those who wants to take a look at some other technology, tool or idea.
OK, what do we have here? A mobile application written with Cordova for 2 platforms: iOS and Android. I’m lazy, I don’t want to check that all critical functionality works as expected after each release. In 2 platforms. And I don’t want anyone to do that, because manual work is stupid in IT. So I need a proper tool to test both applications automatically, so I have enought free time to explore the world around me :) TL;DR Decided to go with Calabash at the end.
Found a nice coworking space in Nha Trang, Vietnam: LivinCollective. Check the map. The place is comfortable, the hosts are really friendly. Working there is free, but it would be great if you buy something (juice or coffee or something to eat) to help run the place. WiFi there was the fastest I had in Nha Trang :) Some pictures of the place:
Everybody knows that using an API with no documentation is like walking on a minefield with no map. In SeeSaw Labs we build APIs and we’re doing our best to provide our customers with such a map :) But how to write a documentation? Here are 3 general approaches. 1. Do it manually Sounds obvious, right? You write the code, you write documentation for it separately. Sounds easy. Now add several dozens of API endpoints and a dozen of developers into this cocktail.
