Solidity Engineer & Protocol Architect | Mobile Tech Lead | Fullstack Web3 Tech Lead @BankBCA | Instructor @pbalabs | prev CTO @CentuariLabs

Joined December 2016
The less you want to babysit an AI coding agent, the more test infrastructure you actually need to trust its output Here are the tests I'd put in place to make sure the code doesn't drift: - Unit tests: deterministic, fast, cheap. Necessary but the weakest signal alone. Coverage percentage doesn't prove correctness. - Property-based testing (Hypothesis, fast-check, QuickCheck): the agent defines invariants, the framework throws hundreds of inputs at them. Catches edge cases a human or agent wouldn't think to write by hand. - Mutation testing (Stryker, mutmut, PIT) breaks your code on purpose and checks if your tests catch it. That's what actually tells you whether your test suite can be trusted - Static analysis and type checking catch a class of bugs before runtime, for free. - Integration tests need real dependencies or realistic fakes, not mocks of your own assumptions. A mocked integration doesn't prove it matches reality. - Contract testing (Pact or schema validation) matters once agents are building against APIs. Catches drift between service versions without a full E2E run. - Differential or golden testing: run new code against a known-good reference, diff the output. Cheap way to catch regressions without writing new assertions every time. - E2E tests (Playwright, Cypress) are slow and brittle. Save them for critical paths, not as your main confidence source. - Fuzz testing, for anything parsing input or handling untrusted data. - Load and chaos testing come later, once something's actually running in production But none of this tests whether the spec was right in the first place. AI still lacks the empathy to understand what the user actually wants These guardrails prove your code does what you told it to do. They don't prove you told it the right thing.
2
1
11
2,177
All of this REA hype, but I just want to say that beware of the software that you guys reverse engineer. There is some software that forbids reverse engineering You guys might get sued because of that
Reverse Engineer Anything 😂 Software is done.
1
143
Heinrich retweeted
Banyak yang tertarik dengan blockchain, tapi belum tahu harus mulai dari mana. @hwisesa23, mentor PBA Labs, sharing journey-nya masuk ke Web3 di video ini 🎥 Certified Blockchain Developer Course PBA Labs menyediakan jalur belajar terstruktur. Link daftar ada di bio 🤓
1
2
133
I don’t think we need a dedicated QA team anymore Now with AI, all software engineers should also learn how to do proper testing, not just build Either the current QA team should learn how to also be a software engineer, or you will be gone
1
2
84
My Codex subscription just ended today and this drops Now let’s switch back to Claude
Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family. It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.
1
112
Heinrich retweeted
Blockchain Developer diproyeksikan jadi salah satu skill dengan pertumbuhan tercepat sampai 2030 (World Economic Forum). PBA Labs siapkan kamu dari nol sampai bisa siap terjun ke industri lewat Certified Blockchain Developer Course, sekarang buka pendaftaran. Cek link 🔗 di bio
1
3
87
• Output tokens: $0 • Every response includes a confidence score • 20–200× faster than frontier chat models Worth a look
After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x cheaper (w/ output tokens free) • Frontier composable intelligence optimized for decisions AFAICT the shortest path to AI-based economic revolution
1
54
I think every engineer now should learn how to become an FDE We still need human empathy to speak with customers and understand their needs Many engineers lack that, and they should practice it If you just focus on engineering things, you will be closer to being replaced completely by AI
47
What do you guys think? If we have the chance to turn back time, will you want to stop the development of AI? Just saw this guy resign from Anthropic. He worked at OpenAI and Anthropic for years and said both companies are racing too fast and not acting responsibly My friends and I also keep discussing whether we really need AI or not in our lives.
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
3
376
Heinrich retweeted
PBA Labs lahir dari perjalanan panjang membangun talenta teknologi Indonesia, dari ribuan peserta sampai alumni yang kerja remote di perusahaan global. Nama ini merefleksikan scope kerja yang makin luas, dari bootcamp sampai kolaborasi lintas institusi. Cek video full-nya 🎥
1
5
108
Heinrich retweeted
Jarang ada engineer yang bisa ship protocol DeFi sekaligus handle aplikasi banking skala nasional. 🔗 Kenalan sama @hwisesa23, Mentor Blockchain Developer @pbalabs. 👇
1
2
5
140
Another AI products that actually blew my mind Feed it a few images and it reconstructs the whole space in 3D And you can even move the camera anywhere
Introducing Atlas: The world's first multimodal world model that generates image and video frames with pixel-perfect camera control and reconstructs them in 3D. Model the world, move the camera, and simulate space & time.
66
When using AI to build a project Do you guys still think about the DSA?
1
46
Let’s just face it Even after the reset, we Plus plan users are still not able to use Sol. Otherwise, it will still drain your limit in just 30 minutes
We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!
3
101
Found this Claude skill that turns a vague request into a sharp prompt But do we actually need it? If I just use plan mode, I already get a chance to refine the task before anything runs. Isn’t that the same thing? github.com/nidhinjs/prompt-m…
1
74
I imagine in the future we will probably also have a robotic competition using Microduck instead of using Lego Robot It will be such a fun learning experience for kids to learn about coding
We have a huge news to share today! Today we are unveiling the first truly accessible RL robot - welcome Microduck A 25 cm tiny open-source biped with 15 actuators and packed with sensors (camera, speaker, LiDAR, NFC, bluetooth, wifi, etc) that you train yourself with reinforcement learning. It's also playable out of the box with more than half a dozen fun and playful pre-trained policies to have it walk, sit, crouch, roller-skate, pick up objects with its articulated beak, and recover on its own. And all for less than $400. See all the details, play with the simulator and order it at: pollen-robotics.com/microduc… (video with sound on 🔊)
1
76
It's really cute Now we can even vibe-code a robot Time to make our own version of Wall-E
We built a small biped robot you can teach new tricks to. Train it in simulation, run it on the real thing. Meet Microduck 🦆 $399, shipping before Christmas. pollen-robotics.com/microduc… github.com/pollen-robotics/m…
1
52
0x Alpha turns out to be a GLM-5.3 Flash Some even got deceived by the Google team since they were vague posting like it was theirs lol
The new AI model that’s swept to the top of online usage charts with high performance at zero cost was created by China’s Z.AI, also known as Zhipu bloomberg.com/news/articles/…
1
73
They brought back the 5h limit plan for plus plan user.. but we still got a reset
1
682
We used to talk about JavaScript frameworks all the time Now it’s all AI models and harnesses Ah, the good old days
1
4
89