By default, I leaned toward Plan B — I believed it had more advantages. And then I asked AI just one more question: “Can you implement all four of these approaches in code?” Ten minutes later, with the help of AI agents, all the code was done. No syntax errors.

Aside from two plans that ran into issues during auto-merging, everything else worked perfectly. Before asking, I already knew AI could technically do it. But when the completed code was laid out in front of me, that sense of powerlessness hit me hard.

That feeling of defeat in front of AI... I couldn’t shake it off. All your experience — ten-plus years as an engineer — distilled into this 10-minute “stare-down” with AI. All your professionalism — a decade of rigor and discipline — compressed into this one moment.

And AI simply says: “Please accept this reality.” I came across a set of “vibe coding” mottos yesterday: Go with the flow, avoid friction. Focus on problems, not the code. Right now, these are the only words I can lean on for comfort and encouragement.

It feels like GitHub has too many spiders, creating an illusion of popularity for open source projects. I’m not sure how GitHub’s recommendation algorithm works, but maybe like X (Twitter), you only get trickles of traffic by jumping on trending topics.

The Web3 space is now split into two camps: the speculative crypto crowd and the idealistic Web3 tech community.

From my experience of closely following the Web3 tech space over the past two years, the Web3 tech circle is similar to the open-source community — a group of idealistic tech evangelists actively promoting Web3 concepts in all possible scenarios. Many tech practitioners are also building and upgrading Web3 infrastructure.

However, this trend still falls short compared to the public consensus formed during Web1 and Web2. Even around the 2000 internet bubble, mainstream society viewed the internet as a technological revolution.

Web3 has yet to form such a unified public consensus. The general public still sees it mostly as a playground for speculators.

Establishing a strong public consensus for Web3 and improving its product experience and public image are, in my opinion, the most urgent issues to address.

I started reading some psychology books, and one explanation really struck me: when you achieve some success or get a reward, your brain releases a lot of dopamine. Then, around 24 hours later, you may feel what’s called “post-reward fatigue.”

When I saw that explanation, I was shocked. It helped me make sense of many of my emotional ups and downs.

After that, I followed some of the book's advice. I started writing a daily emotion diary, and I also began blogging—letting these continuous habits push me forward.

1. Today, I wrote a blog recording my indie coding daily life. When I clicked the "Publish" button to publish my blog, Mirror popped up a window asking me to try switching the network. Mirror's default network is OP, and I'm sure my wallet configuration is correct, but the check window kept loading, which was frustrating. When I changed Mirror's network setting to Polygon, the blog was published immediately. I suggest the Mirror team add a network health monitor, so that your loyal fans don't have to do this work themselves. They enjoy writing on your platform, and that’s an honor for you.

2. After publishing the blog, I tried to create an NFT and encountered the same network issue. I switched to all the networks supported by Mirror, but all of them failed. At one point, I saw Mirror's page invoke the MetaMask charging window, but I couldn't click the confirm button because it was greyed out. I was getting frustrated with these two problems.

3. Mirror.xyz's performance feels like it was developed by an amateur team. I see its topics are always hot, but the user experience is indeed terrible.

I hope Mirror.xyz can improve these issues.

Daily review of my app's data. I found my Google Adsense account is in audit status. Google Ads gave the reason not clearly. This issue I need to handle with higher priority.

Began to write Web3 lesson. This lesson is recording my learning steps, and it will also be a guide for others who want to learn Web3.

I reviewed my work for one startup company three years ago. I summarized my management experience to Bluesky and got lots of likes. That is a glad thing.

In the afternoon, I tried to use Mirror’s NFT feature. I attempted many times to create an NFT, but all actions failed. I noticed that creating an NFT on Mirror doesn’t cost the creator’s gas fee, but in my charge panel, the gas fee showed as $0.01. I don’t understand why this happened, and I’m still trying to find the answer.

After that, I continued with my IELTS lessons. I realized that three years ago, when I was reading tweets, I could understand the content but couldn’t feel the emotions behind the words. Even though I understood what they were talking about, I couldn’t grasp the emotions in the native speaker’s words. Maybe it’s due to the difference between written words and spoken language.