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
Event page link / Meetup group
- From the folks at Amazon
- AWS Activate
- A program to provide resources to startups: from free tier usage, labs, webinars, support and AWS credit
- Self-Starter Package: for any startups
- Portfolio Package: for startups in select accelerators or seed funds. Will be ‘audited’ by Amazon and will be given much better benefits vs Self-Start Package
Cloud Computing in Africa
- From Thomas Shaw, the tech man behind
- Providing unique perspectives with regards to security, reliability, scalability of AWS especially compared to local hosting.
- AWS management console for the iPhone
- In development by Rob Amos @bok_
28th July 2014 – Introduction to Chef held at Sacon Group for the Chef Meetup group
Chef and Chef DK: The Chef Development Kit
- by Michael Ducy (@mfdii), a Global Partner Evangelist at Chef
- PDF slides
- Chef essentially enables the “infrastructure as code” devops movement
- Versionable, testable, and repeatable as application code
- Relies on reusable definitions known as recipes to automate infrastructure tasks
- Recipes use building blocks called resources (e.g. file / template / package)
- Recipes are stored in cookbooks
- A cookbook is the fundamental unit of configuration and policy distribution
- Chef server stores your recipes as well as other configuration data
- Chef client is installed on each node in your network
- Chef client periodically polls the Chef server for new configurations and applies if necessary
- Chef DK
- A component of Chef to enable organizations to develop internal best practices for Cookbook development and testing
- A curated set of open source tools for Cookbook development
- Download at http://downloads.getchef.com/chef-dk
- chef – a new command to make development easier
- Berkshelf – automatically resolve cookbook dependencies
- Test Kitchen – framework for integration testing
- ChefSpec – unit testing of Chef cookbooks
- Food Critic – linting tool for Chef cookbooks
- Standard Chef tools – knife, chef-zero, ohai, chef-client
- Other Links
24th July 2014 MelbDjango Hackfest held at Common Code and hosted by Curtis Maloney for the MelbDjango Meetup group.
Mostly being newbies and with some people interested in testing, Curtis started off showcasing his new Django Classy Settings before covering some topics on testing and other miscellany
TAkeaways / Links from the night