Harvard Material

Knicks lost. Do I care. I bothered to watch the broadcast, and get swept up in the excitement.

Anyway, why I'm here - what would it take to never have to babysit an update again? How could we have our software transparently swap in new modules / components / dependencies / etc without needing a handler?

I struggle with the chat interface - the agent dumps so much material, and I have to recall it while asking questions and clarifications.

How does anyone form an original, defensible opinion about anything? Religion sells the idea that the answers can be found in the book, at the end of the chapter, sometimes. But what does it take to look at a situation and have an informed opinion? How do I look at a problem, and rather than bash my head against it, step back and see where the barriers are? How do I modulate the desperate urge to survive, by doing the "necessary thing," no matter the cost? The belief that I have to push through, mindlessly. This might be good in the beginning, as a survival tactic, but what comes next, when you don't die? You survived - what now?

We're looking for a new fit, sure we can squeeze in or through, but when we're changing shape, where does it chaffe? Where does it constrict and limit our motion? What isn't obvious or clear?

Not knowing the answer isn't strictly a sign of ignorance - but you have to write the story. Sometimes it highlights the limits or shortcomings, the blind spots. Is the truck driver stupid because he can't see around corners?

We should be ashamed that most students aren't Harvard material.But we quickly write it off as a moral failing - the student was lazy, or indifferent. It wasn't that our process failed to create successful pupils, that our learning apparatus is defective, and we've framed a success rate less than 5% as a mark of excellence, rather than a sign that something is wildly ineffective.

Maybe deliberately so.