ddagradi

13 ms·

61.
Hacking Hacker Culture(dominicdagradi.com)
1 points by ddagradi 15y ago|0 comments
62.
MacRuby Ups and Downs(dominicdagradi.com)
1 points by ddagradi 15y ago|0 comments
63.
by ddagradi 15y ago
No argument there. You can always count on Helvetica, Arial, Georgia and Verdana. Reliable old workhorses. And boring beyond belief.
64.
by ddagradi 15y ago
[Disclaimer: My business licenses fonts via Typekit] Blaming Typekit for bad design is an interesting choice. Might as well blame browsers for giving designers access to millions of terrible color choices via CSS while you're at it. Blame b
65.
Apple's Four-Year Product Rollout(shawnblanc.net)
3 points by ddagradi 15y ago|0 comments
66.
TechCrunch's Mascara Tears(37signals.com)
22 points by ddagradi 15y ago|1 comments
67.
The Secret To Rails OO Design(blog.steveklabnik.com)
87 points by ddagradi 15y ago|33 comments
68.
by ddagradi 15y ago
Did you type your password twice? Pretty sure the second field was "My Skills". I almost submitted that accidentally too.
69.
by ddagradi 15y ago
As long as it's a negative number, it's a win. I feel like LoC as a measurement for anything is pretty outdated.
70.
by ddagradi 15y ago
This is not about requesting the content type though, it's about requesting the format of the content. If I make a request to https://api.github.com/users/dominic/gists , I'm getting back JSON, since that's all Github's API supports. Githu
71.
Why yes, that is a Galaxy Tab 10.1 in my pocket(sethclifford.me)
62 points by ddagradi 15y ago|25 comments
72.
by ddagradi 15y ago
Support independent developers. If you can't, that's okay – there's numerous free text editors to use. Try TextWrangler, or search the Mac App Store!
73.
by ddagradi 15y ago
@font-face is pretty widespread, but licensing is a many-headed beast, it's true. Typekit, however, has really extensive browser support ( http://help.typekit.com/customer/portal/articles/6786-browse... ) and, of course, appropriate licensi
74.
On Succeeding Steve Jobs(daringfireball.net)
229 points by ddagradi 15y ago|102 comments
75.
by ddagradi 15y ago
Don't worry - Adobe won't be updating the Creative Suite with these features until at least the next release cycle. I imagine that, as you said, "Resume" will not be supported for performance reasons alone.
76.
by ddagradi 15y ago
On Verizon, the iPhone is always a great choice, especially with new hardware coming out in the near future. Otherwise, figure out what the newest Android is. It changes pretty often. Droids are a solid product line.
77.
Byte Retracts "A Sobering Look At Apple"(informationweek.com)
15 points by ddagradi 15y ago|2 comments
78.
How to Use the iPhone's Home Button(ignorethecode.net)
2 points by ddagradi 15y ago|1 comments
79.
Google's Patent Problems(marco.org)
47 points by ddagradi 15y ago|14 comments
80.
by ddagradi 15y ago
Is it time for Apple to shut down one of the fastest and most used mobile browsers, whose development (along with Chrome) helps drives standards forward on iOS, Android, Mac and Windows? As if.
81.
by ddagradi 15y ago
You're working on a startup? Then you should have more than $500 to invest in your product. Offer a humane hourly rate ($15/hr for a student programmer? Probably), and you might get what you want.
82.
by ddagradi 15y ago
Only very, very roughly. The issue is dedicated capacitive buttons. On-screen buttons can give visual feedback, and are only present when they are contextually appropriate. Capacitive buttons are dedicated spots on the hardware that are a
83.
by ddagradi 15y ago
It's more appropriate on a device you're not as likely to brush up against accidentally, or need to interact with very deeply.
84.
by ddagradi 15y ago
The iPhone's proximity sensor disables the touch screen when it is near your head. Sounds dicey, but in practice has worked nigh flawlessly since launch. The issue here is buttons that you physically press down (like the iPhone home button)
85.
by ddagradi 15y ago
In Honeycomb (and presumably 4.0), the capacitive buttons have been replaced with on screen elements, so sort-of yes. The difference, in my opinion, is that there is on-screen feedback when you press a screen button, vs a capacitive button
86.
by ddagradi 15y ago
Wait, I don't understand this argument. iPhones are one of the few phones that don't have this issue.
87.
by ddagradi 15y ago
Fix the bugs - 1 star reviews aren't helping you.
88.
The Capacitive Button Cult Must Be Stopped(ignorethecode.net)
166 points by ddagradi 15y ago|113 comments
89.
by ddagradi 15y ago
Maybe start the title with "Rumor:"...
90.
by ddagradi 15y ago
To be fair, FCPX is a complete rewrite of the entire codebase. It's a lot like Apple hit the reset button - a weird decision, but not unreasonable to call it an MVP...again.

More ›