Errong Leng

WSC QA: Interactive Catechism Learning App By Q.Z.L Team | Published on 2026-01-20 Demo Video Elevator Pitch Deepen your knowledge of the Westminster Shorter Catechism in English & Chinese with a modern app featuring full Q&A, scripture references, quizzes, text-to-speech, and an AI Tutor for guided learning. What it does Complete catechism Q&A in English & Chinese. Full scripture references for every answer. Interactive quiz mode to test knowledge and memorization. Text-to-speech support for auditory learning. AI Tutor Chat powered by Gemini 3 for real-time guidance. Modern interface for smooth browsing and study. Try it now: Web App | Android w/ ads | Android Paid, no ads Inspiration We wanted a modern, interactive, and accessible way to study the Westminster Shorter Catechism. S...

COCA 16515: Master English Vocabulary Efficiently By Q.Z.L Team | Published on 2026-01-20 We’re excited to announce COCA 16515 , a vocabulary learning app designed to help learners master the 16,515 most frequent English words from the Corpus of Contemporary American English (COCA) . Built from my own experience preparing for IELTS and Canadian PR, this app turns a huge word list into a fun, structured learning journey. Demo Video What it does 16,515 COCA words with bilingual definitions (English–Chinese). Context-rich examples, multiple usages, and pronunciation guides. Flashcards, quizzes, and progress tracking (XP, streaks, mastery goals). Interactive web and mobile apps for study anywhere, anytime. Try it now: Web App | Android w/ ads | Android Paid, no ads Inspiration While preparing for IELTS, I realized that studyi...

在学习祷告中成长 今天下午的讲道围绕祷告展开，信息温柔而充满牧养的关怀。讲员不是要指出我们祷告得不够好，而是鼓励我们： 在学习祷告的过程中，祷告的生命也要不断成长。 讲道首先问到： 我们向谁祷告？ 我们祷告的对象不是遥远的神，而是我们在基督里所认识的天父。藉着主耶稣的救赎，我们成为神的儿女；靠着圣灵的帮助，我们可以呼喊“阿爸，父！”祷告因此不再只是宗教形式，而是儿女与父亲之间亲密的交通。 接着讲员解释： 祷告是什么？ 要理问答说，祷告就是“从心里呼求神”。祷告是一种真实、诚恳、发自内心的与神说话。神早已知道我们心中的需要与软弱，因此我们可以坦然无惧地来到祂面前。 讲道也提醒我们，祷告并不在于言语的多少或表达的技巧，而是在于向神的祈求、感谢、认罪与赞美。当我们不知道该说什么时，可以用圣经的话祷告——例如诗篇或主祷文——因为圣灵会帮助我们祷告。 至于在哪里和什么时候祷告，答案是随时随地。但耶稣也教导我们，个人祷告最好是在安静、私下的地方，与神独处。教会历史中常有固定祷告时间的传统，这不是律法主义，而是出于爱与属灵的操练。 最后，我们被提醒为什么要祷告：因为我们爱神，因为神爱我们，也因为我们需要完全依靠祂的恩典与圣灵的工作。 愿我们在学习祷告的真理时，也在祷告的生命中不断长进。 经文： 马太福音6章；罗马书8章 主题： 在学习祷告中成长

This afternoon’s sermon offered a gentle and deeply pastoral invitation into the life of prayer. The message did not aim to make us feel guilty for not praying “correctly,” but rather encouraged us to grow in prayer as we grow in understanding what prayer truly is. The first question asked was: Who do we pray to? The sermon reminded us that we do not pray to an abstract or distant deity, but to our loving Father . Through Christ, we are children of God, and by the Holy Spirit we cry out, “Abba, Father.” This truth reshapes prayer from a religious duty into a loving conversation within a covenant relationship. Then we were asked: What is prayer? Prayer was described simply as “calling upon God from the heart.” It is speaking honestly and sincerely to the Father — not with perfect words, but with a true heart. This encourages believers to bring their real selves before God, trusting that He already knows and cares. We also learned that prayer is not about using the right number...

Labels: 讲道反思, 犹大书, 信仰争战, 教会, 分辨力 为信仰竭力争辩 诗歌34首《神赐下这宝贵的一日》，为今天的敬拜带来了庄重与敬畏的气氛。 今天的信息来自犹大书3–4节，主题十分清楚，也十分严肃： 教会必须为信仰竭力争辩。 讲员以丘吉尔在战壕中检查士兵的故事作引入，让我看到犹大的处境。犹大原本渴望写一封关于救恩的温柔书信，却发现教会已经处于属灵的战火之中，因此不得不写下劝勉与警告。 最触动我的是，讲道指出：这场争战主要不是面对教会外的世界，而是面对那些混入教会、却歪曲神恩典的人。他们把神的恩典当作放纵情欲的借口。教会最大的危险，其实来自内部。 这让我重新认识到，我们所守护的不是个人的感受或传统，而是 那一次交付圣徒的信仰 ——永不改变的福音真理。在这个一切都不断改变的时代，神的话语仍然坚定可靠。 这篇讲道也让我反思： 我是否真正明白自己所信的真理？ 我是否能凭着“果子”分辨真假教训？ 当真理变得不受欢迎时，我是否仍愿意坚守？ 讲道最后提到，有人把一幅价值连城的名画挂在家中多年，却毫不知情地卖掉。若我们不愿为信仰争战，也许不是因为信仰没有价值，而是因为我们还没有认识它的宝贵。 愿神赐给我们勇气与智慧，在这个时代忠心守护祂的真理。 经文： 犹大书3–4节 主题： 为信仰争战

Hymn 34, “God gave to us this day of days,” set a solemn and worshipful tone for today’s service. Today’s sermon from Jude 3–4 was both sobering and deeply needed. The central message was clear: the church must contend for the faith. The illustration from Winston Churchill standing in the trenches helped me see Jude’s situation more clearly. Jude wanted to write about our shared salvation, but instead found himself writing a warning letter. The church was under spiritual attack, and he had to rally believers to stand firm. What struck me most was the emphasis that this battle is not mainly against the world outside the church, but against those who quietly enter the church and distort God’s grace into a license for sin. The greatest danger comes from within. This reminded me that we are not defending personal preferences or cultural opinions. We are holding fast to the faith once delivered to the saints — the unchanging truth of the Gospel. While the world constantly changes...

Fix INSTALL_FAILED_UPDATE_INCOMPATIBLE When Installing Android APK via ADB After building your React Native Android release APK, you may encounter this error when installing it: adb: failed to install app-release.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package signatures do not match newer version] This means the APK was built successfully, but Android refuses to install it because the app on your device was signed with a different certificate. Why This Happens Android requires that any update to an existing app must be signed with the same keystore as the original installation. Typically this happens when: You installed a debug build previously You switched keystores for your release build You changed your signing configuration If the signatures don’t match, Android will block the installation. How to Fix It Option 1: Uninstall the Existing App (Quick Fix) adb uninstall com.westminstershortercatechismqa adb install app-release.apk Onc...

解决 adb install 时 INSTALL_FAILED_UPDATE_INCOMPATIBLE 签名不匹配错误 在使用 React Native 构建 Android Release APK 后，通过 adb 安装时，可能会遇到如下错误： adb: failed to install app-release.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package signatures do not match newer version] 这个问题并不是编译失败，而是 Android 安装机制阻止了不同签名的应用覆盖安装 。 为什么会出现这个错误？ Android 系统要求：同一个包名的 App，在更新时必须使用相同的签名证书。 如果你之前安装的是： Debug 版本（默认签名） 或者使用了不同的 Release Keystore 而现在你安装的是新的 Release APK（使用了不同签名），系统就会拒绝更新，从而出现此错误。 解决方法 方法 1：卸载旧应用（最简单） adb uninstall com.westminstershortercatechismqa adb install app-release.apk 卸载后再安装即可正常运行。 方法 2：使用统一的 Release Keystore 如果你希望以后可以直接覆盖安装（升级 App），需要保证每次构建 Release 都使用同一个 keystore。 在 android/app/build.gradle 中配置： android { signingConfigs { release { storeFile file("release.keystore") storePassword "your_password" keyAlias "your_alias" keyPassword "your_password" } } buildTypes { release { ...

React Native 使用 TypeScript + Hermes 时 Android Release 构建报错解决方案 如果你把 React Native 项目的入口文件从 index.js 改成了 index.ts ，然后在构建 Android Release 版本时失败，这篇文章可以帮你解决。 常见的报错包括： Task ':app:createBundleReleaseJsAndAssets' property 'entryFile' specifies file 'index.js' which doesn't exist. 或者： java.lang.OutOfMemoryError: Metaspace Execution failed for task ':react-native-xxx:lintVitalAnalyzeRelease' 这通常是由于入口文件未正确配置，以及 Gradle 内存不足导致的。下面是完整修复步骤。 1. 修复入口文件路径错误 React Native 默认查找 index.js ，如果你使用 TypeScript，需要告诉 Gradle 使用 index.ts 。 打开 android/app/build.gradle ，在 react {} 配置中加入： react { entryFile = file("../../index.ts") } 同时确认 package.json 中的入口文件： "main": "index.ts" 并在 metro.config.js 中支持 TypeScript： resolver: { sourceExts: ["js", "json", "ts", "tsx"] } 2. 解决 Gradle Metaspace 内存不足 Android 在 Release 构建时会运行 Lint 分析 React Native 库的 Kotlin 文件，默认内存太小会导致崩溃。 编辑 an...

Fixing React Native Android Release Build Errors with TypeScript & Hermes If your React Native Android release build fails after renaming index.js to index.ts , you're not alone. This is one of the most common issues when modernizing a React Native project with TypeScript and Hermes. Here are the two major errors you’ll likely see: Task ':app:createBundleReleaseJsAndAssets' property 'entryFile' specifies file 'index.js' which doesn't exist. And later: java.lang.OutOfMemoryError: Metaspace Execution failed for task ':react-native-xxx:lintVitalAnalyzeRelease' Let’s fix both problems step by step. 1. React Native Can’t Find Your Entry File React Native expects your app’s entry file to be index.js . When you rename it to index.ts , Gradle doesn’t know where to look. Open android/app/build.gradle and add this inside the react {} block: react { entryFile = file("../../index.ts") } Also make sure your package...

从写代码到定义使命：一次技术负责人的思考 今天，作为一名技术负责人（Tech Lead），我参加了一次领导力培训。这次培训出乎意料地改变了我对团队、责任以及影响力的理解。 我们并没有讨论技术框架、系统架构图，或者性能优化。 相反，我们聚焦在一个更根本的问题上： 学会不断追问“为什么” 作为工程师，我们习惯于问 “怎么做” ： 这个功能怎么实现？ 怎么优化性能？ 这个问题怎么修？ 但领导力，往往始于另一个问题： 为什么这个团队存在？ 如果没有清晰的“为什么”，团队很容易迷失方向，工作变成被动响应，决策也会显得零散而割裂。 一句话使命（Single Statement）框架 培训中介绍了一个非常简单却极具力量的方式，用一句话来定义团队的使命： 为了 <行动>，服务 <人>，从而带来 <影响>。 这个结构迫使我们直面本质： 行动（Action） —— 我们具体在做什么？ 人（People） —— 我们为谁而做？ 影响（Impact） —— 我们真正想带来什么改变？ 这对技术负责人的意义 当成为 Tech Lead 之后，角色已经不再只是“写好代码”。 我们需要对以下内容负责： 使命（Purpose） —— 团队存在的意义 领域（Domain） —— 我们负责什么，不负责什么 责任（Accountability） —— 决策和结果如何被承担 一句清晰的使命宣言，就像团队的指南针： 帮助团队做优先级判断 对齐技术决策 让团队成员在没有指令的情况下也能做出正确选择 向优秀使命学习 培训中我们也参考了一些知名公司的使命表达。 一个经典的例子是： “整合全球信息，使人人皆可访问并从中受益。”   行动清晰，对象明确，影响直接。 它解释了 为什么 Google 会去做它所做的一切，而不需要列出任何具体产品。 回到我自己的角色 这次培训让我再次意识到：领导力的核心不是控制，而是清晰。 当团队真正理解自己的使命时： 责任感会自然提升 协作会更加顺畅 决策能力会从 Tech Lead 扩展到整个团队 接下来...

From Building Software to Defining Purpose: A Tech Lead Reflection Today, as a tech lead, I joined a leadership training that unexpectedly shifted how I think about teams, ownership, and impact. We didn’t talk about frameworks, architecture diagrams, or performance tuning. Instead, we focused on something much more fundamental: Learning to Ask “Why” As engineers, we are trained to ask how : How do we implement this? How do we optimize it? How do we fix it? But leadership starts with a different question: Why does this team exist? Without a clear “why,” teams drift. Work becomes reactive. Decisions feel disconnected. The Single Statement Framework The training introduced a simple but powerful way to define a team’s purpose using one sentence: To <ACTION> for <PEOPLE> so that <IMPACT>. This structure forces clarity. Action — What do we actively do? People — Who do we serve? Impact — What meaningful change do we create...

解决 Android Studio 中 React Native “A problem occurred starting process 'command node'” 错误 如果您在构建 React Native Android 项目时遇到以下 Gradle 同步错误： A problem occurred evaluating project ':react-native-svg'. > A problem occurred starting process 'command 'node'' 即使您在终端中能够正常运行 node 命令，也无法在 Android Studio 中构建成功，本文将帮您快速解决该问题。 常见误区 此错误通常被误认为是 Node.js 或 PATH 配置问题，但实际情况并非如此。 Node.js 已安装并且在终端正常运行。 PATH 和环境变量配置正确。 但是 Android Studio 的 Gradle 同步仍然失败。 真正的原因 该问题通常是因为 Android Studio 中 Gradle 使用的 JDK 配置不正确 。Gradle 运行在 JVM 上，并通过 JVM 启动外部进程（例如 node ）。 如果 Gradle JDK 版本不兼容或配置错误，Gradle 将无法启动这些进程，从而导致该错误，即使系统中 Node.js 正常安装。 解决方案 请按照以下步骤修复： 打开 Android Studio 的 设置 （macOS 下为 Preferences ）。 导航到： Build, Execution, Deployment > Build Tools > Gradle 在 Gradle JDK 中，避免选择默认的 JetBrains Runtime 或内置选项。 选择手动安装的 JDK ，推荐使用类似 Azul Zulu JDK 17 的版本，且要与您的系统架构（如 Apple Silicon 的 aarch64）匹配。 保存并重新同步项目。 这样做能保证 Gradle 正确启动 Node 和其他进程，解决构建失败问题。 m...

Fix “A problem occurred starting process 'command node'” in Android Studio for React Native If you are building a React Native Android project and encounter this error during Gradle sync: A problem occurred evaluating project ':react-native-svg'. > A problem occurred starting process 'command 'node'' —even though node works perfectly in your terminal—this guide will show you how to fix it quickly. Common Misconceptions This error is often mistaken as a Node.js or PATH issue, but that is not always the case. Node.js is installed and working in your terminal. PATH and environment variables appear correct. Still, Android Studio Gradle sync fails with the above error. The Real Cause The issue typically arises because of an incorrect Gradle JDK configuration inside Android Studio . Gradle runs inside a JVM and uses that JVM to spawn external processes (like node ). If the Gradle JDK is incompatible or misconfigured, Gradle will...

Handling Keyboard Appearance in React Native Chat UI (iOS & Android) When building a chat-style interface in React Native, one of the most common UX problems is the input box being covered by the on-screen keyboard . This issue affects both iOS and Android, but the underlying behavior and fixes differ slightly. In this post, I’ll walk through how we solved this problem in a real chat screen implementation, covering: Using KeyboardAvoidingView correctly Adjusting input position dynamically iOS vs Android behavior differences Why Android does require an AndroidManifest.xml change 1. Wrapping the Screen with KeyboardAvoidingView The foundation of the solution is React Native’s built-in KeyboardAvoidingView . The entire chat screen is wrapped inside it: <KeyboardAvoidingView style={styles.root} behavior="padding" keyboardVerticalOffset={Platform.OS === 'ios' ? 90 : 80} > {/* Chat UI */} </KeyboardAvoidingView> T...

React Native：键盘弹出时如何正确调整输入框位置（iOS & Android 实战） 在开发聊天类应用（Chat UI）时，一个非常常见、但又容易踩坑的问题是： 当键盘弹出时，输入框被遮挡，或者整体布局错乱。 本文将结合一个真实的 React Native 聊天界面示例，详细说明： 如何在键盘弹出时自动上移输入框 为什么 KeyboardAvoidingView 是首选方案 iOS 和 Android 需要注意的差异和额外配置 一、核心思路：使用 KeyboardAvoidingView 在 React Native 中，官方推荐用于处理键盘遮挡问题的组件是： KeyboardAvoidingView 在本项目中，整个聊天页面被包裹在 KeyboardAvoidingView 中： <KeyboardAvoidingView style={styles.root} behavior="padding" keyboardVerticalOffset={Platform.OS === 'ios' ? 90 : 80} > {/* Chat content */} </KeyboardAvoidingView> 这样做的好处是： 键盘弹出时，系统自动为内容腾出空间 输入框始终可见，不会被遮挡 无需手动监听 keyboard show / hide 事件 二、behavior 属性如何选择？ KeyboardAvoidingView 的 behavior 决定了布局如何响应键盘： padding （推荐）：通过增加底部 padding 上移内容 height ：减少视图高度（Android 上偶尔会闪动） position ：通过 position 调整（不稳定，较少使用） 在聊天类 UI 中， padding 是最稳定、体验最好的选择 。 三、keyboardVerticalOffset：为什么必须设置？ 如果你的页面顶部有： 导航栏（Navigation Header） 自定义 Header S...

Fix "No task registered for key TrackPlayer" Warning in React Native Track Player v5 The Problem You've implemented audio playback in your React Native app using react-native-track-player , created a nice custom hook, and everything seems to work... until you see this warning in your console: No task registered for key TrackPlayer anonymous @ console.js:662 overrideMethod @ backend.js:17416 anonymous @ setUpDeveloperTools.js:42 registerWarning @ LogBox.js:222 anonymous @ LogBox.js:84 startHeadlessTask @ AppRegistryImpl.js:265 This warning appears when you try to play audio, and while your audio might still work, it's a sign that something important is missing from your configuration. Why This Happens react-native-track-player requires a playback service to be registered before it can handle audio playback properly. This service is essential for: ...

Fixing React Native Path Alias Error: Unable to Resolve Module @/app/App The Problem If you're using path aliases (like @/ ) in your React Native project, you might encounter this frustrating error: ERROR Error: Unable to resolve module @/app/App from /path/to/project/index.ts: @/app/App could not be found within the project or in these directories: node_modules ../node_modules This happens even when your TypeScript configuration is correct and your IDE shows no errors. What's going on? Why This Happens The issue occurs because TypeScript and Metro (React Native's bundler) are two separate systems : TypeScript understands your path aliases through tsconfig.json Metro (the bundler) has no idea about these aliases unless you explicitly configure it Your IDE might show everything is fine because it use...

第十诫——向内、向外、向上 “不可贪恋。” 初看之下，第十条诫命似乎显得抽象、概括，甚至不像其他诫命那样具体。然而，正是在这一点上，第十诫显出它独特而深刻的属灵分量。 第十诫并不肤浅。它直指人心，贯穿整个人生，并最终把我们的目光引向基督。 一、它深深进入我们的内心 世上的法律大多规范外在行为，但神的律法却更进一步。第十诫专注于人内在的世界——那些隐藏在外表之下的欲望、渴求、野心与思想。 贪恋不是用手、脚或口去做的事情，而是发生在心里的事。也许别人看不见，但神看得一清二楚。圣经告诉我们：我们坐下、起来，神都晓得；我们的意念，祂从远处早已察觉。 因此，第十诫对每个人都极具挑战性。我们在外表上也许显得端正、得体、敬虔，但神的律法却追问： 你心里真正渴望的是什么？ 圣经的历史一再告诉我们，罪的问题始于内心。从伊甸园开始，人类的失败不是因为命令不清楚，而是因为心发生了偏移。该隐的暴力、洪水前的败坏、以色列的悖逆，都源于人心的堕落。 第十诫迫使我们诚实地面对自己的内心状态，而不仅仅是外在行为。 二、它广泛涵盖我们的生命 要理问答智慧地指出，第十诫在某种意义上为所有诫命提供了一把钥匙。所有诫命都应从“由内而外”的角度来理解。 主耶稣在登山宝训中清楚地教导这一点：杀人始于怒气，奸淫始于情欲，偷盗、作假见证和毁谤，也都根植于内心扭曲的欲望。 因此，第十诫并非局限于某一个罪，而是延伸到生命的每个层面。它揭示罪的根源，并提醒我们，真正的顺服不是表面的守规条，而是内心与神旨意的对齐。 即便是真正归向神的信徒，也会在这一点上被谦卑下来。要理问答坦率地承认：即使最圣洁的人，在今生也只有新顺服的起头。 这不是为了打击信心，而是为了真实。连被称为“合神心意的人”，也需要悔改与恩典。 三、它最终把我们引向基督 若第十诫只揭露人的失败，结局必然是绝望。但神严格宣讲律法，目的却是出于恩典。 借着律法，我们更深认识自己的罪性，不是为了沉沦，而是为了更迫切地转向基督，寻求赦免与义。 我们无法做到的，基督已经完全成就。祂的顺服是完全的，祂的献祭是充足的，祂的义归算给一切信靠祂的人。 这并不会让人松懈，反而激发感恩的生命。感恩推动祷告，推动更新，也推动我们追求圣洁。基督徒生命的方向始终是向上的——向着坐在父神右边的基督。 ...

The Tenth Commandment Goes Deep, Far, and Up “You shall not covet.” At first glance, the tenth commandment can feel vague, even anticlimactic. It lacks the clear outward actions of the others. No murder. No theft. No false testimony. And yet, as this reflection reminds us, the tenth commandment may be the most searching of them all. Far from being shallow or general, the tenth commandment reaches where no human law can reach. It goes deep into the heart, ranges far across our entire lives, and ultimately lifts our eyes upward to Christ. 1. It Goes Deep into Our Hearts Most laws regulate external behavior. God’s law does more. The tenth commandment focuses squarely on the inner world—the desires, longings, ambitions, and secret thoughts that live beneath the surface of our carefully presented lives. Coveting is not something we do with our hands or feet. It happens within. And while other people may never see it, God does. Scripture reminds us that nothing is hidden from Hi...

主日敬拜反思：从犹大书的问安看我们的身份 地点：Langley Canadian Reformed Church 今天的主日讲道信息，出自《犹大书》短短却极其厚重的开头问安。起初我也和许多人一样，读圣经时往往很快略过这些“格式化”的开头，迫不及待想进入“重点内容”。但今天的信息提醒我：在圣灵默示下写下的每一个字，都不是多余的。 犹大没有急着进入警告假教师、呼吁争辩真道的主题，而是先用一个问安，为整封书信奠定了属灵的根基。也正是在这里，我重新被提醒： 我是谁 。 一、犹大是谁？——主耶稣基督的仆人 讲道中让我印象很深的一点，是犹大的自我介绍方式。他明明是主耶稣的弟弟，却没有以“主的家人”自居，而是称自己为“耶稣基督的仆人”。这不是谦虚的客套话，而是他真实的身份认知。 作为一名信徒，我也不得不反思：如果让我用一句话来定义自己，我会怎么说？是职业？家庭角色？成就？还是——耶稣基督的仆人？ “你们不是自己的人，因为你们是重价买来的。”（林前6:19-20） 这句话在今天的讲道中显得格外真实。我们确实是被释放了，但我们也是被买赎的。我们的人生不再属于自己，而是属于那位为我们舍命的主。 二、我们是谁？——蒙召、蒙爱、蒙保守的人 犹大书一开始，就用三个词来定义收信的信徒： 蒙召的、在父神里蒙爱的、为耶稣基督保守的 。 这是一个完全“被动”的身份描述。不是我们做了什么，而是神为我们做了什么。 蒙召的 ：不是仅仅被邀请，而是被神亲自带进祂的国度。 蒙爱的 ：神呼召我们，不是因为我们配得，而是因为祂爱。 蒙保守的 ：不是我们紧紧抓住神，而是神紧紧抓住我们。 讲道中提到的那句诗歌反复在我心中回响： “祂必保守我，因我救主深爱我。” 在这个充满不确定、动摇信仰根基的时代，这样的确据实在宝贵。 三、真正顺服基督主权的动力 犹大写这封信，是因为教会正面对假教师的冲击。他们高举“自由”，却引人远离基督的主权。这让我意识到：这并不是一个遥远的历史问题，而是今天教会同样面对的挑战。 讲道中提出一个非常深刻的洞见： 人之所以偏离基督的主权，往往不是因为不懂命令，而是因为对神的怜悯、平安和爱认识不足。 顺服不是靠意志硬撑，而是...

Sunday Worship Reflection: Our Identity in Jude’s Greeting Location: Langley Canadian Reformed Church This morning’s sermon drew our attention to a part of Scripture that I often rush past—the opening greeting of a letter. In the Book of Jude, just a few short verses set the tone for everything that follows. Today I was reminded that in God’s Word, nothing is filler. Even a greeting is rich with meaning and spiritual depth. Before Jude warns the church about false teachers or urges believers to contend for the faith, he begins by grounding them in who they are before God. And in doing so, he also reminded me who I am. 1. Who Is Jude? — A Servant of Jesus Christ One of the most striking points in the sermon was Jude’s self-description. Jude was the half-brother of Jesus. He grew up with Him, lived under the same roof, and yet he does not introduce himself that way. Instead, he calls himself “a servant of Jesus Christ.” This challenges me deeply. If I had to summ...

How a JPA save() Call Silently Overwrote My Data (and How to Fix It) I recently encountered a subtle but dangerous issue in a Spring Boot + JPA application. There were no errors, no exceptions, and no failed transactions — yet a database column was silently overwritten with NULL . If you are using Spring Data JPA and updating the same table from multiple endpoints, this is something you should be aware of. The Simplified Scenario We had two REST endpoints updating the same entity, but different fields. The code below is simplified and mangled for illustration. Endpoint A – updates an external reference EntityX entity = repository.findByKey(refId); // update external reference entity.setExternalRef("ABC123"); repository.save(entity); Endpoint B – updates customer email EntityX entity = repository.findByKey(refId); // update email only entity.setEmail("user@example.com"); repository.save(entity); The assumption was that Endpoint B would ...

最近因为需要给国内用支付宝的家人转一笔钱，我实测了一下 从加拿大 → 支付宝 的跨境汇款流程，整体体验比我预期要好不少，特地记录下来给在加拿大的朋友做个参考。 使用背景 人在加拿大 🇨🇦 收款方使用 支付宝（Alipay） 需求：速度快、流程简单、手续费透明 实测平台 我这次使用的是 熊猫速汇（Panda Remit），通过他们的邀请活动页面注册并操作的： 👉 https://p.pandaremit.com/h5activity/launchInvitationCode?countryCode=CAN&shareCode=UzdQMDBD&lang=en-us-u-mu-celsius 实际体验过程 简单说下流程（新手也很容易）： 1. 注册账号并完成基本身份验证 2. 选择 加拿大 → 支付宝 3. 输入金额（实时显示汇率和手续费） 4. 使用加拿大本地方式完成付款 5. 等待到账 到账速度（重点） 👉 第二天就到账了 这一点是我最满意的。 不是“工作日几天内”，而是真正的 第二天支付宝就收到了钱，而且到账信息非常清晰。 优点总结 ✅ 到账速度快（实测次日到账） ✅ 支持直接到支付宝，不用中转 ✅ 操作流程简单，中文界面友好 ✅ 汇率和费用提前显示，比较透明 适合谁？ 在加拿大，需要给国内家人转生活费 留学生 / 新移民 有国内支付宝支出需求的人 小结 如果你也在加拿大，只是想把钱快速、安全地转到国内支付宝，那这种方式确实值得一试。 至少从我这次实测来看，速度和体验都在线。 有需要的朋友可以通过下面这个链接看看当前活动： 👉 https://p.pandaremit.com/h5activity/launchInvitationCode?countryCode=CAN&shareCode=UzdQMDBD&lang=en-us-u-mu-celsius

Debugging Node.js mTLS Client: “Self-signed certificate in certificate chain” When making an API request from a Node.js client to a server that enforces mutual TLS (mTLS) , you might encounter this error: [cause]: Error: self-signed certificate in certificate chain at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34) at TLSSocket.emit (node:events:518:28) at TLSSocket._finishInit (node:_tls_wrap:1078:8) at ssl.onhandshakedone (node:_tls_wrap:864:12) { code: 'SELF_SIGNED_CERT_IN_CHAIN' } Understanding the Issue This error typically occurs when the client cannot fully verify the server’s certificate chain. In mTLS, both client and server need to trust each other’s root CA certificates. If any root in the chain is missing from the client’s CA bundle, the handshake fails. Step 1: Inspect the Server Certificate Chain You can use OpenSSL to see the full server chain: openssl s_client -connect server.example.com:443 -showcerts This will display all ce...

Using Mutual TLS (mTLS) in Next.js (Server-Side Only) In the previous posts, we covered: Part 1: Making mTLS API requests from Node.js clients Part 2: Enabling mTLS in Node.js servers Now we focus on Next.js applications and how mTLS works depending on deployment. Next.js Cannot Access TLS Handshake Directly Next.js middleware and API routes run after the TLS handshake They cannot see client certificates or verify them Next.js built-in server does not expose Node's HTTPS options like requestCert In short: Next.js middleware cannot enforce mTLS or access TLS handshake details . Any enforcement must happen before the request reaches Next.js. Next.js as an mTLS Client (Server-Side API Calls) Next.js can securely call mTLS-protected APIs from server-side code, such as: API routes Server actions import fs from 'fs'; import https from 'https'; import axios from 'axios'; export async function GET(req) { const...

  Enabling Mutual TLS (mTLS) in a Node.js Server In the previous post, we covered how to call an mTLS-protected API from Node.js . In this guide, we flip the perspective and configure Node.js as the server that requires client certificates. This setup is common for: Internal enterprise APIs Service-to-service communication Zero-trust architectures OpenShift / Kubernetes workloads By the end of this post, your Node.js server will: Accept only TLS connections Require valid client certificates Reject unauthorized clients automatically Expose client identity information to your app How Mutual TLS Works (Server Perspective) When mTLS is enabled: The client connects over HTTPS The server presents its certificate The client presents its certificate Both sides verify each other against trusted CAs Node.js can enforce all of this at the TLS layer, before your application code even runs. Required Certificate Files A Nod...