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
Kakao

Kakao

Warning

Over a year old. May be outdated

카카오가 혁신이란 걸 한 적이 있나요?

  • 어떤 사람들은 카카오톡이 타이밍을 잘 잡았을 뿐이라고 말합니다만 세상 일이 어디 운만 가지고 되나요? 타이밍이 모든 것을 결정한다면 지금은 이름도 잘 기억 안 나는 엠엔톡이라는 메신저가 국내 시장을 다 먹었을 겁니다.
  • 카카오톡의 트래픽이 가장 고조되는 시간은 오후 11시 정각이었습니다. 밤 10시에 시작하는 메인 드라마가 끝난 직후 사람들이 하는 가장 먼저 하는 일이 카톡을 켜는 것이니까요. 드라마가 끝나면 트래픽이 동시에 몰리면서 서버가 힘들어했었죠. 초기 기여자들은 매일 밤 11시가 되면 자연스레 컴퓨터 앞에 앉아 서비스를 모니터링하고 부족한 점을 보완했습니다. 이런 날들은 잠깐 며칠이 아니라 1년이 넘게 지속되었습니다. 회식을 하다가도 11시가 되면 자연스레 컴퓨터를 열고, 주말에도 예외는 없습니다. 카톡 서버는 매일 위기였지만 그들은 매일 방어해냈습니다. 엠엔톡은 그러지 못했습니다.
  • 카카오는 전 국민으로부터 절대적인 사랑을 받는 회사였습니다. 누군가 카카오에게 시비를 걸면 전 국민이 달려들어서 카톡은 건들지 말라고 함께 싸워 주던 시기가 있었죠. 요즘에는 카카오가 문어발 사업을 한다, 돈 벌더니 배가 불렀다 말이 많습니다.

하지만 카카오는 그때와 같은 자세로 사업에 임하고 있는가?

카카오톡 서버 개발의 추억

  • 대용량 서비스를 경험해보지 않은 사람들에겐 이상한 일처럼 들릴겁니다. 카카오톡은 공지사항 같은 간단한 코드조차 쉽게 만들기 어려웠습니다. 이렇게 교과서의 첫 장에 나온대로 코딩하면 서버가 죽기 일쑤였습니다. 트래픽이 너무 많은 걸.
    java
    Notice.order(created_at: :desc)
  • 파트너 서비스 개발자들은 이 빨간 뱃지를 무시하곤 했습니다. 에이 그깟 빨간 뱃지가 뭐라고. 우리 트래픽 다 받을 수 있어요. 걱정마세요. 걱정말기는. 빨간 뱃지를 붙여주기만 하면 사람들의 트래픽이 몰렸고 여지없이 서버들이 죽어나갔습니다. 아이고, 잘 준비하라고 그렇게 일렀건만. 대용량 트래픽 경험은 이래서 특별하고 소중합니다.
  • 어느 날 카톡 개발 서버로 트래픽이 엄청 들어오기 시작했습니다. 뭐야 뭐야? 무슨 일이야? 애니팡 개발자들이 프로덕션용 SDK가 아니라 개발용 SDK를 그대로 릴리즈해버린 것입니다. 와씨 무슨 이런 얼간이들이 다있어? 개발 서버 한 대밖에 없는데 이 서버로 애니팡의 트래픽이 몰려오기 시작했습니다. 빨리 앱을 다시 올리라고! 선데이토즈와 긴급하게 연락을 해가면서 어찌어찌 해결했던 것 같습니다. 이런 미친 이벤트가 거의 매일 있었지만 웃으면서 일할 수 있었습니다. 장사가 이렇게 잘 되는데 즐겁지 않을리가? 2012년 가을에 애니팡 하트 메세지가 우리들을 얼마나 괴롭혔는지 생각해보면 그 때 장애 알림이 얼마나 많이 왔는지 알 수 있습니다.
  • 트래픽 폭탄을 맞아 서버가 멈추는 경험을 처음 하게 되면 패닉이 옵니다. 머리는 하얘지고 손가락은 굳어서 아무것도 할 수가 없습니다. 겪어보기 전에는 쉽게 말하지만 한 번 패닉을 경험하면 이게 얼마나 무서운 일인지 알게 됩니다. 서비스 장애가 나면 사람들은 두 부류로 나뉩니다. 서비스의 소중함을 깨닫고 감사하고 응원해주는 사람들. 서비스 안된다고 조롱하고 비난하는 사람들.
  • 저는 감사하고 응원하며 사는 쪽이 되고 싶습니다. 제 주위에도 이런 사람들이 많았으면 좋겠습니다.
Backlinks17