Tweets

You blocked @codeslamio

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @codeslamio

  1. 30 Mar 2016
  2. Retweeted
    30 Mar 2016
  3. 23 Feb 2016

    Thank you Crash Course students. I now pronounce you CODESLAM Computer Science Neophytes. Go forth and automate.

  4. 14 Feb 2016

    Yes, CODESLAM SUNDAY is still running on Valentine's Day. Love it.

  5. 31 Jan 2016

    You may need to park a bit away from Domi to avoid the building re-painting. CodeSlam Sunday begins!

  6. 29 Jan 2016

    "Once a program is working perfectly." When is that again?

  7. 26 Jan 2016

    CS crash course 50% complete

  8. 24 Jan 2016

    CODESLAM SUNDAY begins! 3/8 meetings complete - we've already learned a lot, but there's a lot more CS we'll be packing in!

  9. 19 Jan 2016

    Solving a problem involves making many mistakes. It requires searching,trial&error. Homework will be out tomorrow on that topic- searching.

  10. 12 Jan 2016

    We re-learned how to count tonight - in multiple bases and for many applications! Keep it up codeslammers

  11. Retweeted
    11 Jan 2016
  12. 10 Jan 2016

    CODESLAM SUNDAY 3pm, Domi. I'll be there to work on homework together. *not actual footage of CODESLAM SUNDAY.

  13. 8 Jan 2016

    Assignment 1 is emailed. Please tell me if you did not get it!

  14. Retweeted
    7 Jan 2016

    Computer science is not just learning to code in a particular language. It's about fundamentals that are timeless & adaptive. -

  15. Retweeted
    7 Jan 2016

    Computer science crash course with starts now! Two month sprint taught by .

  16. 7 Jan 2016

    CodeSlam Crash is 13 codeslammers strong! LET'S GO.

  17. 7 Jan 2016

    CodeSlam Crash in 1.5 hours.... get ready.

  18. Retweeted
    29 Dec 2015
  19. 1 Jan 2016

    The codeslam computer science crash course filled in just a few days, see you on January 7!

  20. 12 Dec 2015

    a belated tribute (birthday Dec 10) to Ada, who made programming possible

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·