Errong Leng | Faith & Code — Reflections on Scripture and Software

iTrans – Fast iPhone Photo & Video Transfer for macOS Do you find Photos.app slow or cluttered when backing up your iPhone photos and videos to your Mac? I built iTrans , a lightweight macOS utility that lets you transfer your media directly into folders on your Mac — fast, simple, and without the extra bloat. How iTrans Works Plug in your iPhone Open iTrans Select photos and videos to transfer Choose the destination folder on your Mac Click transfer — done! iTrans is perfect for quick media backups, organizing photos without importing them into Photos.app, or simply moving videos off your iPhone in a flash. Demo Video Check out this short demo showing iTrans in action: Support iTrans To publish iTrans on the Mac App Store, Apple requires a $99 annual Apple Developer Program fee. If you find iTrans useful and want to support its release, you can contribute here: Support iTrans – Help Publish on the Mac App Store Even if you can't contrib...

January Traffic Snapshot: Faith & Code Across the World As January comes to a close, I want to take a moment to reflect on how Faith & Code — Reflections on Scripture and Software has been read and accessed over the past month. 📈 Overall Engagement In January, the blog recorded 8.89K total pageviews . Traffic remained steady throughout the month, with a notable peak in mid-January, suggesting that certain posts resonated more strongly during that period. Rather than relying on a single spike, the overall pattern reflects consistent readership. 🌍 Global Readership The blog continues to reach readers across the world: It’s humbling to see reflections on faith, confession, and vocation being read across cultures and time zones. 💻 Pageviews by Operating Systems Readers accessed the blog using a wide variety of operating systems: The balance between desktop and mobile platforms reflects a readership engaging both in focused reading and on-the-go moments. 🌐...

关怀就是：彼此认罪 今天下午听了教会关于关怀小组主题的一篇讲道，主题是： 彼此认罪 。 说实话，这不是一个让我觉得“舒服”的主题。 如果要列出我们彼此关怀的方式，这大概不会排在前几名。 向神认罪，我可以理解；向另一个人认罪，就感觉很冒险。 讲道一开始就点出了这个张力。是的，罪最终是得罪神的， 也只有神能赦免罪。这一点没有争议。 但雅各书 5:16 仍然说： “你们要彼此认罪，互相代求，使你们可以得医治。” 让我印象最深的不是“你必须去做”，而是 为什么 要这样做。 不是为了暴露自己，也不是为了情绪宣泄， 而是为了得到 安慰 和 劝勉 。 有时候，我们已经向神认过罪了， 但心里的愧疚感仍然挥之不去。 或者反复跌倒，让人开始怀疑： 我真的悔改了吗？神真的饶恕我了吗？ 这时，有另一个基督徒能把福音再一次对你说出来， 用神的话安慰你，并为你祷告， 这本身就是神赐下的一种医治方式。 讲道也提到，罪是很顽固的。 隐藏它，往往只会让它更强。 把它带到光中，才可能有人陪你一起面对， 给你实际的提醒和帮助。 我也很受提醒的一点是： 关怀不仅是“去认罪”， 也是 如何接住别人的认罪 。 不是论断，不是好奇， 而是温柔、福音，以及把事情带到神面前。 而且，它应该止于你。 最后有一个比喻我很喜欢。 我们的生命像一栋房子，有不同的房间。 不是每个人都能进每一个房间，这很正常。 但不应该有一个永远上锁、谁都不能进的房间。 至少，应该有一个人， 能看见整栋房子。 这不是一件容易的事。 但我离开教会时在想， 也许正是这样的真实和敞开， 神用来带来医治、自由， 以及真正彼此相爱的教会生活。

Caring Is: Confessing Sin to One Another This afternoon’s sermon in our care group series was on a topic that honestly made me a little uncomfortable: confessing sin to one another . It’s not something we usually think of as “caring.” If I’m honest, it probably wouldn’t make my top five ways Christians support each other. Confessing sin to God? Yes. Confessing sin to another person? That feels risky. The sermon acknowledged that tension right away. Of course, God is the one who forgives sin. He’s the one we’ve ultimately sinned against. That part isn’t in question. But James 5:16 still says, “Confess your sins to one another and pray for one another, that you may be healed.” What struck me was why we might do this—not to be exposed, embarrassed, or publicly honest, but to receive comfort and counsel . Sometimes you confess a sin to God and still feel guilty. Or you wonder if your repentance is real. Or you keep falling into the same struggle and start questioning whether...

主日早堂讲道反思：犹大书中的一个必要提醒 今天早堂崇拜中所读的经文出自《犹大书》，为整篇讲道定下了基调。这是一封很短的书信，却分量十足，我们所听到的经文并不让人轻松。 犹大原本是想写一封鼓励人的信，谈论众信徒所共享的“同一救恩”。但他却不得不转而警告教会——不是因为外在的逼迫，而是因为内部的危险。有些人悄悄地混进了教会，口中谈论恩典，生活却是否认耶稣的主权。 讲道中最让我印象深刻的，是犹大从哪里开始说起。他并没有立刻详细描述这些假教师，而是先提醒教会一件我们并不太愿意常常思想的事：审判。 跟随耶稣是美好的，是赐生命的，但并不总是容易的。当顺服开始变得有代价时，其他的声音就显得格外有吸引力：“真的那么重要吗？”“是不是太狭窄了？”犹大的回答既简单又令人不安：是的，这真的很重要。神已经定下一个日子，耶稣要在那一天审判世界。 犹大举了三个圣经中的例子——旷野中的以色列人、悖逆的天使，以及所多玛和蛾摩拉。每一个例子都在提醒我们：转身退后、拒绝耶稣的权柄，或是在罪中安顿下来，最终都会走向同一个方向。 这篇信息并不是为了吓唬人，而是为了唤醒人。信仰只有一条路。假教师常常提供“捷径”，看似更轻松，却无法把人带到他们所承诺的终点。 今天早上的讲道让我心里很沉，却也充满感恩。感恩再次被提醒：耶稣不只是我所相信的救主，更是我当顺服跟随的主。

Morning Sermon Reflection on Jude: A Needed Reminder The Scripture reading from the book of Jude set the tone for this morning’s sermon. It is a short letter, but a weighty one, and the passage we heard was not easy to sit with. Jude originally wanted to write something encouraging about the “common salvation” Christians share. Instead, he felt compelled to warn the church. Not because of pressure from outside, but because of danger from within. People had quietly crept into the church, speaking about grace while living in ways that denied the authority of Jesus. What stood out to me most in the sermon was where Jude begins. Before describing these false teachers in detail, he reminds the church of something we don’t like to think about very often: judgment. Following Jesus is good and life-giving, but it isn’t always easy. When obedience becomes costly, other voices can start to sound appealing. Does it really matter? Isn’t this too narrow? Jude’s answer is simple and uncomf...

一次 403 错误的排查实录：Spring Cloud Gateway、WebFlux、PingFederate 与 CORS 一次真实的线上排错记录：一个看似 OAuth / JWT / Spring Security 的 403，最终却是 CORS 问题。 背景 我们在一次系统集成过程中，遇到了一个非常令人困惑的问题，涉及以下组件： Spring Cloud Gateway Spring Boot WebFlux 后端服务 PingFederate（OIDC / OAuth2） 本地运行的 React 前端（ http://localhost:4200 ） 整体请求流程如下： 用户通过 PingFederate 登录（SSO） 前端获取 access token 前端发起 POST 请求 → Gateway → 后端服务 在以下场景中，一切都运行正常： 使用 Postman 直接调用后端 绕过 Gateway，直接调用后端 所有组件都在本地运行 但一旦请求通过 部署在 OpenShift 中的 Spring Cloud Gateway ，所有 POST 请求都会失败，并返回： 403 Forbidden 为什么这个问题如此迷惑 完全相同的 access token，在 Postman 中可以正常使用 GET 请求成功，POST 请求失败 系统中没有配置任何 role 或 scope 校验 不同环境下 401 / 403 的表现不一致 JWT 的 issuer、audience、签名全部正确 所有线索一开始都指向 OAuth 或 PingFederate 的配置问题——但这个判断是错误的。 关键线索：问题是如何被定位出来的 1. Postman 成功，浏览器失败 同一个请求，在不同客户端表现完全不同： Postman → 成功 浏览器（经 Gateway）→ 403 这一步非常关键，它强烈暗示： 问题并不在 token 本身 。 2. 在 Postman 中加上 Origin 头，请求立刻失败 我们在 Postman 中手动加入以下 header： O...

Debugging 403 Errors with Spring Cloud Gateway, WebFlux, PingFederate, and CORS A real-world postmortem on a confusing 403 that turned out not to be OAuth, JWT, or Spring Security — but CORS. Background We recently ran into a frustrating issue while integrating: Spring Cloud Gateway Spring Boot WebFlux backend PingFederate (OIDC / OAuth2) A React frontend running locally ( http://localhost:4200 ) The request flow looked like this: User logs in via PingFederate (SSO) Frontend receives an access token Frontend sends POST requests → Gateway → Backend service Everything worked perfectly when: Calling the backend directly via Postman Calling the backend directly without the gateway Running everything locally But once the request went through Spring Cloud Gateway in OpenShift , all POST requests failed with: 403 Forbidden Why This Was Confusing The same access token worked in Postman GET requests succeeded, POST requests fa...

为什么 Vercel 部署后 PostgreSQL 仍然存在 Idle 连接 如果你在 Vercel 上运行 Next.js ， 并且直接连接 PostgreSQL ，你很可能遇到过下面的错误： remaining connection slots are reserved for roles with the SUPERUSER attribute 这个问题通常在重新部署后更容易出现，即使你的应用流量并不高。 常见现象 PostgreSQL 中存在大量 idle 状态的连接 Vercel 实例已经关闭，但连接仍未释放 新请求无法获取数据库连接 手动终止连接只能暂时缓解问题 真正的原因 这是 Serverless 架构的正常行为 。 Vercel 的工作方式大致如下： Vercel 根据请求启动多个 Serverless 实例 每个实例都会创建自己的数据库连接或连接池 实例结束后，无法保证数据库连接被优雅关闭 PostgreSQL 会继续保留这些连接直到超时 结果就是： 应用已经结束，但数据库连接仍然存在 。 为什么会导致连接数耗尽 在托管 PostgreSQL 服务中，一部分连接被保留给系统和 SUPERUSER。 当 Serverless 实例频繁创建连接时，很容易用完普通用户可用的连接数， 从而触发该错误。 这不是数据库 bug，而是架构不匹配导致的问题。 PgBouncer 如何解决 PgBouncer 位于应用和数据库之间： Vercel → PgBouncer → PostgreSQL 应用连接 PgBouncer，而不是直接连接数据库 PgBouncer 使用少量真实数据库连接服务大量请求 Serverless 实例关闭时，连接会被立即回收 PostgreSQL 不再堆积 idle 连接 对于 Serverless 场景，推荐使用 transaction pooling 模式。 推荐配置 启用 PgBouncer 应用连接 PgBouncer 的 host 和 port Node.js 连接池设置为 1–2 idleTimeo...

Why PostgreSQL Idle Connections Remain After Vercel Deployments If you are running a Next.js application on Vercel with PostgreSQL , you may have encountered this error: remaining connection slots are reserved for roles with the SUPERUSER attribute This issue often appears right after a redeploy or during traffic spikes, even when your application traffic is relatively low. The Symptom PostgreSQL shows many connections in idle state Connections remain even after Vercel instances are shut down New requests fail with connection slot errors Manually terminating idle connections only fixes the problem temporarily What Is Really Happening This behavior is expected in serverless environments . Here is what happens behind the scenes: Vercel spins up serverless function instances Each instance creates its own PostgreSQL connection or connection pool When the instance finishes, it may shut down without gracefully closing the DB connection Post...

如何修复 PostgreSQL “剩余连接槽位保留给超级用户” 错误 ❌ 错误： 您的应用可能会出现如下报错： remaining connection slots are reserved for roles with the SUPERUSER attribute 这通常意味着 PostgreSQL 数据库的连接数已达到上限，部分连接可能是空闲事务会话，占用了可用槽位。 问题分析 PostgreSQL 通过 max_connections 限制并发连接数量。当所有普通槽位被占满时，只有超级用户可以连接。应用中长时间运行或空闲事务会话（ idle-in-transaction ）会占用连接，阻止新连接建立。 检查当前连接 ℹ️ 提示： 在终止任何连接之前，请先检查当前连接状态。 SELECT pid, usename, application_name, state, backend_start FROM pg_stat_activity ORDER BY backend_start; 注意查找 state 为 idle in transaction 的应用用户连接。 终止过期的空闲事务连接 ⚠️ 警告： 仅终止应用用户连接。不要操作 postgres 系统用户或后台工作进程。 SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE state = 'idle in transaction' AND usename = 'your_app_user' AND now() - backend_start > interval '5 minutes'; 将 your_app_user 替换为应用使用的数据库用户名。此操作可以安全释放连接而不会影响正在执行的查询。 注意事项 ❌ 不要终止系统连接（如 TimescaleDB 工作进程、pg_cron 等） ✅...

How to Fix PostgreSQL ‘Remaining Connection Slots Reserved’ Error If your application suddenly fails with an error like: remaining connection slots are reserved for roles with the SUPERUSER attribute It usually means your PostgreSQL database has reached its maximum number of allowed connections. Some of these connections may be idle-in-transaction sessions that are holding slots unnecessarily. This guide shows how to safely free up those connections. Understanding the Problem PostgreSQL limits the total number of concurrent connections through the max_connections setting. When all normal slots are used, only superusers can connect. Long-running or idle-in-transaction sessions from your app can consume slots and prevent new connections. Check Current Connections Before terminating anything, inspect your connections with: SELECT pid, usename, application_name, state, backend_start FROM pg_stat_activity ORDER BY backend_start; Look f...

安全数据清理：如何从大型 Oracle 表中删除旧数据 为了遵守数据保留规定，我们定期清理旧数据。但是，从生产数据库删除数百万条记录需要非常谨慎。以下是我们的做法。 第一步：数据目录与计划 统计所有表并确定保留期限 与法律团队确认保留计划 与其他团队协作，识别下游依赖 第二步：备份表 删除前备份受影响表，确保出现问题时可以快速恢复。 第三步：理解表结构 先识别子表和父表。先删除子表，以避免外键约束错误。 第四步：批量删除 vs 直接删除 在 PT 环境中测试批量删除正常。但在生产环境中： 表超过 700 万行，需要删除超过 100 万行 20K 批量删除导致等待 1.5 小时并触发 FK 错误 出现自动回滚 现在采用增量删除： 每次删除 1 万条并提交 循环执行直到清理完成 速度慢但可控，易于定位 FK 错误 第五步：SQL 示例 -- 删除旧数据示例 SELECT '子表1', COUNT(*) FROM child_table_1 WHERE created_on < ADD_MONTHS(TRUNC(SYSDATE), -144); DELETE FROM child_table_1 WHERE created_on < ADD_MONTHS(TRUNC(SYSDATE), -144); COMMIT; DECLARE v_batch_size CONSTANT PLS_INTEGER := 20000; v_rows PLS_INTEGER; v_cutoff_date DATE := ADD_MONTHS(TRUNC(SYSDATE), -144); BEGIN LOOP DELETE FROM large_table WHERE created_on < v_cutoff_date AND ROWNUM <= v_batch_size; v...

Safe Data Purge: How We Remove Old Records in Large Oracle Tables At our company, we periodically purge old data to comply with data retention regulations. Deleting millions of rows from production databases requires careful planning. Here's how we do it. Step 1: Catalog and Plan Catalog all tables and identify retention periods. Review retention schedule with legal team. Coordinate with other teams to identify downstream dependencies. Step 2: Backup Tables Always backup affected tables before deleting. This ensures quick recovery in case of unexpected issues. Step 3: Understand Table Structure Identify child tables and parent tables. Delete child tables first to avoid foreign key violations. Step 4: Batch Deletes vs Direct Deletes We tested batch deletes in our PT environment and it worked fine. However, in production: Tables have 7M+ rows and 1M+ rows to delete Batch of 20K rows...

主日下午听道反思：比利时信条第28条 “凡要得救的人，必须加入教会。” 第28条的核心教导 今天下午的讲道围绕《比利时信条》第28条展开，强调信徒加入教会的必要性。信条明确指出：在教会之外没有救恩，教会是蒙救赎者的圣洁会众。 讲道澄清，这并不是说救恩来自某一个具体的教会或宗派，而是指出神设立教会，作为祂聚集和保守百姓的正常途径。 救恩与话语的事工 圣经清楚教导，救恩唯独借着信靠耶稣基督而来。罗马书第10章指出，人因听见福音、相信并承认基督而得救。 讲道强调，神通常借着教会中福音的宣讲，使人得着信心。话语的事工属于教会，神也应许要通过祂所差遣的传道人来成就救恩。虽然神能够以非常的方式施行拯救，但信徒并不应期待例外，而是当在神应许施恩的地方寻求祂。 什么是教会？ 讲道提醒我们，“教会”并不首先指建筑物或聚会本身。圣经使用的词是 ekklesia ，意为“被呼召、被聚集的人”。教会是信徒在基督里被召聚在一起的可见群体。 因此，加入教会不是可有可无的选择，而是属基督之人的必然结果。属于基督，也就属于祂的身体。 教会是蒙救赎者的圣洁会众 第28条称教会为“圣洁的”，意思是被神分别出来。教会并非完全无瑕，却是与世界有别的群体。在教会中，信徒接受教导、劝戒、鼓励，并被引导过敬虔的生活。 教会也是蒙救赎者的会众，是那些借着基督的宝血脱离罪恶、同在祂权柄之下生活的人。 作为基督身体的成员而生活 讲道最后指出，每一位信徒在教会中都有其位置与责任。圣灵赐下不同的恩赐，为要造就整个身体。积极参与、彼此关怀和服侍，是忠心教会生活的重要表现。 第28条呼召信徒不仅加入教会，也要顺服教会的教导与治理，这是神为保守信心、建立祂子民所设立的恩典方式。

“Everyone must join the church, because there is no salvation outside of it.” The Central Question of Article 28 This afternoon’s sermon addressed Belgic Confession Article 28, which teaches that all believers are obligated to join the church. The confession states this strongly: there is no salvation outside the church, and the church is the holy assembly and congregation of the redeemed. The sermon carefully clarified that this statement does not mean salvation is found in a particular building or denomination, but that God has appointed the church as the ordinary means through which He gathers and preserves His people. Salvation and the Ministry of the Word Scripture teaches that salvation comes through faith in Jesus Christ alone. Romans 10 emphasizes confession of Christ and belief in His resurrection. At the same time, the sermon highlighted that God ordinarily brings people to faith through the preaching of the gospel. The...

希伯来书 11:13–16 —— 神正在为我们预备更美的家乡 今天早上的讲道让我重新思考什么才是真正的“成功人生”。我们常常用眼前、暂时的事物来衡量成功，比如健康、经济状况、家庭是否顺利、工作是否稳定。当这些方面进展顺利时，我们就觉得人生是成功的；一旦出现问题，内心便充满焦虑与失落。 然而，希伯来书 11:13–16 提醒我们，神的子民一向是用不同的眼光来看待人生。那些信心的伟人都是“存着信心死的”，并没有在今生完全得着神所应许的，却仍然坚信神的话必定成就。 亚伯拉罕和众族长承认自己在世上是客旅、是寄居的。他们虽然生活在神所赐的土地上，却从未把那里当作最终的家。这也帮助我们理解：为什么即使在顺境中，心里仍常常感到不完全满足。这种不安并不是信心软弱，而是提醒我们——这个世界本来就不是我们的终极归宿。 讲道提醒我们，基督徒并不是要把今生经营成永恒的家园，而是要存着盼望，等候那“更美的家乡”，就是属天的家乡。我们活在世上，却不完全属于这个世界。 这也带来了极大的安慰。神有时容许我们经历困难和挫折，是为了提醒我们真正的盼望在哪里。同时，神也赐下宝贵的应许： 祂并不以称我们为祂的子民为耻 ，因为祂已经为我们预备了一座城。 今天清晨，我再次被提醒：我的人生不需要在今世完全圆满。真正的成功不在于地上的安稳，而在于凭信心而活，仰望神所预备的永恒家乡。

God Is Preparing for Us a Better Home This morning’s sermon challenged the way I usually define a “successful life.” So often, success is measured by visible and temporary things—health, financial stability, family life, and career progress. When these are going well, life feels successful. When they are not, discouragement quickly sets in. Hebrews 11:13–16 reminds us that God’s people have always lived with a different perspective. The saints of old lived and died in faith , without receiving the fullness of what God had promised. They trusted God not because life was easy, but because His promises were certain—even when they were unseen. Abraham and the patriarchs acknowledged that they were strangers and exiles on the earth. They lived in the land God gave them, yet they never treated it as their true home. This helps explain why life often feels unsettled. Even in seasons of blessing, something is always missing. That longing is not a failure of faith—it is evidence that we w...

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...