A New Collection of Thoughtful Learning Apps — Now Available on iOS & Android

By -
Image
I’m excited to share a set of mobile apps I’ve recently completed and published on both the Google Play Store and the Apple App Store. These apps are designed with a simple goal in mind: to make meaningful, structured content more accessible, whether you’re studying theology or improving your English vocabulary. 📱 Now Available on Both Platforms All apps are live and available for download: Google Play Developer Page: https://play.google.com/store/apps/dev?id=5835943159853189043 Apple App Store Developer Page: https://apps.apple.com/ca/developer/q-z-l-corp/id1888794100 📖 Theology & Confession Study Apps For those interested in Reformed theology and classical Christian teachings, I’ve developed a series of apps that present foundational texts in a clean, focused reading format: The Belgic Confession Canons of Dort Heidelberg Catechism Westminster Shorter Catechism Each app is designed to provide a distraction-free experience, making it easier to read, reflect, and revisit these im...
Post a Comment

2026年4月19日 主日上午听道反思: 在君王里得避难

By -

诗篇第2篇：在君王里得避难



听完这篇关于诗篇第2篇的讲道，我心里既有一些不安，也有很深的安慰。讲道一开始提出的问题——“列国为什么争闹？”——让我感到非常贴近现实。当我看到今天世界上的战争、政治紧张和各种冲突时，我常常会感到困惑，甚至有些灰心。我通常会觉得问题只是人类彼此无法和平相处。但这篇讲道提醒我，从更深的角度来看，真正的问题是人对神的悖逆。

这种角度其实不是我平时会去想的。正如讲道中提到的，这样的观点不会出现在新闻里。但仔细想想，这是有道理的——如果人拒绝神的权柄，那么真正的和平就不可能存在。离开了那位定义公义与真理的神，世界的秩序就必然是混乱的。

让我印象最深的是神的回应。当列国喧嚷、筹谋的时候，神却不是焦虑或惊慌，反而“发笑”。这个画面非常有力量。它提醒我，无论世界看起来多么混乱，神仍然完全掌权。耶稣基督已经是君王了，这不是未来才会实现的事情，而是现在的事实。这让我在不稳定的世界中，找到一种稳固的依靠。

但这篇讲道也没有让我停留在安逸中。“当以嘴亲子”这个呼召非常直接。信仰不仅仅是相信一些道理，更是降服。这一点对我来说是一个提醒：我是否真的在生活的各个方面顺服基督的权柄？还是在某些地方仍然想自己作主？这让我意识到，悖逆不仅存在于“列国”之中，也可能隐藏在我自己的心里。

我也很感恩讲道中清楚地传讲了福音，没有刻意弱化或包装。信息是直接而迫切的：要悔改，归向基督。乍听之下可能觉得严厉，但其实这是出于怜悯。神之所以警告，是因为祂关心我们。

而最让我感到安慰的，是“避难”这个主题。那位将要审判世界的君王，同时也是为我们舍命的救主。“在他里面得避难，而不是躲避他”，这一点非常深刻。耶稣既是公义的审判者，也是代替我们承受审判的羔羊。祂承担了我们本该承受的刑罚，使我们可以在祂里面得着真正的安全。

讲道中关于飓风“风眼”的比喻让我印象很深。现在的时代就像风暴中的短暂平静——仍然有时间，仍然有机会。但这段时间不会永远持续。这让我不仅为自己的信仰感到警醒，也更加看重向他人传福音的重要性。如果基督真的是唯一的避难所，那么引导别人来到祂面前，就是一件非常重要的事情。

总的来说，这篇讲道帮助我用更合乎圣经的眼光来看待世界，也反思自己的生命。它提醒我，耶稣已经作王，人类的悖逆是真实的，但神的恩典同样真实并且向人敞开。

我祷告，愿自己既有谦卑的心来顺服基督，也有信心来信靠祂的掌权。在这段“风眼”的时间里，好好珍惜神所赐的机会，不仅亲近祂，也帮助身边的人，在祂里面找到真正的避难所。

❤️ Support This Blog

If this post helped you, you can support my writing with a small donation. Thank you for reading.

Coffee ☕ Thanks 🙏 Extra Support ❤️

Comments

Post a Comment

Popular Posts

Fix “A problem occurred starting process 'command node'” in Android Studio for React Native

By -
Image
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...
Read more

Fix up watchman issue with Ghost

By -
# Issue >>     >>     at BunserBuf.<anonymous> (/home/errong_leng/Ghost/core/client/node_modules/fb-watchman/index.js:95:23) >>     at emitOne (events.js:116:13) >>     at BunserBuf.emit (events.js:211:7) >>     at BunserBuf.process (/home/errong_leng/Ghost/core/client/node_modules/bser/index.js:292:10) >>     at /home/errong_leng/Ghost/core/client/node_modules/bser/index.js:247:12 >>     at _combinedTickCallback (internal/process/next_tick.js:131:7) >>     at process._tickCallback (internal/process/next_tick.js:180:9) >> A non-recoverable condition has triggered.  Watchman needs your help! >> The triggering condition was at timestamp=1509698956: inotify-add-watch(/home/errong_leng/Ghost/core/client/node_modules/ember-cli-node-assets/node_modules/broccoli-funn...
Read more

Using Mutual TLS (mTLS) in Next.js (Server-Side Only)

By -
Image
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...
Read more