Productivity tips (former title: Removing distractions)

Removing distractions especially at work can boost your productivity, so they say. I gathered some tips from other blogs and added some more to improve your distraction-freeness productivity.

Close all applications and tabs you don't need. I cannot work when I see 30 windows and always have to think where to click. I have an average number of 2 windows in the taskbar and I am a programmer. I find myself periodically killing windows/tabs, when their numbers exceed 5.

Have a zero mailbox. I have it empty for 10 years now and I still live happily. Move your e-mail from your inbox when you're done with it. Try to read each of your e-mails just once. Take the wanted action (reply, fix something, etc.) and try to immediately decide if you will delete it or archive it.

Have a quite workplace. If you must listen to music, many people find it better to listen to instrumental music only (no vocals).

Clear your desk. I'm a minimalist, so I like my desk clean. I think this could also affect my productivity, but I don't really know.

Turn off on your IM. Or at least turn off the notification of the new messages. Or at least go invisible. I was wrong with turning off this one. Having worked in teams with other people, after some years of experience, I prefer to improve overall team productivity instead of my individual one. That means replying to all questions as soon as possible.

Turn off auto-check on e-mail. You should check for your e-mail once or twice a day. If you have to look on it more, decrease the frequency of auto-checker checks. Auto-checks of e-mail give false sense of urgency. Same as above.

Filter through your Don't use subscriptions. All the kinds. Clean RSS feeds, e-mail subscriptions, etc. After some years, I reconsidered, and I don't subscribe to anything anymore. Life is too short. If I want to learn something, I prefer to actively look for it myself.

Clean your computer desktop. There should be no icon, that you don't want to click multiple times per workday. Now I am on three.

Comments

Post a Comment

Popular posts from this blog

Notes about the Clean Architecture book

The first look into the contents of the book was a bit scary. Some of these things were already explained in Robert Martin's previous books. Then I found out they are explained from a different (software architect's) perspective. Overall, I liked this book better than Clean Coder, but it was less useful for me than Clean Code book of the same author. Part I - Introduction The foreword contained two useful antipatterns: Too authoritative and rigid architecture. Speculative generality in software architecture. The main point of the preface is that not much changed for the last 50 years in software architecture. The rules of software architecture are the same regardless of any variable (time, type of project, ...). When you get the architecture of the software right, you magically don't need horde of programmers maintaining it. Chapter 1 - What is Design and Architecture? There is no difference between software design and architecture. There is a continuum of...
Read more

Notes about the Building Microservices

These are notes for my future self about Sam Newman's book, Building Microservices 2nd edition.  Preface Microservices are an approach to distributed applications that use finely-grained services and change, deploy and release them independently. Microservices have become the default go-to architecture when designing system, which Newman finds hard to justify #surprised and want to share his view on why. Foundation Chapter 1 - What are Microservices? Microservices are independently releasable services modeled around a business domain . They are kind of SOA, but the one which is opinionated about how service boundaries should be drawn and where independent deployability is the key. Microservices should implement information hiding and expose their API in some way, e.g. via REST/JSON API or by emitting events. They should have their own database schema. To highlight that the services are as independent as possible, Newman draws them as hexagons, a homage to Alistair Cockburn's H...
Read more

Notes about A Philosophy of Software Design

My notes about the book by John Ousterhout. It is quite a short book. Originally I made a mistake of reading just the Conclusions of the chapters but there is a lot of contents not in the Conclusions. After really reading the whole book, I started to like the Red Flags and other small pieces of hints. Chapter 2 - The Nature of Complexity Complexity is anything related to the structure of a system that makes it hard to understand or modify. Isolating complexity in a place where it will almost never be seen or touched is almost as good as removing it. There are many symptoms of complexity: Change amplification - when change requires modification in many places.  Cognitive load - how much a developer must know in order to make a change. Sometimes more code is simpler than less code because of cognitive load. Unknown unknowns - it is not obvious which places should be modified or what knowledge the developer must have to make a change. Complexity is caused by 2 things - dependencies a...
Read more