One of my biggest producitity drains is seamlessly switching to different applications. Windows doesn’t have good native ways to do this. Especially when I have 10 or 20 different things open. A picture is worth 1000 words, so take a look at my work environment:
Are you juggling between dozens of apps on limited screen space? Or find yourself typing the same thing over? Looking for the same code/text/unicode/emoji to copy+paste? Find yourself writing typos in your emails, data entry, or programming? Or doing the same repetitive tasks all the time?
Then you need a macro program.
This is my review on it broken down into 2 parts,
Do unit tests take forever for you to write? Here's a macro to automate those tasks.
Whenever I program,I try and write that code as clean as possible. I try to enforce practices such as stylized guides and enforce good github project guidelines as well. And program daily to practice these standards
However, this is not always the case. Sometimes I’ll program in a way that reflects that language or framework, (e.g. writing python in a pythonistic way). Occasionally I’ll have to touch a tool that I’d rather not use (e.g. Autohotkey) that has inconsistent syntax. But there’s no other good alternatives for adding complex windows shortcut hotkeys
DirectoryOpus is becoming one of my newest and favorite tools. Its essentially a windows file explorer on steroids. There’s no other Windows, Mac or Linux equivalent that comes close to the number of features it offers. The only problem with directoryOpus is it has a rather steep learning curve, since there’s so many settings. Its been already a year since I’ve used it, and I still find myself going to its forum to ask beginner level questions.
Its year 2018 and I still haven’t reflected upon all the things I achieved last year, or things I want to do this year. So I will do it now. After digging through all my profiles (stackoverflow, github, bookmarks, projects, photos on phone, workout log, and journal log), this is a comprised list of things I achieved, and what things I want to finish in the future
Building high quality anki flash cards is sometimes difficult and time consuming. When I first started when flash cards, I always asked myself when and why I should make a card. Sometimes it was a spur of the moment decision. Some cards didn’t last very long, or I had to mark them down because they were poorly worded. Other times those cards didn’t follow supermemos 20 rules, which I consider to be a standard goldline practice for making any flash cards for long term memory retention, regardless of subject. Sometimes I make a card which I found interesting but really had no application to any goal I am striving to achieve.