2616 Blooming as Expected
The tulips from the day they arrived to the moment they fully opened.
I recently joined a Yunnan flower group because I got curious about what flower keeping actually feels like.
Watching the whole bouquet open at its own pace made me settle down with it.
Nothing especially big happened this week. Instead, it was this kind of small and certain action that stayed with me the most.
Taking care of one small thing step by step, then watching the result grow the way it is supposed to, is deeply healing in itself. Flowers are like that. Work is like that too.
I also spent this week organizing my workflow. Instead of piling on more scattered scripts and rules, I would rather compress the high-frequency cases into a framework that is steadier, easier to reuse, and less likely to send me into avoidable pitfalls. It is still being polished, but the direction is much clearer than before.
Compared with immediately trying to do more, what I care about now is getting my sense of rhythm back first. What should be done first, what is worth solidifying, and what does not actually need to be solved right away are all slowly starting to take shape. Hopefully, in a few weeks, this can be polished enough to open source.
Things I Saw This Week
His blog is written with a lot of care. The Appdome analysis piece in particular taught me a few reverse engineering moves worth paying attention to. More than the specific content, I think I like the feeling he gives off as a whole, especially this line from his signature: if you are dissatisfied with what you have now, having more later may not make you happy either.
That sentence fits my state this week very well. A lot of the time, the problem is not simply that something is missing. It is that the rhythm has already become messy.
This is JetBrains' independent Git client idea in open-source recreated form. JetBrains talked about making it for a long time, then it quietly went nowhere, and someone else ended up building it in the open.
Once unpacked into Applications, it takes around 1.4 GB, which feels a bit too large for a Git tool. Still, for tasks with many submodules, it is much more comfortable than pure command line work.
Kaku is a deeply customized fork of WezTerm, designed for an out-of-the-box experience.
On X, I saw someone say that the way tw93 writes tools sounds like a true craftsman. I agree. A lot of information online makes me anxious, but when I look at the things he builds and the way he talks about products, it gives me the feeling of moving one step every day and enjoying the process itself. It can even be a little calming before sleep.
What really struck me: vim keybindings, sudo with fingerprint verification, and using AI through a custom model configuration. Warp still does not open this up.
Another comment that stayed with me said, roughly, that this was the first terminal in ten years that felt right without needing any configuration first.
I did run into a few issues on commands I use a lot though, which I may write about later.
In mobile security development, many fixed detection scenarios used to require hand-building a small app every time. Now that Google has shipped Android CLI, it feels like writing the plan and letting it handle the build-and-test loop may be enough. Traditional large-front-end Android development may really be nearing a turning point.
What I learned from this project is the value of turning common needs into an interface that ordinary people can call directly. Saying one sentence to disable a popup in an app is a strong idea.
Loose Notes
Recently I watched some videos where Charles Zhang talked about behavioral psychology, and one line really stayed with me: thought can design behavior, and behavior can change emotion.
"Thought can design behavior. Behavior can change emotion. Watch yourself, then design. Go perform the behavior of doing the things you should be doing. After that behavior is put into practice, it can change your emotion."
A lot of the time, it is not that I first need to think everything through and feel better before I can start doing things. A more effective way may be the reverse: watch myself first, design the behavior first, do the things that should be done first, and let the emotion catch up later.
That is really the same method as changing the flower water and organizing my workflow. Start with those small and certain actions, then let the state return little by little.
Leave a comment