4 ms·
1. Keyboard shortcuts. From Win-plus-number-keys to Autohotkey-defined macros. Makes the time between "think of task" and "accomplish task" instantaneous. 2. N
by Noumenon72 9y ago
1. Keyboard shortcuts. From Win-plus-number-keys to Autohotkey-defined macros. Makes the time between "think of task" and "accomplish task" instantaneous.
2. Notes. From "what was the answer to this bug last time" to "how do you toString an Enumeration?" Increases your memory far beyond human proportions.
3. Abstractifying problems. Don't just google error message, google "Tomcat having trouble compiling JSPs." Don't just be annoyed by scrolling, google "DBVisualizer select database shortcut".
4. Documentation. When you write down "[This class] provides X" and "[This function] accomplishes X" you start to make classes that actually make sense and have a single purpose. When you understand something once and write that down, you don't have to reconstruct your understanding again.
5. Probably taking some time to make your coworkers feel validated and help them out with their own goals.
- riezebos 9y agoAre your (not sensitive) AutoHotkey scripts available on Github or something? Maybe others could learn some neat tricks.
- matt_s 9y ago> 3. Notes This also works in code. Commenting why something was done a certain way, and think of yourself 6 months from now when you have to fix a bug but don't remember what the thing was supposed to do.