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
바잘제트 오버엔지니어링

바잘제트 오버엔지니어링

바잘제트의 오버엔지니어링

1800년대 런던 하수도는 참혹했다. 콜레라 대유행에, 런던 전역에 악취가 끊이지 않아 그레이트 스팅크라는 이름도 있을 정도. 이에 조세프 바잘제트는 1859년 런던의 새로운 하수도를 건설할 총괄 책임자로 선정되었다. 그는 전문가들의 제안을 받아 런던 실정에 맞는 하수도 규격 초안을 설계했다.

하지만 바잘제트는 전문가들이 합의한 최초 하수도 규격에 반대했다. 런던의 산업 폭발을 보았기 때문이다. 급성장하는 런던의 규모에 그는 하수도 전면 재건의 기회는 자주 오지 않을 것이라는 것을 직감했다. 즉, 다음 하수도 재건은 수백 년 뒤에 일어난다는 직감. 그는 이렇게 말했다.

우리는 이 일을 두 번 할 수 없습니다. 그리고 언제나 예기치 못한 일은 생깁니다.

그러고는 파이프 직경을 2배로 늘렸다. Hagen–Poiseuille 방정식에 따르면 유량은 최소 16배 증가했다. 또 그는 당시 포틀랜드 시멘트라는 최첨단 시멘트를 사용했다. 포틀랜드 시멘트는 물속에서도 강도가 유지되는 특정 종류의 시멘트다. 1824년에 특허가 난 포틀랜드 시멘트는 비교적 신기술이었고, 1840~1850년대에 활발히 개선이 진행되고 있었다.

모든 면에서, 설계 규격은 너무 오버엔지니어링이었고, 재료는 미성숙한 기술 도입 강행이었다. 예상 건설비와 공기는 폭증했고, 안전 우려가 쇄도했으며, 많은 정치인과 시민들이 반대했다. 하지만 바잘제트의 강력한 주장에 이는 승인되었다.

흥미롭게도 결국 바잘제트가 옳았다. 바잘제트의 시스템 상당 부분은 150년이 넘은 지금도(소규모 개축은 있었지만) 여전히 사용되고 있다. 20세기에 런던의 인구가 네 배로 늘었음에도, 바잘제트의 과잉설계된 시스템은 부하를 감당하기에 충분하고도 남았다.

분석에 따르면, 바잘제트가 없었더라면(그리고 초기 제안된 파이프 규격과 재료를 사용했더라면) 하수도는 1960년대에 넘쳐흘렀을 것이라고 한다. 그리고, 1960년대에 하수도 규격 재시공을 해야 했다면, 그 사회적 비용은 바잘제트의 오버엔지니어링 비용의 수백-수천 배를 넘을 것이라는 분석도 있다.

오래된 이야기지만, 오늘날의 많은 공학적 의사결정과 너무나 닮아있다. 런던은 성장하는 도시이니 기다리면 바잘제트가 옳게 되는 시점은 반드시 오겠지만, 그에게서 배울 점은 1859년에 그러한 계산된 확신을 했다는 점이다.

AI 없이 순수 조성현이 2026년 1월 7일 작성

Backlinks1