Not naming my first born son after me.
A 33-year-old father of three just shattered a family tradition that dates back to the 1800s, and the fallout has been epic. His dad had drilled it into him since childhood: the firstborn son must carry the same name, sealed with a signature in an antique family bible. But this guy never vibed with his father, and the idea of turning every holiday into a roll-call nightmare felt absurd. So he and his wife picked a fresh name for their baby boy.
Cue the dramatic silence—invites stopped, phones went cold, and the entire clan basically excommunicated them over a name. The internet exploded with opinions on whether he’s the villain or the hero of his own story.

‘Not naming my first born son after me.’
The saga kicks off with a centuries-old expectation that’s practically carved in stone—or at least inked in faded scripture.


Personal feelings and practical headaches collided in one decisive moment.




A quick edit shows the flood of support that rolled in.

Centuries-old naming rituals sound noble on paper, yet they can turn into emotional handcuffs when family ties are already strained.
This dad rejected the chain for two solid reasons: a rocky relationship with his own father and the everyday chaos of identical names. The family’s nuclear response—total radio silence—proves they value the ritual over the people in it. Modern society increasingly celebrates unique identities for kids, seeing forced legacy names as more burden than blessing.
Family psychologist Dr. Eileen Kennedy-Moore wrote in Psychology Today (2022): “Naming a child after a relative can honor heritage, but forcing it when there’s unresolved conflict often creates pressure rather than pride.”
Practical advice? Double down on the choice. Build new holiday traditions with your wife and kids—think matching pajamas and zero confusion at the dinner table. If reconciliation ever feels right, mail a grandkid photo with a simple “We love you” note. Let the bible stay in the past; your family’s future is yours to write.
Here’s what Redditors had to say:
The online crowd turned this into a full-blown roast of outdated traditions, with zero chill for the dramatic relatives.
Commenters cheered the escape plan, insisting toxic relatives aren’t worth a signature line.

![[Reddit User] − I also didn’t name my son after myself- I’m an alright guy but one of me is plenty. He has his own name so that he can...](https://en.aubtu.biz/wp-content/uploads/2025/10/wp-editor-1761613958190-2.webp)


Folks dragged the relatives for prioritizing ink over actual humans.




Savage one-liners mocked the absurdity of bible-thumping name police.

![[Reddit User] − NTA. I think naming your child after yourself is stupid and egotistical. But even if you're cool with it, this is your child, you can name them...](https://en.aubtu.biz/wp-content/uploads/2025/10/wp-editor-1761614079197-2.webp)

Breaking the chain freed this dad from a legacy of resentment and gifted his son a clean slate. Key takeaway: traditions shine brightest when they’re chosen, not enforced. Cherish the people who stick around for you, not your label.
Would you keep a family naming tradition alive or burn the rulebook? Drop your stories below!
