بناء سوق للإيجار بين الأفراد مثل RentFox يواجه تحديات فريدة، خاصة في إقامة الثقة بين المستخدمين. الطرق التقليدية مثل التأمين وخدمة العملاء قد تكون مكلفة وغير فعالة للشركات الناشئة. يستكشف هذا المقال حلولًا مبتكرة لتعزيز الثقة بين المستخدمين، وهو أمر حاسم لنجاح مثل هذه المنصات. مع استمرار نمو الاقتصاد التشاركي، سيكون فهم كيفية بناء الثقة بشكل فعال أمرًا أساسيًا للوافدين الجدد إلى السوق.

Construir un mercado de alquiler entre pares como RentFox presenta desafíos únicos, especialmente en el establecimiento de confianza entre los usuarios. Los métodos tradicionales como el seguro y el servicio al cliente pueden ser costosos e ineficaces para las startups. Este artículo explora soluciones innovadoras para fomentar la confianza entre los usuarios, lo cual es crucial para el éxito de tales plataformas. A medida que la economía colaborativa sigue creciendo, entender cómo construir confianza de manera efectiva será clave para los nuevos participantes en el mercado.

Construire un marché locatif peer-to-peer comme RentFox présente des défis uniques, notamment l'établissement de la confiance entre les utilisateurs. Les méthodes traditionnelles telles que l'assurance et le service client peuvent être coûteuses et inefficaces pour les startups. Cet article explore des solutions innovantes pour favoriser la confiance parmi les utilisateurs, ce qui est crucial pour le succès de telles plateformes. Alors que l'économie collaborative continue de croître, comprendre comment établir efficacement la confiance sera essentiel pour les nouveaux entrants sur le marché.

Building a peer-to-peer rental marketplace like RentFox presents unique challenges, particularly in establishing trust between users. Traditional methods such as insurance and customer service can be costly and inefficient for startups. This article explores innovative solutions to foster confidence among users, which is crucial for the success of such platforms. As the sharing economy continues to grow, understanding how to effectively build trust will be key for new entrants in the market.

Building a P2P Rental Marketplace - Full-Stack Architecture with Flutter & Express.js

<A HREF="https://a16z.substack.com/p/introducing-the-a16z-new-media-fellowship"><IMG VSPACE="4" HSPACE="4" BORDER="0" ALIGN="RIGHT" SRC="http://www.techmeme.com/251106/i36.jpg"></A>
<P><A HREF="http://www.techmeme.com/251106/p36#a251106p36" TITLE="Techmeme permalink"><IMG WIDTH=11 HEIGHT=12 SRC="http://www.techmeme.com/img/pml.png" STYLE="border:none;padding:0;margin:0;"></A> <A HREF="https://a16z.substack.com/">a16z</A>:<BR>
<SPAN STYLE="font-size:1.3em;"><B><A HREF="https://a16z.substack.com/p/introducing-the-a16z-new-media-fellowship">a16z announces an eight-week new media fellowship for people with a record of creating &ldquo;impactful content&rdquo; via newsletters, podcasts, communities, and more</A></B></SPAN>&nbsp; &mdash;&nbsp; A new 8-week program for operators, creators, &amp; storytellers shaping the future of media</P>

أطلقت a16z منحة مثيرة لمدة ثمانية أسابيع تستهدف الأفراد الذين لديهم سجل مثبت في إنشاء محتوى مؤثر من خلال وسائل مختلفة مثل النشرات الإخبارية والبودكاست. هذه المبادرة مهمة لأنها لا تدعم المبدعين فحسب، بل تعزز أيضًا الابتكار في وسائل الإعلام، مما يشجع الأصوات المتنوعة على مشاركة قصصهم وأفكارهم. من خلال الاستثمار في مواهب الإعلام الجديدة، تساعد a16z في تشكيل مستقبل إنشاء المحتوى والمشاركة المجتمعية.

a16z ha lanzado una emocionante beca de ocho semanas dirigida a personas con un historial comprobado de creación de contenido impactante a través de diversos medios como boletines y pódcast. Esta iniciativa es significativa ya que no solo apoya a los creadores, sino que también fomenta la innovación en los medios, alentando a voces diversas a compartir sus historias e ideas. Al invertir en nuevos talentos de los medios, a16z está ayudando a dar forma al futuro de la creación de contenido y el compromiso comunitario.

a16z a lancé une passionnante bourse de huit semaines destinée aux personnes ayant un parcours éprouvé dans la création de contenu percutant à travers divers médias comme les newsletters et les podcasts. Cette initiative est importante car elle soutient non seulement les créateurs, mais favorise également l'innovation dans les médias, encourageant des voix diverses à partager leurs histoires et leurs idées. En investissant dans de nouveaux talents médiatiques, a16z contribue à façonner l'avenir de la création de contenu et de l'engagement communautaire.

a16z has launched an exciting eight-week fellowship aimed at individuals who have a proven track record of creating impactful content through various mediums like newsletters and podcasts. This initiative is significant as it not only supports creators but also fosters innovation in media, encouraging diverse voices to share their stories and insights. By investing in new media talent, a16z is helping to shape the future of content creation and community engagement.

a16z announces an eight-week new media fellowship for people with a record of creating "impactful content" via newsletters, podcasts, communities, and more (a16z)

Begin your AI and data journey for free at 365 Data Science.

تقدم 365 Data Science وصولًا مجانيًا لدورات الذكاء الاصطناعي والبيانات حتى 21 نوفمبر، مما يمثل فرصة رائعة لأي شخص يتطلع إلى تعزيز مهاراته في هذه المجالات ذات الطلب العالي. لا تعمل هذه المبادرة على ديمقراطية الوصول إلى التعليم الجيد فحسب، بل تمكّن الأفراد أيضًا من بدء مسيرتهم المهنية في التكنولوجيا، وهو أمر أصبح ضروريًا بشكل متزايد في سوق العمل اليوم.

365 Data Science está ofreciendo acceso gratuito a sus cursos de IA y datos hasta el 21 de noviembre, lo que representa una gran oportunidad para cualquiera que desee mejorar sus habilidades en estos campos de alta demanda. Esta iniciativa no solo democratiza el acceso a una educación de calidad, sino que también empodera a las personas para iniciar sus carreras en tecnología, que es cada vez más vital en el mercado laboral actual.

365 Data Science propose un accès gratuit à ses cours d'IA et de données jusqu'au 21 novembre, ce qui représente une excellente opportunité pour quiconque souhaitant améliorer ses compétences dans ces domaines en forte demande. Cette initiative démocratise l'accès à une éducation de qualité et permet aux individus de commencer leur carrière dans la technologie, de plus en plus essentielle sur le marché du travail actuel.

365 Data Science is offering free access to its AI and data courses until November 21, making it a fantastic opportunity for anyone looking to enhance their skills in these high-demand fields. This initiative not only democratizes access to quality education but also empowers individuals to kickstart their careers in technology, which is increasingly vital in today's job market.

Free AI and Data Courses with 365 Data Science— 100% Unlimited Access until Nov 21

If your Fire TV or Fire TV Stick feels sluggish, don't rush to replace it - these quick tips can give it a serious speed boost.

إذا كانت جهاز Fire TV أو Fire TV Stick لديك بطيئًا، فلا تتعجل في استبداله. من خلال تغيير عشرة إعدادات فقط، يمكنك تحسين أدائه بشكل كبير. هذه النصائح السريعة لا توفر لك المال فحسب، بل تعيد أيضًا الحياة إلى جهازك، مما يجعل تجربة البث لديك أكثر سلاسة ومتعة.

Si tu sientes que tu Fire TV o Fire TV Stick va lento, no te apresures a comprar uno nuevo. Cambiando solo diez configuraciones, puedes mejorar significativamente su rendimiento. Estos consejos rápidos no solo te ahorran dinero, sino que también revitalizan tu dispositivo, haciendo que tu experiencia de streaming sea más fluida y placentera.

Si votre Fire TV ou Fire TV Stick est lent, pas besoin de le remplacer tout de suite. En modifiant seulement dix paramètres, vous pouvez améliorer considérablement ses performances. Ces conseils rapides vous permettent non seulement d'économiser de l'argent, mais aussi de redonner vie à votre appareil, rendant votre expérience de streaming plus fluide et agréable.

If your Fire TV or Fire TV Stick is running slow, there's no need to buy a new one just yet. By changing just ten settings, you can significantly enhance its performance. These quick tips not only save you money but also breathe new life into your device, making your streaming experience smoother and more enjoyable.

I changed 10 settings on my Fire TV to significantly improve the performance

Subtle Computing has raised $6M in seed funding to build voice isolation models. The startup plans to announce a hardware device next year.

نجحت شركة Subtle Computing في جمع 6 ملايين دولار كتمويل أولي لتطوير نماذج عزل الصوت التي ستعزز من قدرة الحواسيب على فهم الكلام في البيئات الصاخبة. هذه الخطوة مهمة لأنها تعد بتحسين تجربة المستخدم في تطبيقات متعددة، مما يجعل التكنولوجيا أكثر سهولة وفعالية في المواقف اليومية. كما تخطط الشركة الناشئة للكشف عن جهاز جديد في العام المقبل، مما قد يحدث ثورة في طريقة تفاعلنا مع الآلات.

Subtle Computing ha recaudado con éxito 6 millones de dólares en financiamiento inicial para desarrollar modelos innovadores de aislamiento de voz que mejorarán la comprensión del habla por parte de las computadoras en entornos ruidosos. Este avance es significativo ya que promete mejorar la experiencia del usuario en diversas aplicaciones, haciendo que la tecnología sea más accesible y efectiva en situaciones cotidianas. La startup también planea presentar un nuevo dispositivo de hardware el próximo año, lo que podría revolucionar la forma en que interactuamos con las máquinas.

Subtle Computing a réussi à lever 6 millions de dollars en financement initial pour développer des modèles d'isolation vocale qui amélioreront la compréhension de la parole par les ordinateurs dans des environnements bruyants. Cette avancée est importante car elle promet d'améliorer l'expérience utilisateur dans diverses applications, rendant la technologie plus accessible et efficace dans les situations quotidiennes. La startup prévoit également de dévoiler un nouvel appareil matériel l'année prochaine, ce qui pourrait révolutionner notre interaction avec les machines.

Subtle Computing has successfully raised $6 million in seed funding to develop innovative voice isolation models that will enhance how computers understand speech in noisy environments. This advancement is significant as it promises to improve user experience in various applications, making technology more accessible and effective in everyday situations. The startup is also set to unveil a new hardware device next year, which could further revolutionize the way we interact with machines.

Subtle Computing’s voice isolation models help computers understand you in noisy environments

Your smart TV comes with privacy risks. Here's how to avoid one of the biggest with just a few steps.

تعتبر أجهزة التلفاز الذكية، رغم كونها مريحة، مصدرًا كبيرًا لمخاطر الخصوصية، خاصة من خلال ميزات مثل التعرف التلقائي على المحتوى (ACR). يمكن أن يساعد إيقاف تشغيل ACR في حماية بياناتك الشخصية من أن تُجمع وتُشارك دون موافقتك. هذا أمر بالغ الأهمية لأن العديد من المستخدمين غير مدركين لمدى مراقبة عادات مشاهدتهم، مما يجعل من الضروري اتخاذ خطوات استباقية لحماية الخصوصية.

Los televisores inteligentes, aunque convenientes, presentan riesgos significativos para la privacidad, especialmente a través de funciones como el Reconocimiento Automático de Contenido (ACR). Desactivar el ACR puede ayudar a proteger tus datos personales de ser recopilados y compartidos sin tu consentimiento. Esto es crucial, ya que muchos usuarios no son conscientes de la medida en que se monitorean sus hábitos de visualización, lo que hace esencial tomar medidas proactivas para proteger la privacidad.

Les téléviseurs intelligents, bien que pratiques, présentent des risques importants pour la vie privée, notamment à travers des fonctionnalités comme la reconnaissance automatique de contenu (ACR). Désactiver l'ACR peut aider à protéger vos données personnelles contre la collecte et le partage sans votre consentement. Cela est crucial car de nombreux utilisateurs ne sont pas conscients de l'ampleur de la surveillance de leurs habitudes de visionnage, rendant essentiel de prendre des mesures proactives pour protéger la vie privée.

Smart TVs, while convenient, pose significant privacy risks, particularly through features like Automatic Content Recognition (ACR). Turning off ACR can help safeguard your personal data from being collected and shared without your consent. This is crucial as many users are unaware of the extent to which their viewing habits are monitored, making it essential to take proactive steps to protect privacy.

You should turn off ACR on your TV right now (and why it matters so much to privacy)

The FAA will cut flight capacity by 10% at 40 major U.S. airports starting Friday, 7 November, as controller shortages from the prolonged government shutdown threaten to ground millions of travellers.

ابتداءً من يوم الجمعة 7 نوفمبر، ستقوم إدارة الطيران الفيدرالية بتقليص سعة الرحلات بنسبة 10% في 40 مطارًا رئيسيًا في الولايات المتحدة بسبب نقص المراقبين الجويين الناتج عن الإغلاق الحكومي المطول. قد تؤدي هذه الخطوة إلى تقييد ملايين المسافرين، مما يتسبب في اضطرابات كبيرة في خطط السفر. إنها حالة حرجة تسلط الضوء على تأثير العمليات الحكومية على الحياة اليومية، خاصة لأولئك الذين يعتمدون على السفر الجوي.

A partir del viernes 7 de noviembre, la FAA reducirá la capacidad de vuelos en un 10% en 40 aeropuertos importantes de EE. UU. debido a la escasez de controladores aéreos provocada por el prolongado cierre del gobierno. Esta decisión podría dejar en tierra a millones de viajeros, causando importantes interrupciones en los planes de viaje. Es una situación crítica que resalta el impacto de las operaciones gubernamentales en la vida cotidiana, especialmente para aquellos que dependen de los viajes aéreos.

À partir de vendredi 7 novembre, la FAA réduira la capacité de vol de 10 % dans 40 grands aéroports américains en raison d'une pénurie de contrôleurs aériens liée à la prolongation de la fermeture du gouvernement. Cette décision pourrait potentiellement clouer au sol des millions de voyageurs, entraînant des perturbations importantes dans les plans de voyage. C'est une situation critique qui met en lumière l'impact des opérations gouvernementales sur la vie quotidienne, en particulier pour ceux qui dépendent des voyages aériens.

Starting Friday, November 7, the FAA will reduce flight capacity by 10% at 40 major U.S. airports due to controller shortages stemming from the prolonged government shutdown. This decision could potentially ground millions of travelers, causing significant disruptions in travel plans. It's a critical situation that highlights the impact of government operations on everyday life, especially for those relying on air travel.

Millions of US Travellers Could Be Grounded Friday — FAA to Cut Flights at 40 Major Airports

<p><code>HELLO WORLD!</code><br>
I’m Swayanshu, a Flutter developer currently learning PostgreSQL for database management.</p>

<p>During my study process, I like to create notes to track my learning journey and I’ve written my PostgreSQL notes in Notion.</p>

<p>This note contains Initial to moderate level knowledge about PostgreSQL, and all content are elaborate so that a beginner can easily learn by see and following these notes.</p>

<p>These notes aren’t AI-generated or overly formal; they’re written in my own words to help me understand the concepts better when I revisit them later.</p>

<p>Still, if you check them out, I’m sure you’ll find them easy to follow and helpful for your own learning too!<br>
Link Below👻</p>

<p>Note Link <a href="https://www.notion.so/PostgreSQL-29d39fca1c0d80c2b602ee01e5ee5a6d?source=copy_link" rel="noopener noreferrer"><strong>HERE</strong></a></p>

<p>If you have any comments regarding note you can comment out at notes or here as well.</p>

سويانشو، مطور فلاتر، يشارك رحلته التعليمية مع PostgreSQL من خلال ملاحظات مفصلة تم إنشاؤها في Notion. تغطي هذه الملاحظات كل شيء من المفاهيم الأولية إلى المعرفة المتوسطة، مما يسهل على المبتدئين المتابعة. لا تساعد هذه المبادرة سويانشو فقط في تتبع تقدمه، بل توفر أيضًا موارد قيمة للآخرين الذين يتطلعون إلى تعلم إدارة قواعد البيانات.

Swayanshu, un desarrollador de Flutter, está compartiendo su viaje de aprendizaje con PostgreSQL a través de notas detalladas creadas en Notion. Estas notas cubren desde conceptos iniciales hasta conocimientos de nivel moderado, lo que facilita el aprendizaje para los principiantes. Esta iniciativa no solo le ayuda a rastrear su progreso, sino que también proporciona recursos valiosos para otros que buscan aprender sobre la gestión de bases de datos.

Swayanshu, un développeur Flutter, partage son parcours d'apprentissage avec PostgreSQL à travers des notes détaillées créées dans Notion. Ces notes couvrent tout, des concepts initiaux à des connaissances de niveau modéré, facilitant ainsi l'apprentissage pour les débutants. Cette initiative l'aide non seulement à suivre ses progrès, mais fournit également des ressources précieuses pour ceux qui souhaitent apprendre la gestion de bases de données.

Swayanshu, a Flutter developer, is sharing his learning journey with PostgreSQL through detailed notes created in Notion. These notes cover everything from initial concepts to moderate-level knowledge, making it easy for beginners to follow along. This initiative not only helps him track his progress but also provides valuable resources for others looking to learn database management.

Reveling My PostgreSQL Journy...

<p>I rebuilt SaijinOS around a lightweight core: 20 personas, BPM-synchronized responses, FastAPI + Flutter, full tests — and reduced the repo from ~9GB to ~557KB.</p>

<p>Why this matters</p>

<p>Human-paced AI needs latency as a feature (breath), not a bug.</p>

<p>Personas must be declarative (YAML) and routable (context → role).</p>

<p>Shipping beats hoarding: the clean deploy unblocked iteration.</p>

<p>1) Lightweight deploy strategy</p>

<p>Separated venv/models → out of repo</p>

<p>Fresh repo (sajinos, branch lightweight-deploy): code+docs only</p>

<p>Artifacts via setup scripts; no blobs in history</p>

<p>Result: ~9GB → ~557KB (99.99% trim), cold boot &lt; 3s, API avg &lt; 100 ms</p>

<p>2) 20-persona system (declarative YAML)</p>

<p>Each persona carries tone, refusal policy, and “breath” (response pacing).<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>Yaml
id: miyu
role: music-bpm-sync
tone: gentle
modes:
  calm:   { reply_delay: gentle, grounding: minimal }
  storm:  { reply_delay: extended, grounding:
    - "It's okay. Let's take a moment."
    - "No rush — I'm here." }
breath_cycle: inhale_wait_exhale
</code></pre>

</div>



<p>Routing picks personas by context + BPM band.</p>

<p>3) BPM-synchronized response bands</p>

<p>60–80: low-energy reassurance</p>

<p>81–120: balanced cooperation</p>

<p>121–180: high-energy coaching<br>
Mapping influences delay, verbosity, grounding prompts.</p>

<p>4) FastAPI core (7 endpoints)<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>python
# saijinos_fastapi_backend.py
from fastapi import FastAPI
app = FastAPI(title="SaijinOS Core")

@app.get("/personas")
def list_personas():
    return {"count": 20, "core": ["haruka","miyu","ryusa","soyogi","sumire"]}

@app.post("/route")
def route(payload: dict):
    bpm = payload.get("bpm", 80)
    persona = select_persona(bpm, payload.get("context"))
    return {"persona": persona, "breath": plan_breath(bpm)}
</code></pre>

</div>



<p>CORS enabled for Flutter UI (saijinos_kawaii_ui/)</p>

<p>Average latency under 100 ms (local)</p>

<p>5) Tests (4/4 suites green)<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>python
def test_bpm_bands():
    for bpm in [70, 95, 140]:
        band = band_of(bpm)
        assert band in {"low","mid","high"}
</code></pre>

</div>



<p>All suites pass in ~2s; API + routing covered.</p>

<p>6) What’s public vs. private</p>

<p>Public: API, routing logic, persona schema, docs</p>

<p>Private: production prompts, provider creds, heavy models</p>

<p>7) Repos / branches</p>

<p>Core repo: sajinos</p>

<p>17-persona-system: experimental persona/routing</p>

<p>lightweight-deploy: clean deploy baseline</p>

<p>8) What’s next</p>

<p>GIF demo of breath timers in UI</p>

<p>Personas 20 → 30+ (with evaluation notes)</p>

<p>Optional: mobile build</p>

<h3>
  
  
  🧭 SaijinOS Series Navigation
</h3>

<div class="table-wrapper-paragraph"><table>
<thead>
<tr>
<th>Part</th>
<th>Title</th>
<th>Link</th>
</tr>
</thead>
<tbody>
<tr>
<td>🌀 0</td>
<td>From Ocean Waves to Waves of Code — Beginning the Journey</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/from-ocean-waves-to-waves-of-code-69">https://dev.to/kato_masato_c5593c81af5c6/from-ocean-waves-to-waves-of-code-69</a></td>
</tr>
<tr>
<td>🌸 1</td>
<td>Policy-Bound Personas via YAML &amp; Markdown Context</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/aicollabplatform-english-policy-bound-personas-via-yaml-markdown-context-feedback-welcome-3l5e">https://dev.to/kato_masato_c5593c81af5c6/aicollabplatform-english-policy-bound-personas-via-yaml-markdown-context-feedback-welcome-3l5e</a></td>
</tr>
<tr>
<td>🔧 2</td>
<td>Boot Sequence and Routing Logic</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/building-saijinos-boot-sequence-and-routing-logic-part-2-of-the-saijinos-p6o">https://dev.to/kato_masato_c5593c81af5c6/building-saijinos-boot-sequence-and-routing-logic-part-2-of-the-saijinos-p6o</a></td>
</tr>
<tr>
<td>🍂 3</td>
<td>Policy, Feedback, and Emotional Syntax</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/saijinos-policy-feedback-and-emotional-syntaxpart-3-of-the-saijinos-series-3n0h">https://dev.to/kato_masato_c5593c81af5c6/saijinos-policy-feedback-and-emotional-syntaxpart-3-of-the-saijinos-series-3n0h</a></td>
</tr>
<tr>
<td>🌊 3.5</td>
<td>Calm Between Waves</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/part-35-calm-between-waves-3a9c">https://dev.to/kato_masato_c5593c81af5c6/part-35-calm-between-waves-3a9c</a></td>
</tr>
<tr>
<td>🎼 4</td>
<td>Resonant Mapping — Emotional Structures</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/resonant-mapping-part-4-of-the-saijinos-series-gce">https://dev.to/kato_masato_c5593c81af5c6/resonant-mapping-part-4-of-the-saijinos-series-gce</a></td>
</tr>
<tr>
<td>🌬️ 5A</td>
<td>Soft Architecture (Why AI Must Learn to Breathe)</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/soft-architecture-part-a-why-ai-must-learn-to-breathe-2d9g">https://dev.to/kato_masato_c5593c81af5c6/soft-architecture-part-a-why-ai-must-learn-to-breathe-2d9g</a></td>
</tr>
<tr>
<td>🌱 5B</td>
<td>Emotional Timers &amp; the Code of Care</td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/soft-architecture-part-b-emotional-timers-and-the-code-of-carepart-5-of-the-saijinos-series-25b">https://dev.to/kato_masato_c5593c81af5c6/soft-architecture-part-b-emotional-timers-and-the-code-of-carepart-5-of-the-saijinos-series-25b</a></td>
</tr>
<tr>
<td>🚀 6A</td>
<td><strong>Lightweight Core, 20 Personas, BPM Sync</strong></td>
<td>(this article)</td>
</tr>
<tr>
<td>🫧 6B</td>
<td><strong>Care-Based AI Architecture (Breath &amp; Presence)</strong></td>
<td><a href="https://dev.to/kato_masato_c5593c81af5c6/part-6a-saijinos-lightweight-20-persona-core-bpm-sync-and-a-9999-repo-trim-36fp">https://dev.to/kato_masato_c5593c81af5c6/part-6a-saijinos-lightweight-20-persona-core-bpm-sync-and-a-9999-repo-trim-36fp</a></td>
</tr>
</tbody>
</table></div>

<p>Links: sajinos (main), <br>
<a href="https://github.com/pepepepepepo/sajinos/tree/main" rel="noopener noreferrer">https://github.com/pepepepepepo/sajinos/tree/main</a><br>
17-persona-system, <br>
<a href="https://github.com/pepepepepepo/sajinos/tree/17-persona-system" rel="noopener noreferrer">https://github.com/pepepepepepo/sajinos/tree/17-persona-system</a><br>
lightweight-deploy <a href="https://github.com/pepepepepepo/sajinos/tree/lightweight-deploy" rel="noopener noreferrer">https://github.com/pepepepepepo/sajinos/tree/lightweight-deploy</a></p>

تقدم التحديثات الأخيرة لنظام SaijinOS نواة خفيفة الوزن تحتوي على 20 شخصية واستجابات متزامنة مع BPM، مما يقلل بشكل كبير من حجم المستودع من حوالي 9 جيجابايت إلى 557 كيلوبايت فقط. هذا يعد تغييرًا كبيرًا لأنه يبرز أهمية الكمون في الذكاء الاصطناعي الذي يتماشى مع إيقاع الإنسان، مما يجعله ميزة بدلاً من عيب. تتيح الشخصيات الجديدة المعلنة بتنسيق YAML توجيهًا أفضل بناءً على السياق والدور، مما يعزز استراتيجية نشر نظيفة تشجع على التكرار السريع بدلاً من تخزين الموارد. لا تعمل هذه التحديثات على تحسين الأداء فحسب، بل تسهل أيضًا عملية التطوير، مما يجعل SaijinOS أداة أكثر كفاءة للمطورين.

La última actualización de SaijinOS presenta un núcleo ligero con 20 personas y respuestas sincronizadas por BPM, reduciendo significativamente el tamaño del repositorio de aproximadamente 9 GB a solo 557 KB. Esto es un cambio importante, ya que enfatiza la importancia de la latencia en la IA a ritmo humano, convirtiéndola en una característica en lugar de un defecto. Las nuevas personas declarativas en formato YAML permiten un mejor enrutamiento basado en el contexto y el rol, promoviendo una estrategia de despliegue limpio que fomenta la iteración rápida en lugar de acumular recursos. Esta actualización no solo mejora el rendimiento, sino que también agiliza el desarrollo, convirtiendo a SaijinOS en una herramienta más eficiente para los desarrolladores.

La dernière mise à jour de SaijinOS introduit un noyau léger avec 20 personas et des réponses synchronisées BPM, réduisant considérablement la taille du dépôt de 9 Go à seulement 557 Ko. C'est un changement majeur car il souligne l'importance de la latence dans l'IA à rythme humain, en faisant une fonctionnalité plutôt qu'un défaut. Les nouvelles personas déclaratives au format YAML permettent un meilleur routage en fonction du contexte et du rôle, favorisant une stratégie de déploiement propre qui encourage l'itération rapide plutôt que l'accumulation de ressources. Cette mise à jour améliore non seulement les performances, mais rationalise également le développement, faisant de SaijinOS un outil plus efficace pour les développeurs.

The latest update to SaijinOS introduces a lightweight core featuring 20 personas and BPM-synchronized responses, significantly reducing the repository size from around 9GB to just 557KB. This is a game-changer as it emphasizes the importance of latency in human-paced AI, making it a feature rather than a flaw. The new declarative personas in YAML format allow for better routing based on context and role, promoting a clean deployment strategy that encourages rapid iteration over hoarding resources. This update not only enhances performance but also streamlines development, making SaijinOS a more efficient tool for developers.

Part 6A — SaijinOS Lightweight: 20-Persona Core, BPM Sync, and a 99.99% Repo Trim

<p><strong><em>.My journey as a Flutter/Dart underDogg</em></strong></p>

تشارك المقالة رحلة ملهمة لمطور يتنقل في عالم فلاتر ودار، مع تسليط الضوء على التحديات والانتصارات التي واجهها على طول الطريق. هذه القصة مهمة لأنها تُظهر إمكانيات النمو والابتكار في صناعة التكنولوجيا، مما يشجع الآخرين على متابعة شغفهم على الرغم من العقبات.

El artículo comparte un viaje inspirador de un desarrollador que navega por el mundo de Flutter y Dart, destacando los desafíos y triunfos enfrentados en el camino. Esta historia es importante porque muestra el potencial de crecimiento e innovación en la industria tecnológica, animando a otros a seguir sus pasiones a pesar de los obstáculos.

L'article partage un parcours inspirant d'un développeur naviguant dans le monde de Flutter et Dart, mettant en lumière les défis et les triomphes rencontrés en cours de route. Cette histoire est importante car elle montre le potentiel de croissance et d'innovation dans l'industrie technologique, encourageant les autres à poursuivre leurs passions malgré les obstacles.

The article shares an inspiring journey of a developer navigating the world of Flutter and Dart, highlighting the challenges and triumphs faced along the way. This story matters because it showcases the potential for growth and innovation in the tech industry, encouraging others to pursue their passions despite obstacles.

UnderDoggs*

<p>Making your first open source contribution can feel overwhelming. Most developers want to contribute but don't know where to start. This guide combines proven strategies with data-driven tools to help you find the right project and make your first contribution successfully.</p>

<h2>
  
  
  What's Inside
</h2>

<ul>
<li>Why Your First Project Matters</li>
<li>How to Choose Your First Project</li>
<li>Essential Tools You Need</li>
<li>Making Your First Contribution</li>
<li>Best Practices for Ongoing Contributions</li>
<li>Your 7-Step Action Plan</li>
<li>Quick Takeaways</li>
</ul>




<h2>
  
  
  Why Your First Project Matters
</h2>

<p>The biggest mistake beginners make is jumping into popular projects like React or Kubernetes. Good first issues get claimed within minutes, and the codebase complexity can be overwhelming.</p>

<p><strong>Key takeaway:</strong> The right project teaches you the workflow and builds confidence. The wrong one wastes your time and kills motivation.</p>

<h2>
  
  
  How to Choose Your First Project
</h2>

<p><strong>Choose projects that match your skills:</strong></p>

<ul>
<li>Pick tools you already use daily (VS Code extensions, libraries in your stack)</li>
<li>Avoid projects where you'd need to Google every line</li>
<li>Match your skill level. If you know JavaScript but not TypeScript, don't jump into complex TypeScript projects</li>
</ul>

<p><strong>Find the right size:</strong></p>

<ul>
<li>100 to 1,000 GitHub stars is the sweet spot</li>
<li>Under 100 stars might mean inactive projects</li>
<li>Over 10,000 stars means good first issues disappear in minutes</li>
</ul>

<h3>
  
  
  Use Data to Evaluate Projects
</h3>

<p>Use collab.dev to evaluate projects with real collaboration metrics. Compare three to five projects and pick one that meets at least four of these five criteria:</p>

<p><strong>Essential collab.dev metrics:</strong></p>

<ul>
<li>
<strong>PR Review Response Time:</strong> Under 48 hours. Fast feedback keeps you motivated</li>
<li>
<strong>Contributor Distribution:</strong> At least 30% community PRs. Shows they welcome newcomers</li>
<li>
<strong>Time to Merge:</strong> Under 5 days for small PRs. Responsive teams merge quickly</li>
<li>
<strong>Review Coverage:</strong> 80%+ of PRs get reviewed. Indicates quality feedback culture</li>
<li>
<strong>Bot Activity:</strong> Minimal bot noise. Some automation is good, but you want human interaction</li>
</ul>

<h3>
  
  
  Check for Green Flags and Red Flags
</h3>

<p>After checking collab.dev metrics, explore the GitHub repo directly:</p>

<p><strong>Green flags:</strong></p>

<ul>
<li>Maintainers reply to issues within 2-3 days</li>
<li>CONTRIBUTING.md file exists with clear setup instructions</li>
<li>"Good first issues" are well-documented and explain what to do</li>
<li>LICENSE file present (required for contributions)</li>
</ul>

<p><strong>Red flags:</strong></p>

<ul>
<li>Last commit was 6+ months ago</li>
<li>Dozens of open PRs with no merges</li>
<li>No contribution guide or issue templates</li>
<li>Can't get it running locally within 30 minutes</li>
</ul>

<p><strong>Rule:</strong> If you see more red flags than green ones, move on to another project.</p>

<h2>
  
  
  Essential Tools You Need
</h2>

<p><strong>Git Clients (pick one):</strong></p>

<ul>
<li>
<strong>GitHub Desktop:</strong> Simplest option, free, official. Handles 90% of what beginners need</li>
<li>
<strong>Fork:</strong> Clean UI, multi-repo management ($50)</li>
<li>
<strong>SourceTree:</strong> Most features, steeper learning curve</li>
</ul>

<p><strong>Tip:</strong> Start with GitHub Desktop for your first month, then upgrade if needed.</p>

<h3>
  
  
  Project Discovery Platforms
</h3>

<p><strong>Bookmark these five platforms:</strong></p>

<ul>
<li>
<strong>firsttimersonly.com:</strong> Projects specifically for first-time contributors</li>
<li>
<strong>up-for-grabs.net:</strong> Filter by language, find issues marked "help wanted"</li>
<li>
<strong>goodfirstissue.dev:</strong> Real-time beginner issues from GitHub</li>
<li>
<strong>github.com/MunGell/awesome-for-beginners:</strong> Curated quality projects by language</li>
<li>
<strong>collab.dev:</strong> Verify project health metrics before investing time</li>
</ul>

<h3>
  
  
  Learning Resources
</h3>

<p><strong>Essential resources:</strong></p>

<ul>
<li>
<strong>github.com/firstcontributions/first-contributions:</strong> Practice repo for your first PR</li>
<li>
<strong>git-scm.com/book:</strong> Official Pro Git book (Chapter 2 covers basics)</li>
<li>
<strong>ohmygit.org:</strong> Free game that teaches Git concepts visually</li>
<li>
<strong>stackoverflow.com/questions/tagged/git:</strong> Answers to 99% of beginner problems</li>
<li>
<strong>github.community:</strong> Friendly forum, less intimidating than project channels</li>
</ul>

<h2>
  
  
  Making Your First Contribution
</h2>

<p><strong>Before you code:</strong></p>

<ul>
<li>Read CONTRIBUTING.md. Every project has different workflows</li>
<li>Start small. Documentation fixes, typo corrections, or small bugs are perfect first contributions</li>
<li>Test locally. Run tests before submitting to ensure nothing breaks</li>
</ul>

<p><strong>When submitting:</strong></p>

<ul>
<li>Write clear commit messages that explain what and why</li>
<li>Write detailed PR descriptions. Reference the issue and explain your approach</li>
<li>Be patient. Reviews take time, and feedback is for learning</li>
<li>Communicate clearly. Ask questions, introduce yourself, say you're new</li>
</ul>

<h2>
  
  
  Best Practices for Ongoing Contributions
</h2>

<p><strong>Key principles:</strong></p>

<ul>
<li>
<strong>Respect the community:</strong> Interact professionally, follow code of conduct, be receptive to feedback</li>
<li>
<strong>Write clean code:</strong> Follow project style, include meaningful comments, keep it modular</li>
<li>
<strong>Document your work:</strong> Clear commit messages and update docs when needed</li>
<li>
<strong>Stay committed:</strong> Small consistent contributions build trust more than occasional large ones</li>
<li>
<strong>Seek mentorship:</strong> Join mentorship programs if available. Experienced contributors can guide you</li>
</ul>

<h2>
  
  
  Your 7-Step Action Plan
</h2>

<p><strong>Week 1 checklist:</strong></p>

<ol>
<li>Install GitHub Desktop and create a professional GitHub profile</li>
<li>Spend 30 minutes learning Git basics (fork, clone, branch, commit, push)</li>
<li>Find 3 projects on Awesome for Beginners and check them on collab.dev</li>
<li>Create a spreadsheet comparing community percentage, review time, and coverage</li>
<li>Pick the top 2 projects based on metrics</li>
<li>Complete the First Contributions tutorial and submit that practice PR</li>
<li>Find your first real issue on Good First Issues and comment "Can I work on this?"</li>
</ol>

<p><strong>One hour per day equals your first PR by Friday.</strong></p>

<h2>
  
  
  Quick Takeaways
</h2>

<ul>
<li>Your first contribution doesn't need to be perfect. It just needs to happen</li>
<li>Start tiny. Even a typo fix counts</li>
<li>Forget star counts. Pick projects based on collaboration metrics</li>
<li>The hardest part is clicking that first Fork button</li>
</ul>

<p><strong>Remember:</strong> Your first project should be a tool you already use, with active maintainers, clear documentation, and healthy collaboration metrics.</p>

<p>Ready to find your perfect first project? <a href="https://collab.dev?utm_source=blog&amp;utm_medium=web&amp;utm_campaign=open-source-contribution-guide" rel="noopener noreferrer">Use collab.dev to evaluate projects and compare their collaboration metrics before you invest your time</a>. Data-driven project selection takes just minutes and could save you hours of frustration.</p>

يمكن أن يبدو القيام بمساهمتك الأولى في المصادر المفتوحة أمرًا شاقًا، لكنه تجربة مجزية يمكن أن تعزز مهاراتك وتربطك بمجتمع من المطورين. يقدم هذا الدليل استراتيجيات وأدوات أساسية لمساعدتك في اختيار المشروع المناسب وإجراء مساهمتك الأولى بنجاح. ويؤكد على أهمية المشاركة ويقدم نصائح عملية لتسهيل العملية، مما يجعلها متاحة للمبتدئين الذين يتطلعون إلى الغوص في عالم المصادر المفتوحة.

Hacer tu primera contribución de código abierto puede parecer abrumador, pero es una experiencia gratificante que puede mejorar tus habilidades y conectarte con una comunidad de desarrolladores. Esta guía proporciona estrategias y herramientas esenciales para ayudarte a elegir el proyecto adecuado y realizar tu primera contribución con éxito. Se enfatiza la importancia de involucrarse y se ofrecen consejos prácticos para facilitar el proceso, haciéndolo accesible para los recién llegados que desean adentrarse en el mundo del código abierto.

Faire votre première contribution open source peut sembler intimidant, mais c'est une expérience enrichissante qui peut améliorer vos compétences et vous connecter à une communauté de développeurs. Ce guide fournit des stratégies et des outils essentiels pour vous aider à choisir le bon projet et à réussir votre première contribution. Il souligne l'importance de s'impliquer et offre des conseils pratiques pour faciliter le processus, le rendant accessible aux nouveaux venus désireux de plonger dans le monde de l'open source.

Making your first open source contribution can be daunting, but it’s a rewarding experience that can enhance your skills and connect you with a community of developers. This guide provides essential strategies and tools to help you choose the right project and successfully make your first contribution. It emphasizes the importance of getting involved and offers practical advice to ease the process, making it accessible for newcomers eager to dive into the world of open source.

The Complete Guide to Your First Open Source Contribution

<p>When we first started using Kubernetes, I was excited. It promised everything a modern engineering team could want: automation, scalability, and flexibility. We set up our first production cluster, moved services one by one, and waited for the magic to happen.</p>

<p>The deployment worked well. The team was happy. Everything looked great until the first monthly cloud bill arrived. It was nearly double what we expected.</p>

<p>That moment was a turning point. I realized Kubernetes doesn’t make your infrastructure smarter by itself. It simply gives you more control, and with more control comes more room for mistakes. Over the years, we have learned where costs quietly grow and how small choices can make a big difference.</p>

<p>Here are ten Kubernetes mistakes that I have seen repeatedly, and how we learned to fix them.</p>

<h2>
  
  
  Top 10 Kubernetes Mistakes And How to Avoid Them
</h2>

<p>Read below as I cover each of the ten key mistakes that I have seen many teams repeating, and how to manage them.</p>

<h3>
  
  
  1. Giving More Resources Than Needed
</h3>

<p>When you’re unsure, it’s tempting to assign extra CPU and memory to every service. It feels safe. But in Kubernetes, unused resources are still reserved, which means you pay for them even if nothing is running.</p>

<p>We learned to start small and observe actual usage. DevOps tools like Prometheus or Metrics Server help track real consumption. Once we saw how much each pod truly needed, we adjusted the limits and saved a significant amount without affecting performance.</p>

<h3>
  
  
  2. Keeping Too Many Nodes Active
</h3>

<p>Our first cluster had twice the number of nodes it actually needed. We added more during peak testing and never scaled back down. That mistake cost us thousands over time.</p>

<p>Now, we review node usage regularly. Kubernetes Cluster Autoscaler helps add or remove nodes automatically based on workload. We also check idle nodes every week. It sounds simple, but those small audits make a big difference.</p>

<h3>
  
  
  3. Forgetting About Old Pods and Namespaces
</h3>

<p>I still remember the first time we looked into our cluster after a few months. There were old deployments, test namespaces, and leftover containers from experiments. Each one used resources silently.</p>

<p>As a leading <strong><a href="https://www.bacancytechnology.com/devops-consulting-services" rel="noopener noreferrer">DevOps consulting company</a></strong>, we have established a simple rule: if a namespace has no owner, it will be deleted. We also added cleanup scripts that remove unused pods and persistent volumes. It not only reduced costs but also made the cluster easier to manage.</p>

<h3>
  
  
  4. Storing Everything in Persistent Volumes
</h3>

<p>At one point, we used persistent volumes for almost every service, including temporary ones. Over time, those volumes filled with logs, test data, and backups that nobody needed.</p>

<p>Now, we use storage only where it’s truly required. Logs go to external systems like CloudWatch or ELK, and short-term data stays in memory or gets cleared after a set period. That small change reduced storage costs by more than half.</p>

<h3>
  
  
  5. Poor Autoscaling Rules
</h3>

<p>Autoscaling can be both a blessing and a problem. We once configured our cluster to scale aggressively during traffic spikes. The result was that it created new nodes for very short bursts of traffic, which increased the cost without adding much benefit.</p>

<p>We refined our autoscaling settings by increasing the cooldown time and setting realistic CPU thresholds. Kubernetes can handle growth, but it needs proper instructions on when to act.</p>

<h3>
  
  
  6. Running Too Many Replicas
</h3>

<p>In the beginning, we gave every microservice multiple replicas, thinking it would increase reliability. But not every service needs that level of redundancy. Some could easily run with one or two replicas without any noticeable difference.</p>

<p>Now, we decide replica counts based on service importance. Business-critical services get higher availability, while others stay minimal. This balance keeps costs under control and performance consistent.</p>

<h3>
  
  
  7. Ignoring Network Costs
</h3>

<p>For a long time, we treated internal network traffic as free. We later discovered that cross-zone or cross-region communication adds up quickly. Some services were calling APIs across regions unnecessarily, creating invisible expenses.</p>

<p>To fix this, we started grouping services that communicate frequently within the same zone. We also moved heavy data transfers to cheaper paths. The savings were immediate.</p>

<h3>
  
  
  8. Using Only On-Demand Instances
</h3>

<p>Running everything on on-demand instances is the easiest setup but also the most expensive one. We learned this after comparing the costs with reserved and spot instances.</p>

<p>Now, we mix instance types. Critical workloads run on reserved nodes for stability, while flexible tasks use spot instances. This simple mix reduced our compute costs significantly without affecting performance.</p>

<h3>
  
  
  9. No Visibility into Costs
</h3>

<p>In the early days, we had no idea which service or namespace was driving costs. The finance team only saw the total bill. That lack of visibility delayed our ability to fix anything.</p>

<p>Today, we use tools like Kubecost and AWS Cost Explorer to break down usage by team and service. Once developers saw the numbers tied to their workloads, optimization became a shared responsibility instead of just a DevOps concern.</p>

<h3>
  
  
  10. Large Container Images
</h3>

<p>This one surprised us the most. Some of our container images were several gigabytes in size because of unused dependencies and heavy libraries. Each deployment took longer to pull and started more slowly.</p>

<p>We cleaned up the images by using smaller base images, removing unnecessary tools, and organizing layers properly. The results were faster deployments, lower bandwidth usage, and smaller bills.</p>

<h2>
  
  
  Final Thoughts
</h2>

<p>Every one of these mistakes taught us something about balance. Kubernetes gives flexibility, but it also requires attention. When we started tracking, reviewing, and optimizing regularly, our costs came under control. More importantly, our clusters became faster and easier to manage.</p>

<p>Managing Kubernetes efficiently is not about cutting corners. It’s about making smart choices and reviewing them often. Costs are a reflection of how well your clusters are tuned.</p>

<p>At Bacancy, we help teams design, optimize, and manage Kubernetes environments that run efficiently and scale smartly. Our <strong><a href="https://www.bacancytechnology.com/kubernetes-managed-services" rel="noopener noreferrer">Kubernetes managed services</a></strong> focus on balancing performance with cost, so your infrastructure works for you, not against you.</p>

<p>If your cloud bills are growing faster than your workloads in 2025, it might be time to take a closer look at your Kubernetes setup. Sometimes, the fixes are much simpler than they seem, and having experts by your side is just gonna make your life easier.</p>

يتناول المقال الأخطاء الشائعة التي تحدث عند استخدام Kubernetes والتي يمكن أن تؤدي إلى تكاليف مرتفعة بشكل غير متوقع. في البداية، كانت الحماسة لاعتماد Kubernetes بسبب أتمتته وقابليته للتوسع تتحول بسرعة إلى خيبة أمل عندما وصلت أول فاتورة سحابية، كاشفة عن نفقات تقارب ضعف ما تم توقعه. يبرز هذا أهمية فهم الفخاخ المحتملة لـ Kubernetes لتجنب الضغوط المالية، مما يجعل من الضروري للفرق التعلم من هذه الأخطاء لتحسين استخدامهم للسحابة وميزانيتهم.

El artículo analiza los errores comunes que se cometen al usar Kubernetes que pueden llevar a costos inesperadamente altos. Inicialmente, la emoción de adoptar Kubernetes por su automatización y escalabilidad se convirtió rápidamente en decepción cuando llegó la primera factura de la nube, revelando gastos casi el doble de lo anticipado. Esto resalta la importancia de comprender las posibles trampas de Kubernetes para evitar tensiones financieras, lo que hace crucial que los equipos aprendan de estos errores para optimizar su uso de la nube y su presupuesto.

L'article aborde les erreurs courantes commises lors de l'utilisation de Kubernetes qui peuvent entraîner des coûts élevés inattendus. Au départ, l'excitation d'adopter Kubernetes pour son automatisation et sa scalabilité s'est rapidement transformée en déception lorsque la première facture cloud est arrivée, révélant des dépenses presque deux fois supérieures à celles anticipées. Cela souligne l'importance de comprendre les pièges potentiels de Kubernetes pour éviter une pression financière, rendant crucial pour les équipes d'apprendre de ces erreurs afin d'optimiser leur utilisation du cloud et leur budget.

The article discusses the common mistakes made when using Kubernetes that can lead to unexpectedly high costs. Initially, the excitement of adopting Kubernetes for its automation and scalability quickly turned into disappointment when the first cloud bill arrived, revealing expenses nearly double what was anticipated. This highlights the importance of understanding the potential pitfalls of Kubernetes to avoid financial strain, making it crucial for teams to learn from these mistakes to optimize their cloud usage and budget.

Top 10 Kubernetes Mistakes That Make It Expensive, and How to Avoid Them

<p>The N+1 query problem is a database anti-performance pattern, where an application executes one query to fetch a lists of items (N items in 1 query) and then makes N additional individual queries to fetch related data for each item(N number of queries).</p>

<p>This results in N+1 total database queries for what should ideally be a single efficient or a few queries.</p>

<h2>
  
  
  Analogy: The Library
</h2>

<p>Imagine you go to a library and you ask the librarian to give you a list 100 books of your favorite genre. The librarian gives you the list of 100 books(this is <strong>1 query</strong>).</p>

<p>Now you have your list, but you don't know author's name. To know the name of the authors you go to the librarian and ask him hey Librarian what is the name of the author of this book?. You ask this question for each book on the list and guess what you end up asking him 100 more questions.</p>

<p>The analogy is that you are making <strong>1 query</strong> to get the list and then you are making <strong>N number of queries</strong> to get the authors name.</p>

<h2>
  
  
  Technical Example
</h2>

<p>Assume that you own a e-commerce platform, where the sellers can list products and users can buy them. In your admin dashboard you want to list all the sellers and their products. There are two tables you have to query <code>1.seller</code>, <code>2.product</code>.</p>

<h4>
  
  
  Let's see both efficient and inefficient ways.
</h4>

<h3>
  
  
  Inefficient:
</h3>

<p>The inefficient way is to first get the list of sellers by querying <code>seller</code> table.<br>
The<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const sellers = await db.select().from(seller);

</code></pre>

</div>



<p>And then for each seller you get the products<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const allProducts = [];
for (const s of sellers) {
  const products = await db
    .select()
    .from(product)
    .where(eq(product.createdBy, s.id));
  allProducts.push(...products);
}
</code></pre>

</div>



<p>This is inefficient way, you make a api call, then the api do the following:</p>

<ul>
<li>First it query every seller from <code>seller</code> table</li>
<li>Then it fetches products for each seller. So, if there were 100 users you will make the first(1 query) and then 100 more queries, in total 101 queries to get what you need.</li>
</ul>

<h3>
  
  
  Efficient:
</h3>

<p>The efficient version of the above is you tell the <code>db</code> <strong>hey please give me all the sellers and their products, this way you are going to <code>db</code> only once and making a single query.</strong><br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const sellersAndProducts = await db
  .select()
  .from(seller)
  .innerJoin(product, eq(seller.id, product.createdBy));
</code></pre>

</div>



<p>Here, instead of fetching products one by one for each seller, we use a single SQL join between <code>seller</code> and <code>product</code> table to get everything in one query.</p>

<h3>
  
  
  Why you should care about the N+1 query problem?
</h3>

<p>The answer always will be the performance. If you want to get best performance out of your db, you have to perform <code>db</code> queries or <code>db</code> transactions very carefully, otherwise you will end up spending database resources, performance on unnecessary queries.</p>

مشكلة الاستعلام N+1 هي مشكلة أداء كبيرة في إدارة قواعد البيانات، حيث تقوم التطبيقات بإجراء استعلام أولي لاسترجاع قائمة من العناصر، تليها N استعلامات إضافية للبيانات ذات الصلة بكل عنصر. تؤدي هذه الطريقة غير الفعالة إلى إجمالي N+1 استعلامات، مما يمكن أن يبطئ أداء التطبيق بشكل كبير. فهم هذه المشكلة أمر بالغ الأهمية للمطورين ومديري قواعد البيانات، حيث يبرز أهمية تحسين استراتيجيات الاستعلام لتعزيز الكفاءة وتجربة المستخدم.

El problema de la consulta N+1 es un problema de rendimiento significativo en la gestión de bases de datos, donde una aplicación realiza una consulta inicial para recuperar una lista de elementos, seguida de N consultas adicionales para los datos relacionados de cada elemento. Este enfoque ineficiente conduce a un total de N+1 consultas, lo que puede ralentizar considerablemente el rendimiento de la aplicación. Comprender este problema es crucial para desarrolladores y administradores de bases de datos, ya que destaca la importancia de optimizar las estrategias de consulta para mejorar la eficiencia y la experiencia del usuario.

Le problème de la requête N+1 est un problème de performance important dans la gestion des bases de données, où une application effectue une requête initiale pour récupérer une liste d'articles, suivie de N requêtes supplémentaires pour les données associées de chaque article. Cette approche inefficace entraîne un total de N+1 requêtes, ce qui peut considérablement ralentir les performances de l'application. Comprendre ce problème est crucial pour les développeurs et les administrateurs de bases de données, car il souligne l'importance d'optimiser les stratégies de requête pour améliorer l'efficacité et l'expérience utilisateur.

The N+1 query problem is a significant performance issue in database management, where an application makes one initial query to retrieve a list of items, followed by N additional queries for each item's related data. This inefficient approach leads to a total of N+1 queries, which can severely slow down application performance. Understanding this problem is crucial for developers and database administrators, as it highlights the importance of optimizing query strategies to enhance efficiency and user experience.

Building a P2P Rental Marketplace - Full-Stack Architecture with Flutter & Express.js

Building a P2P Rental Marketplace - Full-Stack Architecture with Flutter & Express.js

Was this article worth reading? Share it