Jensen
131 posts


A computer can never be held accountable
Therefore a computer must never make a management decision คือประโยคที่ไม่มีวันตาย
ถ้า AI ลบ Database ใครรับผิดชอบ ดังนั้นก็ยังต้องมีใครซักคนคอยตัดสินใจอยู่ดีไม่ว่าในขั้นตอนไหน
จ้างคนที่เข้าใจว่าระบบทำงานยังไงถูกกว่าชื่อเสียงบริษัทหาย
Chanon N.@KillerNay
คำถามสัมภาษณ์งาน backend 2026 “ตอนนี้เราเขียนโค้ดด้วย AI ได้ 80% แล้ว ทำไมเรายังต้องจ้างคุณอยู่?”
ไทย

Step-1: Learn Rust
Step-2: Understand ownership, borrowing & lifetimes
Step-3: Master memory safety, zero-cost abstractions & type system
Step-4: Build a CLI tool using Cargo
Step-5: Write a multithreaded server using async Rust with Tokio
Step-6: Read the Rust standard library source. question everything
Step-7: Build a production-grade backend (REST/gRPC, DB, caching, msging)
Step-8: Make it fast & safe (profiling & benchmarking)
Step-9: Eliminate bottlenecks with safety
Step-10: Ship it
English

@rachpradhan I think you should add to your tweet that “we” - are me and Claude Code :D
So seems the whole project is vibe-coded :-(
English

We made TurboAPI hit 150k req/s. In under a day. It is now 22x faster than FastAPI
Thanks to the amazing contributions from the people in the comment section, which allowed me to view what made the hyper optimized frameworks work the way that they do!
Here's what changed..

Rach@rachpradhan
I replaced FastAPI's entire HTTP core with Zig. Same decorator API. Same Pydantic models. 7× faster. 47,832 req/s vs FastAPI's 6,800. 2.09ms p50 latency. Introducing. TurboAPI. Here's the story..
English

@nateberkopec 😂 I just updated a large code base from nextjs 13 to 15 with codex 5.2 in under an hour with 305 code changes. You don’t know what you are talking about
English

@nicogarcia @Abstudiobrand How many people got scammed by this nico guy?
English

@Abstudiobrand Nah. You were fired because your work was actually bad.
English

please don’t work with this guy, even if it’s paid or free.
About two months ago, he reached out to me about working on a project for one of his clients. Everything seemed fine at first, I shared my pricing, and he agreed.
But a week later, he came back asking me to do a fake project for free, just so he could use it to attract clients. I was honestly shocked. What kind of person thinks that’s okay?
He kept trying to convince me that it would be a great opportunity. But come on, doing fake free work just to help someone else land clients? That’s not how real collaboration works.
So I’m sharing this to protect other creatives:
🚫 Don’t work with Nico.
🚫 Don’t let anyone manipulate your time, talent, or effort.
We deserve better

English

Another example of the unexpected changes of work due to AI agents is that we will start to see new bottlenecks emerge that we didn’t predict before.
In a world where AI agents make engineers 2-3X more productive, the new bottleneck will be deciding what to build and designing it properly.
AI is better at code gen than design gen right now (or even deciding the right features to build), which means we can bring automation to the downstream workflow faster than the upstream workflow.
We’re going to see lots of examples of new bottlenecks emerge due to AI that didn’t get anticipated. This is also another great example of why you can’t predict what the future of jobs look like until you start to see how the new technology is adopted.
Luke Wroblewski@LukeW
design teams are not ready for the new reality. "we are producing code at 10x of typical high-velocity team."
English

















