I’m solving a variation of the Knight’s Tour Problem [1] with a little home coding project. I know the best way to solve this problem is a recursive function call. I also know the problem I’m trying to solve has three times the number of possibles at each stop. It’s a damn hairy recursive function.…
My favoritest thing about Linq is that no one around here writes it natively. It always ends up in the code base via Resharper translating a block foreach and if/else statements. It looks awesome and is totally terse. Unfortunately, whenever you need to refactor that Linq statement the first thing you end up doing is…
The saddest commit message ever: Punting BugzID:XXX-NNNN On the other hand, I’m going home this evening.
http://xkcd.com/1421/
ESPN is locking down their public API effective December of this year. While I never did more than plonk against it, that was because the functionality was exceptionally limited. I understand that they’re sitting on a goldmine of stats and information but there is a whole mess of potentially awesome applications that could be developed…
“OH HAI! The process to perform incremental testing is taking several minutes per iteration. This sucks! Automate this!” “Automation totally rocks! The process to perform incremental testing is now only about a minute.” [some period of time lapses] “OH HAI! The process to perform incremental testing is taking a whole minute per iteration. This sucks!…
A thing I’m working on is supposed to interact with a Scheduled Task [1] if it exists. Instead of writing out my own parser for this backwater of the Windows operating system I found something lying about at CodePlex [2]. As far as documentation goes, this one is pretty decent [3]…for a CodePlex project. Then…
At turns comforting and horrifying: Programming Sucks [1] [1] http://stilldrinking.org/programming-sucks
It pleases me greatly that the vending machine at work’s row arrays have zero-based indexing.