Learning every day. As an API product founder, when I created our MCP I figured, just enable all API actions. But in the MCP world there’s tradeoffs, context size, reasoning ability, etc. So now the default is 17 tools. 56 available at /all if you want everything.

Learning from the western classics: Hypatia of Alexandria - The most powerful philosopher in late antiquity wasn't a monk or a bishop. She was a mathematician who ran her own school, edited Euclid, & taught that the highest activity of the human mind is the contemplation of eternal truths. The mob killed her in 415 CE. Her ideas didn't die. 1. Mathematics as purification. Hypatia taught that geometry/astronomy weren't vocational skills - they were disciplines that elevated the soul from the sensory to the intelligible. The proof was the practice. In an economy optimized for engagement/narrative, mathematical thinking is an act of resistance. The person who can hold a formal proof in their head has a different quality of attention than the person who only consumes argument. 2. The commentary as the highest form of intellect. Hypatia didn't write original treatises. She edited Euclid, clarified Diophantus, improved Ptolemy. Her genius was refinement, not novelty. The obsession with "original thought" is a modern vanity. Most value is created by people who take existing systems, make them coherent enough to use. Founders who can't explain their idea in terms of what already exists usually don't understand it. 3. Public reason has no tribal membership. She taught pagans, Christians, & foreigners alike, admission by merit, not identity. Her school was a neutral ground in a polarized city. Institutions that gatekeep by affiliation rather than capability degrade their own edge. The moment your hiring or investment thesis prioritizes "people like us" over "people who can think," you've exited the game of compounding returns. 4. Influence w/out office is the most dangerous position. Hypatia held no formal power, yet her counsel was sought by the city's prefect. She was killed not for what she did, but for what she represented - independent intellect in a zero-sum political landscape. 5. She built instruments, not just theories. Hypatia designed astrolabes + hydrometers. She didn't separate the contemplative from the practical. The "ideas vs. execution" dichotomy is false. The deepest theorists are usually the best tool-builders cos they understand the underlying structure. If your philosophy doesn't change how you build, it's decoration. 6. Ideas survive through networks, not individuals. None of Hypatia's original writings exist. We know her through her students' letters, through Synesius, through the historian Socrates Scholasticus. Your work will outlast you only if you teach & share knowledge. Build people, not just products. 7. The eternal is not a consolation prize. Neoplatonism held that the intelligible realm is more real than the material. Hypatia lived this w/out retreating into monastery or escapism. She was in the world, teaching in public, designing instruments, engaging w power. You don't need to renounce to be serious. The highest form of detachment is not withdrawal - it's full engagement without clinging. Run the company. Make the trade. And hold it lightly enough that losing it doesn't destroy you. 💙🏃🏻‍♀️🫶🧠🚀

Learning Likkutei Sichos these days with a solid chavrusa has me wondering what exactly we thought we understood as bochurim when we ripped through them. Now, I can barely finish a sicha in under an hour. And if you start with the ha’oros… forget about it.

Learning about the pros and cons of local ai in realtime here benchmarking Glimmer. This will be the first benchmark I run where the cost is $0...but also my first benchmark that will take 1-3 days to complete 👀

Learning coding unlocks new possibilities. Platforms like language apps make it accessible. Learning continues at any age. Education empowers personal and professional growth. It equips people for real-world challenges. 👍 👑 🍀

“Learning how to adjust in college and building financial literacy helps you longer in life.” In this episode of Nasdaq's The Winning Formula, Super Bowl Champions @JasonMcCourty and @DevinMcCourty, discuss the power of the @ProAthleteCom, the importance of financial literacy, and lessons they learned becoming leaders both on and off the field:

# Learning Palantir Foundry 🚀 Answer "where did this dashboard number come from?" in an instant. Data Lineage is an exploration tool that visualizes the entire flow of your data. 📌 Title and Feature URL Title: Data Lineage URL: 📝 Overview Data Lineage is an interactive visualization tool that comprehensively shows how data flows through the Foundry platform. It helps you understand data movement, dependencies, and transformations across your entire data ecosystem. Because you can trace the lineage from sources through pipelines, the Ontology, and apps as a graph, it sharply reduces the cost of incident response and audit explanations. 🔧 How It Works It represents data dependencies through a graph-based visualization. - Find datasets using project names, table identifiers, or row labels, and browse data directly from Foundry Projects - Expand or collapse ancestor (upstream) and descendant (downstream) relationships for any dataset - View multiple table attributes at once, down to schema details, build timestamps, and source code - Apply custom color schemes to highlight pipeline characteristics such as stale datasets - Create shareable pipeline snapshots to communicate within the team 🛠 Practical Usage - Trace upstream from a dashboard or output dataset to pinpoint the source of a number - When an upstream schema changes, trace downstream to map the blast radius - Color-code stale datasets to discover neglected pipelines - Drill down from a high-level overview into granular technical details like transformation code and execution history - Share pipeline snapshots to document data workflows across functions 🎯 Use Cases - Instantly answering "what is the origin of this dashboard's number" - Identifying the impact scope of upstream schema changes in advance to prevent incidents - Presenting data lineage during audits to cut explanation costs - Finding stale or unused datasets to tidy up pipelines ⚠️ Caveats - This overview page does not explicitly discuss performance or graph-complexity constraints with extremely large pipelines - Lineage covers data flow within the Foundry platform; processing outside the platform is out of visualization scope - The accuracy of lineage depends on transforms and pipelines being properly configured within Foundry #PalantirFoundry# #DataLineage#