Profile_bird

Hey there! JoeOsborn is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving JoeOsborn's tweets.

Already using Twitter
from your phone? Click here.

JoeOsborn

  1. @ChrisSprague (: There'll be a digital prototype of this, so I'll send it your way once it's playable.
  2. Just had my best playtest ever. Awesome work, Jacob and Yun! Thanks for playing, Erin and Sam Roberts!
  3. Wasted a ton of time today trying to write something on WPF. Is it just me, or is it frustratingly over-engineered?
  4. I was just kvetching about LA's chip scene... BUT! Data Beez chiptune tour on Nov. 7th! Happy day-before-birthday to me! Thx @tinycartridge!
  5. @artficlinanity Not really. It depends on what languages/paradigms you've used before. In the end, the library and the idioms take practice.
  6. @artficlinanity Most of my Erlang work is for personal experimentation with concurrency. Facebook Chat and MochiAds are written in it, too.
  7. @rob_rix Generally speaking, I dislike tap-to-click on trackpads. YMMV.
  8. @rob_rix Haven't used the Touch+Pen Wacom gave us as a mouse replacement—have used it briefly for cursor movement, dislike its touch-click.
  9. I remember reading about a research project on organizing/accessing documents without browsing or searching. Twitter, know of anything?
  10. @wespaugh Congratulations!
  11. @sela_davis It's never too late! This is only a draft, so I'll have time to integrate additional responses. Thanks :D
  12. @library_chan Sure, but I still think I need to find and identify trends. Don't want to privilege any viewpoints… This is hard work!
  13. Up to two pages (of five) on my research paper draft. Got my intro/etc done, just have to reduce 21 great survey responses to three pages…
  14. @wespaugh I'm going for the "Yoda" angle—advice that seems measured/reasonable, but may ultimately be useless. My real weakness is shipping…
  15. @wespaugh I mean don't abstract before seeing duplication, just like you don't optimize prematurely. Easy to forget that one. Re:tests, yes.
  16. @wespaugh In other words: pay down your engineering debt with cleanup, remember to ship features. Test->functionality->tidiness->speed.
  17. @wespaugh You aren't gonna need it. Shipping is a feature. Test first. Once and only once. Reduce duplication (but don't break your tests!).
  18. RT @flantz via image to workaround character limit! http://img.ly/6D7
  19. @flantz I wish I could retweet that, but it is too long for me to also include your name ):
  20. Do you make or play games? Please take my "Game Developers & Ethical Responsibility" poll! http://bit.ly/ZL9RE