<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
    <title>Domechn.</title>
    <link>https://domc.me/</link>
    <description>A Developer and A Stupid Person</description>
    
        <item>
            <title>My Daily AI Workflow: Cutting $150/Month with the Right Model Mix</title>
            <link>https://domc.me/en/posts/ai-my-daily-workflow.html</link>
            <description>How I combine multiple AI products to boost efficiency and cut costs</description>
            <pubDate>Fri, 17 Apr 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/ai-my-daily-workflow.html</guid>
        </item>
        
        <item>
            <title>我的日常 AI 工作流：如何组合使用省下 150 美元/月</title>
            <link>https://domc.me/zh/posts/ai-my-daily-workflow.html</link>
            <description>我是怎么组合使用多个 AI 产品来提升效率、节省成本的</description>
            <pubDate>Fri, 17 Apr 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/ai-my-daily-workflow.html</guid>
        </item>
        
        <item>
            <title>I Gave Up on Obsidian and Notion and Built My Own AI-Powered Second Brain</title>
            <link>https://domc.me/en/posts/second-brain-with-ai.html</link>
            <description>I gave up on Obsidian and Notion and built my own AI-powered second brain</description>
            <pubDate>Fri, 10 Apr 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/second-brain-with-ai.html</guid>
        </item>
        
        <item>
            <title>放弃 Obsidian 和 Notion，我用 AI 给自己造了一套第二大脑</title>
            <link>https://domc.me/zh/posts/second-brain-with-ai.html</link>
            <description>放弃 Obsidian 和 Notion，我用 AI 给自己造了一套第二大脑</description>
            <pubDate>Fri, 10 Apr 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/second-brain-with-ai.html</guid>
        </item>
        
        <item>
            <title>Best Practices for Go Monorepo Dependency Management</title>
            <link>https://domc.me/en/posts/go-monorepo-best-practices.html</link>
            <description>Best practices for Go Monorepo dependency management, using modular go.mod files and replace directives to solve version conflicts and improve build efficiency.</description>
            <pubDate>Wed, 21 Jan 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/go-monorepo-best-practices.html</guid>
        </item>
        
        <item>
            <title>Go Monorepo 依赖管理最佳实践</title>
            <link>https://domc.me/zh/posts/go-monorepo-best-practices.html</link>
            <description>Go Monorepo 依赖管理最佳实践，通过模块化 go.mod 和 replace 指令解决多服务依赖版本冲突，提升构建效率。</description>
            <pubDate>Wed, 21 Jan 2026 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/go-monorepo-best-practices.html</guid>
        </item>
        
        <item>
            <title>ArgoCD Monorepo Performance Optimization (Part 2): Cache, Sidecar &amp; Git Tuning</title>
            <link>https://domc.me/en/posts/argocd-monorepo-performance-optimization-2.html</link>
            <description>Part 2: How we reduced ArgoCD sync time from 3min to under 30s — cluster cache tuning (ARGOCD_CLUSTER_CACHE_RESYNC_DURATION), sidecar plugin tarball optimization (95% CPU drop, 3s → 400ms), proactive git fetch, and scheduled git gc with readiness probe gating.</description>
            <pubDate>Mon, 02 Sep 2024 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/argocd-monorepo-performance-optimization-2.html</guid>
        </item>
        
        <item>
            <title>ArgoCD Monorepo 性能优化（二）：缓存、Sidecar 与 Git 策略调优</title>
            <link>https://domc.me/zh/posts/argocd-monorepo-performance-optimization-2.html</link>
            <description>第二篇：我们如何将 ArgoCD sync 时间从 3min 降到 30s 以内——涵盖 cluster 缓存策略调优、sidecar 压缩优化（CPU 降低 95%、3s→4s）、主动 git fetch 以及带 readiness 阈关的定期 git gc。</description>
            <pubDate>Mon, 02 Sep 2024 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/argocd-monorepo-performance-optimization-2.html</guid>
        </item>
        
        <item>
            <title>ArgoCD Monorepo Performance Optimization: Scaling to 100k+ Apps</title>
            <link>https://domc.me/en/posts/argocd-monorepo-performance-optimization.html</link>
            <description>How we scaled ArgoCD to manage 100k+ applications in a single Monorepo — covering repo server tuning, disabling auto-refresh, custom sync workflows, and a controller patch to eliminate jitter.</description>
            <pubDate>Sat, 03 Aug 2024 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/argocd-monorepo-performance-optimization.html</guid>
        </item>
        
        <item>
            <title>ArgoCD Monorepo 性能优化：如何稳定管理 100k+ 应用</title>
            <link>https://domc.me/zh/posts/argocd-monorepo-performance-optimization.html</link>
            <description>我们如何让单个 Monorepo 稳定管理 100k+ ArgoCD 应用——涵盖 repo server 调优、关闭自动刷新、自定义同步工作流，以及彻底消除 controller 抖动的 patch 方案。</description>
            <pubDate>Sat, 03 Aug 2024 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/argocd-monorepo-performance-optimization.html</guid>
        </item>
        
        <item>
            <title>How to Manage Multi-Wallet Crypto Assets: Hardware Wallets &amp; Automated Tracking</title>
            <link>https://domc.me/en/posts/managing-my-crypto-assets.html</link>
            <description>A practical guide to managing multi-wallet crypto assets securely — hardware wallets (Ledger, Tangem), risk diversification strategies, and Track3, an open-source portfolio tracker that auto-syncs balances across wallets and exchanges.</description>
            <pubDate>Fri, 30 Jun 2023 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/managing-my-crypto-assets.html</guid>
        </item>
        
        <item>
            <title>如何管理多钱包加密资产：硬件钱包与自动化追踪实践</title>
            <link>https://domc.me/zh/posts/managing-my-crypto-assets.html</link>
            <description>实用指南：如何安全管理多钱包加密资产——硬件钱包（Ledger、Tangem）选择、分散风险策略，以及开源工具 Track3 如何自动同步所有钱包和交易所的资产数据。</description>
            <pubDate>Fri, 30 Jun 2023 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/managing-my-crypto-assets.html</guid>
        </item>
        
        <item>
            <title>Cilium from 0 to 0.1</title>
            <link>https://domc.me/en/posts/cilium-from-0-to-0-1.html</link>
            <description>Cilium and eBPF from scratch: how Linux processes packets, how Cilium replaces iptables with eBPF programs, XDP/TC hook points, BPF maps, tail calls, and hands-on troubleshooting with bpftool and cilium-dbg.</description>
            <pubDate>Sun, 17 Oct 2021 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/cilium-from-0-to-0-1.html</guid>
        </item>
        
        <item>
            <title>Cilium 从 0 到 0.1</title>
            <link>https://domc.me/zh/posts/cilium-from-0-to-0-1.html</link>
            <description>深入解析 Cilium 与 eBPF 基础，涵盖 Linux 数据包处理流程、eBPF 在 Cilium 中的应用、核心特性使用及故障排查指南。</description>
            <pubDate>Sun, 17 Oct 2021 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/cilium-from-0-to-0-1.html</guid>
        </item>
        
        <item>
            <title>Kubernetes Gateway API</title>
            <link>https://domc.me/en/posts/Kubernetes-Gateway-API.html</link>
            <description>An introduction to the Kubernetes Gateway API (KGA), its evolution from Ingress, and its key features like traffic management, role-oriented design, and extensibility.</description>
            <pubDate>Mon, 10 May 2021 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/Kubernetes-Gateway-API.html</guid>
        </item>
        
        <item>
            <title>Kubernetes Gateway API</title>
            <link>https://domc.me/zh/posts/Kubernetes-Gateway-API.html</link>
            <description>介绍 Kubernetes Gateway API (KGA) 的概念、演进历史以及流量管理、面向角色设计等核心功能，探讨其解决 Ingress 局限性的方案。</description>
            <pubDate>Mon, 10 May 2021 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/Kubernetes-Gateway-API.html</guid>
        </item>
        
        <item>
            <title>A WebSocket Connection Leak Troubleshooting Investigation</title>
            <link>https://domc.me/en/posts/websocket-connection-leak-investigation.html</link>
            <description>Root-cause analysis of a Go WebSocket connection leak — why server-side close doesn't terminate the client goroutine, how to detect goroutine leaks with pprof, and the fix using proper close handshake.</description>
            <pubDate>Sun, 29 Dec 2019 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/websocket-connection-leak-investigation.html</guid>
        </item>
        
        <item>
            <title>记一次 WebSocket 连接泄露排查</title>
            <link>https://domc.me/zh/posts/websocket-connection-leak-investigation.html</link>
            <description>记录一次 Go 服务端 WebSocket 连接泄露的排查过程，分析因服务端未正确处理客户端断开导致连接无法释放的问题。</description>
            <pubDate>Sun, 29 Dec 2019 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/websocket-connection-leak-investigation.html</guid>
        </item>
        
        <item>
            <title>ExitCode: 128 with No Error Message</title>
            <link>https://domc.me/en/posts/exitcode-128-no-error-message.html</link>
            <description>Troubleshooting a mysterious Exit Code 128 in Drone CI caused by Pod image conflicts between the runner and another service modifying image addresses.</description>
            <pubDate>Thu, 21 Nov 2019 00:00:00 -0000</pubDate>
            <guid>https://domc.me/en/posts/exitcode-128-no-error-message.html</guid>
        </item>
        
        <item>
            <title>ExitCode: 128 之无任何错误信息</title>
            <link>https://domc.me/zh/posts/exitcode-128-no-error-message.html</link>
            <description>排查 Drone CI 构建中出现的 Exit Code 128 错误，分析 K8S Pod 镜像地址被其他服务修改导致 runner 更新 Pod 引发的冲突问题。</description>
            <pubDate>Thu, 21 Nov 2019 00:00:00 -0000</pubDate>
            <guid>https://domc.me/zh/posts/exitcode-128-no-error-message.html</guid>
        </item>
        
</channel>
</rss>
    