DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. AI/ML
  4. The Third Time Often is the Charm

The Third Time Often is the Charm

Zone Leader John Vester examines the often used phrase "third time's the charm" to understand if there is more to the story.

John Vester user avatar by
John Vester
CORE ·
Apr. 05, 16 · Opinion
Like (4)
Save
Tweet
Share
2.65K Views

Join the DZone community and get the full member experience.

Join For Free

The expression “the third time’s the charm” references the concept of eventually reaching the *right* solution after a some unsuccessful attempts.  Believe it or not, the neurons in the decision-maker’s brain could be influencing the decision more than one might expect.

As an example, let’s assume that upon analyzing the current state of an application, you architect/design enhancements to resolve issues that either a) currently exist, b) may surface down the road, or c) both.  However, after presenting your ideas, the decision-maker decides to forgo implementing your recommendation.

Now, let’s assume that over time the decision-maker receives similar (if not the exact same) recommendations by other individuals experienced with the application.  Often times this happens after the original architect/designer (“you” in the example above) has moved on to other tasks and responsibilities.  In more cases than not, the decision-maker accepts the recommendation after hearing the same suggestion multiple times.

Initially, I planned to focus on how often I have witnessed this scenario during my career. (Keep in mind, the majority of times that I have seen this happen I have merely been a casual observer.)  My goal was to relay the message that this situation still exists.  Instead, I decided to take things a step further — to try to see if I could figure out why this pattern has continued to repeat itself over the years.

A few years ago, Tübingen neuroscientists concluded that decision-making processes are influenced by neurons in our brain.  They cited the simple of example of how the brain reacts when seeing someone on the other side of the street who resembles an old friend.    The neurons in our brain often use the memories of the relationship from the look-a-like friend to determine how we will react when our paths cross with the individual on the other side of the street.

In our example, when the decision-maker realizes that the same information is being presented, it brings up memories of the prior recommendations that were suggested.  These memories eventually alter the decision in favor of implementing the design enhancements.  As a result, your long overdue recommendation is finally about to be put into place.

During the course of my career, I have experienced being the person making the recommendation and also the person repeating past recommendations which were eventually accepted.  Interestingly enough, it seems like the original architect/designer often receives the label as being “on the bleeding edge” or maybe even “too aggressive.”  While, the individual delivering the recommendation on the time that it is accepted by the decision-maker seems to always receive the label of “hero.”

It is common to focus on the lost time and additional efforts required to convince the decision-maker to finally accept your recommendations.  However, stepping back and looking at things from a higher level, everyone involved should feel proud that the needed enhancements were eventually accepted.

Charm (programming language) Brain (computer virus) application Memory (storage engine) neural network career React (JavaScript library) Label Concept (generic programming)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • PHP vs React
  • Building a Scalable Search Architecture
  • How to Quickly Build an Audio Editor With UI
  • Top 5 Node.js REST API Frameworks

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: