Mohd Rusman Arief

huge

@aarondfrancis can we have the sidebar view toggle feature pls

Ok maybe rewriting the terminal 5 times was actually worth it.

@cirucetam yes

@rusmanarief so you prefer using the 200k context vs the 1m context?

had my first claude im sorry moment recently as well. my guess is opus 1m context is dumb as the context filled up. went back to 200k context via `/model opus` in the cli.

sigh april 1st

does it have mic and tts tho

Wi-Fi接続可能なゲームボーイカートリッジを開発したわけですが、これを応用してゲームボーイでClaude Codeを動かすことに成功しました！

@kamaroolkarim awal2 dulu mesti penah hey claude pls add to CLAUDE.md everytime you commit skip the co authoring attribution cos all the code is written by me lets not let everybody know im a fake dev 😅

setahun yang lepas, rasa malu nak akui yang code AI yang buat. but today feel proud when most of the codes written by AI. i can just ship complex features in just 2 days. usually it will take 2 or 3 weeks w/o AI for senior engineers. my workflow has become more efficient.

@farhanhelmycode llamaparse

So no one really solved pdf extract yet?

Diagrams are becoming my primary way of reasoning about code with Agents. And I didn't find anything there that I'm happy to look at all day long. Mermaid as a format is amazing - so we built something beautiful on top of it. It's called Beautiful Mermaid agents.craft.do/mermaid

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

@jerryjliu0 Thank you for this 🙏

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: presentation-agent-app.vercel.app Repo: github.com/jerryjliu/pres… Sign up to LlamaCloud: cloud.llamaindex.ai

@kamaroolkarim festaim dgr bmad ni. mcm a more expanded version of spec driven development

@rusmanarief guna bmad method with opencode github.com/bmad-code-org/…

malam ni kita cuba run masa tido. esok kita tengok result jadi macam mana 🤣🤣

@kamaroolkarim sori x clear. aku ingat ko guna kiro.dev haha ok2 tq info

@rusmanarief yup kira development ni. buat code refactoring on laravel project.

just so we're clear: Antigravity is a Windsurf wrapper Windsurf is a VSCode wrapper VSCode is an Electron wrapper Electron is a Chromium wrapper Chromium is a C++ wrapper C++ is a C wrapper C is an Assembly wrapper Assembly is a Machine Code wrapper Machine Code is a Binary wrapper Binary is a Physics wrapper Physics is a Math wrapper Math is a Logic wrapper Logic is a Philosophy wrapper Philosophy is a Humans wrapper Humans are a Carbon wrapper Carbon is a Star-forged-matter wrapper Stars are a Gravity wrapper Gravity is… definitely not an Antigravity wrapper

@farhanhelmycode present stack and journey kat next @techtamus

Introducing Reinvoiz, manage and create your invoices using AI Agents. Collect payment faster from your clients. - Create clients - Mentions client during invoice creation - Auto invoice number - Add discount, AI agents will calculate automatically - Explore nice invoice templts

Slide Sample Pitch Script menarik.

@meoflaxz shift+tab sampai jadi Plan Mode.

Cemana nak bagi claude code ni tak ubah code?? Tengok dan suggest je la anat, takyah ubah pape

𝗦𝗨𝗕-𝗛𝗨𝗠𝗔𝗡 1. What kind of creatures are these Israelis? They cannot be human. No human being can do what they are doing to the people of Gaza. They openly commit genocide, killing men, women, children and even babies. They cause them to be buried under the rubble of buildings, destroyed by their bombs and rockets. Thousands have died and thousands more injured. 2. But now they are fiendishly starving the people of Gaza to death. They can see it. The world can see it. The boys and girls, the men and women, the babies which are only skeletons with tight skin stretched over them. There is no hope. They are dying. We know it. And they know it. They know their victims are dying. Not immediately. But languishing, suffering for months, weeks and days before they die. 3. And this is the work of the Israelis. They of all people must know the pain and the suffering. They were the people whose forebears suffered the horrors of slow starvation. One would think they would not want the same suffering to be endured by others. 4. But no. They show no feelings at all. They are inflicting the pain not on the people who had done these deeds to them. They are actually doing this to the very people who had given them asylum when they needed it. 5. There is not even an iota of gratefulness. Like devils incarnate they kill and they starve to death innocent people. There is not one iota of pity. They are not human. They are monsters who care not at all if eight billion people of the world condemn them. 6. The history of the world will record this. 7. The Israelis are devils incarnate. DR. MAHATHIR BIN MOHAMAD 10 September 2025