Thirty minutes at a time
Blog kitt decided around 23:24 on 24 October 2011 to publish this:One of the things I wonder about at the end of the day is just where my day went. I mean, I'm usually aware of every moment of the day, but at the end, I look back with confusion at how short the day was and, sometimes worse, how little I managed to accomplish.
Lately, I've been keeping track of what I eat, when I eat, my exercise: how long and what kind, my car mileage, what I spend including what kind of payment and where I spent the money, and, well, yeah, when I defecate or urinate (such big words for poop and pee!). That last one is embarrassing, but it has revealed interesting information, so I keep doing it.
In an effort to make that "I can't believe Kitt is tracking all of that information" process harder, er, more useful, I decided today to start tracking what I was doing every 30 minutes. I've wanted to do this for a while as a way to gain awareness of my day and mindfulness over my actions. I saw a website where a guy did this, every hour on the hour, and recorded it online. I found that thought fascinating and wanted to try it, but struggled over how to trigger the reminder to stop, record and reflect. That last point is important: looking backward doesn't do any good if you don't use that view to help you moving forward. So, along with recording what I was doing, I wanted to also take a moment to reflect on what I would do in the upcoming 30 minutes, and was it the best thing for me to be doing with that time.
After day one, I have to say, the results have been enlightening, if not inspiring.
08:00 out of bed 08:30 trying to clear Firefox tabs 09:00 archving and clearing Firefox tabs 09:30 reading "drupal modern theming" presentation, thinking about my projects 10:00 getting dressed 10:30 driving to t-mobile store 11:00 waiting in the t-mobile store for bill corrections 11:30 driving to warren's 12:00 leaving post office 12:30 eating lunch 13:00 talking to house contractor 13:30 driving to keith and katie's 14:00 14:30 remembered alarm, checking email 15:00 working on openphoto twitter login, distracted by twitter 15:30 openphoto login, worried about task list fragmentation 16:00 reading IRC, openphoto twitter WSOD issues 16:30 closing computer, chatting with Alex about his day 17:00 finished washing dishes 17:30 making dinner 18:00 sitting on couch, eating dinner 18:30 watching house, IMing Snook 19:00 "watching" house, working on openphoto, still trying to solve problem "the right way" 19:30 ordering a book from Amazon 20:00 couch, giving up on solving openphoto issue "right way" 20:30 couch, putzing 21:00 couch, openphoto, Snook, twitter, yeah 21:30 happy openphoto twitter login done 22:00 prep for bed 22:30 writing emails 23:00 asleep
Number one lesson learned?
I sit too much.
What else did I learn?
I spent far too much time trying to solve the OpenPhoto twitter login issue "the right way." I wanted to solve the bug, rather than just find a fix that would work for me. Part of me was frustrated by the Drupal module's owner saying, "well, this is another modules problem, so I'm just going to close this bug report," and not actually fixing the problem. I hopped on my high horse to FIX. THAT. BUG. DAMMIT.
After a while, i realized I didn't really have the correct set up to track down the problem, and you know what? (wow, am I embarrassed to admit this) commenting out the offending code solved the problem. Even when I triggered the use case where the offending code would trigger, it didn't cause problems, so I'm not 100% my solution isn't correct. It does feel wrong.
Yesterday was also odd in that it was an errand day. I was okay with t-mobile taking more than an hour of my time, which is odd for me, to be okay with waiting. Signs of maturity? How about increased mindfullness and peace with myself? Regardless, waiting isn't as much of a problem for me as it was before.
Not sure how long I'll keep the 30 minute reminders going. My alarm is the Despicable Me Whaaaaaat? that, well, as Kris says, is too cute to ignore. It is delightfully amusing.
So cute that I might need to switch to 15 minute increments.
Kickstarted Paper Punk project!
Blog Posted by kitt at 20:27 on 23 October 2011Another Kickstarter project coming along!
This one is PAPER PUNK - paper building blocks for your imagination, by Grace Hawthorne.
The short description:
WHAT IS PAPER PUNK Paper Punk is a system of paper blocks that allow you to create spectacular looking paper toys and art forms with a few simple folds. Consider Paper Punk as building blocks for your imagination. It’s easy to use (everything you need is included) and very educational (spatial and dimensional thinking, motor skills, math, science, etc.) What I love most about Paper Punk is that it’s BEAUTIFUL and FUN.
My description:
Paper! Awesome!
Grace sent me a little teaser about the project.
I'll tell you: I can't wait!
1dollarscan review
Blog Instead of being asleep at 20:03 on 23 October 2011, kitt created this:I've been converting all of my records to digital formats. I started with a first generation Fujitsu scanner, eventually buying-up to the ScanSnap 300M. It is an awesome scanner: does double sided scanning automatically, scans to PDF at the touch of a button, feeds nominally well, is small enough to carry when travelling, and can run off USB power. I scanned papers, Melissa scanned papers, and Kristi scanned papers. Papers were scanned and shredded, scanned and tossed, or scanned and archived until the seven years are up.
Wow, is it tiring work.
And so slow.
And nearly impossible for books.
So, when I saw the TechCrunch article on 1dollarscan, I pretty much had to try them out, digitize some of my books, in particular, the ones where I want the knowledge they contain, but I'm not attached to the actual book for any reason (other than they are paper, loves me the paper).
The price of the book scans was for $1 per 100 pages scanned (and I'm assuming a book page printed on both sides counts as two pages), with OCR included. For books not with exactly N x 100 pages, the count rounded up, so a 212 page book was 3 sets, or $3. Perfectly reasonable.
For my first order, I sent six books, chosen mostly because they were at the top of my pile of books I wanted the knowledge of, but didn't really want the book. I managed to select a good assortment of books for quality test cases: an organic chemistry textbook, a couple books about character modelling and animation, and one on algorithms. With this selection, I managed to cover illustrations, poorly designed text over dark backgrounds, code examples, mathematical symbols and chemistry formulae. All in all, a nicely diverse selection to see how good the scans would look and how well the OCR would work.
I placed my order on September 5th, Kristi dropped the books off a couple days later. I sorta forgot about the books, until I received an email two weeks later letting me know I COULD SAVE 30% OFF A NEW ORDER! I was waiting to see the quality of the scans before placing another order, so I was a little disappointed by not being able to use that discount.
A month after dropping off the books, I still hadn't received a notice about my scans, so I had no idea what my order status. I sent an email asking what was up, indicating I was sad I couldn't take advantage of offers they had been sending me. I was told, "According to our system, your books have been already scanned on Oct 4 but has been stuck on Quality Check," with a completely reasonable turn around time on the support email (I emailed at 6PM and had a response by 10:30PM that night, so either someone is working late, or support is worldwide - I'm inclined to believe the former).
I was, however, disappointed when I received an email that day announcing their new membership service where books are scanned for $1 for 100 pages, but OCR was an additional $1 per set (100 pages). For an additional $1 per set, the PDF would be named the title of the book. The membership subscription was $100 per month for 50 sets, but hey, that is a $150 value, right?
Well, no. Not really.
$1 per set to name a file is weird, just plain weird. I could understand $1 per book, since there's one book and one PDF file, but I'm not really sure that a 1000 page PDF created by a 1000 page book is 10 times more difficult to rename. So, that $150 value is actually more like around $110 or so.
But there's that $1 per set OCR charge that gets me.
For any reasonable use, the scan is $2 per 100 pages. The math doesn't add up. The website says:
"Free scanning up to 50 sets" means that you don't pay for them, which isn't accurate, because you've paid for the membership. So, maybe "scanning of 50 sets included in membership" is more accurate.
"Includes free OCR and book title" isn't accurate, again, because you've already paid for the sets with the $100 / month charge. So, yeah, it's rather a break even point (I don't think the 10 seconds to rename a PDF is worth the $1 / set, so I'm ignoring it completely in this deal).
What you DO get for that membership is expedited scanning, within 10 business days, unlimited cloud storage of the scanned PDFs, and the ability to send them books from Amazon instead of having to ship them. Since they're local to me, this isn't really a cost I consider.
So, yeah, the membership deal, not really a deal in my mind.
And the next day, on the 11th, I received an email letting me know my files were ready.
So, I completely missed the FANtastic price because I wanted to do a test run. I am disappointed in this result.
What I am NOT disappointed in, however, are the scans. They *are* fantastic. The pages don't bleed through (where you can see the printing from the back of the page). The images are clear. The OCR, even with text over a grey patterned background, has been great for all of the pages I've checked. I am WAY excited about the scans, and plan on sending (literally) 4 meters of books to them to digitize.
The downside of these fantastic scans?
The file sizes.
The six pages were 1.82 GB in a zip file. Unzipping it took so long, I discovered what the Archive Utility logo looks like:
The organic chemistry book? All 1537 pages of it? It was 718MB. At 3/4 of a G of memory, that's over 1% of my ipad's space.
Not so happy with that.
The upside to even THAT disappointment is that 1dollarscan has a fine tune section on their website (place your order after logging in to have access) that will "optimize your reading experience for each device" with supported devices currently being "iPad, iPhone3G, iPhone3GS, iPhone4, HTC Desire, Galaxy S, Kindle3, SONY Reader."
I plan on trying out the fine tuning for my next order, since the organic chemistry book isn't readable on my ipad when added via iTunes.
So, the final verdict on this service is "Hell yes." I'm still sending the 4 meters worth of books to them. Since it'll be over the 200 sets maximum per order, I'll be calling them tomorrow to see if I can get at least part of the discount I missed, maybe on the OCR cost, talk them down to one-and-a-half-dollar-scan or something.
I recognize the company is trying to figure out this service and building up their website feature set, but I keep thinking, take care of me, and I'll become your biggest fan.
Welcome back!
Blog kitt decided around 00:31 on 23 October 2011 to publish this:"Did you just bombard my RSS feed?"
"Yeah, probably."
"With like five posts."
"Yup."
"In one day."
"Nominally."
"Welcome back."
"Thanks!"
How not to encourage attendee interaction
Blog kitt decided around 00:15 on 23 October 2011 to publish this:I went to BADCamp, Bay Area Drupal Camp, in Berkeley today. In it, I noticed a serious difference from Brooklyn Beta in being able to approach people. Last week at Brooklyn Beta, I was somewhat comfortable (there were exceptions) in approaching people, throwing my arms wide, and greeting people I had never met by their first names.
Why?
Here's why:
On my front, and on the front of the person I was about to hug, was a badge. On the badge hanging around my neck was my name, big and visible from a distance. Look at any picture from the Brooklyn Beta Flickr Pool and, if you can see the badge, I can pretty much guarantee you can see the person's name. As I approached in greeting, if the person I was approaching didn't know me, his eyes would quickly flick down to my badge, then back up, and move into an echo of the smile on my face.
Delightfully, because I could see names from a distance, I was able to identify people I had never met, knew only by twitter, and had no idea what they looked like (usually because their twitter icon wasn't a picture, looking at @colly and @jasonsantamaria, the latter with one eyebrow raised), and actively seek them out to say hello and meet them.
I loved this aspect of the conference.
Contrast the Brooklyn Beta badge to the BADCamp badge:
Now, the badge is lovely. The design is cute, and well customized for each attendee.
It is also not readable from any distance over four feet.
I have several times walked past Drupal people I would love to meet, simply because I didn't know who they were, and couldn't tell as I approached. The colors are not contrasting enough to be visible from a distance. The font is not large enough, it's not bold. I cannot read it easily.
Worse, it doesn't contain an easy way to glean contact information from the attendee's badge.
The information contained on it, in tiny print, is an attendee's Drupal user name, the attendee's employer's name, if provided, and, in the larger font, the attendee's name.
No email.
No website.
No employer's website.
No twitter id.
Yeah, so, if you're designing badges for a conference, and want people to talk to each other, the number one thing you should do to reduce barriers between people is put their names very big (bigger than you think you should) on the badge, and in contrasting colors.
Then add an easy way for people to contact each other. On the badge.