Skip to main content

Ducks In A Row

I'm trying to "get all my ducks in a row" as the saying goes. I've got a lot of standing projects, some personal and some professional and many straddling a line between those two.

As part of the process of figuring out what I need to do, I need to figure out what I want to do. I've got a broad range of things demanding my time and a broader range of things I'm wishing I could put my time to. There simply isn't enough of me to go around.

I see so many others around and they seem so much more productive than me. Where do you find the time? How do you do it? I've obviously got some missing element I need to find.

The plan at hand is a simple set of actions.

  • Track my time 24 hours a day. This keeps me focused, especially for non-billable hours.
  • Decide on each standing project if I can do anything. If not now, archive it. If never, delete it.
  • Write every morning. Write more whenever I have something on my mind.
There are things I wish I had time for that I never will. I never sketch any more and I haven't picked up the guitar in a decade. I'll focus on what I can accomplish so that I don't have time to feel bad about the things I cannot accomplish.

Comments

Little tip. You are focusing on the 'what'. That is fine, but its a level 1 prioritization of things. The things you need for todays tasks.

If you want to get to level 2 kind of productivity then you need to be asking 'who' in two directions. Who is demanding tasks of me and is their request superior to other who's on my plate. The second part of the equation is who could some of the requests be delegated to if any? Be sure to include yourself in the matrix of who in the prioritzation.

We go through life with constant demands to get-things-done. Much of the world finds that just perfect. But those that seem more productive are not asking how to be more productive but who to be more productive with.

Find the who.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…