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月26日 主日上午听道反思: 到如今耶和华都帮助我们

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