Skip to main content

Disadvantages of working remote

Just ranting it out loud, I am working remote for the past two years for a startup and there are many advantages of working remote but there are many disadvantages also.

  • Its hard to chase people over phone. As people wont pick up the call or they wont reply to Instant Messages. So you are stuck in your chain of thoughts cursing the monitor.
  • You miss the coffee talk.
  • You miss what's going on in the office and really dont know whats going in the company.
  • In meetings you could be writing code and its easy to get distracted over phone.
  • Some people prefer to chat over talk and thats a pain because you already miss the social connection and typing is always a pain.
  • You miss all company dinners and lunches.
  • Because you save time on travel you tend to overwork.
  • Worse if you are working in a different timezone then people would disturb you off hours.
  • Lots of time is spent in trying to screen share or do go to meeting.
  • People will prefer to talk to person in house and unless you are a rockstar and only you can deliver the feature mostly people will prefer in house person.
  • Lots of things will get discussed in adhoc passageway meeting and you would miss all of that.
  • Dealing with HR is a pain. As you are remote you dont have the luxary of walking into their cube and getting your work done. I am literally screwed on every work that needs to flow through HR. Communicating with them on email leads to frustration and all you can do is curse your monitor.
Also check my post on Advantages of working remote

Comments

  1. Kalpesh, I understand that VERY good, I've been working in such mode for 3.5 years with timezone offset 9-10 hours.

    Last half of year of my working remotely I ended up almost completely shifted to the timezone most of the people work, which meant for me - working from 1-2pm till over-midnight pretty much all the time.

    I think I worked remotely more than enough in my life so far :) Now I'm enjoying coming to the office and talking to people.

    ReplyDelete

Post a Comment

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 Erlang Download Rabbit MQ Server Download Rabbit MQ Java client jars Compile 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.se...

Jersey streaming binary data

In the previous post I showed how you can post binary data to a jersey REST api. You can also use Jersey to serve files, although its better done by apache or nginx but sometimes you might want to serve thumbnails stored in a database out of a service and put varnish in front of the REST api to cache the thumbnails. This is just a demonstration of using jersey to serve binary data in streaming fashion. @Path("/download-service") public class DownaloadService extends SecureRestService { private static final AppLogger logger = AppLogger.getLogger(DownaloadService.class); @POST @Produces(MediaType.APPLICATION_OCTET_STREAM) public StreamingOutput getThumbnail( @FormParam("securityKey") final String securityKey, @FormParam("guid") final String guid) throws JSONException { return new StreamingOutput() { @Override public void write(OutputStream out) throws IOException { try { if (!isAuthorized(securityKey)) { response.sendErro...

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...