Skip to main content

Avoiding Burnout

Burnout is very common in startup and it hits you more often when you are at the same startup for 7+ years. Much of burnout is felt when you are working hard but progress is slow and you have high expectations of yourself and the team. I read this excellent article http://andrewdumont.me/avoiding-burnout/ and it felt almost Deja vu to me.  I work from home so it hits even hard to me as I have less people to share it with. Here are the ways I have been trying to curtail burnout and hope it help others too:

  1. Workplace:Keep your workplace organized and stick to a routine.  I have an office room at home and I am in work mode when I am in that office.
  2. Morning:Keep 1 hour in mornings on something outside work. I read a lot in morning and don't come online or check emails until that 1 hour is done.
  3. Workout: rain, heat or winter, I try to walk for 30 min in afternoon as much as possible. This gives you some time for meta thinking and de stresses you from the morning chaos. Many solutions to tough problems come on this walk. I don’t hear music or podcast on this, I tried but then it felt like more work, I avoid it.
  4. Silence room:Do some grunt work on weekends, be it doing vaccum in house or mowing your lawn, you need 1-2 hours of "Your own time" withot distractions.
  5. Email: fight this monster, I sent most notifications to trash and assume people will call me if they need me. Also when startup becomes big people will copy you on tons of emails so choose which battles are worth fighting and which aren’t.
  6. Hipchat: Avoid this also if you are on creator schedule, I am now a days trying to stick to checking it only if I am waiting for build to finish or have some time before meetings.
  7. Motivation: Set some tough projects for you and work on them. Even if you are making slow progress you should finish it by making some progress every week.
  8. Coding: I like coding so now I have reserved calendar time of 3 hours a day to it.  This is by far the best way for avoiding burnout for me.
  9. Buddy: Have a buddy who you can share some things, may be you will just vent out and he will also but it would de stress you.
  10. Vacations: I try to take 1 big vacation(2weeks)  every year and try to go to national parks for camping where there is no connectivity so you are really unplugged.
  11. HQ visit: this recharges me as I again get some more brainstorming on things outside my purview.
  12. Hobby: I recently picked up photography and I do read and practice that.
  13. Humans: I feel more burnout when I need to make something live and there are many humans in the process chain that makes things slow, things that should take 1 week takes months and then you are burned out as your baby isn’t live.  I try to automate and avoid humans in the process as much as possible. Its unavoidable but if you are lazy and think hard then its doable in many cases.

Comments

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…