Skip to main content

Using email to manage work queue can be deceptive

I loathe on emails that have been replied more than 5-6 times. I am sometimes copied on emails where there are 20 replies. Today I have an email about post commit reviews which has 20 replies, Grrr.  I procrastinated whole day to read it and looks like I am not goint to read it today.

Problem with 20+replies email is that by the time you end up reading all 20 of them you have lost context of what is the final picture.

I saw this infographic from 2012 http://mashable.com/2012/11/27/email-stats-infographic/  that 28% of time is spent on reading emails.  I think for me its may be 50% or more as I work from home and most communication is over emails except very few which happens  over skype or phone calls.


Would love to explore tools to save time.  I found 2 new tools in gmail so far, "Canned Response" and "Mark as Read" button, lets see if it helps.

For e.g. I would be copied on email "23.7.3 CL- 120157 on all Appnodes and EOS nodes in SJC, AVL and AM2", now I don’t want to delete it as I may need it in case there is an issue in prod. But I also want to move it out of my Unread queue as I am using email to manage my work queue. I am hoping now I don’t need to open email and mark it as read, a one click would do it.

Also thinking of adding more filters to just sweep some emails I care less to trash as other members are taking care of dealing with them.



But this got me into thinking should I use email to manage my work queue, I used to use a task list before but problem was that some items would never get done. Then I switched to gmail and all pending work would be in emails  marked as Unread, I would have read it but if any action is required I would mark it as Unread.  I am almost at a tipping point because it takes me almost from 9-4 to talk to my team and deplete the email queue. That leaves sometimes 1 hour or sometimes 2 hours to write any kind of code. Sometimes it feels like I got rid of all emails that came to me in the day but I got nothing productive done. So was I just pretending to work?

Also gmail is deceptive, when I come in morning it shows me I have 76 unread emails but daily there are many emails that have between 3-5 replies and some are suckers with 10+ replies. So really its almost 150+emails to deal with and this is after sending lot of emails to trash directly.

Need to find some other way to manage the work queue, I had  tried using JIRA but that also hasn’t fared well.


Comments

  1. I'm testing Todoist now. It has a nice integration with Gmail that allows you to create to-do items based on (and linking to) an email thread, optionally set dates/projects/labels etc, and archive then original email.

    ReplyDelete
    Replies
    1. My problem is not with task management, for that I can use Mailbox or notes or any other way, problem is sheer amounts of emails to read and reply that at the end of the day dont feel like I achieved anything. I am still a programmer at heart and needs something tangible to produce at end of the day.

      I am thinking of may be moving to no email days.

      Delete

Post a Comment

Popular posts from this blog

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...