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 一月18日 主日下午 听道反思：在学习祷告中成长

By -

在学习祷告中成长



今天下午的讲道围绕祷告展开，信息温柔而充满牧养的关怀。讲员不是要指出我们祷告得不够好，而是鼓励我们：在学习祷告的过程中，祷告的生命也要不断成长。

讲道首先问到：我们向谁祷告？ 我们祷告的对象不是遥远的神，而是我们在基督里所认识的天父。藉着主耶稣的救赎，我们成为神的儿女；靠着圣灵的帮助，我们可以呼喊“阿爸，父！”祷告因此不再只是宗教形式，而是儿女与父亲之间亲密的交通。

接着讲员解释：祷告是什么？ 要理问答说，祷告就是“从心里呼求神”。祷告是一种真实、诚恳、发自内心的与神说话。神早已知道我们心中的需要与软弱，因此我们可以坦然无惧地来到祂面前。

讲道也提醒我们，祷告并不在于言语的多少或表达的技巧，而是在于向神的祈求、感谢、认罪与赞美。当我们不知道该说什么时，可以用圣经的话祷告——例如诗篇或主祷文——因为圣灵会帮助我们祷告。

至于在哪里和什么时候祷告，答案是随时随地。但耶稣也教导我们，个人祷告最好是在安静、私下的地方，与神独处。教会历史中常有固定祷告时间的传统，这不是律法主义，而是出于爱与属灵的操练。

最后，我们被提醒为什么要祷告：因为我们爱神，因为神爱我们，也因为我们需要完全依靠祂的恩典与圣灵的工作。

愿我们在学习祷告的真理时，也在祷告的生命中不断长进。

经文：马太福音6章；罗马书8章

主题：在学习祷告中成长

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