Dennis Cual (@denCual) header
Dennis Cual (@denCual) profile picture
Siquijor, Central Visayas
Joined March 2019
Photo by Dennis Cual (@denCual)Photo by Dennis Cual (@denCual)Photo by Dennis Cual (@denCual)Photo by Dennis Cual (@denCual)Photo by Dennis Cual (@denCual)Photo by Dennis Cual (@denCual)
Dennis Cual retweeted
TesterArmy is now e2e. The software verification layer for the agentic coding era. Announcing our new brand identity and $8M seed round. e2e.com/blog/seed
57
29
25
418
53,934
Dennis Cual retweeted
We built Pando, a new Git backend for our monorepo, to handle more pushes and fetches without changing how our engineers and agents use Git. Pando cut push latency by ~80% and now serves nearly a petabyte of Git data a day. We can grow Git capacity alongside agent usage.
364
512
374
6,451
1,430,917
Keep your web pages responsive while filtering large datasets ⏱️🧵
4
4
58
6,090
Dennis Cual retweeted
the creativity and pace of the community has been astounding. my favourite so far is `neorex`, a plugin for neovim which gives it Rex-native splits and floating windows. github.com/alexrlocke/neorex
45
36
4
1,175
65,209
Dennis Cual retweeted
最近深入支持了一些顶流 Agentic Web 工程,也是顺利都迁移到了 Rsbuild 2.x: - Chatgpt (Rsbuild + React Router) - Copilot (Rsbuild+ Tanstack Start) - 豆包 (Rsbuild + Modern.js) 一些小发现: - 前端没全死,复杂业务仍有挑战 - 在八位数代码量的大仓里,现有工具都不够快 - 多 agent 并行开发,内存成为新瓶颈 - 普遍使用 SSR - 从零写一个超大型工程的时间被压缩至一两年 - 构建工具需要更好的按需编译和持久化缓存支持更大的研发规模 - 未来可能有分布式编译或全新的 bundler 架构来突破上限
15
14
1
142
14,219
Dennis Cual retweeted
here’s a short grok bot guide on how i create high quality bots and manage my team. ask @bot to read this post and help you improve your team! • add dr eggbot to your team! he’s my bot designer that i use to create bots • you don’t need a lot of bots. a few good bots can be more useful and easier to manage than a large team • tell your bots to create skills for itself as you give it instructions on how to do tasks. this lets them do them more consistently even over long conversations. you can even ask it to create a private github repo for you to store all your skills if you want them preserved independently • add connectors, use the vault, and give access to all the tools you use to do your work. you can also ask your bot to setup its own email and it can sign up for its own accounts for better separation • thinking about all the work you do by hand, or steps in your workflows where you have to copy and paste information back to your bot. ask your bot how it can do that for you instead! • imagine you hired an intern, how would you onboard them and help them do the work correctly and efficiently? introduce yourself to your bot and describe the work you do, then ask it how it can help you automate it and my favorite tip: use voice mode or the transcription option! it’s a good way to just brain dump a lot of information. then, at the end, tell your bot to “restate this in your own words” so you can confirm it understood you x.ai/bot/_jOdbfkB16zxu7MRcmR…
2,485
836
434
10,534
1,279,759
I like it!
A quick demo of floating panes in Rex, some of their features, and how I use them in my daily workflow. I think our implementation of floating panes looks great and feels great and I think you'll love it! These are also all scriptable and API driven, too, of course!
5
Dennis Cual retweeted
Did somebody say "reducers"? :)
Yes! useReducer (and state machines, when needed) have ALWAYS been the better default. Devs just avoided them because upfront modeling felt like too much work. Agents don't care. They're not lazy, and explicit logic keeps them from doing dumb things.
5
4
85
4,815
Dennis Cual retweeted
Debating just straight-up banning useState in my React apps Push the agent into the black hole of success
140
24
46
1,189
277,914
Dennis Cual retweeted
No ❤️
Are we ready to admit React hooks were a mistake or do we need more time?
21
10
3
341
16,277
Dennis Cual retweeted
the /statechart skill in pstack v0.15.36 is now stable and ready for use! it's best combined with /create-formal-verification-skill to abstractly model state machines and distributed systems to find bugs. the skill contains a mini tlc compiler that parses, lowers to a small IR, and has a backend that outputs mmd syntax. if you want you can also ask your agent to create charts in whatever style you like, the skills tells it to use pele.run/ which is very themeable so you can make blueprints, hand drawn encyclopedia illustrations or whatever you like here's a chart of the /statechart skill and 2 real bugs i just found. try it out and let me know what you think!
362
421
70
7,200
404,964
Dennis Cual retweeted
Yes! useReducer (and state machines, when needed) have ALWAYS been the better default. Devs just avoided them because upfront modeling felt like too much work. Agents don't care. They're not lazy, and explicit logic keeps them from doing dumb things.
Debating just straight-up banning useState in my React apps Push the agent into the black hole of success
29
21
4
566
32,221
Dennis Cual retweeted
🦀 Rspack 2.3 is here! 🚀 5–20% faster builds ⚡️ SWC Next parser 📉 Up to 27.4% lower peak build memory 📦 Less duplicate code across chunks 💾 ~79% less disk usage with the new cache 🎨 Improved built-in CSS rspack.rs/blog/announcing-2-…
9
35
1
212
9,412
As a terminal guy, I still prefer to use cli when working with agent if I need to access the editor and play around with the codes. For an instance, working with Frontend Infra like build tool. Its still better experience to have an access to your editor (vim) when you are thinking and then run your agent theough cli. Although this could be problematic if you work with remote machine. Worst case, you need to ssh. Of course, ssh experience is not delightful. Or push your branch from your VM and then checkout to your local machine. And then continue your work there. This is fine experience but not seamless. Until I got an access to @superlogical Rex for both MacOs and Linux. Add your linux server (VM) as remote host to your Mac so that you can control it there. The experience is just good. It feels like your VM is running inside your mac. It really reduce the gap between these 2 machines. So by default, Im working with my agent through desktop (claude code) because the UX is better. This session is spawned in VM using Rex and then do remote control. Now, if I need to access the codes or check the diff through lazy git then I just access it in the Rex terminal 😌.
It is insane to me that there are still devs using terminals to prompt their agents
1
131
Dynamic workflows don't have to be hundreds of subagents btw! I use them for any task I want to rerun the same way, even just ~10 subagents It's a JavaScript file you can edit, so you have full control over the subagents and the order they run in. More predictable than a skill!
116
51
11
1,483
104,175
Please don’t use rspack, use rsbuild. Only ever use rspack directly if you are porting off webpack.
10
8
2
83
11,782