Recent Bring Your Own Code
The goal of BYOC is simple: provide an outlet for you, the enquiring software developer, to sharpen your programming skills on a problem a bit more interesting than the normal, boring stuff. That, and to put your code where you mouth is, so to say.
A Fever on a Crappy Day
by Remy Porter
in Bring Your Own Code
on 2015-08-26
It feels like forever ago, we introduced the Lucky Deuce casino contest. This is a series of challenges, brought to you by our pals over at Infragistics, where we call on you to help us build a “scoundrel’s casino”. We are nearing the end of this little BYOC contest- this week is our last "all original" round, and next week, we'll introduce one final challenge that leverages code you may have already written for this contest.
Last week, you had a tricky little problem: you needed to write some code that looked like it was going to cheat, but really would get the cheater caught.
The Lucky Deuce: In the Cards
by Remy Porter
in Bring Your Own Code
on 2015-08-19
Two weeks back, we introduced the Lucky Deuce casino contest. This is a series of challenges, brought to you by our pals over at Infragistics, where we call on you to help us build a “scoundrel’s casino”.
Last Week, you were again given some vague requirements, this time for building a broken slot machine. Once again, we had some seriously great submissions. Like last week, I’ve rehosted the winning code here.
Honorable Mentions
The Lucky Deuce: Getting in the Slot
by Remy Porter
in Bring Your Own Code
on 2015-08-12
Last week, we introduced the Lucky Deuce casino contest. This is a series of challenges, brought to you by our pals over at Infragistics, where we call on you to help us build a “scoundrel’s casino”.
Last week’s challenge was to build a “broken” roulette wheel, that instead of being truly random, avoids recently spun numbers to “feel” more random. I’ve rehosted all of the winners’ code here.
Honorable Mentions
Introducing the Lucky Deuce
by Remy Porter
in Bring Your Own Code
on 2015-08-05
The life of a developer is about being cunning. When presented a problem that could be solved with strenuous, character-building labor, our first instinct is to automate it and cheat our way around it, if at all possible.
Or maybe I’m just projecting. Still, if there’s one thing I’ve noticed, TDWTF readers are a shifty lot of scoundrels. It’s time for us to put that cunning to work.
Forums
Jul 15