πŸ’‘ Remember Box
10 subscribers
2.17K photos
29 videos
1.82K files
11.8K links
πŸ“ Interesting articles
πŸ—ž Ideas & TodoπŸ’‘
πŸ‘“ Random stuff
🎢 Music
πŸ€” Thoughts
πŸ“• Books
πŸ“š Courses
πŸ“Ί Videos
πŸ“ Papers
πŸ•Έ Websites/Blogs
πŸŽ™ Podcasts
πŸ„ Spirituality

In the pursuit of excellence!

The aim is to discover interesting ideas and perspectives.
Download Telegram
don't confuse velocity for progress
you can use skills to orchestrate subagents for complex workflows, which is a great way to optimize context since each subagent gets its own. been testing this today and it works really well. you could even wrap the entire skill in a subagent that invokes it to save more session context, though that might reduce visibility into what's happening (haven't tested this). weirdly enough, i was able to package the subagents within the skill itself in a {skill}/agents/ folder, which is not documented anywhere, but it seems to work pretty well
Playwright + Xvfb + FFmpeg
field math -> permutation -> kernel
memory -> hashrate
❀1
The Tip5 Hash Function for Recursive STARKs

https://eprint.iacr.org/2023/107.pdf
❀1😁1
a distribution channel that doesn't require human persuasion
digital markets can be barrierless, permissionless, liquid, global, 24/7 and competitive in ways that legacy systems can't
the final design is the result of eliminating each misconception until only hardware and protocol limits remain
True performance engineering starts with measurement, not theory.