Our work project uses Go for development, and we ultimately chose XORM for our ORM solution. We encountered many issues during implementation, but the official documentation is limited, so I’m sharing some tips and tricks here.

I don’t know if you’ve experienced a similar pain point as me - connecting a MacBook Pro to a Dell monitor but being unable to adjust the monitor brightness within the system. For someone like me who often works late at night and wants to protect my eyes, I need to lower the brightness. That’s when I found the open-source tool Monitor Control.

By chance, I heard about HHKB on a tech podcast on Podcasts. After waiting for half a year, I finally got the HHKB Professional HYBRID Type-S during JD’s 618 sale. After using it for less than a week, I’d like to share my experience.

Recently, while cleaning up my computer, I carelessly upgraded VirtualBox from 6.0.* to 6.1.10. After the upgrade, I found that I could no longer start the project’s development environment.

Recently, I needed to implement a Google login feature, but the production server could not access Google’s authentication server, so I wondered if I could use a Socks5 proxy in the HTTP Client.

Recently, I encountered a requirement to support Google login, but found that the server could not access Google’s servers. Fortunately, I had an idle SS server, so I started working on it.

With the development of frontend technology, page routing has gradually moved to the frontend, and pages are rendered by client browsers. Projects may not have considered SEO at the beginning, and later require invasive modifications. This open-source project was born to solve this problem.

Previously, there was an Electron-based desktop client called Kitematic, which was packaged with Docker Toolbox and included in Docker for Mac and Docker for Windows.

Due to the pandemic, we can only work remotely from home, but the development environment databases are in the company’s internal network. For databases that are tens or hundreds of GB in size, synchronizing them to your own computer is very time-consuming and occupies local storage space.

Elastic Stack comes with its own HTTP service and allows customizing listening ports. So why use Nginx as a reverse proxy? Mainly for HTTPS and Basic Auth, as we know that only the Enterprise version of Elastic Stack enables user authentication.