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年一月25日 主日清晨讲道反思：神正在为我们预备更美的家乡（希伯来书 11:13–16）

By -

希伯来书 11:13–16 —— 神正在为我们预备更美的家乡



今天早上的讲道让我重新思考什么才是真正的“成功人生”。我们常常用眼前、暂时的事物来衡量成功，比如健康、经济状况、家庭是否顺利、工作是否稳定。当这些方面进展顺利时，我们就觉得人生是成功的；一旦出现问题，内心便充满焦虑与失落。

然而，希伯来书 11:13–16 提醒我们，神的子民一向是用不同的眼光来看待人生。那些信心的伟人都是“存着信心死的”，并没有在今生完全得着神所应许的，却仍然坚信神的话必定成就。

亚伯拉罕和众族长承认自己在世上是客旅、是寄居的。他们虽然生活在神所赐的土地上，却从未把那里当作最终的家。这也帮助我们理解：为什么即使在顺境中，心里仍常常感到不完全满足。这种不安并不是信心软弱，而是提醒我们——这个世界本来就不是我们的终极归宿。

讲道提醒我们，基督徒并不是要把今生经营成永恒的家园，而是要存着盼望，等候那“更美的家乡”，就是属天的家乡。我们活在世上，却不完全属于这个世界。

这也带来了极大的安慰。神有时容许我们经历困难和挫折，是为了提醒我们真正的盼望在哪里。同时，神也赐下宝贵的应许：祂并不以称我们为祂的子民为耻，因为祂已经为我们预备了一座城。

今天清晨，我再次被提醒：我的人生不需要在今世完全圆满。真正的成功不在于地上的安稳，而在于凭信心而活，仰望神所预备的永恒家乡。

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