cho.sh
2,244 notes
Liked on XI made a mistake. When Jack and I decided to organize this $100K Hackathon, my biggest concern was cheating. Unlike a regular hackathon, everyone participates from home. And because the winner is whoever makes the most PROFIT (not revenue), there are so many ways to manipulate the numbers. So I added a $99 entry fee. One thing I’ve learned from building businesses is that people tend to be more committed when they pay for something. I thought it would filter out spam, attract serious builders, and make the competition fairer for everyone. But I completely missed the other side. 3 years ago, I was a living with my apps. Today, I’m financially free. My life changed so much that somewhere along the way, I lost perspective on what $99 means to someone else. For someone in India, someone struggling to pay their bills, or someone trying to make their first dollar online, $99 can be a lot of money. And those are exactly the people I want to help! I’ve spent years sharing what I’ve learned, reviewing random people’s landing pages, and organizing free meetups around the world. Not because there’s money to make, but because I genuinely love seeing people build things and succeed. And somehow, I was so focused on keeping cheaters out that I didn’t realize I was also keeping genuine builders out. That’s my mistake. So I’ve decided to make the $100K Hackathon completely FREE :) Everyone who already paid got a full refund. I’m still worried about cheating. That problem hasn’t disappeared, and Jack and I will have to figure out better ways to verify profits and keep the leaderboard fair. But that’s our problem to solve. Thank you to everyone who shared their thoughts. Sometimes you need people to remind you of things you’ve forgotten. I genuinely hope this hackathon changes someone’s life. ❤️Liked on XIt’s time to bring back Cafe CursorPosted on Xyo @pendev i can't live share edit a .pen file? it's the most needed featurePosted on XI'm coining a word "Agentsplaining" Agents condescendingly assuming the user don't know fuck and repeating the obviousReplied on X@jayhxmo @raycast Hard to explain. It's the small detailsPosted on X@raycast iOS keyboard is insanely good. Might resub Raycast pro just cuz of thisReplied on X@ishuagra02 I saw a theory that F5.2 is a post train of 5.1, but O5.5 is a distillation of F5.5(unreleased new pretrain) and thats why O5.5 > F5.2Liked on X@anaclumos don't know what is actually improved 👀Posted on Xam i the only one underimpressed with 5.2 fableReplied on X@bvvst great minds think alike https://t.co/YRFWhb1mcOLiked on XClaude Fable 5.2 is out and it's the perfect time to run this god-level prompt on your codebase: "I want you to audit our codebase, is anything here unnecessary, overly complicated in our current setup, or based on weak assumptions? Challenge them. - What can be deleted entirely? - What can be simplified now that unnecessary pieces are gone? Then make the changes. Prefer deleting over simplifying, simplifying over optimizing, and optimizing over automating. This product is being used by thousands of customers, do not cut any corners." This prompt is one I run often and leads to the best results.Replied on X@akshayadinesh19 @bot can we please BYOM for botsLiked on XTo be fair, the Chinese models have a much lower refusal rateLiked on XF*CK IT, im creating a library of AI slop indicators. my feed is full of taste larpers. stay tuned https://t.co/5Muv8nQRm3Liked on XJENSEN! THATS NOT WHAT WE MEANT BY CHINESE MODELS!!!!!!!Liked on Xmy parents had to declare bankruptcy when I was a kid, so they had every reason to pressure me towards a more stable career path instead, they were so patient with me, even as i failed startup after startup for years so getting to tell my mom that everything turned out okay was a really special moment :) for those who can't read Korean, her first message roughly translates to: "Really!!! Congratulations my son. So much :') Thank you God!" i know I've been posting about my exit for like a week now, but it really is a big deal for me and my family! i'll share more about how this all happened and some tactical advice later this week, but for now i'm just riding out all the emotions to quote my mom, thank you God!!!!Liked on X@thefarmers_Dog it stands for Egg GzampleLiked on X🦍 Introducing Memorilla: memory as a modality for LLMs Memorilla turns everything a frozen LLM needs to remember into just 16 memory embeddings ⚡ It uses up to 4,212× fewer tokens and is 27× faster than full context inference while more accurate 🎯 Pushes the Pareto frontier over RAG and agentic memory in personalization, long-document and knowledge QA A thread 🧵:Liked on XThere's a huge product opportunity downstream of Tailscale etc too. At @tldraw we've started designing for "high trust networks" and it's been a beautiful thing. 1. Features that would be a nightmare on the internet are okay on my computer and mostly okay on private networks. Websites that execute user-generated scripts, control production systems, allow for users to send desktop notifications, spend tokens, or directly prompt my agent. Crazy stuff that would only make sense if everyone was in a committed polycule. 2. When everyone on the server can be trusted to have _external_ reasons for good behavior (eg keeping their job, or maintaining friends, family, church, mafia org), the software can be designed in a default social way. Most apps default to isolation, low horizontal visibility, highly restricted collaboration. Makes sense if the social contracts are inside of the app, but if you can trust that they live outside of the app then you can get wild. Example being small group chat names as an emergent comedy phenomenon because anyone in the group can change the name. 3. This can work for commercial products, too, not just internal stuff. Security matters more than ever but the way we've seen that manifest is that more companies are more confident in their own solutions than anything we could provide, to the point where owning data and access is a better value proposition than having it managed. Always has been true for big companies but now even small companies can get a good secure network set up pretty easily, and the hooks we need to build are easy enough. tldraw offline got us started down this road (and shout out to @pendev for first introducing me to the idea of desktop + mcp). We've been bringing that product to private networks and it's been exciting to see how much we can get away with. Keep an eye outReplied on X@saradu birds eye viewLiked on XApplications close in 2 days!! If you have a cool bio idea, and $5-10k will go a long way for you, please apply!!! https://t.co/NCvmrNC53cLiked on XWe've been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™. (And it's not Tauri, it's GPUI, so good guess everyone.) Alright, back to staring at the WoW Forever login screen.Reposted on XOh boy. https://t.co/X7SSskGuGvLiked on XRIP .si domain squatters
몬테카를로와 라스베가스 알고리즘

몬테카를로와 라스베가스 알고리즘

Warning

Over a year old. May be outdated

은 많이들 알지만, 이걸 이랑 묶어서 생각하는 사람은 아주 드물다. 이름에서 짐작하듯 둘 다 베팅과 보상에 기대는 알고리즘이다. 근데 나는 이 두 알고리즘이 결국 시간과 정보가 서로 얽혀 있는 우주의 물리적 구조를 슬쩍 보여 주는 것 같고, 시간과 정보를 서로 바꿔 쓸 수 있을지도 모른다는, 말로 설명하기 어려운 느낌이 든다.

몬테카를로 알고리즘은 무작위 샘플링으로 복잡한 문제의 대략적인 답을 구한다. 테이블에 다트를 던진다고 해 보자. 무작위로 백만 개를 던지면 다트는 거의 고르게 흩어진다. 한 점을 골라 원을 그리고 그 안의 다트를 세면, 원과 테이블의 면적 비율을 추정할 수 있다. 거기서 원주율을 추산하는 거다.

라스베가스 알고리즘도 비슷한데, 조금 더 정교하다. 좋은 예가 QuickSort다. QuickSort는 기준점을 무작위로 골라서 기준점보다 작은 값은 왼쪽, 큰 값은 오른쪽으로 나누고, 왼쪽과 오른쪽 하위 집합에서 같은 과정을 반복한다.

여기서부터 재밌다. 두 경우 모두 무언가에 무작위로 베팅했는데, 지지리도 운이 없을 때 잃는 게 다르다.

  • 몬테카를로에서 운이 나쁘면 틀린 결과가 나온다. 예를 들어 던진 다트가 우연히 전부 원 안에 들어갔다고 해 보자. 테이블과 원의 면적이 같다고 나올 거고, 완전히 틀린 답이 나온다. 빠른 실행 시간을 보장받는 대신 정확도에 리스크를 거는 셈이다.
  • 라스베가스에서 운이 나쁘면 실행 시간이 훨씬 길어진다. 예를 들어 QuickSort가 매번 하위 집합에서 제일 작은 값을 고른다고 해 보자. 실행 시간이 어마어마할 거다. 높은 정확도를 보장받는 대신 실행 시간에 리스크를 거는 셈이다.

사실 빠르면서 정확하게 답을 찾는 건 우주의 특성 때문에 불가능하다(고 알려져 있다. 아직까진...). 그래서 이 두 방법은 빠르고 정확한 결과에 다가가려는 근사치다. 근데 정확도를 높이려고 실행 시간을 내주고, 실행 시간을 줄이려고 정확도를 내줄 수 있다는 게 재밌지 않나?

더 재밌는 건 둘을 서로 바꿀 수 있다는 점이다. 몬테카를로를 특정 신뢰 수준에 닿을 때까지 계속 돌리면 라스베가스가 된다. 반대로 라스베가스 알고리즘을 일찍 멈추고, 틀렸을 수도 있는 결과를 받아들이면 몬테카를로가 된다. 이 과정이 NP 문제의 환원이랑 비슷해 보이는데, 아직 자세히 공부해 보진 않아서 어떤 연결점이 있는지는 잘 모르겠다.

그럼 이게 무슨 뜻일까?

어쩌면 시간과 정보는 같은 물리적 속성일지도 모른다

근데 때문에 두 개의 다른 값으로 보이는 건지도 모른다. 아직 입증된 건 아니지만, 어쩌면 P-NP 문제의 답이 될지도 모른다.

Backlinks0

No backlinks found