30yo. Grew up on a small farm in rural Illinois. Studied Physics / Math at a no-name liberal arts school in the Midwest. Got a job as a programmer out of school working for Sears Portrait Studio (no lie). Wrote a piece of OSS software over Thanksgiving break 2012 that front-paged on HN. Major tech co reached out the following week. Got the job, moved to SF, etc. I now work for a fairly well-known startup, living 'the dream.' Incredibly thankful for the opportunities that I've had.
At face value, I like the idea of RubyMotion, but I can't help but feel like it's a crutch to avoid picking up a few subtleties in Objective-C. The article even points out that RubyMotion doesn't hide much of the API from you, so in some ways it feels like 6 in one hand, half a dozen in the other. I'm not trying to be a naysayer, but I don't think the barrier to entry is as high as some make out to be.
This wouldn't be a difficult enhancement. I'd probably add some sort of enum to indicate what edge the bar should be along. Some of the view layout logic would obviously need to change, namely the glow effect would need to rotate and reposition based on what position the bar was in (not a difficult thing, of course). This is not necessarily a high priority for me right now (I'd like to add some customization API for look and feel in the near term).
An optional swipe-to-hide/reveal feature is something I was planning on implementing. Look for that soon!
If you are currently "manually testing in the simulator," don't forget that there are existing automated solutions for UI testing in iOS, including KIF (mentioned above) and Apple's own UIAutomation.
I've actually written a small framework for UIAutomation to make it less cumbersome, if that's a factor in adopting UIAutomation: http://www.github.com/jaykz52/mechanic
I posted an item yesterday to try out the service, but noticed that it was including a link to a zoomed in map hovering right over my house in the post (the same map is included in the "yardsale" version of the post). I'm a little cautious about posting my location/address on a site like CL (though I use the site frequently).
I promptly deleted the post and notified the ryan of my concerns; he promptly replied to my email and mentioned that he "fuzzed" my location details so that my perceived location was not so pinpointed. I haven't reposted anything to verify, though.
Here's a gist of the auto-gened CL post:
The title is essentially an ellipsis'ed version of your yardsale post (it cuts off at some character count, not sure the exact number). It uses the price you set as the CL price. Here's the post body:
"Hey everyone, I've got a [your yardsale post auto-inserted here]
Interested? Get in touch <shortened link to yardsale post>here</link>
<another yardsale link>View All Images</link> / <link to map>show map</link>
Posted with <link to Yardsale homepage>Yardsale</link> (free!). lovingly made in San Francisco.
It's reportedly due to the nature of how Kickstarter handles transactions: they don't process payment until after the funding period closes (and only if the project meets or exceeds its goal). Amazon Payments is basically the only payment processor that allows this sort of "delayed" charging from what I understand.
someVariable = someVariable || {foo: 'bar'} is one of my favorite ways to cock the heads of my less JavaScript-inclined pairing partners. Both effective and terse.
Yeah, I was thinking the same thing. I was wondering if the person was making a play on words with 'silicon,' but considering his grasp of English, that might be giving too much credit.