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.

41 Comments - Last Comment @ 2015-08-27

Foxy Checksum

by Remy Porter in CodeSOD on 2015-08-25

Pavel D inherited some… we’ll call it “software”… that helps run warehouse operations for a boiler/heating manufacturer. That software was a Visual FoxPro database.

Now, this application needs to read barcodes off of products in the warehouse. Since the laser-scanners can sometimes mis-read those barcodes, the database uses a custom check-sum algorithm.

55 Comments - Last Comment @ 2015-08-26

Nil, null, nihilism

by Mark Bowytz in Error'd on 2015-08-21

"Figures. A suggestion devoid of meaning," writes Blake R..

67 Comments - Last Comment @ 2015-08-24

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

21 Comments - Last Comment @ 2015-08-20

At Least There's Tests

by Remy Porter in CodeSOD on 2015-08-18

Having automated tests for a project is a good thing, as a general rule. We can debate the broader merits of “TDD”, “ATDD”, “BDD”, “ATBDDSM”, how much test coverage is actually worth having, and if we should view our test approach as a series of metrics that must be met, instead of some guidelines that will help improve our development process.

Our first exhibit today is from Paul. It’s a JUnit test, that, well, maybe misses the point of writing unit tests:

39 Comments - Last Comment @ 2015-08-19
View Article Archives »