anarchy golf
august 2010 by rtlechow
"This is a golf server. You can enjoy short coding here in several languages (80 languages). The purpose of this server is not serious competition. Joke problems are welcomed and you can speak freely about problems and can release spoilers. For serious competition with ranking, enter Code Golf.
IRC channel for this golf server: #anagol in freenode. Please feel free to join the channel to talk about various things around golf."
challenge
coding
code
competition
contest
development
game
programming
language
IRC channel for this golf server: #anagol in freenode. Please feel free to join the channel to talk about various things around golf."
august 2010 by rtlechow
Like, Python
april 2010 by rtlechow
"A full list of Like, Python keywords is below (swearing optional):
Valleygirl: omg, so, like, totally, right, toootally
Frat guy: friggin, fuckin, dude, man, bro, broheim, broseph
Internets: lol, rofl, teh, ohai, plz
Snoop: yo, homey, homeboy, sup, dog, shit, girl, ma, biatch, ho, shiiit
Local: wicked, hella, anyways
Misc: just, hey, yeah, ok, um, uh, ah, actually, something"
art
code
coding
development
humour
humor
linguistics
programming
python
languages
language
software
Valleygirl: omg, so, like, totally, right, toootally
Frat guy: friggin, fuckin, dude, man, bro, broheim, broseph
Internets: lol, rofl, teh, ohai, plz
Snoop: yo, homey, homeboy, sup, dog, shit, girl, ma, biatch, ho, shiiit
Local: wicked, hella, anyways
Misc: just, hey, yeah, ok, um, uh, ah, actually, something"
april 2010 by rtlechow
lbrandy.com » Blog Archive » Never trust a programmer who says he knows C++
april 2010 by rtlechow
"Just mention that C++ is an extremely large and complex language, and the post-valley people will give you 127 different tiny frustrations they have with the language. The pre-valley people will say “Yea, I guess. I mean, it’s just C with classes.”. "
c++
programming
learning
funny
interview
coding
c
humour
april 2010 by rtlechow
Software Craftsmanship 2009 : TDD As If You Meant It
march 2010 by rtlechow
"45 minutes: do a bit of programming. A simple problem will be presented. Attendees solve it working in pairs, with the navigator VERY strictly enforcing this micro-process:
1) write exactly ONE failing test
2) make the test from (1) pass by first writing implementation code IN THE TEST
3) create a new implementation method/function by:
3.1) doing extract method on implementation code created as per (2), or
3.2) moving implementation code as per (2) into an existing implementation method
4) only ever create new methods IN THE TEST CLASS
5) only ever create implementation classes to provide a destination for extracting a method created as per (4).
6) populate implementation classes by doing move method from a test class into them
7) refactor as required
8) go to (1) "
tdd
design
coding
software
testing
kata
refactoring
exercise
1) write exactly ONE failing test
2) make the test from (1) pass by first writing implementation code IN THE TEST
3) create a new implementation method/function by:
3.1) doing extract method on implementation code created as per (2), or
3.2) moving implementation code as per (2) into an existing implementation method
4) only ever create new methods IN THE TEST CLASS
5) only ever create implementation classes to provide a destination for extracting a method created as per (4).
6) populate implementation classes by doing move method from a test class into them
7) refactor as required
8) go to (1) "
march 2010 by rtlechow
related tags
acoustic ⊕ advice ⊕ agile ⊕ analysis ⊕ antipatterns ⊕ app ⊕ architecture ⊕ archive ⊕ art ⊕ audio ⊕ auditory ⊕ background ⊕ best ⊕ bestpractice ⊕ bestpractices ⊕ blocks ⊕ blog ⊕ book ⊕ books ⊕ branch ⊕ browser ⊕ bugtracking ⊕ c ⊕ c++ ⊕ calendar ⊕ canvas ⊕ career ⊕ challenge ⊕ cheatsheet ⊕ checklist ⊕ class ⊕ cocoa ⊕ code ⊕ coding ⊖ collaboration ⊕ community ⊕ competition ⊕ compression ⊕ computer ⊕ computerscience ⊕ conference ⊕ contest ⊕ continuousintegration ⊕ conventions ⊕ cool ⊕ craftsmanship ⊕ cs ⊕ css ⊕ culture ⊕ data ⊕ debug ⊕ debugging ⊕ design ⊕ dev ⊕ developer ⊕ development ⊕ diff ⊕ dna ⊕ documentation ⊕ dojo ⊕ dom ⊕ dvcs ⊕ editor ⊕ erb ⊕ events ⊕ exercise ⊕ faq ⊕ framework ⊕ frameworks ⊕ freelance ⊕ fscript ⊕ fun ⊕ funny ⊕ game ⊕ geek ⊕ git ⊕ github ⊕ google ⊕ gotchas ⊕ graph ⊕ guide ⊕ guidelines ⊕ hack ⊕ hacking ⊕ haskell ⊕ hiring ⊕ howto ⊕ html ⊕ humor ⊕ humour ⊕ idioms ⊕ image ⊕ interesting ⊕ interview ⊕ interviewing ⊕ iphone ⊕ ipod ⊕ javascript ⊕ job ⊕ jobs ⊕ joel ⊕ jquery ⊕ js ⊕ js1k ⊕ kata ⊕ keyboard ⊕ language ⊕ languages ⊕ learning ⊕ libraries ⊕ library ⊕ linguistics ⊕ linux ⊕ lisp ⊕ literacy ⊕ mac ⊕ macosx ⊕ management ⊕ manifesto ⊕ mapping ⊕ math ⊕ mathematics ⊕ merge ⊕ methodology ⊕ mobile ⊕ monad ⊕ monads ⊕ narrative ⊕ network ⊕ objc ⊕ object ⊕ objective-c ⊕ objectivec ⊕ ocaml ⊕ oo ⊕ oop ⊕ opensource ⊕ osx ⊕ patch ⊕ pattern ⊕ performance ⊕ persistence ⊕ philosophy ⊕ phone ⊕ plugins ⊕ practices ⊕ presentation ⊕ problems ⊕ process ⊕ programmers ⊕ programming ⊕ project ⊕ prototype ⊕ python ⊕ quickref ⊕ rails ⊕ read ⊕ reading ⊕ recruiting ⊕ recruitment ⊕ refactoring ⊕ reference ⊕ ror ⊕ ruby ⊕ rubyonrails ⊕ science ⊕ scrum ⊕ senses ⊕ session ⊕ sinatra ⊕ social ⊕ software ⊕ sound ⊕ standards ⊕ story ⊕ style ⊕ styleguide ⊕ tdd ⊕ technology ⊕ testing ⊕ tips ⊕ tools ⊕ tutorial ⊕ tutorials ⊕ unix ⊕ usage ⊕ utilities ⊕ vi ⊕ video ⊕ vim ⊕ visualization ⊕ w3c ⊕ web ⊕ webdesign ⊕ webdev ⊕ wiki ⊕ wikipedia ⊕ workflow ⊕Copy this bookmark: