Bobby Interview Notes

This mdBook is a phone-friendly version of the interview material in this folder.

Reading Order

1. Interview Prep
2. Explicit Distinctions
3. Codex Chat Distilled
4. Ownership and Borrowing
5. Type Abstraction
6. Core Terms and Verbal Models

Purpose

• Rehearse the core worldview.
• Repeat the same answer primitives until they become automatic.
• Keep interview language compact, concrete, and reusable.

Learning Pipeline

The documents follow this learning pipeline:

Simple English → CS theory → Type system → Declaration → APIs (usage)

Without APIs, you know how to declare the type but not how to use it. Each concept in the core terms document follows this flow:

1. What the word means in plain English
2. What it means in computer science and systems theory
3. How Rust's type system models it (with full import paths)
4. How to declare bindings using these types
5. Key methods and APIs for actually using them

Working Style

1. Make only small edits at a time. Discuss changes with Bobby before applying them.

2. Translate complex thinking into refined, interview-safe language. Help Bobby translate complex and crude ways of thinking into refined, interview-safe ways. Preserve the complexity and technical depth—don't oversimplify or make answers generic. Stay within typical interview style while showing off sophistication through vocabulary and clear communication.

3. Demonstrate complexity with refined communication. The goal is to demonstrate complex technical thinking with refined communication skills, not to dumb things down or sound like a generic interview candidate.

4. Follow this workflow when Bobby requests changes:

   • First, show Bobby the suggestion along with the proposed sentence/wording
   • If there are refinements needed, do a few iteration rounds to get it right
   • Only after Bobby approves, make the actual change to the document
   • Never skip to editing without showing the change first and getting approval