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年3月08日 主日下午听道反思: 人生如旷野

By -

人生如旷野



今天下午的讲道让我想到，人生有时候会像在旷野中一样。我们可能会面对困难的人际关系、长期未实现的盼望，或者失去亲人的悲伤。在这些时刻，我们很容易只专注于自己的困难和处境。

讲道提出了一个很重要的问题：当人生感觉像在旷野时，我们该怎么办？我们只是一直看着自己的环境，还是转向神、切切地寻求祂？

在 诗篇 63 中，大卫真的在旷野里。他远离家乡，也不能在圣所里敬拜神。但他没有只想着自己的困难，而是转向神，说：“神啊，你是我的神，我要切切地寻求你。”这让我们看到，他与神的关系是非常个人、真实的。

大卫也说，神的慈爱比生命更好。即使人生充满困难，神坚定不变的爱仍然托住我们，也真正满足我们的心。这个世界不能给我们的，神却能给我们。

讲道也提醒我们，要通过祷告、默想圣经和赞美诗歌来切切地寻求神。这些属灵操练帮助我们在困难的日子里仍然亲近神。

最后，讲道把我们的目光带到 耶稣基督。因着耶稣，我们可以与神有真正的相交。即使人生像在旷野中，神仍然与我们同在，并且会托住我们。

这篇讲道鼓励我，在困难的时候更切切地寻求神，相信祂坚定不变的爱一定会托住我，也会满足我的心。

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