We are getting more and more busy each day without accomplishing much. When we are not busy, we get distracted by other people, devices and even cats on the internet. We end up feeling exhausted at the end of the day without getting nearer to our life long goals, without finishing off our side projects and without writing as much as we should. We only have 24 hours a day and It is important that we spend them on the tasks that really matter. There are many productivity tools out there which can help you get more things done, but I found the tool call Kanbanflow to be simple and very effective.
Kanbanflow combines the ideas of Pomodoro™ technique and Kanban board. It helps me visualize the important tasks I need to carry out during the week and focus on each tasks by using Pomodoro™ technique. The default Kanbanflow board has 4 columns named __ To-do, Do Today, In Progress and Done. You can add or remove columns as you like. Kanban board helps you manage the tasks visually. Built in Pomodoro™ timer allows you to focus on current task and track the time spending on it. Your productivity can be measured not only by the tasks you have completed but also by how many Pomodoro™ periods you have done for the day. You can also review how long did it take for a task to finish.
The simplest way to use Kanbanflow is to create a list of important tasks in To-do column. Each morning, plan your day by assigning the tasks from To-do column into Do today column. Move the task you are going to do next to In progress column. Use Pomodoro™ timer to work on them. When you finish a task, move it into Done column. If you like to plan for the week, add columns for each day of the week and put tasks in there.
I am a very happy user of this tool now and I can plan and execute my important tasks better than before. Do give it a try if you haven’t done so.
Today when I turned on my Z800 Workstation PC at work, it won’t start. There was no beeps, no display and no warning, just a blank screen staring at me while the power was on and the fans were running inside. I tried turning on and off the power a few times with no luck.
There are regular data processing tasks I need to run for the day and they can’t wait until the pc is repaired. Usually it takes a few weeks just to repair a pc in my company. It seemed like I am in deep shit and it’s only Monday! Instead of panicking, I simply logged in to another computer in the office and restored the data required for the project I am working on. It took about 5 minutes to restore and I started working on my scheduled tasks for the day.
This is all possible thanks to CrashPlan from code42. It is a great backup software with very useful features. It is very easy to install, setup and configure. Please go to the product web page https://www.code42.com/crashplan/ for more details.
The best feature I like and which saved me big time today is the ability to back up to your friends/coworkers computers. They provide paid service – cloud back up plan for unlimited storage space. I just use free feature which allows me to backup to another computer. And it worked great and left me with very satisfying experience. I would recommend this hassle free software if you are not already using anything yet.
When working in ArcMap, one would encounter all kinds of wired-ass problems for all kinds of unknown reasons. One of them is when you are working on a map document for a while, and out of the blue, unable to open the attribute table of a layer or layers in the document.
The error usually occurs when you right click on a layer and click “Open attribute table”. Instead of showing the attribute table, ArcMap displays you the following message and an empty attribute table. The strange thing is you still can select the rows in the attribute table and you can see how many rows in the table as well. It is just that all the rows are now empty.
There are a few ways to solve this problem. One easy way, which worked for me, is to export out the problematic layer to a new geodatabase and then import it back to your map document. I hope this is helpful to those who encounters similar problem using ArcMap.