Phawin retweeted
Hey @culpium members.
It's my pleasure to offer Culpium Executive members one of the first exclusive privileges of a founder-level subscription.
Details inside my next article, tomorrow.
Culpium Executive offers exclusive access & other perks
Sign up now:
culpium.com/subscribe
Phawin retweeted
Canceling 8 x ChatGPT 500 subs w/@OpenAI.
If you value your time, then OpenAI just isn't it right now.
Poor service availability, and inference is super, super slow. This isn't even about model quality; the problems go far beyond that. @claudeai is 100/100 better choice right now, faster inferencing, better availability and the models are better too.
Phawin retweeted
We're starting to see some agentic Rust forks (or alternative implementations) focused on iteration speed.
More-so than the specific projects, I'm interested in the ideas being explored (and how they could evolve upstream), so wanted to collate a few here...
Phawin retweeted
Introducing tsrs: a Rust port of the TypeScript compiler 🦀
We are not forking TypeScript!
◆ In close collaborating with the TypeScript team
◆ Up to 8x faster than TS 7.0 & ~70% less memory
◆ Runs in WASM, so it works in your browser & on Workers
◆ Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescri…
how do you trust your agents' work more? copy this post/link and give it to your @bot or agent!
1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again.
2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time.
3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill.
4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default.
this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night.
install github.com/cursor/plugins/tr… and create a new Project:
1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture
2. use /recall on my past transcripts to learn how i steer agents
3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data.
4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me
Phawin retweeted
AI made Spotify engineers faster at shipping code. But it also exposed a new problem: keeping quality under control at that speed.
Spotify shares what it learned the hard way, from production incidents and code churn to testing, mobile quality, and infrastructure pressure.
The lesson for every engineering team building with AI:
Generating code faster is easy. Shipping reliable software faster is the real challenge.
A must-read for software engineers :
engineering.atspotify.com/20…
Phawin retweeted
True. Most people aren’t using today’s AI to its full potential.
Hi, I'm Felix. I'm an eng lead working on Claude. I love watching people take flight and do things they never thought possible.
We often describe that as "being more ambitious" when using AI, which is tricky advice to follow. I wrote a tutorial:
felixrieseberg.com/how-to-be…
Phawin retweeted
ชอบประโยคนี้มากเลย
"Don’t let your kids best days financially be while they are living with you"
ถ้าวันนี้ได้หมดทุกอย่างที่ต้องการแล้ว จะเหลืออะไรไว้ภูมิใจตัวเองในอนาคต
youtu.be/H3CYQWfAMNo?t=3141&…
Phawin retweeted
Apple says you need a Mac to build iPhone apps.
Today I built one on Omarchy Linux, submitted it to the App Store, installed it on my iPhone over USB, and stopped it at a breakpoint in the debugger.
No Mac anywhere.
It's all open source:
github.com/joshuaswarren/oma…
Phawin retweeted
GPT-6.1 Sol is our most demanded model pretty much ever both across both the API and subscriptions.
Within ChatGPT & Codex, we were under heavy load, but have brough more capacity online and the speed should get much better in the coming hours, reaching almost twice the speed compared to what we served yesterday.
Phawin retweeted
If you're learning system design, check out my fundamentals series: teapawt.net/system_monarch/status/…
Replying to @system_monarch
1) Load Balancing: teapawt.net/system_monarch/status/…
2) CDN: teapawt.net/system_monarch/status/…
3) Caching: teapawt.net/system_monarch/status/…
4) Cache Invalidation: teapawt.net/system_monarch/status/…
5) Rate Limiting: teapawt.net/system_monarch/status/…
6) API Gateway: teapawt.net/system_monarch/status/…
7) CAP Theorem: teapawt.net/system_monarch/status/…
8) Sharding: teapawt.net/system_monarch/status/…
9) Replication: teapawt.net/system_monarch/status/…
10) Partitioning: teapawt.net/system_monarch/status/…
11) Queues: teapawt.net/system_monarch/status/…
12) Microservices: teapawt.net/system_monarch/status/…
13) Microservices Vs Monoliths: teapawt.net/system_monarch/status/…
14) Fault Tolerance: teapawt.net/system_monarch/status/…
15) Database Scaling: teapawt.net/system_monarch/status/…
16) Service Discovery: teapawt.net/system_monarch/status/…
17) Consistency models: teapawt.net/system_monarch/status/…
18) Eventual Consistency: teapawt.net/system_monarch/status/…
19) Distributed Transactions: teapawt.net/system_monarch/status/…
20) Leader Election: teapawt.net/system_monarch/status/…
21) Horizontal vs Vertical Scaling: teapawt.net/system_monarch/status/…
22) Back of the Envelope Estimation: teapawt.net/system_monarch/status/…
23) Idempotency, Data Latency & Finale: teapawt.net/system_monarch/status/…
A pretty big change is that Pi now has MCP at the core. How is this even possible? What made us change our way? earendil.com/posts/you-said-…
Phawin retweeted
Took the time and wrote down everything I have been learning about GPUs and CUDA. Consider checking it out!
Phawin retweeted
ตอนจบใหม่อ่าน paper, ดู youtube คนอินเดียสอน, ไป join event เรียนรู้จากคนเก่งๆ, ฝากเจ้านายสั่งหนังสือจาก Amazon
ใช้อะไรใหม่ๆ ที่ในไทยมีไม่กี่คนได้ใช้ จนปัจจุบันมันแพร่หลายไปแล้วหลายอัน
ทุกวันนี้มี tools มากมาย แค่กระดิกตีนงานก็อาจจะเสร็จไปแล้ว 60-70% อะไรที่เคย learning curve แม่งมี lift ช่วยแทบหมด ถึงมันมีอะไรในรายละเอียดเยอะ แต่คนหัวไวๆ ก็ส่งงานไปได้แล้วพยายามเข้าใจมันไปด้วย ยังไงก็ไวกว่าคนรุ่นก่อนแน่ๆ
เคยเจอ gen z เก่งๆ มาหลายคนส่วนตัวนี่ชอบมากๆ ทั้ง open, หัวไว, ใช้ tools ใหม่ๆ เป็น ยังไงชีวิตก็ไปได้ไวกว่าคนอื่น คู่แข่งแทบไม่มี
ถ้าจุดขายคนรุ่นใหม่คือ digital native การสร้าง folder ไม่เป็นนี่มันเอ๊ะไปจนถึงขั้น organize ชีวิตได้เลย
จริงๆ เลิกพูดเรื่องคน gen นั้นนี้ อาจจะได้ มองทุกคนเป็นคนเหมือนกัน แล้วดูเอาว่าใครทำอะไรได้ ใครมีประสบการณ์เท่าไร ใครเรียนรู้ได้ เวลาเจอสถานการณ์ยากๆ แล้วแก้ปัญหาได้ แล้วคุณอยากจะทำงานกับใคร ที่ราคาเท่าไรพอ
Phawin retweeted
I’m starting to not care that much about new model releases.
I don’t really have an urge to go and try all of them out right away.
Not sure if something changed from my side or if I’m already pretty happy with where ai coding was already.
Phawin retweeted
the best way to learn inference is by implementing it yourself
tensortonic.com
Phawin retweeted
new post: the senior engineer death spiral
sunilpai.dev/posts/the-senio…
a friend just started a big job and asked for some advice. so I braindumped a monologue about a super common failure mode I see with engineers and posted it here, hope it helps whoever it can.































