Thanks to Tru-Synergy for hosting Brunei Geek Meet #4 and thanks for all those who attended! It was a much better turn out than I expected and hope for more meetups to come!
Open Source Involvements: Experience in working on the OpenMRS CPM open source project
- People Management is essential
- there is a need to manage expectations
- High barriers of entry => great killer of enthusiasm
- Reproducible developer environments
- Project Management: list of things to work on
- It takes time
- commit 4 – 8 meetups to see where you can contribute
- nothing is too small
- Places to contribute
- OpenHatch is a non-profit dedicated to matching prospective free software contributors with communities, tools, and education. openhatch.org
- CodeTriage: receive a different open issue in your inbox every day. codetriage.com
Testing: TDD, BDD, WTH?
- TDD: Test Driven Development (Red, Green, Refactor)
- Write test (watch test fail in test suite: Red)
- Write code (to make test pass: Green
- BDD: Behaviour Driven Development
- Focuses on clear understanding of software behavior from stakeholders
- Focuses on why code should be created: thinking “from the outside in”
- Given [initial context]
- when [event occurs]
- then [ensure some outcomes]
- Unit Tests
- Testing core unit of works
- Isolated: no interaction with other systems (e.g. databases, web services)
- Integration Tests
- Test the integration between 2 different “units” / systems (e.g. your core system and the database / web service)
- Database interaction: test database or in-memory databses (H2 / SQLite)
- Functional Tests
(Note: Due to conflicting schedules we had to postpone to 12th September from the initial date of 9th)
As I’ll be in the country this coming week, I’ve scheduled a long over due Brunei Geek Meet and hope to share my experiences working on an Open Source project namely the OpenMRS CPM that is hosted weekly by ThoughtWorks.
We’re happy to have Tru Synergy hosting our meetup and hope to see any interested developers / project managers / tech enthusiasts there! The event is free and you can RSVP here.
Agenda: 7pm – 830pm
- 7:00 – 7:10: Intro
- 7:10 – 7:40: Talk #1: Open Source Involvements: Experiences from the Trenches of an Open Source Project
- 7:40 – 8:10: Talk #2: Testing: TDD BDD WTH?
- 8:10 – 8:30: Discussions
- 8:30 onwards: Discussions at the bar! (I mean some coffee place)
Open Source Involvements: Experiences from the Trenches of an Open Source Project
Tim will share his experience working on an OpenMRS module for the pass 8 months and discuss ways to get open source projects off the ground, what to expect and how to contribute to them. We can also discuss community projects for Brunei
Testing: TDD BDD WTH?
Testing is a key part in the development life cycle and can provide assurance that your code is doing what it is meant to do. We’ll explore some basics of testing referencing the OpenMRS module in the first talk
RSVP for the Brunei Geek Meet Tuesday 9th September: 7pm – 830pm
Hope to see you there!
After the last post, I gave Google yet another call and found out that there have been similar issues: getting a confirmation on the website but no emails nor courier. They set things up yet again and thankfully the courier finally came to pick up the goods on Tuesday (they came on Monday but we were out for a company lunch, and didn’t even ring my number).
So after 3 weeks, 2 emails and about 5 calls, I have finally managed to get a replacement Nexus 4 and returned my old one. That totally felt much harder than it sounds (more reason to buy from physical brick and mortar stores?)
P.S. Recorded the hold music and found out that it is “The Lighthouse and The Whaler-Untitled (This Is an Adventure)” – listen on YouTube thanks to Shazam (at first I though it couldn’t find it due to the name having “Untitled” in the name…
So after the last post, I followed up with an email to Google Support and this time there was a response within 30 minutes, with the RMA details as below (full email). Hurrah!
2 days later I got my replacement device. Double hurrah! Backed up and restored data to the new device and on to returning the old device
Packing the device on Friday 29th and re-reading these directions, I realised that I didn’t get any confirmation email nor shipping labels. Cue a another call to Google support and Google Support lady (first one I’ve spoke to, previous 2/3 calls have all been guys) says that they don’t email shipping labels to Australia and that the courier man should have it.
Courier man never came yesterday, so retried requesting another return request today and got a “Collection for given RMA Number has already been requested”. So yet another Google Support call….
After my last post on Google’s Support, I gave Google another call and thankfully William managed to further process my support ticket: he said that it was lodged and escalated but there wasn’t any updates on it.
He asked me to check my Google wallet billing and shipping address and after some verification with him, that it would be processed accordingly. He was saying something along the lines that it takes 2 days for the system to get updated after changing my billing/shipping address and it would then be processed. But alas still nothing.
Is this what customer support is meant to be? The customer having to manually follow up on things only to get things done?
So my Nexus 4 started acting up 2 weeks ago: the left section of the screen doesn’t respond to touch: essentially anything between the vertical red and blue lines is non-responsive to touch. Watch the video to see it in action.
So I called Google and they advised to do a factory reset, which I did 8 days ago, and proceeded to reply the email I got for my case (which I still have no reply as of today).
So I gave them a call the following day, which they told me that my device is still under warranty and that their “Termination Team” would get back to me. It’s been a full week since I called them and they have yet to get back to me.
A twisted idea that came to mind, is that the longer they make me wait, the more chances I have for accidentally dropping my phone and getting it cracked or something that puts it out of warranty, and thus my wanting to document my perfectly fine looking phone (i.e. not physically damaged) just in case they were to try pull this stunt if I do accidentally drop it (I am being too paranoid aren’t I?).
But anyway, Google support, where art thou? Can you please terminate me/my Nexus 4 in a good way?
P.S. If Google support is having manpower issues, I wouldn’t mind helping them out to ensure customers aren’t getting left waiting for a week without a response.
Event Page | Meetup Page | @melbcss | Github
Advanced methods for making HTML email exciting
Managing Colour Variables
Build stupid things with :checked