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年2月8日 主日早晨听道反思：我是“做梦的人”，还是“挖掘的人”？

By -

听道反思：我是“做梦的人”，还是“挖掘的人”？



今天听完犹大书的信息，有一个问题一直在我心里回响： 我是在依靠神的话，还是在依靠自己的感觉？

犹大并没有把假教师描述成不属灵或不敬虔的人，反而称他们是“依靠自己梦的人”。问题不在于他们有没有属灵经历，而在于他们把经历当成了权柄。

这让我反思自己。很多时候，我也是凭感觉做决定——只要我觉得平安、舒服、有把握，就认为这是从神来的。但今天的信息提醒我：感觉不是根基，神的话才是。

从人的角度看，罪不是抽象的，它真实地污染我们自己。而这种污染，并不只来自明显、公开的罪，也来自日常生活中看似无害的习惯。

比如不断刷抖音、短视频，随意浏览网页，让大量碎片化、刺激性的内容充满我们的眼睛和思想。没有人强迫我们这样做，但久而久之，这些内容正在塑造我们的欲望，使我们对神变得迟钝。我们每天所“消费”的内容，从来都不是中立的，不是在塑造我们，就是在扭曲我们。

从神的角度看，不顺服从来不是小问题。当我选择按自己的方式生活，其实是在把主权从基督手中拿走，放在自己身上。我口里承认祂是主，生活中却常常自己当王。

从天使的角度看，更让我感到羞愧。连天使都不敢轻看神的权柄，而我却有时用“现在是恩典时代”来为自己的不顺服辩护。犹大提醒我，这不是自由，而是骄傲。

但感谢神，信息没有停留在责备中。耶稣已经成全了律法。律法不再是控告我的审判官，而是在基督里，成为引导我如何生活的蓝图。

当撒但控告我时，我的回应不在于我做得够不够好，而在于基督已经为我成就了一切。顺服不再是换取生命的条件，而是已经得着生命后的回应。

今天我被提醒：不要满足于做梦，要甘心挖掘；不要只问“我感觉如何”，而要问“神已经说了什么”。

愿神帮助我继续活在祂话语的权柄之下，让我的生命不再制造属灵的污染，而是因基督的恩典，散发出更新与生命的气息。

❤️ 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