So I do have kind of an extensive questionnaire, so we just touch on a few things, but one thing I think first and foremost is, what are your values? And I think it's really essential to do some sort of values clarification exercise. You can find a ton of them online. You can find a list of values and just pull out your core values and just compare them with each other because when you are aligned, it's great. Or when you're adjacent, it's also great. I might care a lot about excellence, Lenny, you might care a lot about learning. Fantastic. Those are great values that we can kind of, go together. I might care about excellence and you might care about work-life balance. Wow, let's talk about that because I think it's going to be really important as we go through our startup journey that we understand both of us, what does work-life balance mean and what does excellence mean?

One of the founders I worked with, he would text or Slack his co-founder on weekends and the co-founder wouldn't respond. And that was extremely frustrating to the person, to the co-founder I was talking to. And it turned out, after they finally addressed it, it really was about wanting to have some downtime and some, quote unquote, "Balance."

I'm so great at bringing things up." But the person who's close to you might say, "You seethe until you're ready to bring something up and it's really uncomfortable in the seething period." So it just gives you a little more self-awareness about how you actually handle conflict.

The other person might be a person who totally wants to talk about the conflict but wants to let it settle first and wants to also go through their own thinking process about what's important to them and might actually feel like they've resolved it themselves without having to have a conversation with you.

And if you're the person who's like, "Let's talk about it, let's talk about it, let's talk about it." And they're like, "I'm working through it myself." Now you have conflict over the conflict and it just turns into dynamic that's not necessary.

the early television speaker technology was closer in design to a telephone: built to maximize vocal range over other things. But in Cinema we’re a lot more free. This was mixed in Dolby Atmos, native. So sound was always a very key strategy.

I think TV is so dialogue-driven because in the early days, you couldn’t really have very cinematic images. You’re just looking at a small screen. What are you gonna do? You gotta tell me the story with talking.

our aim in Dune, which is a vast ensemble piece with a complex story and complex backgrounds and Frank Herbert’s almost fractal approach to storytelling, we had to have utter clarity and delivery of ideas.

There’s been some recent discussion about burdensome amounts of dialogue in film because of the influence of Television. From my background in Britain, it’s probably something I recognize more as the heritage of Radio and Theater rather than Television.

What’s the pace, the overall pace of a film? When I say pace, I don’t just mean how fast the cuts are. I mean what is moving you, underneath? What is the big drive in the story and how do we cross-cut those? If you cut off the flow too soon, it’s just an age old editing conundrum.  In TV often – Mad Men for example is constantly doing the Chinese plate trick of going between different story strands, keeping each plate spinning, and that works in TV because of the medium.

in a feature film where you want a strong feeling of drive, it’s sometimes a better idea to kind of combine stories or to let them flow. I’m basically playing with Paul’s story, the Harkonnen story, and on Jessica laying “the Way." Irulan’s diaries always gave us an opportunity to clarify their progress. And to that end, Denis shot a beautiful amount of material of the diary room.

There wer so many more angles than we needed because he knew that we might need to improvise one [a diary scene] and we did.

Designers move from idea to a wireframe, a prototype, a logo, or even just a drawing. Developers move from a problem or feature to a coded solution that is solved and released. Both are creative, both are in aid of the end-user. The Design Engineer role is also creative and authors code but systematically translates a design towards implementation in a structured way.  I have never worked anywhere where there wasn't someone trying to close the gap. This role is often filled in accidentally, and companies are totally unaware of the need. Recruiters have never heard of it, and IT consultancies don't have the capability in their roster. We now name the role "Design Engineer" because the gap is widening, and the role has become too complex to not exist.