663 karma · joined November 28, 2008
[ my public key: https://keybase.io/raamdev; my proof: https://keybase.io/raamdev/sigs/6Zr3wUvZIizNlQsaB__n4zhA_6BnB2lyVx3Ho4Jxzy4 ]
I'd say the greatest insight that I've had from writing 1,000 words every single day for nearly the past year has been that simply writing 1,000 words every single day is not enough to foster real improvement. The habit definitely helps you overcome the initial resistance that you might feel towards getting started, and if you're not already good at typing or transferring thoughts in your head into words on the screen, I'm sure it helps with that too, but there comes a point at which, if you actually want to continue growing and becoming a better writer, you need a goal other than "write every day".
For me, the act of writing something that I intend to publish, to share with others, forces me to work on the writing, to tweak it, to think about how it can be made better, to question its clarity, to question the value of what I'm sharing. If what I'm intending to share contains a story, then knowing that it's going to be shared forces me to work on storycraft, to think about how someone else is going to interpret what I wrote. None of that happens naturally when you write privately, when your only goal is to see the word counter pass 1,000.
I've found that the greatest advancements in my own writing have come when I was blogging regularly (comparing posts from one year to another makes this very obvious). Whenever I've stopped blogging regularly for long periods of time, I find that my writing stops improving, even if the overall amount of writing I'm doing on a regular basis doesn't change that much (e.g., Slack messages, comments like these, etc.).
I'm not saying that you cannot improve as a writer when you write privately, just that improvement requires working toward specific goals that you know will challenge you to improve. Write a haiku. Write a short story. Look up from your laptop, find an object, and then try to write 1,000 words describing that object in as fine detail as possible. Do the same thing with an emotion that you've felt. And if you can, share what you write. Even if others don't give you feedback, the very knowledge that somebody, somewhere, will likely be judging your writing will cause you to subconsciously work a little harder to write better, to rewrite and to edit (which is the work that actually produces good writing).
Do you have any advice for someone wanting to become a firefighter? Or any resources that you can point me to?
I've been a solo dev for nearly a decade (8 years) and I found that sometimes it makes complete sense to pay for an office. Before my daughter was born, I was able to work from almost anywhere: noisy cafes, at home, the library, etc. But after she was born it was like my brain needed a space away from home where I could close a door and have a room all to myself, a place where I couldn't hear family sounds or be within walking distance of anyone I knew. I tried cafes and libraries but, oddly, they no longer worked for me—the noise and the people walking by suddenly became a huge distraction. I couldn't focus. I decided to rent a tiny artist studio for $350/mo that I found on CraigsList and it was the best $350 that I spent each month in terms of direct impact on my ability to get work done.
On top of the skeleton we add muscles and tissues and everything else, with the muscles doing the vast majority of the supporting work for the skeleton, i.e., for the most part, the muscles (and tendons) dictate the effective range of motion, i.e., what the skeleton is currently possible of doing. But muscles can be stretched and lengthened, or they can be neglected and become stiff like an old rubber band (e.g., from sitting in the same position for years on end). Stiff muscles restrict range of motion, preventing the skeleton (which, without the muscles, would be fully capable of achieving its design range of motion) from achieving the full range of motion.
Are we all built to some universal specification? That depends on how you define "built" and how you define "universal". Our cells "build us" and our DNA defines a specification. Humans do follow a general standard: between 4.5-6.5 feet tall, two legs, two arms, one head, bipedal motion, etc. There are no 3-foot, 8-arm humans (like an octopus) and no humans with a 8-foot nose (like an elephant).
There are plenty of factors that can affect what range of motion each of us will be able to achieve, including injuries, age, and lifestyle (you're not going to become a world-class runner sitting at a computer for 12 hours a day 7 days a week), but if you're a relatively healthy 20-50 year old, and you put in the time required, you can go from being extremely stiff and inflexible to doing splits and backflips.
The first part of Pain Free explains how muscular imbalances form and, most insightful to me, how every human body has the same design range of motion (with a few exceptions due to birth defects or disease), that is every human body is designed to have the same range of motion but muscular imbalances formed as the result of specific repeated activities (or lack of activity) impede that design range of motion. All of the exercises in the Egoscue Method require no special equipment, only simple things like a chair or a wall (which further convinced me that it's not a fad out to sell something). Highly recommend reading these books if you're interested in this topic.
1. https://www.amazon.com/Pain-Free-Revolutionary-Stopping-Chro...
2. https://www.amazon.com/Pain-Free-Your-PC-Computer/dp/0553380...
What I'm realizing is that it takes active participation and interest in indentifying things to really learn their names and their histories, not just a passing interest.
The Cornell Lab of Ornithology has a site [1] and an app that is amazing for identifying birds. My favorite feature is how it also lists birds that are similar, which makes it a lot easier to find the specific bird you're looking for. I then compare visual information with the auditory information of the birds calls to make a concrete identification.
My problem hasn't been where to backup photos but how the heck to manage (and make use of) tens of thousands of photos. I mean, 50 years from now when each of us has several hundred thousand photos, what exactly are we going to do with them all? And our children and grandchildren? Those are going to be pretty big (and ever-increasing) photo albums. We need better ways of managing and making use of them. Apple has made good progress here with Moments and facial recognition and grouping by location, but all of that is siloed in Apple's infrastructure.
That's the anniversary of the first human spaceflight, celebrated as Yuri's Night (and also, awesomely, my birthday):
> Yuri's Night is named for the first human to launch into space, Yuri Gagarin, who flew the Vostok 1 spaceship on April 12, 1961.
My daughter is three years old and for the past year or so, whenever she becomes frustrated that she can't do something—whistle, pronounce a word, build a lego set, draw a letter—I calm her down and remind her that not being able to do it is part of learning how to do it. I often use the example of how she didn't always know how to walk or talk, that she failed lots of times but she tried and tried and tried and eventually she got it, that after falling down so many times now she's running around the room and talking non-stop.
I've been blown away by how that reframing of difficulty has made her seemingly unstoppable. Sure, she still gets frustrated and overwhelmed, but when she starts whistling—full on whistling at three years old—and she tells me, "Daddy! I tried and tried and tried and eventually I got it!", I can't help but think that there's something to this. When she doesn't know I'm watching, I've observed that she seems a lot more determined to do things even when she's repeatedly failing—she doesn't give up as quickly as she did (often quickly followed by a tantrum) before I started explaining to her that learning requires challenge.
If that's the case, then wouldn't it just take 48 customers to a given table (who don't request water) to start saving water?
While it's awesome making a living working on open-source software, the business side of things is no longer fun or challenging for me, so I'm in the process of transitioning to something else, namely more of what I love: writing and publishing.
- I use the Drafts app [1], which has a incredibly powerful feature that lets you create custom commands that include a series of steps, such as "Append to /refile.org file in Dropbox", which I have setup as a "Save to Journal" command
- I have a TextExpander snippet that includes the proper Org-Mode format for an entry, complete with a the date and tags and even a default entry title all filled in. All I do is type "Jjj" inside Drafts and I'm ready to start typing my journal entry.
To write a journal entry from my mobile device:
- I launch Drafts, type my TextExpander abbreviation ("Jjj") to fill in the Org-Mode template, then just start typing my journal entry.
- When I'm done writing my journal entry, I hit the "Save to Journal" action in Drafts, which appends that entry to my refile.org file on Dropbox.
- Once a week or so I open the refile.org inside Emacs and for each entry I run a custom function [2] that refiles that entry into my main journal-2017.org file. The function properly files the entry into the right spot in the datetree. Processing my refile.org file literally takes a few seconds, as I have that function bound to a key that I just run with the cursor over each entry.
I've been using this process for a few years now and it's incredibly easy and reliable, not to mention completely free of any proprietary data formats, which is exactly what I wanted for journaling. I'm using a similar process (Drafts app + TextExpander + Dropbox) to make Ledger CLI [3] entries from my iPhone very easy, so that I can keep my financial ledger up-to-date when I'm out.
[1] http://agiletortoise.com/drafts/
[2] https://github.com/raamdev/dotfiles/blob/master/emacs.d/conf...
I've read Stephen King's On Writing and several other books on novel writing and as a programmer what I really liked about The Story Grid was its analytical approach to storytelling, as opposed to a more emotional, intuitive, "just keep writing and eventually the good stuff will come" approach.
I don't follow GTD exactly the way David presents it in the book, but that's just the thing: What I learned from the book was not a specific method, but how to think about task management in a way that makes sense given the limited capacity of my brain to remember a large number of transitory things.
I've used Carbon Copy Cloner (a glorified rsync + a great UI) for 5+ years and I've survived no less than two total disk failures. The best part is that CCC makes my full-disk backups bootable, so I can literally plug in my USB drive (or my 256GB SD Card--yes, I do full-disk backups to SD cards) and boot my entire laptop directly from the external drive, bypassing my (possibly defunct) internal disk. That allows me to continue working while I wait to get my laptop replaced.
When the new laptop arrives, I install CCC and do the imaging in reverse, copying the external disk to my new Mac. Then I reboot and my laptop is back to the way it was the last time I used it. (This depends on replacing my old laptop with a new one using the same hardware, but that's not difficult if I stay within a few years of the latest hardware.)