I'm not sold on the usefulness of "freeze" to prevent accidental property reassignment, since no exception will be thrown. I think I'd rather take my chances that the reassignment will cause a runtime error. (Better than that though, mark fields as "readonly" in Typescript.)

You forgot to plug your self deprecating marketing udemy course link!

I like crawfords style:

function Human(spec) {
  let {first, last} = spec;

  function sayName() {
    console.log(`My name is ${first}.`);
  }

  return Object.freeze({
    sayName
  });
}

let person = Human({"first": "Foo", "last":"Bar"});
person.sayName(); // My name is foo
console.log(person.name); // "undefined"
person.name = "Riley"; // Can't add property name, object is not extensible