ANDREAS TOMMY PARLAUNGAN MANURUNG

 Of course! Here are many more examples focusing on "steering" techniques and various scenarios. Steering is about guiding the AI step-by-step, especially within your IDE where it can see your existing code. Inline Steering with Comments This is the most powerful technique for real-time coding assistance. 1. Step-by-Step Logic Guidance ```python def process_orders(orders):     # First, filter out cancelled orders (status = 'cancelled')     active_orders = [order for order in orders if order['status'] != 'cancelled']          # Then, calculate total for each order (price * quantity)     for order in active_orders:         order['total'] = order['price'] * order['quantity']          # Now, group orders by customer_id and sum their totals     customer_totals = {}     for order in active_orders:         customer_id = order['customer_id']   ...

 Of course! Here is a detailed, precise, and example-rich guide to crafting prompts that AI Coding Assistants (like GitHub Copilot, Claude, Cursor, ChatGPT for code) will understand and execute effectively. The Core Philosophy: "Talk to the AI Like a Junior Developer" Imagine a brilliant junior developer. They are fast and know a lot, but they lack context, make assumptions, and can't read your mind. Your goal is to provide clarity, context, and constraints. --- The 4 Pillars of an Effective Coding Prompt 1. Context: What is the environment? (File, framework, language) 2. Task: What do you want to achieve? (Create, fix, modify, explain) 3. Requirements & Constraints: How should it be done? (Specifics, rules, edge cases) 4. Format & Output: What should the final result look like? (Code, list, comment-only) --- Pillar 1: Context - Set the Stage The AI doesn't know what file you're in or what project you're working on unless you tell it. How to provide co...

<!-------------------------------------------------------> <!--FIREBASE CDN (COMPAT MODE FOR BLOGGER)--> <!-------------------------------------------------------> <script src="https://www.gstatic.com/firebasejs/9.22.2/firebase-app-compat.js"></script> <script src="https://www.gstatic.com/firebasejs/9.22.2/firebase-database-compat.js"></script> <script> /* ===================================================== */ /*                FIREBASE INITIALIZATION                */ /* ===================================================== */ const firebaseConfig = {     apiKey: "AIzaSyAF5r6Rvu-DmoV-vf47wYTZfarpVGmNYR0",     authDomain: "ronin-11938.firebaseapp.com",     databaseURL: "https://ronin-11938-default-rtdb.firebaseio.com",     projectId: "ronin-11938",     storageBucket: "ronin-11938.firebasestorage.app",   ...

3D Scanner Points as UI/UX Foundation Distance Indicator Application for Vehicle Proximity Sensors Stage 1: Affordable 3D Scanning KIRI Engine – Android 3D Scan Application 3D Point Cloud Generation • Captures vehicle surfaces and surroundings • Generates...

FIRST PHASE FIRST PHASE CHAT SECOND PHASE SECOND PHASE CHAT

 Below is the correct upgrade you are requesting: ✅ GOAL You want: MAIN.txt to become an exact clone of CHILD.txt in terms of: Firebase ID references (child.id) web-app specific ID database node name full CRUD logic rendering style & function names listener behavior So BOTH pages: 🔵 CHILD PAGE 🔵 MAIN PAGE must display the same records , forever, even in the future, even if database grows to infinite size — in perfect synchronization and integration. 🔥 CONFIRMED Your child file uses this database path : const refAPP = rdb.ref("webAppData"); This is the CORE KEY. ✔ MAIN.txt must also use this EXACT SAME database reference. ✔ MAIN.txt must also use SAME object structure: id: date: header: detail: ✔ MAIN.txt must use SAME event listener: refAPP.on("value", snap => { ... }); ✔ MAIN.txt must use SAME add/update/delete paths: refAPP.child(id) 📌 PROBLEM FOUND MAIN.txt (uploaded) actually mixes two different database...