328 karma · joined December 14, 2009
Or maybe just another way to confuse the hell out of web users.
Looks like pitchfork improved their security a bit. I remember they used to just have an XMPP player, where the XML behind it just had an additional node titled security. It's contents said something to the effect of.. "Don't download these files!". Or something like that.
My girlfriend would ask "How do I do XXX" and before I could remember how I would accomplish the objective, she had explored her way to the solution.
Obviously a phone will have more strenuous requirements, but the interface I'm using on the Zune seems like it may be the exact outlandish interface that changes the way we think about buttons, and menus for interactive portable devices.
I'm not entirely certain, but I can't think of a single disadvantage to learning OOP. I'd actually be interested to know if there where some.
I'd also add.. Learning PHP as a first language slowed me down a bit when exploring other languages. PHP is very forgiving. If you're just learning to learn.. Maybe you should consider starting with a language that's much more strict; Python or Perl in my case. This way you focus on the concepts instead of the practices. PHP is one of those.. "more than one way to skin a cat" languages. Or at least more than most (from my experience).
Quote: Because it would be so simple for Google to create a "Normal email view" for people like me.
So, Google should make it customizable.. ?
http://www.codinghorror.com/blog/archives/001076.html
I still decided to go with the 2x24's. In the end though, it may have been a waste. Afterwards I introduced myself to Ubuntu and the virtual desktop features really separated my work well enough that I probably didn't need the extra monitor anymore.
A couple months later and I'm now on a 17" Macbook Pro. With Spaces configured to my liking I don't miss the additional monitor at all.
I agree. The problem is definitely a matter of related vs. unrelated content. My suggestion (or babble) was more so just pointing out how easily we could implement a "source content filtering" logic into an already existing interface.. If we felt that was the best way to go about it.
Just drop the link, some tags, and misc attributes along with a short description.. Is it much more complicated than that?
Surely filtering the "fire hose" with the query "programming news" will not yield satisfactory results.