I used to write a lot. I had been keeping a personal blog and a technical one for years. I moved house a few times, and every time I threw away a bunch of useless stuff. Now, I have completely ditched my personal blog and have kept only a handful of posts in this blog that might still make some sense. I was reading this book from John Z. Sonmez lately and I started wondering why I no longer write.
When I started my blog back in early 2010s I was tired of fining half-baked solutions that didn’t work. The author would throw out a few random things and you were meant to stitch them together in order to get something working but then you realize they missed a big piece of work. Off to the next entry in the Google search results (I’m sure Google was a thing then). When I wrote about something I also provided fully working code with it, which was pretty good and I was getting good feedback. I pretty much stopped doing that when I joined Atlassian.
That was a fairly big shift for me I think. After joining Atlassian back in early 2014, I suddenly realized “Oh shit, this place is out of my league”. I kept my head down, learning from people around me. In the first few months I was overwhelmed with the amount of information coming from the fire hose. Once thing settled down it was interesting to see when an advanced topic came up, not only people had heard about it but they also had a few ideas. After a while this became normal to me and every time I thought about writing, a sound in my head would say “what’s the point, you’re most likely going to be wrong!”. I couldn’t risk looking like an idiot. Once or twice I wrote about the side project I was doing, and that was all. I’m going to trying something new and start writing again. I might have a different perspective that might be interesting for some people. Yeah, let’s look like an idiot.
Our workspace is full of interruption these days and it has become harder to do work that requires focus. Are you among those people who avoid the interruption by blocking some time in their calendar? How long before someone comes along and double books you? A similar story is people inviting you to a meeting while you are away on leave or dropping kids at school.
You can’t train everyone to use the ‘Find a time’ feature of Google Calendar. One solution is to auto-decline invites for that 7am meeting without you moving a finger.
The rest of this article is about Google Calendar, you may stop reading if you use something else 😉 There used to be “Automatically declining events” configuration in Labs, but it doesn’t seem to be available anymore (at least to me). However, it is still easy to do simple automation like this using “Google Apps Scripts”. Have a look here to see how it works.
I had used Apps Scripts before, so I wrote one (using this as a starting point) to do what I needed. It tracks my out of office hours and declines all the incoming invites with a polite response. Check it out here on GitHub, copy and modify it to fit your purpose. When you run it for the first time, you will need to grant access to manage your calendar and send emails as you. Set it to run every few minutes and you are all set. No more meetings when you are away.
This entry has been cross-posted in Codolution’s blog.
After recently announcing end-of-life for Relay ME, I have got a lot of responses from people who were using this app and relied on it for their business, and couldn’t find any alternatives to it. Unfortunately, or fortunately, texting is still a big thing and we don’t have a proper bridge to bring it to our online world. I was wondering if I could do something so we could keep this app working for as long as possible, given the fact that we can’t spent much time maintaining it. As a result, we have this app and its server-side components (used for OAuth flow, linking to GMail) open-sourced. You can find them on GitHub now (here, and here). You can now start contributing to this app, fix issues, and add features to it by sending pull-requests in GitHub. There will also be a public Trello board to track tasks and issues, to give visibility about what is happening in this space.
In terms of app maintenance, it will be kept alive but I don’t think any technical support can be provided at this stage. We hope that we can fix bugs and improve the app by getting help from developer community in the future.
This entry has been cross-posted in Codolution’s blog.
It was a few years ago that I started working on an Android app called Relay ME, just to learn how to write an Android app. Its aim was to forward texts as emails, and allow the user to reply to them using email.
Despite lack of proper resources it didn’t take me a lot of time to make it work. It was the time of apps with black background, if you still remember it, and expectations weren’t high. If your app just worked you were in a very good shape 😉 However, a lot of things changed while I was keeping this app alive. I did things that are now taken for granted, dealt with things that are history (ActionBarSherlock, ADT Plugin, and Google OAuth 1 for example), implemented best practices to become obsolete next year, and scrambled to fix issues caused by new releases of the platform. Creating and maintaining a mobile app requires a decent amount of effort these days, especially if there is big pile of historical baggage to carry around and technical debt to pay. The time has come for me to close this project to be able to focus on the current work at hand. The biggest take away for me was to never underestimate the time you need to spend on customer support and investigating issues.
I have already open-sources the codes for the Android app in https://github.com/codolutions/relay-me-android-studio-project. I hope it can be useful for someone who wants to do something similar to this. If you are a developer interested in maintaining Relay ME and supporting its user base on Google Play, get in touch with me at firstname.lastname@example.org. All I need from you is interest and commitment.