2026-04-17 17:45:00
Notes about how to use ripgrep to search hidden files and configuration related to Neovim.
2026-04-15 00:11:35
We have a Python project where there are several developers, and we have a mature CI pipeline to do code linting, formatting check for python, yaml, json, and testing etc. The problem with CI pipeline is that you can only get feedback after you commit your code and push to the remote repo. The feedback is not instant and may be delayed for several minutes. If there are some linting issues, you then need to fix the issue and make another commit. This is also making the PR history messy.
2026-04-03 05:18:10
A major Neovim release (version 0.12) has been released a few days ago, after more than one year from the last major release (version 0.11). The following is a list of feature I am interested. For a complete set of features, check full changelog and news.
vim.pack
#
Now you can use the builtin vim.pack API to manage your plugins.
Check this detailed post if you want to migrate to vim.pack.
2026-04-01 01:10:40
When unit-testing a function that make multiple external calls/requests, we want to mock the actual call and return the mock results. For each call, we might want to return different results.
2026-03-28 02:12:27
Previously, our projects are still using the old Python 3.10, which will be deprecated soon this year. We are also using the good old pip and venv for the project/package management. This is already posing some issues for us:
requirements.txt is not a lockfile and thus does not ensure a fully reproducible python environmentIn order to solve these problems, I took the effort to migrate our project management to uv. Here are some of the things that I learned in the process as a first-time uv user.
2026-02-15 23:06:55