<p><a href="https://github.com/cloudstreet-dev/The-Virtues-of-Vanilla-JavaScript" rel="noopener noreferrer">https://github.com/cloudstreet-dev/The-Virtues-of-Vanilla-JavaScript</a></p>

<p>A book by Claude Code Sonnet 4.5</p>

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

El lanzamiento de 'The Virtues of Vanilla JavaScript' por Claude Code está generando entusiasmo en la comunidad de desarrolladores. Este libro enfatiza la importancia de dominar el JavaScript básico sin depender de frameworks, lo que puede llevar a mejores prácticas de codificación y a una comprensión más profunda del lenguaje. A medida que los desarrolladores buscan mejorar sus habilidades, este recurso es oportuno y relevante, fomentando un regreso a los fundamentos que pueden empoderarlos en sus proyectos.

La sortie de 'The Virtues of Vanilla JavaScript' par Claude Code suscite de l'enthousiasme dans la communauté des développeurs. Ce livre souligne l'importance de maîtriser le JavaScript de base sans dépendre des frameworks, ce qui peut conduire à de meilleures pratiques de codage et à une compréhension plus profonde du langage. Alors que les développeurs cherchent à améliorer leurs compétences, cette ressource est opportune et pertinente, encourageant un retour aux fondamentaux qui peuvent les renforcer dans leurs projets.

The release of 'The Virtues of Vanilla JavaScript' by Claude Code is generating excitement in the developer community. This book emphasizes the importance of mastering core JavaScript without relying on frameworks, which can lead to better coding practices and a deeper understanding of the language. As developers seek to enhance their skills, this resource is timely and relevant, encouraging a return to the fundamentals that can empower them in their projects.

The Virtues of Vanilla JavaScript

<p>&nbsp;As US educators embrace AI in the classroom, firms are selling software to flag mentions of self-harm, raising concerns over privacy and control.</p>

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

A medida que la tecnología de IA se vuelve más común en las aulas de EE. UU., los educadores están utilizando cada vez más chatbots para monitorear el bienestar de los estudiantes. Si bien estas herramientas pueden ayudar a identificar signos de autolesionismo, también plantean preocupaciones significativas sobre la privacidad y el alcance de la vigilancia en los entornos educativos. Este cambio hacia la vigilancia constante podría afectar la confianza y la libertad de los estudiantes, convirtiéndolo en un tema crítico para padres y educadores.

Alors que la technologie de l'IA devient de plus en plus courante dans les salles de classe aux États-Unis, les éducateurs utilisent de plus en plus des chatbots pour surveiller le bien-être des élèves. Bien que ces outils puissent aider à identifier des signes de comportements autodestructeurs, ils soulèvent également d'importantes préoccupations concernant la vie privée et l'étendue de la surveillance dans les établissements éducatifs. Ce passage vers une surveillance constante pourrait affecter la confiance et la liberté des élèves, ce qui en fait un enjeu crucial pour les parents et les éducateurs.

As AI technology becomes more prevalent in classrooms across the US, educators are increasingly using chatbots to monitor student well-being. While these tools can help identify signs of self-harm, they also raise significant concerns about privacy and the extent of surveillance in educational settings. This shift towards constant monitoring could impact students' trust and freedom, making it a critical issue for parents and educators alike.

Chatbots Are Sparking a New Era of Student Surveillance

<p><span data-teams="true">The TRADE sits down with Nicholas Phillips, market structure research analyst at Bloomberg Intelligence (BI), following the publication of BI's 'European institutional equity trading study 2025’ report, to explore Europe’s renewed trading momentum, what to look out for in 2026, and the continued developments in post-trade, dark trading caps, rising bilateral, and more.</span></p>
<p>The post <a href="https://www.thetradenews.com/fireside-friday-with-bloomberg-intelligences-nicholas-phillips/">Fireside Friday with… Bloomberg Intelligence’s Nicholas Phillips</a> appeared first on <a href="https://www.thetradenews.com">The TRADE</a>.</p>

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

En una reciente discusión, Nicholas Phillips de Bloomberg Intelligence compartió información sobre los hallazgos de su informe 'European institutional equity trading study 2025'. Destacó el resurgimiento de la actividad de trading en Europa y las tendencias que se anticipan para 2026, incluyendo avances en los procesos post-negociación y regulaciones sobre trading oscuro. Esta conversación es significativa ya que arroja luz sobre el paisaje en evolución del trading de acciones, lo cual es crucial para los inversores y participantes del mercado que buscan navegar por las complejidades del mercado europeo.

Lors d'une récente discussion, Nicholas Phillips de Bloomberg Intelligence a partagé des informations sur les résultats de leur rapport 'European institutional equity trading study 2025'. Il a souligné la résurgence de l'activité de trading en Europe et les tendances à anticiper en 2026, y compris les avancées dans les processus post-négociation et les réglementations sur le trading obscur. Cette conversation est importante car elle éclaire l'évolution du paysage du trading d'actions, ce qui est crucial pour les investisseurs et les acteurs du marché cherchant à naviguer dans les complexités du marché européen.

In a recent discussion, Nicholas Phillips from Bloomberg Intelligence shared insights on the findings of their 'European institutional equity trading study 2025' report. He highlighted the resurgence of trading activity in Europe and what trends to anticipate in 2026, including advancements in post-trade processes and dark trading regulations. This conversation is significant as it sheds light on the evolving landscape of equity trading, which is crucial for investors and market participants looking to navigate the complexities of the European market.

Fireside Friday with… Bloomberg Intelligence’s Nicholas Phillips

<p>Hi there. In this article, I'll be going over the process of how you can create a macOS 26 Tahoe USB bootable installation drive.</p>

<h2>
  
  
  YouTube Video
</h2>

<p>If you would prefer to see a video of this article, there is a video version available on YouTube below:</p>

<p><iframe width="710" height="399" src="https://www.youtube.com/embed/BBiWy6FrtM4">
</iframe>
</p>

<h2>
  
  
  Requirements
</h2>

<p>To do this, you'll need macOS 10.15 or above (I used macOS 15) and a 32GB USB stick or higher to create the installation drive.</p>

<p><strong>Before you start, make sure to backup any data that is on the USB stick as the USB stick will be erased as part of the process.</strong></p>

<h2>
  
  
  Downloading the macOS 26 Tahoe Installer
</h2>

<p>Unlike previous versions of macOS, macOS 26 Tahoe is not available in the App store. It can only be downloaded via the command line for the full version that is used to create an installation disk.</p>

<p>To begin with, you'll need to open the terminal application. To this, use spotlight by pressing command and space together. Then, type <em>terminal</em> and hover over to the terminal application. It looks like a black box with a white arrow. Left click on it to open the application.</p>

<p>Your terminal may look different to mine but don't worry.</p>

<p>You can also get to it by opening a Finder window, going to Applications, then Utilities and then double clicking on Terminal.</p>

<p>First, you need to determine what the latest version of Tahoe is. There are two ways to do this. First, you can use this <a href="">webpage</a>, which shows it is being 26.1 at the time of writing this article.</p>

<p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7p6roxf0ufy5frukae2c.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7p6roxf0ufy5frukae2c.png" alt="Image 1" width="800" height="354"></a></p>

<p>The second method is to run the following command in the terminal:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight shell"><code>softwareupdate <span class="nt">--list-full-installers</span>
</code></pre>

</div>



<p>The latest version is at the top, which again is 26.1.</p>

<p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcogm6l42kciu08k750nl.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcogm6l42kciu08k750nl.png" alt="Image 2" width="800" height="461"></a></p>

<p>The next step is to download the installer for macOS 26.1. To do that, run the following command. If a newer version is available, replace <code>26.1</code> with that version, if you want to:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight shell"><code>softwareupdate <span class="nt">--fetch-full-installer</span> <span class="nt">--full-installer-version</span> 26.1
</code></pre>

</div>



<p>It will now download the installer. This will take some time.</p>

<p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffqmovocs202pw2bwdjib.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffqmovocs202pw2bwdjib.png" alt="Image 3" width="800" height="462"></a></p>

<h2>
  
  
  Creating the USB Installation Drive
</h2>

<p>Now that the installer has finished downloading, you should be able to see it in the Applications folder in Finder.</p>

<p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9gkffyhw77ufowhtpd54.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9gkffyhw77ufowhtpd54.png" alt="Image 4" width="800" height="495"></a></p>

<p>The next step is to make the USB installation drive. First, make sure your USB stick is connected to your Mac.</p>

<p>Mine is connected and it's called <em>usbstick</em>.</p>

<p>I would recommend renaming your USB stick to a name that has no spaces to make it easier.</p>

<p><strong>Once again, remember to backup anything that is on the USB stick that you want to keep.</strong></p>

<p>When you are ready, run the following command in the terminal. Replace <code>usbstick</code> with the name of your USB stick.<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight shell"><code><span class="nb">sudo</span> /Applications/Install<span class="se">\ </span>macOS<span class="se">\ </span>Tahoe.app/Contents/Resources/createinstallmedia <span class="nt">--volume</span> /Volumes/usbstick
</code></pre>

</div>



<p>Press enter and then type in your password, or the username and password for an administrator account if your account doesn't have that level of permission.</p>

<p>When it asks you to confirm the USB stick can be erased, press <code>y</code> and then enter.</p>

<p>Your USB stick will disappear from Finder and then come back with the name of <em>Install macOS Tahoe</em>. This is normal.</p>

<p>The progress will be shown on the screen.</p>

<p>Once it has completed, the terminal will look like the below image.</p>

<p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ff69snvwmd4xsra2ugsos.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ff69snvwmd4xsra2ugsos.png" alt="Image 5" width="800" height="462"></a></p>

<p>You can now use that to boot from and install, or reinstall macOS 26 Tahoe on a <a href="">supported Mac</a>.</p>

<p>Thanks for reading and have a nice day!</p>

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

Este artículo ofrece una guía sencilla sobre cómo crear una unidad USB de instalación de macOS 26 Tahoe, facilitando la instalación o actualización del sistema operativo. Con instrucciones claras y un tutorial en video disponible en YouTube, se adapta tanto a los aprendices visuales como a aquellos que prefieren la orientación escrita. Esto es especialmente importante, ya que tener una unidad de arranque puede simplificar la solución de problemas y la recuperación del sistema, asegurando que los usuarios puedan mantener sus dispositivos de manera efectiva.

Cet article propose un guide simple pour créer un lecteur USB d'installation bootable macOS 26 Tahoe, facilitant ainsi l'installation ou la mise à niveau du système d'exploitation. Avec des instructions claires et un tutoriel vidéo disponible sur YouTube, il s'adresse à la fois aux apprenants visuels et à ceux qui préfèrent les conseils écrits. Cela est particulièrement important car avoir un lecteur bootable peut simplifier le dépannage et la récupération du système, garantissant que les utilisateurs peuvent maintenir efficacement leurs appareils.

This article provides a straightforward guide on creating a macOS 26 Tahoe USB bootable installation drive, making it easier for users to install or upgrade their operating system. With clear instructions and a video tutorial available on YouTube, it caters to both visual learners and those who prefer written guidance. This is particularly important as having a bootable drive can simplify troubleshooting and system recovery, ensuring that users can maintain their devices effectively.

How To Create A macOS 26 Tahoe USB Installation Drive

<p>You don’t need to shout to be heard; you need to be clear and verifiable. Teams that treat publishing like a product discipline consistently outperform those chasing hacks. That’s why many engineering leaders pair solid writing with measurable distribution and—only where it helps—specialist partners offering <a href="https://techwavespr.com/services/" rel="noopener noreferrer">digital marketing services</a> to keep the pipeline of attention honest and repeatable. This piece distills a pragmatic framework for content that survives scrutiny and compounds over time.</p>

<h2>
  
  
  The Operating Model: From “Post and Pray” to Repeatable Pipelines
</h2>

<p>Great articles don’t appear out of nowhere—they move through a pipeline with explicit gates. Think of it as CI/CD for ideas:</p>

<ul>
<li><strong>Discovery → Drafting → Review → Publish → Observe.</strong></li>
</ul>

<p>At each stage, you’re validating something different: whether the topic matters, whether the draft is clear, whether claims are supported, whether the page renders fast and clean, and how readers actually engage. This isn’t bureaucracy; it’s how you protect your future self from firefighting.</p>

<p><strong>Discovery</strong> is about narrowing to problems your readers already feel. The fastest test is to write the problem in one sentence and ask a skeptical colleague if it describes a real moment they’ve lived. If they hesitate, refine until they can retell it in their words.</p>

<p><strong>Drafting</strong> prioritizes specificity. Replace abstractions with measurements (“p95 latency dropped from 480 ms to 160 ms”) and name the trade-offs. Engineers recognize truth in constraints. Avoid performative flourishes; ship facts.</p>

<p><strong>Review</strong> is a multidisciplinary check: technical accuracy, legal and privacy considerations, and plain-language clarity. The review should be adversarial but bounded—identify a small set of non-negotiables (e.g., security statements must be vetted; benchmarks must be reproducible). Everything else is style, not a blocker.</p>

<p><strong>Publish</strong> with a minimum of ceremony but maximum reliability. If your site breaks on mobile, the message never lands. If you embed media, ensure fallbacks. If you annotate with structured data, verify it. This sounds obvious until you audit a few dozen pages and find preventable failures.</p>

<p><strong>Observe</strong> like an engineer: define a hypothesis before release (“We expect 40%+ of readers to expand the code sample and average time-on-page of 2:30”), then log events and read them. If the hypothesis fails, write a brief note and iterate. That humility builds more credibility than any slogan.</p>

<h2>
  
  
  Signals That Help Machines and Humans Understand Your Page
</h2>

<p>We don’t have to guess how parsers and browsers treat core elements—there’s public guidance. For example, the <strong>robots meta tag</strong> is precisely documented by <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name#robots" rel="noopener noreferrer">MDN Web Docs</a>. Misusing it can quietly hide your excellent work. Likewise, clear directives for crawlers are outlined in Google’s official documentation on <a href="https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag" rel="noopener noreferrer">robots meta directives</a>. You don’t need to become a specialist to benefit: read the short sections relevant to your use case, pick defaults that match your intent (e.g., indexable article pages, non-index utility endpoints), and avoid contradictory signals.</p>

<p>Beyond directives, content earns trust through <strong>coherence</strong>:</p>

<ul>
<li>
<strong>Titles that promise exactly what the body delivers.</strong> If the headline says “How We Cut p95 by 3×,” your method and measurement must be visible above the fold.</li>
<li>
<strong>Stable URLs.</strong> Breaking links is reputational debt. Treat slugs like API versions; change only with migration plans.</li>
<li>
<strong>Readable structure.</strong> Short paragraphs, code blocks that run, diagrams with alt text, and captions that say what the reader should notice.</li>
<li>
<strong>Transparent authorship.</strong> A byline with real identity and a sentence on why this person is qualified. Anonymous thought leadership rarely persuades engineers.</li>
</ul>

<h2>
  
  
  The Only Checklist You Actually Need
</h2>

<p>Use this once per article. If you can’t check a box truthfully, fix the cause instead of gaming the symptom.</p>

<ul>
<li>
<strong>One-sentence reader problem is clear</strong> (share with a skeptic; they should nod).</li>
<li>
<strong>Core claim is measurable</strong> (numbers, method, and where data lives).</li>
<li>
<strong>Page renders fast and clean</strong> (mobile first; images sized; no layout shift).</li>
<li>
<strong>Directives match intent</strong> (no accidental <code>noindex</code>; canonical is correct; no conflicting hints).</li>
<li>
<strong>Source links are authoritative</strong> (stand on primary docs or peer-reviewed material, not hearsay).</li>
<li>
<strong>Reproducibility where relevant</strong> (runnable code, version pins, or data snapshot).</li>
<li>
<strong>Post-publish hypothesis defined</strong> (what success looks like and what you’ll do if it doesn’t happen).</li>
</ul>

<p>Keep this list visible to your team. It’s short on purpose; bloat turns checklists into theater.</p>

<h2>
  
  
  Writing That Respects the Reader’s Time
</h2>

<p>Engineers are allergic to hand-waving. To earn trust, write like you debug:</p>

<ol>
<li>
<strong>State the claim.</strong> Put the outcome up front. Don’t make people dig.</li>
<li>
<strong>Show the path.</strong> Provide the minimal context to reproduce. If there are three plausible methods, say why you chose one.</li>
<li>
<strong>Expose trade-offs.</strong> Every decision has a downside—latency for compute, privacy for convenience, simplicity for flexibility. Calling that out makes the win believable.</li>
<li>
<strong>Acknowledge prior art.</strong> Name the people and projects you built upon. It’s generous and prevents reinventing the wheel.</li>
<li>
<strong>Invite falsification.</strong> Offer a way to challenge your result—dataset link, script, or a note on environments where your approach might fail.</li>
</ol>

<p>This style doesn’t just “sound technical.” It protects your team when later decisions reference your document. You’ll thank yourself when a VP says, “Why did we pick this?” and you can point to a paragraph that still holds up.</p>

<h2>
  
  
  Distribution Without the Guilt
</h2>

<p>You don’t need tricks to reach the right readers—you need <strong>consistency</strong> and <strong>fit</strong>. Publish where developers already hang out (like Dev.to and your project’s repo), cross-post summaries to communities that value your topic, and keep the voice consistent. Avoid anchor spam and cartoonish calls to action. Invite contact for real reasons: bug reports, benchmarks on different hardware, adoption stories, or counterexamples.</p>

<p>When you link to resources, choose anchors that fit naturally into the sentence. The goal is to be helpful first. Over-optimized phrasing reads strangely to humans and invites the wrong kind of attention from machines. Think of links as citations, not bait.</p>

<h2>
  
  
  Governance: Tiny Rituals That Prevent Big Headaches
</h2>

<p>A lightweight content guild—two to four people who care—can review each draft for clarity, risk, and usefulness. Rotate the “final approver” so the process never bottlenecks. Archive decisions in a living doc: when a topic performed poorly, say so and explain what you learned; when an article exceeded expectations, annotate why (timing, community tie-in, or a strong demo). Over a quarter, this becomes an internal playbook your future teammates will treat as gold.</p>

<h2>
  
  
  The Payoff
</h2>

<p>When you adopt an engineering posture toward content, the benefits accumulate: fewer hotfixes after publish, fewer awkward retractions, more inbound from readers who actually implemented your work, and a library you can confidently resurface months later. Most importantly, you build an audience that trusts you—because your writing respects their time and intelligence.</p>

<p><strong>Bottom line:</strong> publish less often, but make each piece unarguably useful. Measure outcomes, admit misses, and iterate in public. That honesty travels further than any tagline.</p>

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

En el mundo de la creación de contenido, la claridad y la verificabilidad son clave para ganar confianza. Este artículo enfatiza que los equipos que tratan la publicación como una disciplina de producto tienden a superar a aquellos que dependen de trucos rápidos. Al combinar una escritura sólida con una distribución medible y colaborar con socios especializados cuando es beneficioso, los líderes de ingeniería pueden crear un canal de atención confiable. Este enfoque no solo mejora la calidad del contenido, sino que también asegura su efectividad para llegar a la audiencia, convirtiéndolo en una estrategia crucial para el éxito en el panorama digital actual.

Dans le monde de la création de contenu, la clarté et la vérifiabilité sont essentielles pour gagner la confiance. Cet article souligne que les équipes qui considèrent la publication comme une discipline de produit ont tendance à surpasser celles qui s'appuient sur des astuces rapides. En combinant une rédaction solide avec une distribution mesurable et en collaborant avec des partenaires spécialisés lorsque cela est bénéfique, les leaders en ingénierie peuvent créer un pipeline d'attention fiable. Cette approche améliore non seulement la qualité du contenu, mais garantit également son efficacité pour atteindre le public, ce qui en fait une stratégie cruciale pour réussir dans le paysage numérique d'aujourd'hui.

In the world of content creation, clarity and verifiability are key to earning trust. This article emphasizes that teams treating publishing as a product discipline tend to outperform those relying on quick hacks. By combining solid writing with measurable distribution and collaborating with specialist partners when beneficial, engineering leaders can create a reliable pipeline of attention. This approach not only enhances the quality of content but also ensures its effectiveness in reaching the audience, making it a crucial strategy for success in today's digital landscape.

Build Content Like an Engineer: Systems, Signals, and Checks That Earn Trust

<p>If you've ever seen <strong>"TBA/TBA"</strong> as a passenger name in a flight booking, it's not a glitch—it's a feature. After booking a cheap group fare on Yatra.com, I discovered the hidden world of airline group bookings, and uncovered a <strong>real bug</strong> with same-name passengers.</p>

<p>In this post, we'll unpack:</p>

<ul>
<li>How group fare booking systems work</li>
<li>Why "TBA" exists in airline PNRs</li>
<li>What developers building travel systems should know</li>
<li>
<strong>A critical bug I found</strong>: Same-name passengers causing seat swaps</li>
</ul>




<h2>
  
  
  ✈️ 1. What Are Group Fares?
</h2>

<p>Group fares are special airline rates for <strong>10+ passengers</strong> traveling together on the same flight and date.</p>

<p><strong>Common use cases:</strong></p>

<ul>
<li>🏢 Corporate trips</li>
<li>💒 Weddings and family gatherings</li>
<li>🕌 Pilgrimage or religious tours</li>
<li>🏀 School or sports teams</li>
</ul>

<p>Unlike individual bookings, group fares are:</p>

<ul>
<li>
<strong>Negotiated</strong> directly with airlines or via GDS</li>
<li>More <strong>flexible</strong> with payment schedules</li>
<li>Allow <strong>placeholder names</strong> initially</li>
</ul>




<h2>
  
  
  2. Business Logic: The Group Booking Flow
</h2>

<p>Here's how it works from an OTA or travel agent's perspective:</p>

<div class="table-wrapper-paragraph"><table>
<thead>
<tr>
<th>Step</th>
<th>Process</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>1️⃣</td>
<td><strong>Group Quote Request</strong></td>
<td>Agency requests fare for route, date, and passenger count</td>
</tr>
<tr>
<td>2️⃣</td>
<td><strong>PNR Creation (TBA stage)</strong></td>
<td>Airline/GDS creates group PNR with placeholders like <code>TBA/TBA</code>
</td>
</tr>
<tr>
<td>3️⃣</td>
<td><strong>Deposit &amp; Hold</strong></td>
<td>Group pays deposit to hold seats</td>
</tr>
<tr>
<td>4️⃣</td>
<td><strong>Name Finalization</strong></td>
<td>12–72 hours before flight, replace "TBA" with real names</td>
</tr>
<tr>
<td>5️⃣</td>
<td><strong>Ticketing</strong></td>
<td>Once names finalized, tickets are issued</td>
</tr>
</tbody>
</table></div>




<h2>
  
  
  📋 3. What Does "TBA" Actually Mean?
</h2>

<p><strong>TBA = To Be Advised</strong></p>

<p>When creating a group booking, actual passenger details may not be known yet.</p>

<p><strong>Example in GDS (Amadeus/Sabre):</strong></p>

<p>Each entry reserves a seat while allowing the agent to:</p>

<ul>
<li>
<strong>Hold inventory</strong> without final names</li>
<li>
<strong>Track blocked seats</strong> in airline systems</li>
<li>
<strong>Display flight details</strong> before passenger confirmation</li>
</ul>

<h4>
  
  
  How GDS Systems Power This Magic
</h4>

<p>Behind the scenes, OTAs don't talk directly to each airline. They use <strong>GDS (Global Distribution System)</strong> — think of it as the "API gateway" of the travel industry.</p>

<p><strong>The Big Three:</strong></p>

<ul>
<li>
<strong>Amadeus</strong> (European dominance)</li>
<li>
<strong>Sabre</strong> (Strong in Americas)</li>
<li>
<strong>Travelport</strong> (Galileo/Worldspan/Apollo)</li>
</ul>




<h2>
  
  
  ⏰ 4. The 12-Hour Rule
</h2>

<p>Most airlines require final passenger names <strong>no later than 12 hours before departure</strong>.</p>

<p><strong>What happens at finalization:</strong></p>

<ul>
<li>✅ All "TBA" placeholders updated with real names</li>
<li>⚠️ Unnamed passengers may auto-cancel</li>
<li>🎫 Group PNR transitions to ticketed state</li>
</ul>

<p>This is why Yatra/MMT show "flight details visible before 12 hours" — the system holds the group block, but names are pending.</p>




<h2>
  
  
  5. System Architecture Flow
</h2>

<p><strong>Key technical points:</strong></p>

<ul>
<li>Placeholders stored in PNR until replaced</li>
<li>Airlines track via group booking IDs (not individual tickets)</li>
<li>Background jobs handle PNR sync and updates</li>
</ul>




<h2>
  
  
  💻 6. How OTAs Handle This (Developer View)
</h2>

<p>For platforms like Yatra or MakeMyTrip:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight javascript"><code><span class="c1">// Simplified model</span>
<span class="kd">const</span> <span class="nx">groupBooking</span> <span class="o">=</span> <span class="p">{</span>
  <span class="na">pnr</span><span class="p">:</span> <span class="dl">"</span><span class="s2">ABC123</span><span class="dl">"</span><span class="p">,</span>
  <span class="na">status</span><span class="p">:</span> <span class="dl">"</span><span class="s2">TBA_PENDING</span><span class="dl">"</span><span class="p">,</span>
  <span class="na">passengers</span><span class="p">:</span> <span class="p">[</span>
    <span class="p">{</span> <span class="na">firstName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">TBA</span><span class="dl">"</span><span class="p">,</span> <span class="na">lastName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">TBA</span><span class="dl">"</span><span class="p">,</span> <span class="na">title</span><span class="p">:</span> <span class="dl">"</span><span class="s2">MR</span><span class="dl">"</span> <span class="p">},</span>
    <span class="p">{</span> <span class="na">firstName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">TBA</span><span class="dl">"</span><span class="p">,</span> <span class="na">lastName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">TBA</span><span class="dl">"</span><span class="p">,</span> <span class="na">title</span><span class="p">:</span> <span class="dl">"</span><span class="s2">MS</span><span class="dl">"</span> <span class="p">}</span>
  <span class="p">],</span>
  <span class="na">finalizationDeadline</span><span class="p">:</span> <span class="dl">"</span><span class="s2">2025-11-08T10:00:00Z</span><span class="dl">"</span><span class="p">,</span>
  <span class="na">flightDetails</span><span class="p">:</span> <span class="p">{</span> <span class="na">visible</span><span class="p">:</span> <span class="kc">false</span> <span class="p">}</span> <span class="c1">// visible after name update</span>
<span class="p">};</span>
</code></pre>

</div>



<p><strong>Backend requirements:</strong></p>

<ol>
<li>Handle placeholder data models</li>
<li>Schedule PNR refresh/update jobs</li>
<li>Implement deadline alerts</li>
<li>Validate against duplicate names (see bug below!)</li>
</ol>




<h2>
  
  
  7. <strong>CRITICAL BUG I DISCOVERED: Same-Name Collision</strong>
</h2>

<h3>
  
  
  The Problem
</h3>

<p>When booking through Yatra's group fare system, I found:</p>

<p><strong>If two passengers have the same name:</strong></p>

<ul>
<li>❌ During web check-in, the system will display both passengers names when the PNR and last name are entered together.</li>
<li>❌ Boarding passes get mixed up</li>
<li>❌ Airport staff can't distinguish passengers</li>
<li>❌ Potential security and check-in issues</li>
</ul>

<h3>
  
  
  Example Scenario
</h3>



<div class="highlight js-code-highlight">
<pre class="highlight javascript"><code><span class="c1">// Booking for two people with same name</span>
<span class="nx">passengers</span><span class="p">:</span> <span class="p">[</span>
  <span class="p">{</span> <span class="na">firstName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">Amit</span><span class="dl">"</span><span class="p">,</span> <span class="na">lastName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">Kumar</span><span class="dl">"</span><span class="p">,</span> <span class="na">seat</span><span class="p">:</span> <span class="dl">"</span><span class="s2">12A</span><span class="dl">"</span> <span class="p">},</span>
  <span class="p">{</span> <span class="na">firstName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">Amit</span><span class="dl">"</span><span class="p">,</span> <span class="na">lastName</span><span class="p">:</span> <span class="dl">"</span><span class="s2">Kumar</span><span class="dl">"</span><span class="p">,</span> <span class="na">seat</span><span class="p">:</span> <span class="dl">"</span><span class="s2">12B</span><span class="dl">"</span> <span class="p">}</span>
<span class="p">]</span>

<span class="c1">// What happens in airline system:</span>
<span class="c1">// PNR shows: KUMAR/AMIT MR + KUMAR/AMIT MR</span>
<span class="c1">// Boarding pass generates wrong seat for one passenger</span>
</code></pre>

</div>



<h3>
  
  
  Why This Happens
</h3>

<ol>
<li>
<strong>GDS Name Formatting</strong>: Airlines use <code>PNR and LASTNAME</code> combination</li>
<li>
<strong>Duplicate Detection</strong>: System may treat as duplicate entry</li>
<li>
<strong>Seat Assignment Logic</strong>: Uses last name as primary key</li>
<li>
<strong>Group PNR Merge</strong>: Multiple "AMIT KUMAR" entries cause confusion</li>
</ol>

<p><strong>Recommended fixes for OTAs:</strong></p>

<ul>
<li>🔍 Pre-booking validation for duplicate last names</li>
<li>📝 Force middle name or mobile number for duplicates</li>
</ul>




<h2>
  
  
  🔮 8. Future: NDC and Modern APIs
</h2>

<p><strong>IATA's NDC (New Distribution Capability)</strong> is modernizing group fares:</p>

<ul>
<li>⚡ Real-time quotes and seat holds</li>
<li>🔄 Easier passenger data updates via REST APIs</li>
<li>📉 Reduced reliance on "TBA" placeholders</li>
<li>🤝 Direct airline-to-OTA connections</li>
</ul>

<p>Though many airlines still support TBA for backward compatibility.</p>




<h2>
  
  
  9. Key Takeaways
</h2>

<div class="table-wrapper-paragraph"><table>
<thead>
<tr>
<th>Point</th>
<th>Reality Check</th>
</tr>
</thead>
<tbody>
<tr>
<td>✅ <strong>"TBA" is a feature, not a bug</strong>
</td>
<td>Intentional placeholder system for group inventory management</td>
</tr>
<tr>
<td>⏰ <strong>The 12-hour rule has a twist</strong>
</td>
<td>Names often start reflecting from <strong>midnight</strong> (not exactly 12 hours), which can frustrate travelers expecting earlier updates</td>
</tr>
<tr>
<td>💰 <strong>How OTAs really make money</strong>
</td>
<td>Indian OTAs like Yatra/MMT book group fares and mark them up—this is on <strong>top of</strong> convenience charges. That "cheap fare" might just be a group booking arbitrage</td>
</tr>
<tr>
<td>🚨 <strong>Same-name = system chaos</strong>
</td>
<td>Multiple passengers with identical last names create PNR conflicts, seat swaps, and boarding issues</td>
</tr>
<tr>
<td>🎭 <strong>The agent model</strong>
</td>
<td>OTAs aren't always direct airline partners—many operate as <strong>super-agents</strong> booking group blocks and reselling individually</td>
</tr>
</tbody>
</table></div>




<h2>
  
  
  💬 Discussion
</h2>

<p><strong>For developers building travel systems:</strong></p>

<ol>
<li>How does your system handle group booking placeholders?</li>
<li>Ever encountered the same-name bug I found?</li>
</ol>

<p>Drop your experiences in the comments! 👇</p>




<h2>
  
  
  🔗 Useful Resources
</h2>

<ul>
<li><a href="https://www.iata.org/en/programs/airline-distribution/retailing/ndc/" rel="noopener noreferrer">IATA NDC Program</a></li>
<li><a href="https://developers.amadeus.com/" rel="noopener noreferrer">Amadeus API Documentation</a></li>
<li><a href="https://developer.sabre.com/" rel="noopener noreferrer">Sabre Dev Studio</a></li>
</ul>




<p><em>This post is based on real-world experience booking through Yatra.com. If you found this helpful, consider sharing it with your travel-tech friends! ✈️</em></p>




<p><strong>Tags:</strong> #traveltech #backend #systemdesign #api #devstory</p>

يتناول المقال عالم حجوزات المجموعات في شركات الطيران، مع التركيز بشكل خاص على التسمية 'TBA/TBA' التي تظهر في حجوزات الرحلات. هذه ليست خللًا، بل ميزة مقصودة تنشأ من تعقيدات حجز أسعار المجموعات. يشارك الكاتب تجارب شخصية من تجربة حديثة مع Yatra.com، موضحًا كيفية عمل هذه الأنظمة للحجز وتأثيراتها على المطورين في صناعة السفر. يمكن أن يساعد فهم ذلك كل من المسافرين والمهنيين في التكنولوجيا على التنقل بشكل أكثر فعالية في تفاصيل السفر الجماعي.

El artículo se adentra en el intrigante mundo de las reservas de grupo de aerolíneas, centrándose específicamente en la designación 'TBA/TBA' que se ve en las reservas de vuelos. Esto no es un error, sino una característica deliberada que surge de las complejidades de reservar tarifas grupales. El autor comparte experiencias personales de una reciente experiencia con Yatra.com, arrojando luz sobre cómo funcionan estos sistemas de reserva y las implicaciones para los desarrolladores en la industria de viajes. Comprender esto puede ayudar tanto a los viajeros como a los profesionales de la tecnología a navegar más eficazmente por las sutilezas de los viajes en grupo.

L'article explore le monde fascinant des réservations de groupe dans les compagnies aériennes, en se concentrant spécifiquement sur la désignation 'TBA/TBA' que l'on voit dans les réservations de vol. Ce n'est pas un bug, mais une fonctionnalité délibérée qui découle des complexités de la réservation de tarifs de groupe. L'auteur partage des expériences personnelles d'une récente expérience avec Yatra.com, éclairant le fonctionnement de ces systèmes de réservation et les implications pour les développeurs de l'industrie du voyage. Comprendre cela peut aider à la fois les voyageurs et les professionnels de la technologie à naviguer plus efficacement dans les nuances des voyages en groupe.

The article delves into the intriguing world of airline group bookings, specifically focusing on the 'TBA/TBA' designation seen in flight reservations. This isn't a glitch but a deliberate feature that arises from the complexities of booking group fares. The author shares personal insights from a recent experience with Yatra.com, shedding light on how these booking systems function and the implications for developers in the travel industry. Understanding this can help both travelers and tech professionals navigate the nuances of group travel more effectively.

How Airline Group Fares Really Work: The Business & Tech Behind 'TBA' Passenger Names

<a href="https://www.techspot.com/news/110174-nearly-2026-most-people-use-123456-password.html" target="_blank"><img src="https://www.techspot.com/images2/news/ts3_thumbs/2025/11/2025-11-07-ts3_thumbs-819.jpg" width="800" height="560" style="padding: 15px 0" title="It's nearly 2026 and most people still use '123456' as a password" /></a><br />The latest shame-inducing most-common-passwords report comes from tech research and review site Comparitech. Using information leaked on data breach forums in 2025, its researchers aggregated more than 2 billion real account passwords, creating a list of the 100 most-used.<br /><br /><a href="https://www.techspot.com/news/110174-nearly-2026-most-people-use-123456-password.html">Read Entire Article</a><br /><br />

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

A medida que nos acercamos a 2026, un nuevo informe de Comparitech revela que muchas personas todavía dependen de contraseñas débiles como '123456'. Esto es preocupante porque resalta un problema persistente en la ciberseguridad, donde los individuos no adoptan prácticas de contraseñas más fuertes a pesar de las advertencias sobre las violaciones de datos. El uso continuo de contraseñas tan fáciles de adivinar pone en riesgo la información personal y sensible, lo que hace crucial que los usuarios prioricen mejores medidas de seguridad.

À l'approche de 2026, un nouveau rapport de Comparitech révèle que de nombreuses personnes continuent de s'appuyer sur des mots de passe faibles comme '123456'. Cela est préoccupant car cela met en lumière un problème persistant en matière de cybersécurité, où les individus ne parviennent pas à adopter des pratiques de mots de passe plus solides malgré les avertissements continus concernant les violations de données. L'utilisation continue de mots de passe aussi facilement devinables met en danger les informations personnelles et sensibles, rendant crucial pour les utilisateurs de donner la priorité à de meilleures mesures de sécurité.

As we approach 2026, a new report from Comparitech reveals that many people still rely on weak passwords like '123456'. This is concerning because it highlights a persistent issue in cybersecurity, where individuals fail to adopt stronger password practices despite ongoing warnings about data breaches. The continued use of such easily guessable passwords puts personal and sensitive information at risk, making it crucial for users to prioritize better security measures.

It's nearly 2026 and most people still use '123456' as a password

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

En la última entrega de la serie sobre desarrollo multi-agente, el artículo profundiza en las complejidades de la programación con Claude Code y los desafíos que se enfrentan en este enfoque innovador. Destaca la importancia de la supervisión humana en la dirección de los agentes de IA, especialmente al navegar por las complejidades de las pruebas basadas en propiedades con Hypothesis. Esta discusión es crucial, ya que arroja luz sobre el equilibrio entre la autonomía y la orientación en el desarrollo de la IA, lo cual es esencial para maximizar el potencial de estas tecnologías.

Dans le dernier volet de la série sur le développement multi-agents, l'article explore les complexités de la programmation avec Claude Code et les défis rencontrés dans cette approche innovante. Il souligne l'importance de la supervision humaine dans la direction des agents IA, en particulier lors de la navigation dans les subtilités des tests basés sur les propriétés avec Hypothesis. Cette discussion est cruciale car elle met en lumière l'équilibre entre autonomie et orientation dans le développement de l'IA, essentiel pour maximiser le potentiel de ces technologies.

In the latest installment of the Multi-Agent Development Series, the article delves into the complexities of coding with Claude Code and the challenges faced in this innovative approach. It highlights the importance of human oversight in directing AI agents, especially when navigating the intricacies of property-based testing with Hypothesis. This discussion is crucial as it sheds light on the balance between autonomy and guidance in AI development, which is essential for maximizing the potential of these technologies.

Why your genius agent is also brain dead: The tale of 7000 scenarios and the knowledge we almost lost

<h2>
  
  
  I got locked out of the GST portal for the third time because my password "didn't meet requirements."
</h2>

<p>No explanation. Just "Invalid password."<br>
After wasting 30 minutes trying different passwords, I decided to build a tool that would tell me exactly what was wrong with my password for different government portals.<br>
Result: PasswordChecker.in - Built in 2 weekends with vanilla JavaScript. No React. No Vue. No frameworks.<br>
Here's how I did it.</p>


<h2>
  
  
  Why No Frameworks?
</h2>

<p>Speed. I wanted the tool to be:</p>

<ul>
<li>Fast to load (&lt; 50KB total)</li>
<li>Fast to build (2 weekends)</li>
<li>Fast to run (real-time password checking)</li>
</ul>

<p>Adding React would add 130KB+ before I wrote a single line of code. For a single-page tool, that's overkill.</p>

<p>The Tech Stack</p>

<blockquote>
<ul>
<li>Frontend: Vanilla JavaScript + Tailwind CSS</li>
<li>Styling: Tailwind CDN (for rapid prototyping)</li>
<li>API: Have I Been Pwned (k-Anonymity model)</li>
<li>Hosting: Vercel</li>
<li>Source Control: GitHub</li>
</ul>
</blockquote>

<p>Total bundle size: ~48KB (including Tailwind)<br>
Feature #1: Real-Time Password Strength Checker<br>
The Requirements<br>
Different Indian government portals have different password requirements:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const portalRequirements = {
  uidai: {
    minLength: 8,
    requiresUppercase: true,
    requiresLowercase: true,
    requiresNumber: true,
    requiresSpecial: true,
  },
  gstn: {
    minLength: 10,
    requiresUppercase: true,
    requiresLowercase: true,
    requiresNumber: true,
    requiresSpecial: true,
    maxLength: 15,
  },
  incomeTax: {
    minLength: 12,
    requiresUppercase: true,
    requiresLowercase: true,
    requiresNumber: true,
    requiresSpecial: true,
    maxLength: 14,
  },
};
</code></pre>

</div>



<h2>
  
  
  The Core Logic
</h2>



<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>function checkPasswordStrength(password) {
  const checks = {
    length: password.length &gt;= 8,
    uppercase: /[A-Z]/.test(password),
    lowercase: /[a-z]/.test(password),
    number: /[0-9]/.test(password),
    special: /[!@#$%^&amp;*()_+\-=\[\]{};':"\\|,.&lt;&gt;\/?]/.test(password),
  };

  // Calculate score (0-100)
  let score = 0;
  if (checks.length) score += 20;
  if (checks.uppercase) score += 20;
  if (checks.lowercase) score += 20;
  if (checks.number) score += 20;
  if (checks.special) score += 20;

  // Additional points for length
  if (password.length &gt;= 12) score += 10;
  if (password.length &gt;= 16) score += 10;

  return {
    score: Math.min(score, 100),
    checks,
    strength: getStrengthLabel(score),
  };
}

function getStrengthLabel(score) {
  if (score &gt;= 80) return 'Very Strong';
  if (score &gt;= 60) return 'Strong';
  if (score &gt;= 40) return 'Moderate';
  if (score &gt;= 20) return 'Weak';
  return 'Very Weak';
}
</code></pre>

</div>



<h2>
  
  
  Real-Time Updates
</h2>



<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const passwordInput = document.getElementById('password');
const strengthMeter = document.getElementById('strength-meter');

passwordInput.addEventListener('input', (e) =&gt; {
  const password = e.target.value;
  const result = checkPasswordStrength(password);

  // Update UI
  updateStrengthMeter(result);
  updateChecklist(result.checks);
  checkPortalCompliance(password);
});
</code></pre>

</div>



<h2>
  
  
  Feature #2: Password Generator
</h2>

<p>Users needed passwords that were:</p>

<p>Strong (meets requirements)<br>
Memorable (not random gibberish)<br>
Portal-specific (works for UIDAI, GST, etc.)</p>

<p>The Memorable Password Algorithm<br>
Instead of generating <code>xK9!mP2@</code>, generate <code>Quick7Tiger$42</code><br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>function generateReadablePassword(requirements) {
  const adjectives = ['Quick', 'Brave', 'Smart', 'Cool', 'Swift'];
  const nouns = ['Tiger', 'Eagle', 'Wolf', 'Lion', 'Hawk'];
  const specials = ['@', '#', '$', '%', '&amp;', '*'];

  const adjective = adjectives[Math.floor(Math.random() * adjectives.length)];
  const number1 = Math.floor(Math.random() * 9) + 1;
  const noun = nouns[Math.floor(Math.random() * nouns.length)];
  const special = specials[Math.floor(Math.random() * specials.length)];
  const number2 = Math.floor(Math.random() * 90) + 10;

  let password = `${adjective}${number1}${noun}${special}${number2}`;

  // Adjust for portal requirements
  if (requirements.minLength &gt; password.length) {
    password += Math.random().toString(36).substring(2, requirements.minLength - password.length + 2);
  }

  return password;
}
</code></pre>

</div>



<p>Output: Passwords like <code>Smart5Wolf@73</code> - easy to remember, meets all requirements.</p>

<h2>
  
  
  Feature #3: Data Breach Checker
</h2>

<p>This was the most complex feature. I needed to check if a password appeared in data breaches without sending the password to any server.<br>
The k-Anonymity Model<br>
Have I Been Pwned (HIBP) uses k-Anonymity:</p>

<ul>
<li>Hash the password (SHA-1)</li>
<li>Send only the first 5 characters of the hash</li>
<li>Server returns all breached passwords matching those 5 chars</li>
<li>Client checks if full hash is in the list
</li>
</ul>
<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>async function checkPasswordBreach(password) {
  // Hash password
  const hash = await sha1(password);
  const prefix = hash.substring(0, 5);
  const suffix = hash.substring(5).toUpperCase();

  // Query HIBP API (only send first 5 chars)
  const response = await fetch(`https://api.pwnedpasswords.com/range/${prefix}`);
  const data = await response.text();

  // Check if full hash is in response
  const hashes = data.split('\n');
  for (let line of hashes) {
    const [hashSuffix, count] = line.split(':');
    if (hashSuffix === suffix) {
      return {
        found: true,
        count: parseInt(count),
      };
    }
  }

  return { found: false };
}

// SHA-1 implementation
async function sha1(str) {
  const buffer = new TextEncoder().encode(str);
  const hash = await crypto.subtle.digest('SHA-1', buffer);
  const hashArray = Array.from(new Uint8Array(hash));
  return hashArray.map(b =&gt; b.toString(16).padStart(2, '0')).join('');
}
</code></pre>

</div>


<p>Privacy: Your password never leaves your browser. Only the first 5 characters of its hash are sent.</p>
<h2>
  
  
  Feature #4: Multi-Portal Compatibility Test
</h2>

<p>Test one password against 10 portals simultaneously.<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>function testPortalCompatibility(password) {
  const portals = [
    { name: 'UIDAI', requirements: portalRequirements.uidai },
    { name: 'GSTN', requirements: portalRequirements.gstn },
    { name: 'Income Tax', requirements: portalRequirements.incomeTax },
    // ... more portals
  ];

  return portals.map(portal =&gt; ({
    name: portal.name,
    compatible: checkRequirements(password, portal.requirements),
    issues: getIssues(password, portal.requirements),
  }));
}

function checkRequirements(password, requirements) {
  if (password.length &lt; requirements.minLength) return false;
  if (requirements.maxLength &amp;&amp; password.length &gt; requirements.maxLength) return false;
  if (requirements.requiresUppercase &amp;&amp; !/[A-Z]/.test(password)) return false;
  if (requirements.requiresLowercase &amp;&amp; !/[a-z]/.test(password)) return false;
  if (requirements.requiresNumber &amp;&amp; !/[0-9]/.test(password)) return false;
  if (requirements.requiresSpecial &amp;&amp; !/[!@#$%^&amp;*]/.test(password)) return false;

  return true;
}
</code></pre>

</div>



<h2>
  
  
  Deployment
</h2>

<p>Local Development:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code># No build step!
python -m http.server 8000
# Visit localhost:8000
</code></pre>

</div>



<p>Production:<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>git push origin main
# Vercel auto-deploys
</code></pre>

</div>



<p>No webpack. No babel. No build process.</p>

<h2>
  
  
  Performance Optimizations
</h2>

<ol>
<li>Debounced Input
Don't check password on every keystroke:
</li>
</ol>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>function debounce(func, wait) {
  let timeout;
  return function executedFunction(...args) {
    clearTimeout(timeout);
    timeout = setTimeout(() =&gt; func.apply(this, args), wait);
  };
}

const debouncedCheck = debounce((password) =&gt; {
  checkPasswordStrength(password);
}, 300);

passwordInput.addEventListener('input', (e) =&gt; {
  debouncedCheck(e.target.value);
});
</code></pre>

</div>



<ol>
<li>Lazy Load Breach Check
Only check breaches when user clicks "Check for Breaches":
</li>
</ol>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// Don't auto-check (expensive API call)
breachCheckButton.addEventListener('click', async () =&gt; {
  showLoader();
  const result = await checkPasswordBreach(password);
  hideLoader();
  displayResult(result);
});
</code></pre>

</div>



<ol>
<li>Cache API Responses
</li>
</ol>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>const breachCache = new Map();

async function checkPasswordBreach(password) {
  const hash = await sha1(password);
  const prefix = hash.substring(0, 5);

  // Check cache first
  if (breachCache.has(prefix)) {
    return checkHash(breachCache.get(prefix), hash);
  }

  // Fetch and cache
  const response = await fetch(`https://api.pwnedpasswords.com/range/${prefix}`);
  const data = await response.text();
  breachCache.set(prefix, data);

  return checkHash(data, hash);
}
</code></pre>

</div>



<h2>
  
  
  Lessons Learned
</h2>

<h3>
  
  
  1. Vanilla JS is Fast Enough
</h3>

<p>For most tools, you don't need a framework. Vanilla JS is:</p>

<ul>
<li>Faster to load</li>
<li>Easier to debug</li>
<li>Fewer dependencies</li>
<li>More portable</li>
</ul>

<h3>
  
  
  2. Real-Time Feedback is Critical
</h3>

<p>Users type fast. Your UI must keep up. Debouncing is your friend.</p>

<h3>
  
  
  3. Privacy Matters
</h3>

<p>For a password tool, <strong>client-side only</strong> was non-negotiable. No backend. No database. No tracking.</p>

<p>Users can inspect the source and verify nothing is sent to any server (except the HIBP API with anonymized data).</p>

<h3>
  
  
  4. Government Standards are Inconsistent
</h3>

<p>Every portal has different requirements. No standardization. This makes users' lives harder—and creates opportunities for tools like mine.</p>

<h2>
  
  
  What's Next
</h2>

<p><strong>Planned Features:</strong></p>

<ul>
<li>Browser extension (auto-fill government portals)</li>
<li>Bulk password checking (CSV upload)</li>
<li>API for developers</li>
<li>Dark mode</li>
</ul>

<p><strong>Tech Debt:</strong></p>

<ul>
<li>Add proper testing (currently manually tested)</li>
<li>Consider Web Components for reusability</li>
<li>Add service worker for offline support</li>
</ul>

<h2>
  
  
  Try It Yourself
</h2>

<p><strong>Live:</strong> <a href="https://www.passwordchecker.in" rel="noopener noreferrer">passwordchecker.in</a><br><br>
<strong>Source:</strong> (Will open-source if there's interest—comment below!)</p>

<h2>
  
  
  Conclusion
</h2>

<p>You don't need React to build useful tools. Sometimes vanilla JavaScript is the right choice.</p>

<p><strong>Key Takeaways:</strong></p>

<ul>
<li>Keep it simple</li>
<li>Client-side for privacy</li>
<li>Real-time feedback</li>
<li>Focus on UX</li>
</ul>

<p>Built in 2 weekends. 500+ users in the first week. Zero frameworks.</p>




<p><strong>Questions? Ask in the comments!</strong></p>

بعد مواجهة عمليات قفل متكررة من بوابة GST بسبب مشكلات في كلمة المرور، قرر مطور أن يتخذ الأمور بيده وأنشأ PasswordChecker.in باستخدام JavaScript العادي. تساعد هذه الأداة المستخدمين على تحديد ما يجعل كلمات مرورهم غير صالحة لمختلف البوابات الحكومية، مما يسهل عملية تسجيل الدخول ويقلل من الإحباط. إنه مثال رائع على كيفية أن التحديات الشخصية يمكن أن تؤدي إلى حلول مبتكرة تفيد الآخرين.

Después de enfrentar bloqueos repetidos en el portal GST debido a problemas con su contraseña, un desarrollador decidió tomar el asunto en sus propias manos y creó PasswordChecker.in utilizando JavaScript puro. Esta herramienta ayuda a los usuarios a identificar qué hace que sus contraseñas sean inválidas para varios portales gubernamentales, agilizando el proceso de inicio de sesión y reduciendo la frustración. Es un gran ejemplo de cómo los desafíos personales pueden llevar a soluciones innovadoras que benefician a otros.

Après avoir été bloqué à plusieurs reprises sur le portail GST à cause de problèmes de mot de passe, un développeur a décidé de créer PasswordChecker.in en utilisant du JavaScript pur. Cet outil aide les utilisateurs à identifier ce qui rend leurs mots de passe invalides pour divers portails gouvernementaux, simplifiant ainsi le processus de connexion et réduisant la frustration. C'est un excellent exemple de la façon dont des défis personnels peuvent conduire à des solutions innovantes qui profitent aux autres.

After facing repeated lockouts from the GST portal due to password issues, a developer took matters into their own hands and created PasswordChecker.in using vanilla JavaScript. This tool helps users identify what makes their passwords invalid for various government portals, streamlining the login process and reducing frustration. It's a great example of how personal challenges can lead to innovative solutions that benefit others.

The Virtues of Vanilla JavaScript

The Virtues of Vanilla JavaScript

Was this article worth reading? Share it