Thanks to my attendees!

I had a great time sharing with my community colleagues at Tampa Code Camp 2022. My topic was “Getting Started with ReactJS”, and we had an engaging discussion. I’m grateful that my peeps came with excellent questions and points of view. It was A LOT of fun!

As promised, here is the information I presented.
(Pssst! I was able to get it down to around 3MB!) This is a link to a OneDrive share.

Note that you’ll need to run the command npm install on the /talk/my-app folder before you run npm start.

Please reach out to me if you have questions.

See you next time!

Thanks to my attendees!

8 years and counting, and no one ever reacted to this with a “What the heck?!?”?

I ran into an interesting and silly issue today. First, I invite you to form your own opinion about the following block of code.

source:, line 53
 * Returns a Boolean value that indicates whether a value is the reserved value NaN (not a number).
 * @param number A numeric value.
declare function isNaN(number: number): Boolean;

Go ahead — stare at it for a bit. Think about what this function is supposed to do. Read the commented description again. Then stare at it some more. At this point, I’m scratching my head and second guessing myself, with a “What the heck?” thrown in for good measure.

If you haven’t figured out my point yet, consider this: A rock doesn’t need proof that it’s a rock. It simply is. So… if logic serves… why would I need to test a number to see if it’s a number? Kind of defeats the whole purpose, don’t you think?

For you JavaScript purists out there, I get it: There are a thousand ways to write a number in JS. HOWEVER, with Typescript’s “strong typing”, the function ONLY accepts a number. So then what is the point of this function? Exactly — the purpose has been negated. In its current state, this function can only EVER return true. So, pointless.

I figure when I get some time I’ll create a pull request to fix this interface and function, because this is just silly. Please, feel free to beat me to it. Because this is not a good reason to use @ts-ignore.

8 years and counting, and no one ever reacted to this with a “What the heck?!?”?

(JAX) Code Impact 2017

Today I geeked out with some very cool people over at the University of North Florida. Special thanks to Bayer White and his cohorts for putting together a great event full of fun, learning and awesome content.

My talk was of course about Cortana… but a significant break from the regular rhetoric. Today, it was all about Cortana Skills and proof positive that Cortana is/can be useful (and intriguing!) on Android and iOS as well. As promised to those folks who braved my one hour session, here is the slide deck that we covered. Thanks again for attending!

(JAX) Code Impact 2017

Having trouble adding a Developer or Administrator to your Facebook App?

… GRRRRRRR!  Sometimes I really, really, really don’t like how other people make things so hard.

I recently needed to add a colleague as an Administrator on a FB App. Until then he didn’t even have a Facebook account and only created one for this purpose. So, once he verified that he was a real person we thought it would be straight forward to add him.

It wasn’t. Not. No. Never. Not by a long shot.

I’m going to spare you all the gory details (like his account getting deactivated twice and FB constantly logging him out), as well as some lost hair by simply saying this: Make sure that anyone you want to add as a Developer or Administrator to a FB App goes to and creates an app. All you need to do is click the button, provide a bogus name that it will accept, click “Next” and wait for these screen to finish downloading.

Takes about 15 seconds. Not several hours and choice curse words.

For more information, see here:

Having trouble adding a Developer or Administrator to your Facebook App?