Content about #Experience

Have you seen Claude Code’s Sub-Agent feature and immediately wanted to design a bunch of them? Backend Agent, Frontend Agent, and so on—it feels like getting more powerful tools. But do you really need them?

During WebConf 2025, chatting with friends about this topic revealed that many people are still unfamiliar with when to use Sub-Agents. Two talks at the conference provided good entry points: ihower’s AI Agents Development and 91APP’s Chief Architect Andrew’s From Service to Agent.

I was originally planning to release a tool that applied techniques from my COSCUP talk in August. However, I discovered that there are many considerations in development, and practical usage has its barriers.

I decided to start from a simpler, more immediately accessible angle. Recently, I finally completed the basic functionality of ccharness, which can improve Claude Code’s output quality from a different perspective.

Recently, due to work-related reasons, I took a moment to revisit Open Policy Agent and discovered that the Cedar Language introduced by AWS is more suitable for implementing a policy mechanism similar to AWS IAM in software applications. Since it is built on Rust, I decided to try writing an extension in Rust so that it can be utilized in Ruby.

The Form Object is a common pattern in Rails when our form becomes complex. But the tutorial in network’s example usually incapable of Rails’ form helper.

And I start thinking about is it possible to support form helpers without too many changes?

Before we starting to discuss architecture, our mentor let us ask some questions.

Between this meetup and previous meetup, my customer breaks their migration due to some incorrect plan. So I raise a migration question to discuss the zero-downtime migration plan.

This meetup we review previous discussions and switch to the next topic. Based on the high concurrency we talk about the last meetup, we simulate an architecture and evolution it.

About 1 year ago, I build a Ansible playbook for the customers of 5xRuby.

When the customers grow it is hard to use the fork feature to maintenance the customer’s playbook.

I have to update the main version and sync the changes to the fork version for each customer. Therefore I decided to split the common parts to a single role repository.

Yesterday is the first meetup of the TGONext project, we are learning from Taiwan’s high-level technical leaders. After the opening, our mentor Ant let our polling for the topic we want to discuss in this half-year project time.

We decide to pick up 4 topics to discuss and the first topic is “high concurrency.”

Include me, write test is many people’s nightmare. Many junior programmers feel it is hard to define which should be tested. So, I decided to share my experience after I tech my colleague today.