Comments on: JavaBat

By: Kevin W

Kevin W — Wed, 03 Jun 2009 00:07:00 +0000

The Javabat problems aren’t difficult until Array 3s, String3s, and Recursion 2s. Of course I do still have a few Recursion 1s that are incomplete, but I am working on them.

They definitely do get you thinking analytically, but at the same time, help you look at the possible ways of solving these problems MULTIPLE ways. I feel as though the final problems, as I’m getting down to the last 20 or so, are beginning to cause a bit of aggravation, and therefore causing me to just work on the RPG I’m working on instead…Haha.

By: Ben Chun

Ben Chun — Sun, 27 Jan 2008 17:29:31 +0000

I see your point, Dad… I guess I was just thinking that if I’m getting stuck or puzzling on some of these problems, how hard will they be for students? Pretty hard, I’ll bet. In a real-life coding situation, you’d never deny yourself the ability to use output to help debugging and development. I want to be sure that students don’t feel that programming requires you to be a genius — because it doesn’t. Just methodical patience and analytical thinking.

Using output is a little different than just “going by what the computer says” because the programmer has to decide what to output. Maybe the best analogy is that your [emissions system] warnings are like compiler errors, which JavaBat does provide. Fortunately, the compiler is a bit more informative than a car’s onboard diagnostics! Funny story, by the way…

By: Dad

Dad — Sun, 27 Jan 2008 17:11:57 +0000

First, congratulations on your AP assignment.

re: cheating or working smart …
The check engine light for the Subaru lead to a visit with the ‘automotive technician’.
“Computer diagnostic say [emissions system] so we’re going to change the oxygen sensor and then do a tailpipe check.” Even though 3 months ago it passed the state mandated biannual smog check.

That was good for about 150 miles until the light signaled again …
“Computer diagnostics say [emissions system] so we’re going to do a complete service and do a tailpipe check since you’re only a few thousand miles from your major service and it could just need it early”.

That was good for about 150 miles until the light signaled again …
“Computer diagnostics say [emissions system] but since everything is running ok we think its just the computer code and you should just ignore it; we reset the computer and maybe we’ll just change the gas cap – it could not be sealing right”

That was good for about 150 miles and …
“Computer diagnostics say [emissions]”
-customer- “I noticed a small tube next to the gas intake that is loose”
-service technician- “I’ll have the supervisor look at it”
-supervisor- “We had a guy go under the car and tighten the clamp to the tube”

That has been good for the last 35,000 miles