Bridging the Nerd Gap

A few mornings per week before I begin work, I like to walk to a nearby park, say Morning Prayer and plan my day. I use the iPad on these trips and I was going to bring my recently-procured iPad mini today. For some reason, though, I picked up my iPad 3, opened the Smart Cover and looked at the screen.

I decided right then that I’m going to return the mini. I’ll tell you why right now.

Things I Love About the Mini

The size and weight. These two factors make the device extremely portable and easy to use.

Things I Don’t Love About the Mini

The size.

Huh?

Having a super small device is nice and all, but the iPad mini (and you may very well disagree with this) is aimed squarely at the “I consume stuff” market. Put another way, I type on my iPad a lot and the iPad mini sucks for typing. Even when employing an external keyboard, it was a clumsy, subpar affair compared to my iPad 3 + Logitech Ultrathin. Online gambling on iPad offers a smooth, responsive gaming experience with sharp visuals and intuitive touch controls. Whether at home or on the move, players can access top games easily. Choosing a casino en ligne retrait instantané ensures quick access to winnings, making the iPad a preferred device for mobile bettors.

Also, the screen. This may be the king of all “spoiled white guy” complaints, but I found myself, in some situations, squinting to read the iPad mini screen from less than a foot away. Daddy can’t abide that. The retina display is simply too beautiful and I won’t step back.

Finally, the battery seemed to drain far more quickly on the mini than on the iPad 3. This is entirely anecdotal and may just be my dumb perception, but there you go.

Brass Tacks

I’ll be honest; I tried like hell to like the mini. I really did. And it’s a fine machine, just not for me.

I have been using my iPad as a mostly-complete laptop substitute for a good while now and it’s been wonderful. The number of concessions I’d need to make in order to adapt the mini to such a role are simply too many.

I type a lot. Sometimes it’s source code and sometimes it’s English, but I spend a good amount of my time moving the cursor to the right in one way or another.

Because I type so much, it’s important to me that I have the best tools for the job I’m currently doing. Not too long ago, I changed my primary text editor from the venerable vim to the (relatively) new kid on the block, Sublime Text 2. ST2 was far more Mac-like than vim (yes, even the MacVim variant), but it really lacked polish. So, I hopped over to the App Store and dropped more than a little cheddar on what has become my new text editing home: the grand poobah of them all, BBEdit.

It’s been great. BBEdit has its quirks and I’ve had to learn new ways to perform common tasks, but I’m really happy. Amidst this, exploring various slot apps has also added an extra layer of enjoyment to my experience, and I couldn't be more content. Here at 슬롯사이트 2023, you can find the most popular slot sites in 2023.

The Problem

Much of my daytime work for Evernote involves explaining how a given chunk of source code works. I routinely utilize Github’s gist facility to quickly publish some code and easily embed it in the web page I’m writing (here’s an example).

One feature I really loved about Sublime Text 2 (which isn’t a native feature, but was provided by an add-on package) was the ability to quickly create gists without leaving the app: highlight a few lines of code or whatever, strike a key chord and fill in a couple of fields (filename and description). A few seconds after hitting Return, the gist would be created and the URL would be in my pasteboard.

Sadly, BBEdit has no such capability, either out of the box or with a third-party add-on.

So, I built it.

The Thing

(Warning: lots and lots of nerdy programming talk ahead)

The solution is comprised of two parts: a Python program, makeGist.py, that creates gists and a small AppleScript program that provides the interface between BBEdit and the Python program. Let’s quickly discuss each, shall we?

makeGist.py

As previously mentioned, this program lets you create gists from the command line. It can actually be used on its own if you feel so inclined. Running it looks like this:

python makeGist.py -f filename.txt -d "gist description" -c "contents of the gist"

Running that exact command will produce this result:

$ python makeGist.py -f filename.txt -d "gist description" -c "contents of the gist"

https://gist.github.com/14bf8c1e27bf15a6ed14 

(I’m also leaving the gist up if anybody wants to see that I’m not lying).

There’s also an optional -p parameter, which will create a public gist (the default behavior is to create private gists).

In a nut, each of these parameter values is shoehorned into a simple value object, then converted to JSON and sent to the Github gist API. Since, chances are, most of you reading this don’t really care about what all that means, I’ll let those who are interested peruse the source code.

Once it’s done doing its business, it prints out the HTTP URL of the gist to the console.

Now, the part that ties it to BBEdit…

Make BBEdit Gist.scpt

This monstrosity merely provides the user interface to makeGist.py. Specifically, it does the following:

1. Grabs the current directory (so it knows where to find makeGist.py).
2. Defines an absurdly long shell command (which is how makeGist.py is run).
3. Prompts the user for a gist description and lets them choose a public or private gist.

When the script is run, the user is greeted with this awful dialog:

Yep, pretty awful, but it gets the job done and I couldn’t design my way out of a wet paper sack and I’m fine with all of it.

Once the user completes the single field and clicks one of the buttons (assuming it’s not the Cancel button which, like it says on the tin, aborts the app), it asks BBEdit for the selected text in the front-most buffer. If no text is selected, it takes all of the text in the front-most buffer. That text, combined with the options chosen by the user, are used to construct the parameters to makeGist.py. The script is run and the output—the URL of the newly-minted gist, if all went well—is shoved into the system pasteboard.

Using the Thing

First, download the source files from Github. You need both the Python script and the AppleScript file. Drop them both into ~/Library/Application Support/BBEdit/Scripts/.

Next, open makeGist.py and update github_user and github_pass to your Github username and password.

Finally, restart BBEdit and you should see “Make BBEdit Gist” in the Scripts menu. Highlight some text (or don’t), then click that menu item. Assuming the bailing wire and chewing gum didn’t give way, you’ll have a gist URL in your clipboard in a couple of seconds. Spiffy!

What’s Wrong with The Thing

Because I’m not actually a real programmer, I’m shipping this thing with some known issues. Like you do.

Let’s start with authentication.

As it stands right now and like I mentioned a second ago, you’ll need to populate the github_user and github_pass variables at the top of makeGist.py before you can use it. These credentials are used to procure an auth token from Github which is then used to create gists. I’m not sure how long these auth tokens are valid and I wanted to avoid having to build in a UI for the user to enter their Github login, so this is where I landed. I understand there’s some awesome gitcredentials madness available, but I’m not that smart and I haven’t had oodles of free time to investigate it.

Next, user interface.

There are currently no alerts or notifications when a) the process is finished or b) there was a problem. These can be chalked up to my inexperience with AppleScript and, frankly, a bit of laziness. I wanted the workflow to be optimized for minimal user input and, as such, I felt that popping up a “We’re Done!” dialog at the end of the process would be inelegant.

Finally, we come to real, not-crappy error handling.

makeGist.py does check for various exception types during execution and, near as I can tell, won’t loudly unwind the call stack if things go south. That said, it also doesn’t do any fancy stuff like retrying in the event of a timeout, etc.

Oh, I almost forgot: this software is provided without warranty and if it turns your Mac into a smoldering heap of unicorn entrails, don’t come crying to me.

Takeaway: if any of this makes you squeamish or angry, please don’t use The Thing (or, if you’re up for it, fork the project and fix the bug/add the feature!)

In Conclusion

I had an itch and I scratched it — it’s that simple. As with most of the goofy, one-off software bits I publish here, I have no clue if this will be useful to anybody but me.

If you do end up using it:

1. Awesome!
2. Let me know (either using Github’s issues feature or via Twitter) if you have any problems with it.
3. If you have any Python and/or AppleScript chops and feel like making the thing better, do feel free to fork the project and send me a pull request with any features/fixes you add.

Either way, I hope you guys dig this thing.

Yesterday morning, I drove to the Apple Store and purchased an iPad mini. For the next two weeks, I’ll be conducting an experiment.

History

I’ve been using my iPad (2 succeeded by 3) a lot. Mostly for writing, emailing and other things that don’t require a full-blown computer. And it’s been great - I love my iPad.

When the iPad mini was announced, I was a bit intrigued. The size and weight sounded nice, but the price and lack of a retina display were pretty major turn-offs. I had a perfectly good iPad 3 (that was rev’d about 6 freaking weeks after I bought it, but I’m not bitter, I swear) that did everything I needed.

But I started to notice something: virtually all of my online pals who had bought the mini on launch day would not shut up about it. Common refrains included:

• “Man, this exactly what the iPad was meant to be. It’s perfect.”
• “I’ve used this mini for a week and I just sold my iPad (2|3|4).”
• “I thought the non-retina display would be a deal-breaker, but I totally don’t care/notice any more.”

These are people for whom I have a great deal of respect and whose opinions I generally share. After hearing what I estimate to be a couple dozen people expressing opinions like those listed above, I knew I had to at least try it.

The Experiment

I’ve written about the iPad before and how it fits into how I work. To summarize:

• 50% writing (emails, blog posts, etc.)
• 20% task management stuff (almost exclusively in OmniFocus)
• 20% reading (iBooks, Kindle and Comixology)
• 10% miscellany (games, web browsing, general screwing around)

I knew the mini would be perfectly suited to the latter two use cases, but the first two-obviously-account for the majority of my iPad use. I needed to be sure that the mini would do at least as well in each role as the iPad 3 did.

As of today, I have two weeks to evaluate this before one of two things happens:

• I return the iPad mini and Smart Cover
• I sell my iPad 3

Financially, this will basically be a wash. While I did pay a good bit more for my iPad 3 than for the mini, the going rate for a pristine iPad 3 on eBay is comparable to a similarly-equipped mini (according to my non-exhaustive research, that is).

The experiment will be, of course, to see how the mini performs in place of my beloved iPad 3.

(Both my iPad 3 and iPad mini are 32gb with Verizon LTE, if you’re curious - and they’re both black)

Concerns

When it came time to compose text on my iPad 3, I would almost invariably attach it to my well-loved Logitech Ultrathin keyboard case. For some reason, I really loved only having to carry a single thing. This doesn’t seem to be an option with the mini since, near as I can tell, there aren’t any really great case+keyboard options yet available for it.

For the time being, I suspect I’ll be relegated to unearthing and toting around the InCase Origami, replete with Apple Bluetooth keyboard, in addition to the mini itself (the configuration being employed to compose this post, I might add). I realize that carrying two pieces of equipment instead of one is hardly worth whining about, but it’s important to me.

Part of what has made the iPad such an indispensable part of how I work is the speed with which I can deploy it and begin typing/working. I don’t know that the mini will afford me such a luxury.

Despite the near-universal claims of my comrades, I do wonder how long it will take me to acclimate to the non-retina display (or if I will at all).

First Impressions

1. Having written most of this post using the mini (which is propped up in the afore mentioned InCase Origami), I have to say that it is nice so far. The screen isn’t so small that I have trouble reading the text that I’m writing and the whole contraption doesn’t look altogether ridiculous.
2. The size and weight really are pretty spectacular.
3. The non-retina display looks remarkably worse than the retina display on my iPad 3.
4. The Smart Cover (red, if you’re wondering) is a bit of a turd; it doesn’t sit flush against the screen when closed-a problem I expect will go away after a few days of use-and the iPad seems unstable when propped up on the collapsed Smart Cover.
5. The device itself is beautiful; Apple’s hallmark fit and finish are present and accounted for and it’s every bit as nice to hold and admire as any other Apple product I’ve owned or used.

I’m afraid that’s about all I have to say at this point. Heck, my applications aren’t even finished installing yet. My son has insisted we reserve judgement until he’s had a chance to play Angry Birds Star Wars, which sounds smart to me.

Miscellaneous Thoughts

When I mentioned on Twitter that I had purchased a mini for evaluation purposes, I was inundated with messages from friends and followers who were unshakably confident I would end up keeping the mini.

If I do end up keeping the mini, I’ll almost certainly sell my Kindle 4 (if it’s worth anything).

If anybody has any specific questions about this, ping me on Twitter.

Recently, my wife and I got all gussied up and went to the symphony (they snuck me in the back door because I’m me). Because my good friend and brother-in-law is such a cool guy, he agreed to babysit our two kids for the evening.

We got home and he was curled up on the couch.

“I didn’t have the WiFi password.”

He wasn’t bummed, but I was bummed for him. Because I care, people.

Anyway, this happens somewhat frequently. People come to my house and they ask me for my WiFi password. No sweat really, but the password is long and complicated and I want to find a way to make them type it instead of me.

So I made a thing.

The Building Blocks of The Thing

GMail has a feature called Canned Responses. Basically, they’re pre-written emails that you can configure either quickly pop in as a reply to a message or send automatically using GMail’s Filters. I chose the latter for this particular case.

GMail has another feature (which, from what I’ve read, is available lots of places) which I’ll call the “+address feature”. I have no idea if it’s actually called that, but go with me.

Say your email address is [email protected]. Just say. You can tell people your email address is [email protected] and any emails sent to that address will end up in your inbox. Spiffy.

But what you may not know, is that you can create filters based on these +address thingies. And filters can be configured to send canned responses. You may see where I’m going with this.

The Thing

To solve this problem of my guests not having my WiFi login information, I followed these steps:

1. Created a new Canned Response in GMail containing my WiFi network name and password.
2. Created a filter that will automatically reply with said Canned Response when people email a certain “+address”.
3. There is no spoon.

Now, when my friends come over and ask for the WiFi info, I just tell them to email the special address and they’ll get the info in a few seconds.

Why You Might Think This is Stupid

That’s all fine and good, smarty pants, but if people don’t have WiFi, how are they supposed to send the email that gets them the WiFi information? Didn’t think’a that, didja!?

Actually, I did.

Because most of my friends are wealthy trust fund babies or whatever, they all have smartphones. And smartphones, as you may recall, don’t require WiFi to send and receive email. So, they send the email from their phone, get the WiFi info and plug it into their phone and computer. Boom.

Or you could just tell them the WiFi password, dummy.

Granted, but like I said earlier, my WiFi password is a super long string of characters that even I haven’t memorized. Maybe I’m being lazy, but programmers value laziness as a virtue.

Isn’t this inherently insecure?! What if some crazy hacker knob figures out the email address and gets your WiFi login!? Sheesh, you really are an idiot.

Two things:

1. This person would have to be pretty crafty to guess my secret email address (and, yes, I know “security through obscurity” is dumb and irresponsible; sue me).
2. This information is only valuable to people who are currently—or will soon be—within about a hundred feet of my house. I’m not a doctor, but I’m pretty sure this excludes almost everybody in the whole world.

How to Do The Thing

Assuming you still want to partake in this foolishness, here are the steps to create your own Thing. You’ll need a GMail account, by the way.

1. Enabled Canned Responses in GMail Labs — In GMail, click Settings, go to the Labs tab and find Canned Responses. Click “Enable”, then “Save Changes” (at the top or bottom).
   
2. Open a new GMail message and type whatever you want the Canned Response to say into the message body. When you’re done, click the Canned Responses menu and choose “New canned response”. Call it whatever you want when prompted for a name (I called mine “WiFi info”).
   
3. Click over to Settings > Filters. Scroll all the way to the bottom and click “Create New Filter”.
4. For the “To:” field, enter your super secret “+address”, then click “Continue”.
5. Set the filter to automatically send the Canned Response and Archive the message.
   
6. Pour the gin because you’re finished.

This little trick certainly has wider application, so let that big hefty brain of yours swim around in this little pool of awesome for awhile and see if you don’t come up with your own fancy implementation.

Anyway, I hope this is useful to you. Ping me on Twitter and let me know if it is (or isn’t).

About a year ago, my pal Myke and I decided to start a podcast together called Cooking with Brett and Myke. We weren’t sure we’d have enough chemistry or potential topics to last us very long, but we went for it.

Yesterday, almost 50 episodes later, Myke and I recorded and published the final episode of Cooking with…. It’s something that I absolutely loved doing and, now that it’s over, I’m more than a little sad about it.

But it had to be done.

For various reasons, I recently decided that I needed fewer obligations. My family, my job and my little side business were all immovable and weren’t candidates for the chopping block. That left only a small number of things, including the podcast. So, it got the axe. And it sucks.

It’s super easy to speak hypothetically about killing ones darlings in the name of the greater good. And I know it was the right decision here. But, I still had to kill one of my darlings.

I’m not happy it’s over, but I’d be lying if I said I wasn’t a little bit glad to have regained a few of my internal cycles.

Anyway, to everybody who listened and was in on all of the stupid jokes and tolerated my abominable accents, you have my sincere thanks. I don’t doubt that Myke and I will be clogging up the Internet tubes again someday.

For now, I’m comforted by an old proverb:

Don’t cry because its over, smile because it happened.

Oh, and if you enjoyed our show, do check out some of the other 70Decibels offerings. And tell Myke what a bang-up job he’s doing (because he really is).

I’ve built yet another Text Expander snippet that will probably be useful to almost nobody, but I find both useful and entertaining.

People ask lots of dumb questions (myself included). In many cases, such dumb questions could be answered with a quick Google search. Hell, the information you want might be in the search result description so you don’t even have to click through! Criminy!

When I am lucky enough to get one of these head-scratchers, I personally love to employ a site called lmgtfy.com, which stands for “Let Me Google that For You”. If you asked me how many US pints were in a US quart, I might send you this link. It’s hilarious and is also a fun way to tell your friends and loved ones to maybe take three seconds and search for the answer before bothering other people.

Before, I’d visit lmgtfy.com, type in the phrase I knew would produce the answer to the question I was being asked, and click the big button to generate the unique URL that I could send to my friend. Lots of steps, methinks. Not anymore!

I give you my Text Expander snippet to create a lmgtfy.com URL using whatever is in your clipboard:

And here it is as a Gist:

#!/usr/bin/env python
 
import sys
from urllib import urlencode
 
param = '%clipboard'.strip()
rooturl = "http://lmgtfy.com/?"
try:
	qs = urlencode({'q':param})
except:
	qs = ''
finally:
	sys.stdout.write("%s%s" % (rooturl, qs))

Yeah, yeah, looks great. How does it work, freak show?

Practical example: if I copied “proper cooked chicken temperature” to my clipboard and typed ;;lmg, it would print the following:

http://lmgtfy.com/?q=proper+cooked+chicken+temperature

Totally nifty, right?

Remember:

• If you’re going to use this, make sure you choose “Shell Script” at the top of the Text Expander composer area. Otherwise, it won’t work.
• (This software might cause your house to explode, hair to fall out or shirts to wrinkle as if for no reason at all. No warrantees, blah blah blah.)

At the Evernote Trunk Conference in San Francisco (where I'll be sitting awkwardly when this post is published), our intrepid CEO Phil Libin announced the launch of the next generation of the Evernote Trunk. I played a small role in helping get this thing off the ground and I'm super proud of all of my coworkers who did most of the work.

And, as it happens, my 34th birthday is this Monday, August 27.

In celebration of these momentous occasions, I'm stoked to offer a special deal on my best-selling ebook, Evernote Essentials. From now until midnight (PST) on August 29 2012, you can get 20% off of my ebook with the coupon code OLDFART.

More than 15,000 smart, attractive people have used Evernote Essentials to jumpstart their journey to Evernote masterhood. Grab your copy now — I think you'll dig it.

Oh, and just as a reminder, everybody who buys Evernote Essentials gets all future updates for free. I'm almost done with version 3.0 and let's just say that, if you have any interest in it, buying soon would be a very good idea. Ahem.

Thanks for reading, friends. ¡Viva la Evernote!