<h2>
 
 
 GIMME THE MEAT
</h2>

<a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FMShel%2FsshOuroboros%2Fmain%2Fstatic%2FgameRecord.gif" 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%2Fraw.githubusercontent.com%2FMShel%2FsshOuroboros%2Fmain%2Fstatic%2FgameRecord.gif" width="560" height="420"></a>

sshOurboros -- multiplayer game where snake eats itself and grows

To play go here <code>ssh web2u.org -p6996</code>

The Rules:

<ol>
<li>The goal is to claim the most space</li>
<li>Secondary goal is to kill as many other Ourboroses as you can 
The how:</li>
<li>To claim space you need to either eat your own tail or reach tiles you've already claimed, 
tiles that are enclosed when you do so become yours!</li>
<li>To kill other snakes you hit their tails 
To watch out:</li>
<li>Other players can kill you by hitting your exposed tail</li>
<li>Other players can take your tiles.</li>
</ol>

The source: <a href="https://github.com/MShel/sshOuroboros/tree/main" rel="noopener noreferrer">https://github.com/MShel/sshOuroboros/tree/main</a>

<h2>
 
 
 Walk through on how it works and why
</h2>

When you Sign Up to the game you are presented with 254 Ansi colors<a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/ui/SetupForm.go#L117-L124" rel="noopener noreferrer">or maybe less if there are active players in the game right now</a>. 
Why 254? glad you asked! Thats what <a href="https://en.wikipedia.org/wiki/ANSI_escape_code" rel="noopener noreferrer">we have in terminal</a> - (void color + wall color).

But now that you've signed up there are players there! What the heck? all the colors were available. Well that's bots -- we try to keep all 254 colors busy at all times sshOuroboroses never sleep as <del>cool</del> kids say.

You joining the world of sshOuroboros actually already caused drama and we had to kick the <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/GameManager.go#L228-L230" rel="noopener noreferrer">bot with your color out</a>

Alright we are in and passing commands back and fro through your <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/GameManager.go#L100-L102" rel="noopener noreferrer">players channel</a> 
And that's fantastic but now we are getting to the meat of the game which is - how do we claim the territory? Well one AI would say its been solved bazzillion times you do flood fill by defining boundaries and calculating out of boundary tiles and swapping color for others....One would say that and it would not work? why-- because we have 254 bots that potentially need to scan <a href="https://github.com/MShel/sshOuroboros/blob/main/internal/game/Config.go" rel="noopener noreferrer">350_000 tiles</a> or cells on every 100ms move. That's going to be too slow.

So here comes my concurrent simplistic implementation: 
Imagine your ouroboros it can hit a tail or base from only 4 different sides and most of the time from one side it would be the area to claim and from other- the area you don't need to touch, so we need to explore only those 2(its not exactly this logic but ~90% of it). Now we throw 2 goroutines if one of them exited before finding the wall we kill another and we are done! <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/SpaceFiller.go#L53" rel="noopener noreferrer">link to code</a>

The bots, oh those pesky bots in my first implementation I had a separate ticker for the bot master and it would be responsible for moving them around, that worked great till I started testing with 250 of them now it did not work at all =D the amount of kills of players that were killed and claims for tiles by bots who were killed was astonishing so I've scrapped that and now we assign strategy directly to player and run bots strategies right in the main loop. <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/GameManager.go#L213-L218" rel="noopener noreferrer">link</a>

Talking about bots when I started I had this plan of multiple strategies and random selection of strategy based on bot situation........but ain't got time for that so I have this little Default strategy file that is Actual If conditions all around with some <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/DefaultStrategy.go#L9" rel="noopener noreferrer">ridiculous logic</a> 
Now the nice part it is an implementation of interface that is used in <code>*Player</code> which theoretically unblocks me from saying later -- yeahyeah its bad but I can throw it away and rewrite. Also that is one of the areas I see as future major change in this project(see whats next? section below)

We have this 350_000 tile thing going on with 254 players on it how the heck do do we show it on the terminal you ask? well we cant -- not on most terminals, we need viewport of limited width and height and hopefully bother bubbletea(the rendering lib) update only with small portion of it. [here] we ask for chunk of map (<a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/GameManager.go#L304-L331" rel="noopener noreferrer">https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/game/GameManager.go#L304-L331</a>) And <a href="https://github.com/MShel/sshOuroboros/blob/db5cd9fdc0d1e674d6fc56a9b3fc3ad0a863a8ef/internal/ui/GameView.go#L233-L270" rel="noopener noreferrer">here</a> we render it. 
This whole view function is kinda nasty and was a huge pain to write but it works most time anyway. 

So here you go that's the key parts of the game, there are a lot more areas to cover but those are the most interesting ones IMHO(ask me about anything else and answer I will)

<h2>
 
 
 Whats In the Future
</h2>

Well here I need your dear Reader advice, I've got following ideas that I'm planning to think about next, but if something completely different comes to your mind(hopefully about the game) do let me know. Anyway, help me pick!

<ul>
<li>New game play as Bots strategy (add lua VM and allow strategy to be small executable lua script to be submitted by user)</li>
<li>Variable ouroboros speed press <code>x</code> to go real Fast type of situation</li>
<li>More games -- we have one with 256 players we can easily provision many with 256, though my server will have to be improved(its 10$ on linode and its meh)</li>
</ul>

<h2>
 
 
 Why did I write it?
</h2>

Well Ai and <code>terminal.shop</code>... Ai is to blame for it, I <del>was</del> am slightly depressed by on slot of claims that AI will take over everything I like and make me write documentation and that is my 2'd least favorite thing in this career(1't are useless meetings that only end up in more useless meetings).

So hearing all that and watching Prime on youtube talking about how awesome ssh coffee stuff is I was like "lets try to write an ssh game cause its fun and be open minded about AI".

Now the good -- Ai wont take my job for now and that's not only because I tend to be very openly opinionated about things but also because:

<ol>
<li>Flood fill -- it could not figure it out, it did provide classical algorithms that did not scale but it was of no help at the end</li>
<li>Concurrency issues -- It can not figure those out like at all, the game had a lot of those in my original iterations, ai could not suggest any sort of fix that would address performance bottlenecks</li>
</ol>

Also good'ish? -- Ai was good at helping me with code I did not want to write like view files, I just dont care about them enough 
Or the HighScore sqlite crud thingy, that also was pretty much all AI

Now the bad -- I can write 250 more articles about how AI cant really replace anyone but it wont help the narrative been pushed by those weird AI CEO's :-(

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

El nuevo juego multijugador sshOuroboros, desarrollado en GoLang, está causando sensación en la comunidad de jugadores. Combina la diversión del juego multijugador con el giro único de la integración SSH, ofreciendo a los jugadores una experiencia fresca y atractiva. Este enfoque innovador no solo mejora la jugabilidad, sino que también muestra la versatilidad de GoLang en el desarrollo de juegos. A medida que los videojuegos continúan evolucionando, sshOuroboros se destaca como una adición notable, atrayendo tanto a jugadores casuales como a entusiastas de la tecnología.

Le nouveau jeu multijoueur sshOuroboros, développé en GoLang, fait sensation dans la communauté des joueurs. Il combine le plaisir du jeu multijoueur avec la touche unique de l'intégration SSH, offrant aux joueurs une expérience fraîche et engageante. Cette approche innovante améliore non seulement le gameplay, mais met également en valeur la polyvalence de GoLang dans le développement de jeux. Alors que le jeu continue d'évoluer, sshOuroboros se distingue comme un ajout remarquable, attirant à la fois les joueurs occasionnels et les passionnés de technologie.

The new multiplayer game sshOuroboros, developed in GoLang, is making waves in the gaming community. It combines the fun of multiplayer gameplay with the unique twist of SSH integration, offering players a fresh and engaging experience. This innovative approach not only enhances gameplay but also showcases the versatility of GoLang in game development. As gaming continues to evolve, sshOuroboros stands out as a noteworthy addition, appealing to both casual gamers and tech enthusiasts alike.

sshOuroboros multiplayer game in goLang with ssh, and the story.

&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.

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

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

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.
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>.

في مناقشة حديثة، شارك نيكولاس فيليبس من بلومبرغ إنتليجنس رؤى حول نتائج تقريرهم 'دراسة تداول الأسهم المؤسسية الأوروبية 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

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.

<h2>
 
 
 YouTube Video
</h2>

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

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


<h2>
 
 
 Requirements
</h2>

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.

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.

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

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.

To begin with, you'll need to open the terminal application. To this, use spotlight by pressing command and space together. Then, type terminal 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.

Your terminal may look different to mine but don't worry.

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

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.

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

The second method is to run the following command in the terminal: 


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

</div>



The latest version is at the top, which again is 26.1.

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

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: 


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

</div>



It will now download the installer. This will take some time.

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

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

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

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

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

Mine is connected and it's called usbstick.

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

Once again, remember to backup anything that is on the USB stick that you want to keep.

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


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

</div>



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.

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

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

The progress will be shown on the screen.

Once it has completed, the terminal will look like the below image.

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

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

Thanks for reading and have a nice day!

يوفر هذا المقال دليلًا بسيطًا حول كيفية إنشاء محرك 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

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.

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

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

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

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.

Discovery 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.

Drafting 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.

Review 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.

Publish 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.

Observe 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.

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

We don’t have to guess how parsers and browsers treat core elements—there’s public guidance. For example, the robots meta tag 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.

Beyond directives, content earns trust through coherence:

<ul>
<li>
Titles that promise exactly what the body delivers. If the headline says “How We Cut p95 by 3×,” your method and measurement must be visible above the fold.</li>
<li>
Stable URLs. Breaking links is reputational debt. Treat slugs like API versions; change only with migration plans.</li>
<li>
Readable structure. Short paragraphs, code blocks that run, diagrams with alt text, and captions that say what the reader should notice.</li>
<li>
Transparent authorship. 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>

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

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

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

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

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

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

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.

<h2>
 
 
 Distribution Without the Guilt
</h2>

You don’t need tricks to reach the right readers—you need consistency and fit. 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.

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.

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

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.

<h2>
 
 
 The Payoff
</h2>

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.

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

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

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

If you've ever seen "TBA/TBA" 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 real bug with same-name passengers.

In this post, we'll unpack:

<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>
A critical bug I found: Same-name passengers causing seat swaps</li>
</ul>




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

Group fares are special airline rates for 10+ passengers traveling together on the same flight and date.

Common use cases:

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

Unlike individual bookings, group fares are:

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




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

Here's how it works from an OTA or travel agent's perspective:

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




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

TBA = To Be Advised

When creating a group booking, actual passenger details may not be known yet.

Example in GDS (Amadeus/Sabre):

Each entry reserves a seat while allowing the agent to:

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

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

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

The Big Three:

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




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

Most airlines require final passenger names no later than 12 hours before departure.

What happens at finalization:

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

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




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

Key technical points:

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

For platforms like Yatra or MakeMyTrip: 


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

</div>



Backend requirements:

<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. CRITICAL BUG I DISCOVERED: Same-Name Collision
</h2>

<h3>
 
 
 The Problem
</h3>

When booking through Yatra's group fare system, I found:

If two passengers have the same name:

<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>// Booking for two people with same name
passengers: [
 { firstName: "Amit", lastName: "Kumar", seat: "12A" },
 { firstName: "Amit", lastName: "Kumar", seat: "12B" }
]

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

</div>



<h3>
 
 
 Why This Happens
</h3>

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

Recommended fixes for OTAs:

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

IATA's NDC (New Distribution Capability) is modernizing group fares:

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

Though many airlines still support TBA for backward compatibility.




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




<h2>
 
 
 💬 Discussion
</h2>

For developers building travel systems:

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

Drop your experiences in the comments! 👇




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




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! ✈️




Tags: #traveltech #backend #systemdesign #api #devstory

يتناول المقال عالم حجوزات المجموعات في شركات الطيران، مع التركيز بشكل خاص على التسمية '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> 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. <a href="https://www.techspot.com/news/110174-nearly-2026-most-people-use-123456-password.html">Read Entire Article</a>

مع اقتراب عام 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

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

Kerminal es un nuevo emulador de terminal gratuito y de código abierto, diseñado para desarrolladores que necesitan una herramienta moderna y segura para gestionar conexiones SSH y despliegues. Con características como la sincronización entre dispositivos y cifrado de nivel empresarial, Kerminal aborda las frustraciones comunes que enfrentan los desarrolladores con aplicaciones de terminal anticuadas. Esta innovación no solo mejora la productividad, sino que también prioriza la seguridad, convirtiéndose en un avance significativo en el ámbito de las herramientas de desarrollo.

Kerminal est un nouvel émulateur de terminal open-source et gratuit, conçu pour les développeurs qui ont besoin d'un outil moderne et sécurisé pour gérer les connexions SSH et les déploiements. Avec des fonctionnalités telles que la synchronisation multi-appareils et le cryptage de niveau entreprise, Kerminal répond aux frustrations courantes des développeurs face aux applications de terminal obsolètes. Cette innovation améliore non seulement la productivité, mais privilégie également la sécurité, ce qui en fait une avancée significative dans le domaine des outils de développement.

Kerminal is a new, free, open-source terminal emulator designed for developers who need a modern and secure tool for managing SSH connections and deployments. With features like multi-device synchronization and enterprise-grade encryption, Kerminal addresses the common frustrations developers face with outdated terminal applications. This innovation not only enhances productivity but also prioritizes security, making it a significant advancement in the realm of development tools.

How I Built Kerminal: A Free, Open-Source Terminal & SSH Manager with Multi-Device Sync

The Repository Pattern, documented in Martin Fowler's "Patterns of Enterprise Application Architecture," separates data access logic from business logic. This article demonstrates its implementation in Golang through a real-world e-commerce example.

The Problem 
Without proper separation, your code mixes business logic with database operations: 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>func ProcessOrder(orderID string) error {
 db.Query("SELECT * FROM orders WHERE id = ?", orderID)
 // Business rules buried in database code
}
</code></pre>

</div>



Problems:

<ul>
<li>Tight coupling to database</li>
<li>Hard to test</li>
<li>Code duplication</li>
<li>Can't switch databases easily</li>
</ul>

The Solution: Repository Pattern

The pattern provides an abstraction layer between business logic and data access, treating data like an in-memory collection.

Benefits:

<ul>
<li>Testability (easy to mock)</li>
<li>Flexibility (switch databases)</li>
<li>Clean separation of concerns</li>
<li>Centralized data access</li>
</ul>

Implementation

Domain Model 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// domain/product.go
package domain

import "time"

type Product struct {
 ID string
 Name string
 Price float64
 Stock int
 Category string
 CreatedAt time.Time
 UpdatedAt time.Time
}

func (p *Product) Validate() error {
 if p.Name == "" {
 return errors.New("name required")
 }
 if p.Price &lt; 0 {
 return errors.New("invalid price")
 }
 return nil
}
</code></pre>

</div>



Repository Interface 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// repository/interface.go
package repository

import (
 "context"
 "github.com/yourusername/ecommerce-repository/domain"
)

type ProductRepository interface {
 Create(ctx context.Context, product *domain.Product) error
 FindByID(ctx context.Context, id string) (*domain.Product, error)
 FindAll(ctx context.Context) ([]*domain.Product, error)
 FindByCategory(ctx context.Context, category string) ([]*domain.Product, error)
 Update(ctx context.Context, product *domain.Product) error
 Delete(ctx context.Context, id string) error
}
</code></pre>

</div>



PostgreSQL Implementation 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// repository/postgres.go
package repository

import (
 "context"
 "database/sql"
 "github.com/yourusername/ecommerce-repository/domain"
)

type PostgresProductRepository struct {
 db *sql.DB
}

func NewPostgresProductRepository(db *sql.DB) *PostgresProductRepository {
 return &amp;PostgresProductRepository{db: db}
}

func (r *PostgresProductRepository) Create(ctx context.Context, product *domain.Product) error {
 query := `
 INSERT INTO products (id, name, price, stock, category, created_at, updated_at)
 VALUES ($1, $2, $3, $4, $5, $6, $7)
 `
 _, err := r.db.ExecContext(ctx, query,
 product.ID, product.Name, product.Price, 
 product.Stock, product.Category, time.Now(), time.Now())
 return err
}

func (r *PostgresProductRepository) FindByID(ctx context.Context, id string) (*domain.Product, error) {
 query := `SELECT id, name, price, stock, category, created_at, updated_at 
 FROM products WHERE id = $1`

 product := &amp;domain.Product{}
 err := r.db.QueryRowContext(ctx, query, id).Scan(
 &amp;product.ID, &amp;product.Name, &amp;product.Price,
 &amp;product.Stock, &amp;product.Category, &amp;product.CreatedAt, &amp;product.UpdatedAt)

 if err == sql.ErrNoRows {
 return nil, fmt.Errorf("product not found")
 }
 return product, err
}

func (r *PostgresProductRepository) FindByCategory(ctx context.Context, category string) ([]*domain.Product, error) {
 query := `SELECT id, name, price, stock, category, created_at, updated_at 
 FROM products WHERE category = $1`

 rows, err := r.db.QueryContext(ctx, query, category)
 if err != nil {
 return nil, err
 }
 defer rows.Close()

 var products []*domain.Product
 for rows.Next() {
 p := &amp;domain.Product{}
 err := rows.Scan(&amp;p.ID, &amp;p.Name, &amp;p.Price, &amp;p.Stock, 
 &amp;p.Category, &amp;p.CreatedAt, &amp;p.UpdatedAt)
 if err != nil {
 return nil, err
 }
 products = append(products, p)
 }
 return products, nil
}

func (r *PostgresProductRepository) Update(ctx context.Context, product *domain.Product) error {
 query := `UPDATE products SET name=$1, price=$2, stock=$3, 
 category=$4, updated_at=$5 WHERE id=$6`
 _, err := r.db.ExecContext(ctx, query, product.Name, product.Price,
 product.Stock, product.Category, time.Now(), product.ID)
 return err
}

func (r *PostgresProductRepository) Delete(ctx context.Context, id string) error {
 query := `DELETE FROM products WHERE id = $1`
 _, err := r.db.ExecContext(ctx, query, id)
 return err
}
</code></pre>

</div>



In-Memory Implementation (Testing) 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// repository/memory.go
package repository

import (
 "context"
 "sync"
 "github.com/yourusername/ecommerce-repository/domain"
)

type InMemoryProductRepository struct {
 mu sync.RWMutex
 products map[string]*domain.Product
}

func NewInMemoryProductRepository() *InMemoryProductRepository {
 return &amp;InMemoryProductRepository{
 products: make(map[string]*domain.Product),
 }
}

func (r *InMemoryProductRepository) Create(ctx context.Context, product *domain.Product) error {
 r.mu.Lock()
 defer r.mu.Unlock()
 r.products[product.ID] = product
 return nil
}

func (r *InMemoryProductRepository) FindByID(ctx context.Context, id string) (*domain.Product, error) {
 r.mu.RLock()
 defer r.mu.RUnlock()

 product, exists := r.products[id]
 if !exists {
 return nil, fmt.Errorf("not found")
 }
 return product, nil
}

func (r *InMemoryProductRepository) FindByCategory(ctx context.Context, category string) ([]*domain.Product, error) {
 r.mu.RLock()
 defer r.mu.RUnlock()

 var products []*domain.Product
 for _, p := range r.products {
 if p.Category == category {
 products = append(products, p)
 }
 }
 return products, nil
}
</code></pre>

</div>



Business Service 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// service/product_service.go
package service

import (
 "context"
 "github.com/yourusername/ecommerce-repository/domain"
 "github.com/yourusername/ecommerce-repository/repository"
)

type ProductService struct {
 repo repository.ProductRepository
}

func NewProductService(repo repository.ProductRepository) *ProductService {
 return &amp;ProductService{repo: repo}
}

func (s *ProductService) CreateProduct(ctx context.Context, product *domain.Product) error {
 if err := product.Validate(); err != nil {
 return err
 }
 return s.repo.Create(ctx, product)
}

func (s *ProductService) GetProduct(ctx context.Context, id string) (*domain.Product, error) {
 return s.repo.FindByID(ctx, id)
}

func (s *ProductService) GetProductsByCategory(ctx context.Context, category string) ([]*domain.Product, error) {
 return s.repo.FindByCategory(ctx, category)
}
</code></pre>

</div>



Main Application 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>// main.go
package main

import (
 "database/sql"
 "log"
 "net/http"
 "github.com/gorilla/mux"
 _ "github.com/lib/pq"
)

func main() {
 db, _ := sql.Open("postgres", "postgres://user:pass@localhost/ecommerce?sslmode=disable")
 defer db.Close()

 // Switch implementations easily
 repo := repository.NewPostgresProductRepository(db)
 // Or use: repo := repository.NewInMemoryProductRepository()

 service := service.NewProductService(repo)

 r := mux.NewRouter()
 r.HandleFunc("/products", createProduct(service)).Methods("POST")
 r.HandleFunc("/products/{id}", getProduct(service)).Methods("GET")
 r.HandleFunc("/products", listProducts(service)).Methods("GET")

 log.Fatal(http.ListenAndServe(":8080", r))
}
</code></pre>

</div>



Testing Example 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>func TestProductService(t *testing.T) {
 repo := repository.NewInMemoryProductRepository()
 service := service.NewProductService(repo)

 product := &amp;domain.Product{
 ID: "1", Name: "Mouse", Price: 29.99, Stock: 50, Category: "electronics"}

 err := service.CreateProduct(context.Background(), product)
 if err != nil {
 t.Fatal(err)
 }

 found, _ := service.GetProduct(context.Background(), "1")
 if found.Name != "Mouse" {
 t.Errorf("expected Mouse, got %s", found.Name)
 }
}
</code></pre>

</div>



Database Schema 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>CREATE TABLE products (
 id VARCHAR(255) PRIMARY KEY,
 name VARCHAR(255) NOT NULL,
 price DECIMAL(10, 2) NOT NULL,
 stock INTEGER NOT NULL,
 category VARCHAR(100) NOT NULL,
 created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
 updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

CREATE INDEX idx_category ON products(category);
</code></pre>

</div>



Running the Project 


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code># Setup
go mod init github.com/yourusername/ecommerce-repository
go get github.com/gorilla/mux github.com/lib/pq

# Run with PostgreSQL
DATABASE_URL="postgres://user:pass@localhost/ecommerce" go run main.go

# Run with in-memory (testing)
USE_MEMORY=true go run main.go

# Test API
curl -X POST http://localhost:8080/products \
 -d '{"id":"1","name":"Mouse","price":29.99,"stock":50,"category":"electronics"}'

curl http://localhost:8080/products/1
curl http://localhost:8080/products?category=electronics
</code></pre>

</div>



Key Advantages

<ol>
<li>Easy Testing: Swap PostgreSQL for in-memory implementation</li>
<li>Database Independence: Change databases without touching business logic</li>
<li>Clean Code: Each layer has one responsibility</li>
<li>Maintainability: All queries in one place</li>
</ol>

When to Use 
Use Repository Pattern when:

<ul>
<li>Complex business logic</li>
<li>Need to support multiple databases</li>
<li>High test coverage required</li>
<li>Large team with separate concerns</li>
</ul>

Avoid when:

<ul>
<li>Simple CRUD apps</li>
<li>Prototypes</li>
<li>Very small projects</li>
</ul>

Conclusion 
The Repository Pattern provides a clean separation between business logic and data access. This example shows how to implement it in Golang with real code that you can use in production.

References

<ul>
<li>GitHub: <a href="https://github.com/mayrafc/golang-repository-pattern.git" rel="noopener noreferrer">https://github.com/mayrafc/golang-repository-pattern.git</a>
</li>
<li>Martin Fowler's Book: "Patterns of Enterprise Application Architecture"</li>
</ul>

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

El artículo sobre el Patrón de Repositorio en Golang destaca un principio de diseño de software crucial que ayuda a los desarrolladores a separar el acceso a datos de la lógica de negocio. Utilizando un ejemplo real de comercio electrónico, ilustra cómo este patrón puede mejorar la mantenibilidad y claridad del código. Esto es importante porque adoptar tales mejores prácticas puede llevar a aplicaciones más robustas, facilitando la gestión de sistemas complejos y mejorando la calidad general del software.

L'article sur le modèle de dépôt en Golang met en avant un principe de conception logicielle crucial qui aide les développeurs à séparer l'accès aux données de la logique métier. En utilisant un exemple concret de commerce électronique, il illustre comment ce modèle peut améliorer la maintenabilité et la clarté du code. Cela est important car l'adoption de telles meilleures pratiques peut conduire à des applications plus robustes, facilitant ainsi la gestion de systèmes complexes et améliorant la qualité globale des logiciels.

The article on the Repository Pattern in Golang highlights a crucial software design principle that helps developers separate data access from business logic. By using a real-world e-commerce example, it illustrates how this pattern can enhance code maintainability and clarity. This matters because adopting such best practices can lead to more robust applications, making it easier for developers to manage complex systems and improve overall software quality.

sshOuroboros multiplayer game in goLang with ssh, and the story.

sshOuroboros multiplayer game in goLang with ssh, and the story.

Was this article worth reading? Share it