In the blink of an eye, April has passed, yet I still haven’t gotten around to writing. It’s not simply a matter of lacking time, I’ve just been so immersed in Flakes that I haven’t been able to pull myself away. With quite a few readers clamoring for an update, I decided to write and release a portion first. Since the beginning of the year, from using Flakes to uniformly manage various services and environments on macOS on my MacBook to the present, nearly all my Linux workstations and servers have been taken over and configured by Flakes. One could say it has become unstoppable. Paired with the powerful drive of Claude Code, I have found the ultimate best practice for Vibe DevOps.

Yea yea I know, so many people on Hacker News have so many different opinions about AI Coding. Some people say that AI coding has completely changed programming, while others claim that AI coding is merely wasting people’s time. Although most people are not so binary in their views, I can’t help but ponder why there is such a significant divide regarding AI coding. Even among my peers in the industry, this great divergence exists. Actually, I’m also an AI coding user, from the earliest Copilot to the current Claude Code, I have kept up with the trends of the times. However, personally, I have also experienced many changes in my attitude toward AI coding. In this article, I would like to use a mathematical way to answer why people’s experiences with AI coding are so different, and whether we can use a formula to determine if our projects should use AI coding.

Today, this machine is quite an old model, HPE’s ProLiant DL388p Gen8, which has been in service for ten years. The initial problem was that I couldn’t access iLO, I thought I had forgotten the password, so I asked someone to debug it on-site. As a result, I found that the BIOS management password couldn’t be used normally either. After resetting it using the S6 on the motherboard, I could access iLO with the default password, but nothing would load…

Recently, I got in touch with a Dell RTX 4070 graphics card, which was taken from another workstation of ours. PCI passthrough is an old skill that I’ve even written articles about. However, after confidently executing the passthrough, I found that the card couldn’t be used normally in the virtual machine. I suspected the graphics card itself, but when plugged it into another device, it was easily driven. I doubted the newly upgraded PVE 9.0, but even with the old kernel, it couldn’t passthrough. I switched the type of virtual machine multiple times, but this card simply wouldn’t work in the virtual machine. In the end, I began to suspect that this card was different because it was OEM…

Recently, I returned to my parents’ house for the Eid al-Adha, and then I had to go on a business trip, so I could only bring my MacBook Air. This gave me an opportunity to explore some SSH functionalities on macOS. Those familiar with me know that I always connect to servers or sign commits using the FIDO2 SSH with YubiKey. However, frequently plugging and unplugging the YubiKey on a mobile device like a MacBook has indeed been a significant mental burden for me. Consequently, I began to research a secure and convenient SSH solution on macOS, leading to the wonderful way…