Profile_bird

Hey there! kevinclark 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 kevinclark's tweets.

Already using Twitter
from your phone? Click here.

kevinclark

  1. Desperately need to speed up this feedback cycle. Right now it's: 1. Make a trivial change. 2. Wait 4 minutes for build and test. 3. Goto 1.
  2. @bittenapple Just basics for now: http://bit.ly/5aTKuT
  3. @bittenapple The (older) "Learning OpenGL" book is online, I'm working through some examples and playing on my own: http://bit.ly/STcO2
  4. Playing with OpenGL.
  5. @bryanl It defines unary ~. In irb it looks like that gets added to self (whatever that is.. calls itself main)
  6. And I'm spent. I think that's enough flame for the night. #concludingrant
  7. @chezbut Sorry, should clarify: the ASF (who finds ways to keep others from releasing software and calls it policy) not Apache (web server)
  8. No, seriously. Fuck Apache.
  9. @timconverse Welcome back to the tribe.
  10. I love the Japanese speakers at Rubyconf. They're just so friendly and excited about what they're talking about. #rubyconf
  11. @williamallthing Nope, I keep getting his stuff in my gmail. Credit card information, travel receipts, other random crap.
  12. Think I have the phone number of the guy who has my email address as his Reply-To. Wonder if he'll call me back.
  13. Every few months I remember just how epic nethack is and lose a weekend.
  14. @thione "Proof" is for places other than the internet.
  15. No, you're right, Microsoft IT. Your reboot of my machine was much more important than my 12 hour build.
  16. The Apache Software Foundation: because what your open source project needs is red tape.
  17. @eventualbuddha Which banks survived the purge?
  18. @tenderlove Just after we get to split CA into 3.
  19. If employers ask for code samples they should be required to give samples of their own.
  20. Bad unit tests are worse than no unit tests.