Raymond Christopher

Aku pernah mengajar di KELAS PRAKERJA. Itu kan GRATIS ya. Tahu gak POV-ku sebagai pengajar gimana? Sebagai gambaran: Tiap kelas berlangsung 5 hari. Tiap sesinya 3 jam. Itu aku berasa bicara dengan tembok 🥲 Hampir semuanya OFF CAM dan PASIF. Buka sesi tanya jawab, gak ada yang nanya. Lalu, pas dikasih tugas tahu gak apa yang kudapat? Anggap ada 15 peserta. Itu bisa 10-12 nya ngerjain asal-asalan. Bahkan ada yang kelihatan banget pake chatGPT 😭 Ya, kelas gratis sering yang datang MENTAL GRATISAN. Mau cerita lain dari contoh ilmu yang dikasih GRATIS? Aku punya grup menulis. Terbuka dan gratis untuk umum. Semua bisa diskusi dan belajar di situ. Tapi, KALAU MAU ✨ Karena yang kudapat banyak banget SILENT READER. Tiap aku sharing materi, sepi dari tanggapan. Padahal yang "seen" itu banyak banget. Sementara itu, di balik materi webinar hingga komunitas, ada effort yang kucurahkan. Ada waktu yang kugunakan buat nyiapin materi. Ada pengalaman yang kubagi cuma-cuma. Di situ aku punya kesimpulan: MENTAL GRATISAN dan MENTAL SIAP BAYAR itu berbeda ✨ Contoh: Aku beberapa kali itu bootcamp berbayar. Di sana suasananya aktif sekali. Sesi tanya jawabnya hidup. Tugas dikerjain sungguh-sungguh. ILMU BERBAYAR ternyata jauh lebih dihargai dari ILMU GRATISAN. Nah, kalau ada yang bilang "Kok ujung-ujungnya jualan kelas?" Ya, buat menyaring siapa saja yang siap dengan ilmu. Termasuk menghargai yang membagikan ilmunya ✨

if you really have higher iq and understand how important tokens are, you should start coding in mandarin and see how token efficient it is

𝗟𝗟𝗠𝘀 𝗔𝗿𝗲 𝗡𝗼𝘁 𝗥𝗲𝗮𝗱𝗶𝗻𝗴 𝗬𝗼𝘂𝗿 𝗖𝗼𝗱𝗲 We keep calling LLMs "AI coding assistants." But writing code and understanding code are not the same thing. Researchers from Virginia Tech and Carnegie Mellon University just ran 750,000 debugging experiments across 10 models to determine how well LLMs actually understand code. The results show that you should not blindly trust your AI coding assistant when debugging. Here is what they found: 𝟭. 𝗔 𝗿𝗲𝗻𝗮𝗺𝗲𝗱 𝘃𝗮𝗿𝗶𝗮𝗯𝗹𝗲 𝗯𝗿𝗲𝗮𝗸𝘀 𝘁𝗵𝗲 𝗱𝗲𝗯𝘂𝗴𝗴𝗲𝗿 Researchers created a bug, confirmed that the LLM found it, then made changes that don't touch the bug at all, such as renaming a variable or adding a comment. In 78% of cases, the model could no longer find the same bug. The bug was still there. The variable names and comments changed, and that was enough. 𝟮. 𝗗𝗲𝗮𝗱 𝗰𝗼𝗱𝗲 𝗶𝘀 𝗮 𝘁𝗿𝗮𝗽 Adding code that never runs reduced bug-detection accuracy to 20.38%. Models treated dead code as live, and flagged it as the source of the bug. But the bug was in another line. So, LLMs cannot reliably distinguish "this runs" from "this never runs." 𝟯. 𝗠𝗼𝗱𝗲𝗹𝘀 𝗿𝗲𝗮𝗱 𝘁𝗼𝗽-𝘁𝗼-𝗯𝗼𝘁𝘁𝗼𝗺, 𝗻𝗼𝘁 𝗹𝗼𝗴𝗶𝗰𝗮𝗹𝗹𝘆 56% of correctly found bugs were in the first quarter of the file. Only 6% were in the last quarter. The further down the code, the less attention the model pays to it. If the bug lives in the bottom half of your file, the model is already less likely to find it. 𝟰. 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻 𝗿𝗲𝗼𝗿𝗱𝗲𝗿𝗶𝗻𝗴 𝗮𝗹𝗼𝗻𝗲 𝗰𝘂𝘁 𝗮𝗰𝗰𝘂𝗿𝗮𝗰𝘆 𝗯𝘆 𝟴𝟯% Changing the order of functions in a Java file caused an 83% drop in debugging accuracy. The code still remained the same. Where the code physically sits in the file matters more to the model than what the code does. So, obviously, this is a sign of pattern recognition, not real code understanding. 𝟱. 𝗡𝗲𝘄𝗲𝗿 𝗺𝗼𝗱𝗲𝗹𝘀 𝗵𝗮𝗿𝗱𝗹𝘆 𝗺𝗼𝘃𝗲 𝘁𝗵𝗲 𝗻𝗲𝗲𝗱𝗹𝗲 Claude improved ~1% between 3.7 and 4.5 Sonnet on this task. Gemini improved by ~1.8%. Every model release comes with a new benchmark leaderboard and new headlines. But the ability to reason about code under realistic conditions is improving slowly. 𝟲. 𝗧𝗵𝗲𝘀𝗲 𝘄𝗲𝗿𝗲 𝗯𝗲𝘀𝘁-𝗰𝗮𝘀𝗲 𝗰𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝘀 The study used single-file programs with ~250 lines, and each had a clear description of what the code should do. The authors say this was intentional. They wanted the best-case conditions. Real production code is multi-file, cross-module, and poorly documented. It will perform worse for sure. Here are three things worth changing based on the research: 🔹 𝗣𝗮𝘀𝘀 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗰𝗼𝗻𝘁𝗲𝘅𝘁, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗰𝗼𝗱𝗲. When asking an LLM to debug, include test output, stack traces, and failure messages alongside the source. Without runtime details, the model is guessing based on the code. 🔹 𝗗𝗼𝗻'𝘁 𝘁𝗿𝘂𝘀𝘁 𝗶𝘁 𝗼𝗻 𝗱𝗲𝗲𝗽-𝗳𝗶𝗹𝗲 𝗯𝘂𝗴𝘀. If the suspect code is in the bottom third of a long file, the model will have trouble finding it. Consider splitting the context or feeding the relevant function directly. 🔹 𝗖𝗹𝗲𝗮𝗻 𝘂𝗽 𝗱𝗲𝗮𝗱 𝗰𝗼𝗱𝗲 𝗯𝗲𝗳𝗼𝗿𝗲 𝘂𝘀𝗶𝗻𝗴 𝗔𝗜 𝗱𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀. Commented-out blocks and unreachable branches will mislead the model. It cannot filter them out. We rate AI coding tools on HumanEval. That tests whether a model can write a function from a description, but this says nothing about finding a bug in code it didn't write. Those are different problems. We're using the wrong benchmark.

Kimi is quietly becoming the model nobody talks about but everybody uses. No hype threads. No benchmark wars. No CEO drama on X. Just a model that works well and minds its own business.

the founder of openclaw joined the company that was founded to make AI open and now charges you per token. and is now telling you open models aren't there yet. i run qwen 3.5 27b on a single 3090. 50 tok/s. it writes code, handles tool calls, runs agent sessions for hours. the model built a full space shooter, 3,000+ lines, from a single prompt. i published the data. "open models aren't there yet" is what you say when your harness can't parse tool calls on local models and you blame the model instead of fixing the harness. i have the DMs. people switch from openclaw to hermes agent and their "broken" models suddenly work. pair a good model with a good harness like hermes agent where parsers are built per model. your data stays on your machine. no API key. 0 subscription. no one training their next model on your thinking. don't listen to someone with an OpenAI paycheck telling you open source can't do the job. install it. test it yourself. the receipts are on my timeline. he built a harness that couldn't handle local models and chose the API paycheck over fixing it. that should tell you everything.

codex is a better programmer it reads more before changing things and gets my edits right more often -- auto-compact is also stronger, so it can stay on track during long tasks but as a harness, claude code is still better in some ways: > less tools, including no hooks > worse ux, especially when resizing

Anyway, aku punya respek yang besar thd Muhammadiyah. Beberapa kawan baikku juga aktivis di sana, dan sangat keren. Terlepas dari isu tambang atau apa, Tapi Muhammadiyah ini ga sekadar Ormas. Punya sekolah, kampus, rumah sakit, dsb yang bener2 sustainable dan bermanfaat bagi masyarakat. Cabang sekolahnya aja ada di luar negeri. Assetnya juga besar. Satu lagi: gak dekat dengan Israel. 🤙🏼

Am I the only one who thinks that ChatGPT is becoming more and more outdated, imprecise, and unoriginal? It just tells you what you want to hear

would you rather have: - $200k stanford degree - $200k claude code credits