JDBC query with bind variables can have performance issue

It seems like I am on a performance kick after finding this note on My Oracle Support "Poor Performance With Query Called From JDBC Using Bind Variables Compared To A DATE Column" from document ID 1557194.1 which teaches us about the reasons a JDBC query might not use the best access path/plan based on what kind of DATE or TIMESTAMP variables you use.

When too many bind variables is a bad thing

It has hardly been a full week, and my streak has been snapped yet again by missing my post last night!  I will fix that with asking if you know how many bind variables make a SQL statement no longer bind sensitive?  Give up?  Obviously the title of this MOS article "SQL Containing More Than 8 Bind Variables is not Marked as Bind Sensitive" from note ID 1983132.1 gives the answer away, but the answer changes for when you try to take advantage of the 12c Adaptive Cursor Sharing option so check out the article!