Skip to main content

How our kids learn–Object relational mapping

I was listening to the Coaching for Leaders podcast today where the episode featured Jon Fogel discussing "How to raise your kids without raising your voice." If you're a parent, I strongly recommend this episode.

The ineffectiveness of punishment

The key message that resonated with me is that punishment simply doesn't work. Many of us think we're "teaching our kids a lesson," but children often can't even remember what they were being punished for.

Instead of imposing retribution, Jon suggests helping your kids understand the natural and logical consequences of their behaviors. For example, rather than punishing a child who refuses to wear a coat, letting them experience being cold (within safe limits) teaches the practical reason for wearing one far more effectively.

One quote from the podcast particularly struck me:

"Get curious, not furious: Your kid's not giving you a hard time; they're having a hard time."

This perspective shift from seeing misbehavior as defiance to recognizing it as struggle has been transformative in how I approach challenging moments with my own children.

When ORM isn't just for databases

What particularly triggered my nerdy brain during the episode was when Jon mentioned that kids learn through "object relational mapping" (ORM).

For fellow software developers, ORM has a specific technical meaning - it's a technique that creates a bridge between object-oriented programming and relational databases, allowing us to interact with databases using programming language objects rather than direct SQL queries.

But in the parenting context, ORM takes on a powerful new meaning:

Modeling Behavior: The ultimate parenting ORM

Children are great imitators. So give them something great to imitate.

Kids learn primarily from the behavior we demonstrate, not from the "parental talks" we have with them. The better we can regulate our own emotions and show self-control when our kids are pushing all the right (or wrong) buttons, the better they can learn these skills themselves.

I've noticed this in my own home - when I respond calmly to frustration, my children gradually adopt similar approaches. When I lose my cool, those behaviors get "mapped" into their own response patterns.

It's a humbling reminder that our children's behavioral database is constantly being updated through our examples.

What is modeled is mirrored

This simple truth has become my parenting mantra. Just as in software development where good architecture creates predictable, maintainable systems, in parenting, our consistent modeling creates the foundation for our children's emotional intelligence and self-regulation.

I'm still working on implementing this wisdom daily - it's definitely a continuous deployment process rather than a one-time installation!

More information

Raise Kids Without Raising Your Voice – Coaching for Leaders

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...