Posted January 28th, 2011 @ 01:36am by Erik J. Barzeski
I ditched Entourage in favor of Mail back in November, and despite some early frustrations, I think I'm finally getting the hang of it.
I now know where to put my cursor so that a backspace or forward space won't remove those bizarre quoting lines Mail uses.
I've come to find tremendous joy in pasting screenshots in without having them hit my desktop (the control key is your friend when taking screenshots).
I've used FastScripts - a tool I recommend often - to handle account switching with a keyboard shortcut.
Speaking of Red Sweater, MarsEdit's shift-cmd-d keyboard shortcut finally makes sense to me now.
I think Mail and I might get along just fine after all.
P.S. Someone should develop a plugin for Mail called "Alpha Mail." I don't care what it does, I might buy it just because it sounds cool.
Posted January 27th, 2011 @ 01:34am by Erik J. Barzeski
If I'm brief in my email replies, online a lot in the next three weeks, and up until 3am most nights, it's because we're really, really close to launching Analyzr.
If you're interested in golf video analysis software for Mac OS X, sign up at http://analyzrgolf.com/ and we'll let you know when the application is shipping.
Posted January 26th, 2011 @ 06:37pm by Erik J. Barzeski
Really, Mac OS X? You can't find a file with the word "shaft" in it on the Desktop?
Posted January 25th, 2011 @ 10:17pm by Erik J. Barzeski
Got a message yesterday on my phone that our flights back to Erie from Phoenix - which were to leave today at 9:30am - will now instead leave at 2:20pm. Our arrival time back in Erie was going to be about 9pm. Now we'll be lucky to be home before 2am.
How is this possible? Why can an airline just completely screw with your plans and do nothing - like a small refund, a voucher for an in-flight adult beverage or six, etc. - to make up for it?
Not cool, American Airlines. Not cool.
Posted January 24th, 2011 @ 10:14pm by Erik J. Barzeski
Just nine holes. Was two over (testing out a face-on putter) until I started goofing around on the last hole. Played a fade as I focused on dorsiflexing the LW more to the top and cutting off the swing a little shorter, but it was a consistent little bleeder that worked well.
Earlier in the day one of the pros told us that he doesn't "believe" in the new ball flight laws. As if science, physics, and empirical data are things in which you can "believe" or "not believe"…
Posted January 23rd, 2011 @ 07:54pm by Erik J. Barzeski
Uh, the tumbleweeds whipping through the practice range were nice.
I will say this (and please, my brevity is not because I have nothing to say, just in a bit of a time pinch), though: despite a strong left-to-right wind, very few balls faded more than five yards. In a still wind virtually EVERY ball that our students hit would have gently drawn to the left.
Everyone got better. Many remarkably so. One student, who missed day one due to the death of a friend, caught up and did incredibly well.
I plan to play a little tomorrow, if possible. We have all day. But right now (see the above comment about a time pinch!), Let's Go Steelers!
Posted January 22nd, 2011 @ 09:47pm by Erik J. Barzeski
So, we're in Phoenix (Goodyear), AZ to do a two-day golf school. It's not as warm as usual, but since it's about -16° C back home, I'll take what I can get…
Here's Andy Patnou, rising star and fan of the way we teach at Golf Evolution, working with Andre Park, who came all the way from Korea to work with us. How cool is that?
Posted January 21st, 2011 @ 01:16pm by Erik J. Barzeski
Posted January 20th, 2011 @ 03:37pm by Erik J. Barzeski
Spotted outside a beer distributor in Harborcreek…
Beer: Still Cheaper Then a Dictionary. Or a brain.
Posted January 19th, 2011 @ 07:21pm by Erik J. Barzeski
I posted a quickie snapshot of the Analyzr website last night to the Facebook group and it drew some positive comments.
It's heavily inspired by Apple's site, but has its own flavor as well. I won't finish it before this weekend, but it'll be ready well in advance of the product launch in early February.
Analyzr is on track and looking really good. Our beta testers have beat on the thing and not found much wrong, and the praise has been universal. Most of the things they've said would be nice (but not necessary) are already things we have planned for the 1.0 or 1.x releases, so… we're cautiously optimistic.
Posted January 18th, 2011 @ 02:46pm by Erik J. Barzeski
It's interesting to me that this Drobo post from late 2008 is still getting hits. But, then again, the information is pretty good and still relevant, so in that regard not surprising at all.
The point of this post? Just to point that out and to say that my Drobo continues to hum along just fine and dandy, and that I'm considering replacing the four drives in it now (500 GB drives) with some 2 TB Western Digital green drives - $99 before rebate and $79 after seems like a good deal.
Then again, there's no pressing need, and the longer you wait the cheaper storage gets…
Posted January 17th, 2011 @ 08:25pm by Erik J. Barzeski
I bought a copy of Mindset: The New Psychology of Success by Carol Dweck based on the recommendation of a friend. I'm also reading a PDF called The Talent Myth.
The former talks about how people tend to be either of a "Fixed Mindset" or a "Growth Mindset." The author posits that you can change from one to the other, but she offers an interesting experiment.
Some little kids were given some easy puzzles. When they completed them, they were asked if they wanted to try a harder puzzle or complete the same puzzle again.
The "Fixed Mindset" kids kept playing with the easy puzzles. The "Growth Mindset" kids acted like the person was stupid for asking if they'd like to play with a puzzle they'd already solved, and many made comments about how they loved the challenge or wanted to know what the puzzles were called so their parents could buy them for them when they ran out.
This coincides a bit with The Talent Code. Kids were praised for either "working hard" or for "being smart," and the kids who were praised for working hard kept working hard, while the "smart" kids simply avoided anything where they might fail at appearing smart.
I'm looking forward to reading this book.
Posted January 16th, 2011 @ 01:56pm by Erik J. Barzeski
Who serves the best burger (of those listed)?
Posted January 15th, 2011 @ 01:47pm by Erik J. Barzeski
I know at least four people who are waiting on the new MacBooks and MacBook Pros to be announced and released.
They're not in a rush - they just don't want to buy a computer and have it replaced by a better computer at the same or even a lower price a week or two later… so the old adage about "if you always wait, you'll never buy" doesn't really apply to them.
I've checked their life cycle. The MacBook is over 240 days old when the average is 195 and the MacBook Pro is at nearly 280 when the average is 208.
My last post on this was November 14.
It's somewhat more relevant to me now because we'll be shipping Analyzr soon and Pros will be switching to Macs. I would hope they aren't put in the same position of feeling screwed by a better, cheaper replacement a week after buying.
Posted January 14th, 2011 @ 09:21am by Erik J. Barzeski
Since this post - the comments on which were tremendously helpful, both public and private, so thank you to those who helped - Dave and I have narrowed down the ideas we like for Analyzr's demo mode.
Regardless of the option we choose, we'll have a watermark across the screen. It's fairly annoying, and looks like this:
We may adjust the opacity somewhat - I might have gone a bit light with this version (25%) but not by much.
At any rate, the watermark is the first line of defense, and for the Pro version of our software, the best if a pro is considering buying it. We also have to be careful not to harm sales of our Home version by potential Home customers saying "the watermark isn't too bad, so I'll just use the Pro demo."
So, we're currently at these three options (there's a poll in the extended entry). Note: in the case of 1 and 3, these options "reset" when you re-launch the application.
NSLog(@"Finish Reading %d Words", 472); »