algorithmic_thinking (@algorithmthink) header
algorithmic_thinking (@algorithmthink) profile picture
Köln, Deutschland
Joined February 2017
Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)Photo by algorithmic_thinking (@algorithmthink)
algorithmic_thinking retweeted
15 best #AI #researchers on X:
list of 15 best AI researchers on X: 1. @karpathy — Andrej Karpathy 2. @rasbt — Sebastian Raschka 3. @AndrewYNg — Andrew Ng 4. @drfeifei — Fei-Fei Li 5. @demishassabis — Demis Hassabis 6. @GaryMarcus — Gary Marcus 7. @ai_explorer25 — AI Explorer 8. @maximelabonne — Maxime Labonne 9. @chipro— Chip Huyen 10. @ilyasut— Ilya Sutskever 11. @thsottiaux — Thibault "Tibo" Sottiaux 12. @bcherny — Boris Cherny 13. @geoffreyhinton — Geoffrey Hinton 14. @JeffDean — Jeff Dean 15. @fchollet — François Chollet
1
1
22
algorithmic_thinking retweeted
The #SecondBrain Guide: How to Stop Re-Explaining Yourself to #Claude
It’s getting f*cking ridiculous: people are still building their Claude second brain by hand while Obsidian’s own CEO already open-sourced the shortcut 4 repos that do the setup for you, all checked on GitHub: → obsidian skills by kepano, Obsidian’s CEO. 49.8K stars. teaches Claude how Obsidian actually works → claude obsidian. 15K stars. wiki, ingest, query and lint as ready-made commands → obsidian second brain. 4.8K stars, 48 commands, runs in Claude Code, Codex and Gemini → second brain starter. interviews you and writes a 9-phase build plan for your exact setup half the guides going around still quote old star counts and an install script that doesn’t even exist anymore the full guide is in the article below, install commands included save it so you don’t lose it
1
1
62
algorithmic_thinking retweeted
#Karpathy-Style #Knowledge Stack with #opensource tools
Karpathy sketched the second brain. these 7 open-source repos already built it for Obsidian + Claude Code 250,000+ GitHub stars between them, and every one is free to clone sorted by stars: 1. graphify - 134k stars turns your codebase, docs, SQL schemas and PDFs into one knowledge graph you can query ↳ github.com/Graphify-Labs/gra… 2. Understand-Anything - 88k stars maps any codebase into an interactive knowledge graph you can click through ↳ github.com/Egonex-AI/Underst… 3. claude-obsidian - 15.8k stars a second brain that organizes itself: drop in a source, Claude Code files it ↳ github.com/AgriciDaniel/clau… 4. obsidian-second-brain - 4.9k stars long-term memory for Claude Code, stored as plain markdown in your vault ↳ github.com/eugeniughelbur/ob… 5. mcp-obsidian - 4.5k stars one MCP server and Claude can read, search and write your whole vault ↳ github.com/MarkusPfundstein/… 6. claudesidian - 2.6k stars a starter vault designed around Claude Code from the first note ↳ github.com/heyitsnoah/claude… 7. second-brain - 756 stars an Obsidian wiki the model keeps up to date, built on Karpathy's LLM Wiki pattern ↳ github.com/NicholasSpisak/se… where to start: > your knowledge lives in code -> graphify > your knowledge lives in Obsidian -> claude-obsidian > you just want Claude to remember -> obsidian-second-brain > you live in Claude Desktop -> mcp-obsidian the skills that sit on top of all seven are in the full map below ↓
1
1
35
algorithmic_thinking retweeted
"Mathematical Introduction to Deep Learning: Methods, Implementations, and Theory" Download 737-page PDF at arxiv.org/pdf/2310.20360
1
40
257
8,670
algorithmic_thinking retweeted
Applied Methods in the Theory of #Nonlinear #Oscillations by V. M. Starzhinskii. aimed at engineers with a strong mathematical background, scientists working in #mechanics, applied #mathematics and #physics #soviet #mir mirtitles.org/2018/05/25/app…
10
13
111
2,004
algorithmic_thinking retweeted
Mathematics algorithm SVM (Support Vector Machine) is a classic nonlinear classifier in Machine Learning. Download 640-page PDF "Learning with Kernels: Support Vector Machines, Regularization, Optimization, and Beyond" here: mcube.lab.nycu.edu.tw/~cfung…
1
50
1
333
14,465
algorithmic_thinking retweeted
25
147
10
1,258
43,980
algorithmic_thinking retweeted
24
191
12
1,903
37,307
algorithmic_thinking retweeted
Explore this huge curated collection of some of the best mathematics books ever written — spans classical foundations, probability, analysis, geometry, and problem-solving texts used by mathematicians, scientists, engineers, & AI researchers: github.com/valeman/Awesome_M… The list is organized by these topics: Math Machine Learning Physics Econometrics Optimization Information Theory Signal Processing History Probability
1
40
261
10,260
algorithmic_thinking retweeted
📚 Open Access (free) Kockelman, P. (2025). Mathematical Models of Meaning: A Dynamical Systems Approach to Possible World Semiotics. MIT Press. doi.org/10.7551/mitpress/156…
11
103
9
666
19,025
algorithmic_thinking retweeted
Education isn’t about knowing everything. It’s about understanding that there is always more to learn and discover.
58
654
26
3,612
98,763
algorithmic_thinking retweeted
#DeepLearning with PyTorch... 1) Cheat sheet [PDF]: dropbox.com/scl/fi/e4xngykrf… 2) Learn fundamentals with hands-on coding [PDF]:  dropbox.com/scl/fi/lfo7r6fnd… 3) #GenerativeAI with Python and PyTorch: amzn.to/4fYjiBn book v/ @PacktDataML
2
54
278
11,307
algorithmic_thinking retweeted
#STEM in #China 🇨🇳 🚀
You can now earn a PhD in China by creating a product instead of writing a 100-page dissertation! China has grown tired of PhD students writing research papers that no one reads and is now demanding that they build real products instead. This radical shift in the philosophy of higher education in China represents a formal transition from "textual academia" to "utilitarian academia," where the traditional doctoral dissertation is replaced by the creation of a tangible product. The brilliance of this idea lies in its direct approach to the scourge of "dead research" that consumes years of researchers' efforts only to remain locked away in drawers, thus transforming the university from an intellectual silo into a productive engine that feeds the market and fosters innovation immediately.
1
1
11
algorithmic_thinking retweeted
Noether's Theorem is arguably the single most elegant bridge between symmetry and conservation in physics, showing that deep symmetries aren't optional, they dictate what must be preserved. It was discovered by Emmy Noether in 1918 (published amid World War I chaos, her work initially overlooked due to gender barriers), it states: Every continuous symmetry of the action (a functional encoding the system's dynamics) corresponds to a conserved quantity. Time-translation symmetry → energy conservation; spatial-translation symmetry → momentum conservation; rotational symmetry → angular momentum conservation. This theorem flips causality: conservation laws aren't primitive observations or axioms they're inevitable mathematical consequences of nature's indifference to when/where/how we look at a system. Rationality upgrade: our "priors" about why things like energy don't just vanish aren't ad hoc; they're tied to timeless symmetries. Breaking a symmetry (e.g., in the early universe or particle physics) means the corresponding conservation fails, explaining phenomena like baryogenesis. Noether, a brilliant algebraist forced to lecture under Hilbert's name at Göttingen, proved this at Einstein's urging her result underpins virtually all modern theoretical physics, from quantum field theory to general relativity. Without it, we'd treat conservation as empirical coincidence rather than deep necessity.
12
73
1
367
10,963
algorithmic_thinking retweeted
I think it must be a very interesting time to be in programming languages and formal methods because LLMs change the whole constraints landscape of software completely. Hints of this can already be seen, e.g. in the rising momentum behind porting C to Rust or the growing interest in upgrading legacy code bases in COBOL or etc. In particular, LLMs are *especially* good at translation compared to de-novo generation because 1) the original code base acts as a kind of highly detailed prompt, and 2) as a reference to write concrete tests with respect to. That said, even Rust is nowhere near optimal for LLMs as a target language. What kind of language is optimal? What concessions (if any) are still carved out for humans? Incredibly interesting new questions and opportunities. It feels likely that we'll end up re-writing large fractions of all software ever written many times over.
Shifting structures in a software world dominated by AI. Some first-order reflections (TL;DR at the end): Reducing software supply chains, the return of software monoliths – When rewriting code and understanding large foreign codebases becomes cheap, the incentive to rely on deep dependency trees collapses. Writing from scratch ¹ or extracting the relevant parts from another library is far easier when you can simply ask a code agent to handle it, rather than spending countless nights diving into an unfamiliar codebase. The reasons to reduce dependencies are compelling: a smaller attack surface for supply chain threats, smaller packaged software, improved performance, and faster boot times. By leveraging the tireless stamina of LLMs, the dream of coding an entire app from bare-metal considerations all the way up is becoming realistic. End of the Lindy effect – The Lindy effect holds that things which have been around for a long time are there for good reason and will likely continue to persist. It's related to Chesterton's fence: before removing something, you should first understand why it exists, which means removal always carries a cost. But in a world where software can be developed from first principles and understood by a tireless agent, this logic weakens. Older codebases can be explored at will; long-standing software can be replaced with far less friction. A codebase can be fully rewritten in a new language. ² Legacy software can be carefully studied and updated in situations where humans would have given up long ago. The catch: unknown unknowns remain unknown. The true extent of AI's impact will hinge on whether complete coverage of testing, edge cases, and formal verification is achievable. In an AI-dominated world, formal verification isn't optional—it's essential. The case for strongly typed languages – Historically, programming language adoption has been driven largely by human psychology and social dynamics. A language's success depended on a mix of factors: individual considerations like being easy to learn and simple to write correctly; community effects like how active and welcoming a community was, which in turn shaped how fast its ecosystem would grow; and fundamental properties like provable correctness, formal verification, and striking the right balance between dynamic and static checks—between the freedom to write anything and the discipline of guarding against edge cases and attacks. As the human factor diminishes, these dynamics will shift. Less dependence on human psychology will favor strongly typed, formally verifiable and/or high performance languages.³ These are often harder for humans to learn, but they're far better suited to LLMs, which thrive on formal verification and reinforcement learning environments. Expect this to reshape which languages dominate. Economic restructuring of open source – For decades, open-source communities have been built around humans finding connection through writing, learning, and using code together. In a world where most code is written—and perhaps more importantly, read—by machines, these incentives will start to break down.⁴ Communities of AIs building libraries and codebases together will likely emerge as a replacement, but such communities will lack the fundamentally human motivations that have driven open source until now. If the future of open-source development becomes largely devoid of humans, alignment of AI models won't just matter—it will be decisive. The future of new languages – Will AI agents face the same tradeoffs we do when developing or adopting new programming languages? Expressiveness vs. simplicity, safety vs. control, performance vs. abstraction, compile time vs. runtime, explicitness vs. conciseness. It's unclear that they will. In the long term, the reasons to create a new programming language will likely diverge significantly from the human-driven motivations of the past. There may well be an optimal programming language for LLMs—and there's no reason to assume it will resemble the ones humans have converged on. TL; DR: - Monoliths return – cheap rewriting kills dependency trees; smaller attack surface, better performance, bare-metal becomes realistic - Lindy effect weakens – legacy code loses its moat, but unknown unknowns persist; formal verification becomes essential - Strongly typed languages rise – human psychology mattered for adoption; now formal verification and RL environments favor types over ergonomics - Open source restructures – human connection drove the community; AI-written/read code breaks those incentives; alignment becomes decisive - New languages diverge – AI may not share our tradeoffs; optimal LLM programming languages may look nothing like what humans converged on ¹ teapaw.org/mntruell/status/201282… ² teapaw.org/anthropicai/status/201… ³ wesmckinney.com/blog/agent-e… ⁴ github.com/tailwindlabs/tail…
680
637
145
7,955
1,211,610
algorithmic_thinking retweeted
The Longest Equation in Physics ✍️
101
299
27
2,331
125,005