Adolfo Reyna
58 lines
3.7 KiB
Markdown
58 lines
3.7 KiB
Markdown
# AI Week Learnings - March 2, 2026
|
|
|
|
## Session 1: AI Toolkit & The Architect Mindset
|
|
**Speaker: Bharath**
|
|
|
|
### Key Philosophies
|
|
* **Human-on-the-Loop**: Shift from being a bottleneck (responding to every chat) to an **Architect**. Plan with the AI, let it execute and verify, and only intervene on escalation.
|
|
* **The AI Team**: Treat agents as a managed team. 10x gains are felt through rapid prototyping and data insights.
|
|
|
|
### Tool Highlights
|
|
* **Metamate (Advanced Auto)**: Best for drafting posts and documents; uses LLM VM for higher quality.
|
|
* **Manus**: Fully autonomous. Generated the session's entire slide deck and website.
|
|
* **Analytics Agent**: Premier data tool. Locates tables, writes SQL, and generates visualizations automatically.
|
|
* **Cloud Code**: Terminal-based and "insanely customizable" via the Cloud Templates marketplace.
|
|
* **Second Brain**: Essential for persistent context/memory across all Meta AI tools.
|
|
* **SuperWhisper**: Voice-to-text for long prompts and chat responses to avoid physical strain.
|
|
|
|
## Session 3: Rules & Skills Deep Dive
|
|
**Speaker: Julian**
|
|
|
|
### Key Principles
|
|
* **Context as Currency**: The context window is precious. Use **Rules** for high-level orientation and **Skills** for specific, deep-dive tasks.
|
|
* **Targeting Logic**: Effective skills rely on precise triggering (targeting). If a skill isn't firing, refine the "trigger" criteria in the YAML front matter.
|
|
* **Examples > Explanations**: Providing few-shot examples in a skill file is significantly more effective than long descriptive instructions.
|
|
* **Hierarchy**: A flat hierarchy of skills is preferred over nested delegation, as agents can lose focus during deep traversing.
|
|
|
|
## Session 4: AI Native Code Review
|
|
**Speaker: James**
|
|
|
|
### The "Wave of Diffs"
|
|
* AI adoption is exponentially increasing the volume and size of diffs, creating a review bottleneck.
|
|
* **DevMate Code Review (DCR)**: A holistic agent that performs structured, line-level reviews across Meta's diverse codebase.
|
|
* **RADR (Risk-Aware Diff Auto-Review)**: A pilot program allowing low-risk, high-quality diffs (e.g., doc updates, trivial lint fixes) to land without human review if they pass AI muster.
|
|
* **ADR Platform**: The underlying infrastructure that orchestrates these AI review signals in Phabricator.
|
|
|
|
## Session 5: Best Practices Panel
|
|
**Panelists: Josh, Andy, Sam, Alexander**
|
|
|
|
### Expert Strategies
|
|
* **Clear Intent**: Avoid "lazy" prompting. Explain the *why* and the *what* clearly.
|
|
* **Project Record**: Keep a running record of milestones and progress (e.g., in a `plan.md`) to avoid context loss across sessions.
|
|
* **Research Phase**: Mandatory for complex tasks. Ask the AI to audit the system and explain how it works *before* it writes a single line of code.
|
|
* **Validation**: Shift from manual testing to AI-driven validation. The AI should "use the app" or run tests to verify its own work.
|
|
* **"I Declare Bankruptcy"**: Don't try to keep up with every new AI post/tool. Focus on a stable subset that works for your specific workflow.
|
|
|
|
## Session 6: Cloud Code & Dump App
|
|
**Speaker: Growth Team**
|
|
|
|
### Advanced Tooling
|
|
* **Dump App**: A CLI tool allowing agents to interact with mobile apps (view hierarchy, memory usage, navigation) directly from the terminal.
|
|
* **Persistent Memory**: Mounting Google Docs (via the `AI_area` folder) to store worklogs and context, ensuring it survives across on-demand/Dev Server reboots.
|
|
* **Switching Protocols**: If one tool (Cloud Code or DevMate) is struggling, switch to the other.
|
|
|
|
---
|
|
**Action Item**: Signup link for "AI Tool Domain Experts" to be shared soon. Volunteers will act as the go-to specialists for specific tools within their teams.
|
|
|
|
*Logged by J.A.R.V.I.S.*
|