As I have written before, I’ve used just about every note solution around. Unfortunately I haven’t found a magic bullet (yet). This post is really an exploration into the pros and cons for my own personal workflow and this the things I find important when managing notes. Hopefully after doing this exploration I can actually settle on one platform for the long haul and stop procrastinating by switching note platforms and writing blog posts about it.
I keep my personal nodes in a bunch of Markdown files inside a Dropbox folder. I’ve used just about every note-taking app there is and ended up settling on this system. It’s served me really well so far.
I have one note at the top level called
scratch.md that I use for quickly writing things down when I’m in a hurry. I decided to speed this up even more with this little shell alias:
As part of my regular annual website refresh, I decided to take a pretty drastic step and move from WordPress to a static site generator called Hugo. I’ve kept my WordPress install continually up to date since early 2009 and it served me well, but I needed a change. I also went back through the archives and culled all my old blog posts - I only kept the most trafficked and the ones that Future Will might want to reference.
Something I noticed as a general trend with modern technology (especially in mobile development) is a trend away from shiny, glossy UI elements like icons and buttons to a more flat, conservative style.
Here’s a really interesting discussion I found about the subject on the UX stackexchange site http://ux.stackexchange.com/questions/35576/what-explains-the-current-shift-from-glossy-uis-to-matte-uis Looks like the main culprits would be Windows and Android, while Apple seems to be sticking with what they know (for iOS at least).
tl;dr - It depends.
Pair programming is defined as the act of two programmers working at one workstation on one task at a time. One programmer enters the code (the driver), leaving the other programmer free to audit the code in real time as it’s being written (the observer). The idea behind it is simple: two heads are better than one. When someone else is watching you, your proclivity for stupid typos and silly programmatic errors is significantly less (forgetting semicolons for example).