handling mistakes in presenting

Yesterday, I gave a presentation to about 30 teenagers about the upcoming FTC (FIRST Tech Challenge) transition from Robot-C to Java. I agreed to do it a week ago while on vacation. This meant I didn’t have any weekend days to actually write up the deck. I wound up doing it the night before. The concepts were fine, but I figured I’d have at least one mistake in the deck.

I proofread the deck in the morning and corrected some errors. But I still felt rushed and like I missed something. I wound up announcing at the beginning that I had two prizes for the first two students who found an error in the presentation. One kid did. (I had a redundant keyword in a method. It wasn’t wrong per se, in that the program still worked. It was non-standard and not what I wanted to show.) This student got a FIRST flashlight in exchange for his finding. Nobody else found an error.

I liked this technique, because I was that kid who saw errors when I was younger (and still do). I was left wondering what I should do with the info. Does the presenter want to know? Should I keep quiet? Will the presentation be given again? By stating that I wanted it brought up early on, there was no doubt. I think it also helped foster a culture of other questions during my presentation because I made it known that I wanted the audience to speak up when a doubt crossed their mind.

I’ve rarely use this technique at Toastmasters because most presentations are shorter and questions aren’t welcome. And when I’m giving a workshop for adults, I feel like they will speak up as needed. It went well though and I’m thinking I might try the “prize” idea again with adults in the future.

Last week, I met the CEO of Communication for Geeks at the NY SPIN where we were both giving 10 minute talks. While none of the above is specific to geeks, it is a nice coincidence that I had an interesting “communication” experience shortly thereafter.

Another interesting thing that happened was that this is the first time I spoke with an ASL interpreter. I only noticed two differences:

  1. The interpreter wanted to see the deck in advance to prepare. (Luckily she only wanted to see it 10 minutes before and not days in advance!)
  2. For the first few minutes, I was worried about talking too fast. I often speak faster than I should when presenting and was worried if I was going to fast for her. The answer was that I wasn’t. I quickly forgot about it. When asking afterwards, she said the pace was fine. I’m impressed with her buffering because she was always a few words (or more) behind where I was! Luckily, I do pause when speaking so there was time to catch up.

 

griping about a “password” system

I emailed a company today asking for my account to be linked. I did NOT ask for a password reset. What I got was an email with plain text copy of my password. Aghhhhh! That’s just asking for someone to hack my account (or all the accounts.) Passwords should be stored using a one way hash at least.

Problem 1 – username

My user id is not my last name, email or anything I have any shot of remembering. And I didn’t get to pick it. Which means it is written down.

Problem 2 – storing the password in plain text

This company shouldn’t be storing passwords in plain text or any “encoding” where they can get the original password. And the only thing I can think of to make that worse is to email the password.

Problem 3 – password requirements

Since my password was sent in the clear, I went to change it. I wanted to make it a sentence about not emailing the password. That way if someone does it again, he/she at least has to read my note. I changed the letter s to $ in my sentence as one might expect. Guess what? Only letters and numbers are allowed.

Really guys? It’s 2015.

using our OCA 8 book to study for the OCA 7?

As of now, Oracle isn’t allowing developers to take the OCA 8 + OCP 7 to get OCPJP 8 certified. This means that some readers who have already bought our OCA 8 book might want to take the OCA 7. (In particular, those who need to get OCPJP certified by September or so and don’t want to take the beta exam.) Those new to Java/certs and just starting out now aren’t likely to find this constraining and can take the OCA 8.

Timeline

I’m predicting the OCP 8 exam will be released in September because:

  • The beta is launching April 25th.
  • I’m guessing they will give two months taking us to June.
  • Then Oracle needs 10 weeks to prepare the real exam taking us to September.

The beta is good because is is $50. It is bad because it is longer and you don’t get your score for months.

How do I “backport” the book for the OCA 7 exam

This matrix compares the OCA 7 and OCA 8 exams. This means you can read the OCA 8 book to study for the OCA 7 exam with the following changes:

  1. Skip the section on dates/times in Chapter 3.
  2. Skip the section on lambdas/predicates in Chapter 4.
  3. Skip the parts about static/default methods in interfaces in Chapter 5.

You’ll slightly overstudy this way. For example, OCA 7 doesn’t ask you to describe encapsulation. But not by any significant amount.

What JDK should I use?

Remember to either use a Java 7 JDK or compile with the -source 1.7 flag. For example:

javac -source 1.7 Jeanne.java

This will ensure you aren’t accidentally relying on a Java 8 feature. For example, the final keyword works a bit differently in Java 8. Not in a way that affects the OCA exam scope. But you could get confused if compiling with a different version