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
OpenAI가 새로운 테크 리바이스로 등극하다

OpenAI가 새로운 테크 리바이스로 등극하다

Warning

Over a year old. May be outdated

노트

이 글의 원문은 영어입니다.

OpenAI가 방금 GPT-3.5-turbo 모델로 돌아가는 ChatGPT API를 내놨다.

1,000토큰에 0.002달러고, 채팅이 아닌 데에도 쓸 수 있다.

Shopify, Instacart, Quizlet, Snap 같은 회사들은 벌써 이 API를 써 보고 있다.

소프트웨어에 또 한 번 큰 순간이 왔다.

시대의 골드러시가 방금 시작됐다.

골드러시의 진짜 승자는 리바이스였다.

광부들한테 금 캐는 데 필요한 도구를 팔아서 큰돈을 벌었고, 정작 금 캐기 경쟁에는 끼지 않았다.

이 조용한 전쟁의 무기상이었던 셈이다.

AT&T 같은 통신사 다음으로 테크 업계의 최신 리바이스는 AWS였다.

골드러시 때문에 청바지랑 곡괭이 수요가 폭발했듯이, 디지털 전환 때문에 AWS 같은 클라우드 컴퓨팅 수요가 폭발했다.

그리고 OpenAI가 방금 자기들이 다음 리바이스가 되겠다고 못 박은 셈이다.

AI 네이티브의 부상

이전 리바이스였던 AWS가 테크 판을 어떻게 바꿔 놨는지 보자.

지각 변동이 몇 개 있었다.

  • 비싼 온프레미스 엔지니어가 줄었다 -- 서버를 세팅하고 인프라를 관리하는 온프레미스 시스템 엔지니어가 꼭 있어야 하던 시절은 지났다. 이제는 하드웨어 걱정 없이 앱을 빠르게 배포한다.
  • 애완동물에서 가축으로 -- 컴퓨팅 초창기에는 회사들이 서버를 애완동물처럼 다뤘다. 하나하나 이름을 붙이고 따로따로 돌봤다. 근데 서버가 늘어나니까 서버를 소 떼처럼 다루기 시작했고, 한 번에 여러 대를 관리하는 자동화 도구에 돈을 쓰기 시작했다. 덕분에 안정성이나 성능을 포기하지 않고도 인프라를 빠르게 늘릴 수 있었다.
  • MSA와 서버리스의 부상 -- AWS 덕분에 작고 독립적인 서비스를 쉽게 띄우고 관리할 수 있게 됐고, 그게 마이크로서비스 아키텍처(MSA)로 이어졌다. 개발자는 따로따로 확장되는 작은 모듈형 서비스를 엮어서 복잡한 앱을 만들고, 안정성과 성능도 챙긴다. 2014년에 나온 AWS Lambda부터는 아예 서버를 관리하지 않고도 앱을 만들고 돌릴 수 있게 됐다.

그럼 AI 네이티브 시대에는 뭐가 비슷하게 일어날까.

  • 비싼 데이터 엔지니어와 ML 엔지니어가 줄어든다 -- AI 네이티브 플랫폼 덕분에 전문가가 아니어도 AI 모델을 쉽게 만들고 배포할 수 있다. 그래서 전담 AI 엔지니어가 덜 필요한 경우가 많아진다.
  • 모델을 처음부터 만들지 않고 만들어진 모델을 쓴다 -- AWS가 이미 만들어진 인프라 부품을 주듯이, AI 네이티브 플랫폼은 이미 만들어진 머신 러닝 모델을 준다. 내 데이터로 커스터마이즈하고 학습시키면 된다.
  • AI 모델을 만들고 배포하는 자동화 도구가 뜬다 -- 자동화 도구 덕분에 회사들이 클라우드에서 서버 수백 대를 관리하게 됐듯이, AI 네이티브 플랫폼 덕분에 모델을 만들고 배포하는 과정도 자동화된다.
  • 모놀리식 AI 앱에서 마이크로서비스 기반 AI 아키텍처로 -- 마이크로서비스 아키텍처로 작은 모듈형 서비스를 엮어 복잡한 앱을 만들었듯이, 이제는 작은 모듈형 AI 모델을 엮어서 복잡한 AI 앱을 만든다.
  • AI 개발과 배포가 누구나 하는 일이 된다 -- AWS가 클라우드 컴퓨팅을 누구나 쓰게 만들었듯이, AI 네이티브 플랫폼은 AI 개발과 배포를 누구나 하게 만든다.

근데 질문이 하나 남는다. 결국 OpenAI도 또 하나의 dumb pipe가 될까?

Backlinks2