Focused work

-

I have seen many complain about working too hard. They complain about not able to spend time with family.
Most of them have these complaints:

  • No work life balance.
  • Too many distractions at work.
  • Lot of time spent on meetings.
  • Working over time.
  • ....
Most of the time issue is focus on work. If you go through this blog it highlights how people spend their time. Data in the link is collected by a tool called RescueTime. https://www.rescuetime.com/

This tool continuosly checks what you are doing. It classifies the work as productive and non productive. It measures how much time you spend in the computer and on what you spend the time. 

If you want to improve your life and your work probably you can use this tool. They do provide a free version. You will know immediately how much of time you are spending on actual work. If you are complaining about spending lot of time at work then probably you can use the data collected by this tool to ask a raise with your manager. If tool tells you are spending lot of time on entertainment it is time to shift gears and start working.

Either way a tool which measures your work will help you improve your life.  

Comments

Post a Comment

Popular posts from this blog

Greedy computing with API

-
Image
 We all know computing resources have a cost. Memory, long term storage, transportation and computing all have their own costs. There are lot of scenarios where your API end point won't be able to respond in time. These are scenarios where you need to use more resources to provide a response. Let us be greedy with our resources and explore different patterns which can solve this. Polling  This is a commonly used pattern where the caller initiates a process. Then keeps on checking if the process is complete. If the process is complete then the caller reads the data needed.  This is a good pattern when both systems are part of the same organization. At least developers of caller and callee should be able to discuss this implementation.  Call back This is an improvement over polling pattern. Here the caller supplies a call back URL to the long running process. Once the process is complete it calls the callback URL and informs the caller that process results are availabl...
Read more

ChatGPT for cavemen

-
Image
I heard a lot about ChatGPT and thought to come out of my cave to find out what the hype is about. Is it going to eat all my lunch or eat me for lunch?  Like any product I gave it all my details and signed up. I asked it about quantum computing an it gave some answer. So far so good. Next day I wanted to check its blogging skills. So I opened chatGPT and I got this . I checked throughout the day and it is still down. So it won’t eat me till it is fed few more servers.  Continuing after it was up.  I asked it to write a blog about itself. Here is what was generated by chatGPT.
Read more

Event driven architecture for micro services

-
This is a work in progress. I am designing an event driven architecture to be used in systems using micro services. Micro service architecture is popular because it solves few problems in development process. While it solves some problems it also brings in new problems to the table. Bad designs impact micro services harder than monoliths. But this is thought is for another time.  How micro services talk to each other. In a monolith you have one gigantic database, or you can easily call another component to process the information. In a microservice you can use a Que (or event bus) to pass the information. This is the problem I want to discuss. Main issue with que is it is not designed for this scenario. There are few products which give a good solution by providing a subscription-based approach. But these are large implementations. Using these is similar to bringing an excavator to plant a sapling in your garden. Yes, many people go with using these large implementations to resolve...
Read more