<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bayjy on Medium]]></title>
        <description><![CDATA[Stories by Bayjy on Medium]]></description>
        <link>https://medium.com/@bayjysh?source=rss-bca3e3b0cadc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hOLf5aQJfe3ylfvcw9FceQ@2x.jpeg</url>
            <title>Stories by Bayjy on Medium</title>
            <link>https://medium.com/@bayjysh?source=rss-bca3e3b0cadc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:26:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bayjysh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How Operating Systems and Networks Shape User Experience]]></title>
            <link>https://bayjysh.medium.com/how-operating-systems-and-networks-shape-user-experience-83e2498e6a92?source=rss-bca3e3b0cadc------2</link>
            <guid isPermaLink="false">https://medium.com/p/83e2498e6a92</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[operating-systems]]></category>
            <category><![CDATA[network]]></category>
            <dc:creator><![CDATA[Bayjy]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 12:46:27 GMT</pubDate>
            <atom:updated>2026-11-18T13:45:07.068Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever clicked a button and waited longer than expected for something to happen? Or experienced a video call where the other person’s words and movements did not match? These moments may seem ordinary, but they reveal something important about how technology works.<br>This article explores the connection between Computer Science and Human-Computer Interaction (HCI), focusing on how operating systems, computer networks, and processing speed shape our everyday digital experiences. It looks at concepts such as CPU scheduling, network latency, real-time processing, and interface feedback. The main idea is simple: a digital product should not only work correctly; it should also respond at the right time and in a way that makes sense to the person using it.</p><p>Think about the last time you used an application that took forever to load. Maybe you clicked a button several times because nothing seemed to happen, or waited for a page to respond while wondering whether your internet connection was the problem. It is a small moment, but it can completely change how we feel about a digital product.<br>This is where Computer Science and Human-Computer Interaction meet. We often think of user experience in terms of colours, layouts, typography, and navigation. However, there is another side of the experience that users may not even notice: what happens behind the screen.<br>Every time we click, scroll, type, or upload something, different parts of a computer system start working together. The operating system manages resources, the processor executes instructions, and networks transfer information when an application communicates with a server. All these processes influence how quickly the system responds.<br>As someone interested in both programming and interface design, I find this connection particularly interesting. A well-designed interface can attract attention, but the technology behind it determines whether the interaction actually feels smooth. This article explores how operating systems and networks influence that experience.</p><p><strong>1. Understanding Response Time and Latency</strong><br>Let’s start with a simple question: what actually happens between clicking a button and seeing the result?<br>In Computer Science, latency generally refers to the time delay between an action and its result, or between sending and receiving information. In interactive applications, it is especially important because users expect the system to react when they do something.<br>For example, when we send a message, open a webpage, or move an object on the screen, the result does not appear by magic. Several operations take place in the background.<br>Some common sources of delay include:<br> • Processing delay: The time the processor needs to handle a request.<br> • Operating system delay: The time involved in scheduling processes, managing resources, and handling events.<br> • Network latency: The time required for information to travel between a device and a server.<br> • Rendering delay: The time needed to prepare and display changes on the screen.<br>Each delay may be very small, but together they can make an application feel either responsive or frustrating.<br>One interesting reference point comes from Jakob Nielsen, a well-known researcher in usability. In his work on response times, he explains that responses within 0.1 seconds usually feel immediate. Around one second generally allows users to maintain their flow of thought, while longer delays can interrupt their attention.</p><p><strong>2. The Role of Operating Systems in Interactive Performance</strong><br>We usually notice an operating system when something goes wrong: an application freezes, a computer becomes slow, or several programs start competing for resources. But its role in creating a smooth experience is much bigger than that.<br>One of the main responsibilities of an operating system is CPU scheduling. Since several programs can run at the same time, the operating system must decide which process gets access to the processor and when.<br>Imagine joining an online meeting while downloading a large file and editing a document. All these activities require system resources. The operating system has to manage them so that one task does not unnecessarily interrupt another.<br>If an interactive application does not receive enough processing time, its response may become delayed. A video can freeze, an animation can become choppy, or an interface may stop reacting for a moment. From a technical perspective, this involves resource management. From the user’s perspective, it simply feels like a bad experience.</p><p><strong>3. Real-Time Processing and Human Interaction</strong><br>Another concept that connects operating systems with HCI is real-time processing.<br>In Computer Science, a real-time system is not simply a system that works very fast. It is a system where the timing of the result matters. In other words, producing the correct result is not enough; it must also be delivered within a required time limit. In some systems, a result that arrives too late can be considered a failure [4].<br>This becomes especially important in areas such as medical monitoring, industrial control, navigation, and multimedia applications.<br>Consider an online game. When a player presses a key, they expect the character to move almost immediately. If the response comes too late, controlling the character becomes difficult. The same principle applies to video calls: when audio and video are delayed, even a normal conversation can feel unnatural.<br>There is also an important distinction here. Not every interactive application is a strict real-time system. A medical monitoring system may have critical timing requirements, while a file-sharing application can usually tolerate a longer delay. The required response time depends on what the system is designed to do.<br>For developers, understanding these differences is essential. It helps them choose suitable processing methods and system architectures. For designers, it explains why certain interactions feel smooth while others feel disconnected.</p><p>After looking at operating systems, networks, and interface design together, one thing becomes clear: the quality of a digital experience depends on much more than what appears on the screen.<br>CPU scheduling influences how applications receive processing time. Network latency affects how quickly information moves between devices and servers. Real-time processing helps systems meet important timing requirements, while interface feedback makes system behaviour easier to understand.<br>What makes this topic interesting is that these technical processes and human experiences are closely connected. A delay that looks insignificant in a performance report may feel much more noticeable to someone trying to complete an important task.<br>For computer scientists, understanding these connections helps create software that is efficient and reliable. For interface designers, it provides a better understanding of the technical conditions behind the interactions they design.<br>I believe this is one of the most interesting parts of modern technology: the best digital experiences happen when the system works well behind the screen and the user barely has to think about it. A successful interaction is not only about getting the right result. It is also about getting that result at the right moment.</p><p><strong>References</strong><br><em> 1. Nielsen, J. (1993). Response Times: The 3 Important Limits. Nielsen Norman Group. </em><a href="https://www.nngroup.com/articles/response-times-3-important-limits/"><em>https://www.nngroup.com/articles/response-times-3-important-limits/</em></a><em><br> 2. Wong, A. Y., &amp; Seltzer, M. (2000). Operating system support for multi-user, remote, graphical interaction. Proceedings of the 2000 USENIX Annual Technical Conference. </em><a href="https://www.usenix.org/conference/2000-usenix-annual-technical-conference/operating-system-support-multi-user-remote"><em>https://www.usenix.org/conference/2000-usenix-annual-technical-conference/operating-system-support-multi-user-remote</em></a><em><br> 3. Caldwell, B. S., &amp; Wang, E. (2009). Delays and user performance in human-computer-network interaction tasks. Human Factors, 51(6), 813–830. </em><a href="https://doi.org/10.1177/0018720809359349"><em>https://doi.org/10.1177/0018720809359349</em></a><em><br> 4. IEEE Technology Navigator. Real-Time Systems. </em><a href="https://technav.ieee.org/area/real-time-systems/"><em>https://technav.ieee.org/area/real-time-systems/</em></a><em><br> 5. Shneiderman, B., Plaisant, C., Cohen, M., Jacobs, S., Elmqvist, N., &amp; Diakopoulos, N. (2016). Designing the User Interface: Strategies for Effective Human-Computer Interaction (6th ed.). Pearson.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83e2498e6a92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Türkmenistanda Junior UX dizaýner bolmak]]></title>
            <link>https://bayjysh.medium.com/t%C3%BCrkmenistanda-junior-ux-diza%C3%BDner-bolmak-fadeb8463316?source=rss-bca3e3b0cadc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fadeb8463316</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Bayjy]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 14:36:38 GMT</pubDate>
            <atom:updated>2025-12-30T08:17:01.232Z</atom:updated>
            <content:encoded><![CDATA[<p>Meniň UX/UI dizaýna başlanyma ýaňy 1 ýyl boldy, ýöne muňa garamazdan indi başlajaklara kömegim deger diýip pikir etdim. Makalany öz tejribämde öwrenen zatlarymyň esasynda ýazýan.</p><p>UX (User Experience) we UI (User Interface) çatyşýan ýeri köp bolsa-da, asyl biri-birinden tapawutlanýan işler.</p><p>UI – islendik bir programmanyň (website, application we ş.m.) interfeýsiniň dizaýny bolup, dizaýnerlar esasan Figma-da işleýärler. UI dizaýnerlar reňkler, typography, component, autolayout, variables, tokens we ş.m. bilen işleşmeli bolýarlar.</p><p>UX – user-yň we kompaniýanyň problemalaryny döredilen UI-yň üsti bilen çözmek. Figma, Miro ýaly toollar ulanylyar.</p><p>Indi, Junior UX Dizaýner nämeleri başarmaly?</p><h3>User Research</h3><p>Bu user-yň isleglerine, zerurlyk we kynçylyk çekýän ýerlerine düşünmek we olary çözmäge çalyşmak.</p><p>Ilki bilen, oz proýektiňiz barada hemme zada gowy düşünmeli, nirelerde nämäniň ýetmeýändigine göz ýetirmeli we anyklamaly. Muňa has gowy düşünmek üçin Google Form-da opros geçirip bilersiňiz. Soraglar dogry berilse proýektiňize kömegi uly. Soňra konkurentlaryňyzyň eden işlerini görmeli, gowy we pes ýerlerine düşünmeli. Bu ýerde etmeli zat konkurentiň eden bet işini göçürmek däl-de, ondan ylham almak we has gowy dizaýn çykarmak.</p><h3>User Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NjuEQ9D7Ceyszkm5Q-a8mg@2x.jpeg" /></figure><p>Ilki başda, “Şul user flow nämä geregaý, dizaýn edip otyrkam hem flowyny edip gitsem bolýara” diýýädim. Emma, development prosessa geçilende käbir app screen-laryň ýa-da funksiýalaryň ýetmeýändigine göz ýetirdim. Ýagny, eden işimde düşnüksiz flow ýüze çykýardy. Soňra has ulurak proýekt gelende, user flow etmelidigine düşündim we Miro-da döredip başladym. Belki siz hem men ýaly boş yere wagt ýitgisi diýip pikir eden bolmagyňyz ahmal, ýöne etýän proýektiňiziň kiçi ýa-da uludygyna garamazdan user flow etmek dizaýnyň successful (üstünlikli) bolmagyna getirer. Başyndan soňuna çenli anyk we arassa user flow döretmek user-yň etjek hereketini öňünden görmegini (predict) we yalňyş düşünmegini azaltmaga kömek edýär.</p><p>Dogry user flow nädip döretmeli?</p><p>Konkurentlaryňyzyň ýa-da halaýan bir application-yň user flow-na seredip, olardan bir zatlar öwrenmek gowy başlangyç bolup biler.</p><h3>Wireframe</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77Sa5i-qxlecq5oqP0fblQ@2x.jpeg" /></figure><p>Wireframe – ediljek dizaýnyň ideýasy. Ol kontendyň dogry ýerde goýulmagyny we nähili funksiýalaryň ýerine ýetirilmelidigini görkezýär. Muny, klient, team leader ýa-da manager-a dizaýn ideýaňyz hökmünde görkezip bilersiňiz. Sebäbi ideýaňyzy görkezmek üçin high fidelity dizaýn etmek köp wagtyňyzy alar. Wireframe etmegiň netijesinde, ýalňyşlyklaryňyza düşünip, feedback alyp bilersiňiz we uýtgeşmeleri aňsat geçirip bilersiňiz.</p><h3>Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RZ-Y-sMHWLXL0QtsAqtlyA@2x.jpeg" /></figure><p>Prototyping bilen dizaýnyň flow-ny test edip bolýar. Ony etmek development cycle-da ýüze çykyp biljek köp problemalary aýyrýar. Bu klienta pikir edilen flowy görkezmäge kömek edýär. Gysgaça aýdylanda, bu etjek işiňizde kemçilikleri azaltmaga we has arassa dizaýn çykarmaga getiryär.</p><p>Meniň pikirimçe Türkmenistanda UX dizaýn indi has ösmeli we üns berilmeli ugur, soňam bu agzalan step-lardan başga-da köp etmeli işler bar, elbetde. Ýöne şulary hem başaryp bilmek uly zat. Gurak, çala-mula edilen dizaýn bilen üstünde işlenen we çyny bilen “care” edilen dizaýnyň tapawudy özüni görkezýär. Muňa düşünmek üçin hökman dizaýner bolmagam gerek däl. Asyl dizaýn söýülip edilýän iş diýilmeginem şoňa baglaýan.</p><p>Maňa bu ugurda özümi ösdürmäge kömek eden we ylham berýän käbir esbaplar:</p><ol><li>Medium</li><li>“Don’t make me think” by Steve Krug</li><li>“Steal like an artist” by Austin Kleon</li><li>“Show your work” by Austin Kleon</li><li>Documentaries: “Abstract: The art of design”, “Helvetica”, “Objectified”</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fadeb8463316" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>