<?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 Thiyagaraj T on Medium]]></title>
        <description><![CDATA[Stories by Thiyagaraj T on Medium]]></description>
        <link>https://medium.com/@thiyagaraj-t?source=rss-f192f15079a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*RCi0Tt4ya1o9Pju4YUBGdw.png</url>
            <title>Stories by Thiyagaraj T on Medium</title>
            <link>https://medium.com/@thiyagaraj-t?source=rss-f192f15079a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:58:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thiyagaraj-t/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[The 90/10 Rule: The Inconvenient Truth About Agentic AI — It’s All Plumbing, No Brain]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/hackernoon/the-90-10-rule-the-inconvenient-truth-about-agentic-ai-its-all-plumbing-no-brain-5032dac420ee?source=rss-f192f15079a6------2"><img src="https://cdn-images-1.medium.com/max/1576/1*yBmiu0R-erljXunoRkYcJw.png" width="1576"></a></p><p class="medium-feed-snippet">The real challenge in building AI agents isn&#x2019;t the AI&#x200A;&#x2014;&#x200A;it&#x2019;s everything else</p><p class="medium-feed-link"><a href="https://medium.com/hackernoon/the-90-10-rule-the-inconvenient-truth-about-agentic-ai-its-all-plumbing-no-brain-5032dac420ee?source=rss-f192f15079a6------2">Continue reading on HackerNoon.com »</a></p></div>]]></description>
            <link>https://medium.com/hackernoon/the-90-10-rule-the-inconvenient-truth-about-agentic-ai-its-all-plumbing-no-brain-5032dac420ee?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5032dac420ee</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[agents]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[agentic-workflow]]></category>
            <category><![CDATA[voice-agent]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 06:22:20 GMT</pubDate>
            <atom:updated>2025-09-10T08:03:33.784Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Slash GraphQL - Design Principles]]></title>
            <link>https://thiyagaraj-t.medium.com/slash-graphql-design-principles-489268b5cba5?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/489268b5cba5</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[dgraph]]></category>
            <category><![CDATA[graph]]></category>
            <category><![CDATA[design-principles]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 05:03:52 GMT</pubDate>
            <atom:updated>2021-03-08T05:03:52.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7UMLhX7rWEgnY7W-" /><figcaption>Photo by <a href="https://unsplash.com/@maxmckinnon?utm_source=medium&amp;utm_medium=referral">Max McKinnon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Our passion for user experience</h3><p>Creating an incredible user experience is a fundamental core value at Dgraph. This holds true for our latest product offering — Slash GraphQL. Slash GraphQL is a fully-managed GraphQL backend database service that lets you focus on building apps, not managing infrastructure. Building Slash required a design process that focused on creating the right user experience to realize this vision.</p><p>Often, we need to make design decisions across multiple teams. Design and collaboration on this scale require a well-defined design philosophy — a common design “manifesto” that reflects our <em>shared purpose</em> through a set of design principles. Our engineering and design teams use this set of design principles to guide our design decisions and to lay the foundations for our design system. With Slash GraphQL, our goal is to enable developers to build apps that leverage production-ready GraphQL and a high-performance graph backend.</p><p>In a nutshell, we have just one purpose — <em>ridiculously simplify backend development!</em></p><p>Translating this goal into reality is all that matters to everyone who is building Slash GraphQL. To achieve this purpose, we use our design principles to inspire our team to continuously improve our product. The design principles described below help us to achieve something spectacular — <em>thinking like one single mind.</em></p><h3>Our design principles -</h3><ol><li><em>Direction over choice</em>. We want developers to focus on app development and guide them on a success path, rather than asking them to spend time navigating a labyrinth of choices to configure and manage Slash. Fewer clicks for the app developer means more work for us during Slash design, but less work for you, the app developer.</li><li><em>Enable super users</em>. Our users are developers — who love keyboard shortcuts and keyboard-based navigation, and who love to become power-users with any tool they use in their workflow. Accessibility for all developers is important, as is helping you to supercharge your workflow.</li><li><em>Build purposeful interfaces</em>. We want interfaces to resemble similar patterns and speak to the actions developers want to perform. Every piece of the screen needs to match user intent and help the user to take action.</li><li><em>Build “toy-like” (indestructible) interactions</em>. Developers are smart, fast-moving, and results-oriented. We need to ensure that each interaction is reliable, make sure that error handling is robust, and make sure that error messages are clear and actionable. We imagine that we are building a toy for a baby — it should have no sharp edges or small parts that can easily break off and be swallowed.</li></ol><p>Are these principles written in stone? The answer is: No! As Slash GraphQL evolves, so our principles will evolve in response to the needs of our users. Our design principles are based on time-tested design principles, but over time we will refine the principles that guide the development of Slash.</p><h4><em>Originally published at </em><a href="https://dgraph.io/blog/post/slash-design-principles/"><em>https://dgraph.io</em></a><em>.</em></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=489268b5cba5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React useState lazy initialization in one glance]]></title>
            <link>https://thiyagaraj-t.medium.com/react-usestate-lazy-initialization-in-one-glance-478d8fa79ae1?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/478d8fa79ae1</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[hooks]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Tue, 17 Nov 2020 17:14:14 GMT</pubDate>
            <atom:updated>2020-11-17T17:14:14.012Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d2uaplN7i2FvhI2M" /><figcaption>Photo by <a href="https://unsplash.com/@polarmermaid?utm_source=medium&amp;utm_medium=referral">Anne Nygård</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>How</h4><p><strong>useState</strong> is the simplest React hook out in wild but it has a very interesting feature — lazy initialization</p><p>If you provide <strong>useState</strong> with a function, then it will be executed only on the initial render.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/802e36186f02a43a1cede777a46bad9b/href">https://medium.com/media/802e36186f02a43a1cede777a46bad9b/href</a></iframe><h4>When to use</h4><p>Any function that is computationally expensive can be initialized lazily.</p><p>Reference</p><ul><li><a href="https://reactjs.org/docs/hooks-reference.html#usestate">https://reactjs.org/docs/hooks-reference.html#usestate</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=478d8fa79ae1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Honest FOMO Developer]]></title>
            <link>https://thiyagaraj-t.medium.com/the-honest-fomo-developer-5cda59c9af12?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cda59c9af12</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Sun, 08 Nov 2020 13:37:04 GMT</pubDate>
            <atom:updated>2020-11-08T13:48:14.235Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Am I doing it right? Is my project structure correct? Am I getting too biased over a library? Is the naming convention I follow accepted universally? Importantly — Am I doing it right?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*JCcMmzpyoInE82RdtOQ5ig.gif" /><figcaption>Yes, No, Yes, Yes … Maybe</figcaption></figure><p>Does your mind ever get into this rambling of self-doubts on your choices &amp; your own framework of getting things done? I often face this, and sometimes it bothers me for days. This can be very frustrating &amp; it definitely needs to be addressed. Also if you are a javascript developer, you totally get what I am saying, right?</p><p>So I tried a bunch of options — Talking to friends working in other companies, attending conferences, attending workshops &amp; following the ‘influencers’ twitter trail. Yes, it does add some value to your general exposure but I still felt something was missing. All these insights were outward, but I was looking out for more authentic insights inward driven. That&#39;s where I hopped on to open source projects.</p><p>Open source projects are great, the bravest thing you can do as a developer is to open source your code. It&#39;s letting all guards down thus bringing in a lot of feedback from diverse schools of thought. Not all open-source projects might have the best quality. Curating good ones itself could be a challenge.</p><p>So before you think- “Ah, I don&#39;t’ have the time to work on a giant open-source project” Let me clear that out — You don’t need to know everything about a project to contribute. Usually, people suggest to start with documentation it&#39;s a great way to start open-source contributions) <strong>but </strong>there is another way you can really get started to code.</p><p>It&#39;s an unusual suspect; Test cases. Any good open-source project will have test cases. Maybe picking up a few test cases will really help you to understand the project. Test cases help you to logically explore the code &amp; also understand how to set it up, build the project, unlike the experience you get in adding documentation.</p><h4>The Final note — To put you to sleep at night, peacefully</h4><p>Have I cracked the case? No, and I do not think this pursuit ever ends. Problems evolve so will the approach in the way we weigh our options.</p><p>Building your rationale over your choices takes time. There is nothing like <em>“the right way”</em> of doing things. Each problem comes with its own demands. It&#39;s all about making <strong>trade-offs.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cda59c9af12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Firebase developers need to checkout Slash GraphQL]]></title>
            <link>https://thiyagaraj-t.medium.com/why-firebase-developers-need-to-checkout-slash-graphql-eace9175e1a3?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/eace9175e1a3</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[firestore]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Fri, 06 Nov 2020 18:58:34 GMT</pubDate>
            <atom:updated>2020-11-08T13:09:23.704Z</atom:updated>
            <content:encoded><![CDATA[<h3>Find out why every Firebase developer needs to checkout Slash GraphQL</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BUYAcOach5muCZZ7xJo5GA.png" /><figcaption>Use Slash GraphQL — just work with GraphQL, no strings attached</figcaption></figure><h3>TL;DR</h3><p>Don’t wait for the nightmare of migrating away from Firebase one day when it doesn’t scale anymore for your application. Use Slash GraphQL — just work with GraphQL, no strings attached.</p><p>Okay, before I share my view on this, here is an honest disclosure — I work as a front-end engineer at Dgraph Labs but the view expressed in this article is totally personal and based on my own experience of building apps.</p><h4>The Firebase Spark</h4><p>No doubt that Firebase is great! I was an early adopter and have seen firebase evolving from a real-time database as a service to the popular app development ecosystem it is now.</p><p>Firebase is popular among developers because it’s very easy to onboard and integrate your app with its services. The developer doesn’t need to worry about setting up infrastructure &amp; can iterate on the app faster than ever before. That’s what makes firebase so attractive amongst the app developer community.</p><h4>GraphQL Explosion</h4><p>GraphQL came into the picture recently &amp; there is a lot of excitement in this space. I have written <a href="https://codeburst.io/the-case-for-graphql-16090de30972">a case for GraphQL </a>before as well. For the first time, a language is being conceived for APIs. That lead inception to a bunch of powerful tools &amp; libraries for client applications that can talk GraphQL. <a href="https://www.apollographql.com/docs/react/get-started/">Apolo client </a>is definitely one of the most favorite open-source GraphQL libraries out there with more than 15k stars on GitHub.</p><p>But one thing which all frontend developers get frustrated with is— <em>Resolvers</em></p><p>That&#39;s a big bummer. Nobody wants to write more code just to enable GraphQL.</p><h4>Taking the leap forward</h4><p>The good news is Slash GraphQL was launched recently this year. In a nutshell, it gives you a production-ready GraphQL hosted backend. All you need is to define a GraphQL schema and you get a /graphql endpoint like magic with no resolvers!</p><p>Now that’s super powerful, with a GraphQL backend you can not only query &amp; mutate data but with GraphQL subscriptions, you can get real-time updates. Pretty much all the things that Firestore does.</p><p>So what&#39;s the deal-breaker?</p><p>Let&#39;s says you prototyped an app using Firebase. In the first 3 months of the application launch, the app got 5k users! Everything is great!</p><p>Until after 6 months, the traffic spiked by 500%. The load gets high and Firebase didn’t scale as you expected. You eventually decide to set up your own infrastructure &amp; plan to architect services to solve your problem. But wait, what happens to all the nice firebase code that went into the app?</p><p>This is a nightmare for any engineer. Migrating away from a third party library is not the most exciting part of the job.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FdlMIwDQAxXn1K%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FdlMIwDQAxXn1K%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExa2o4cWNma2pkbHdjc3ZzMXZ1OTN0OWcyNmdndHA5MHd2Z3lsanA3ZCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FdlMIwDQAxXn1K%2Fgiphy.webp&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d019cb82b00dfaf002276c41cf65cec/href">https://medium.com/media/0d019cb82b00dfaf002276c41cf65cec/href</a></iframe><p>That&#39;s where Slash GraphQL trumps over firebase by making GraphQL the language to talk to the backend. No strings attached!</p><p>Imagine the same scenario now — you prototyped your app using Slash GraphQL, you used apollo client. And let&#39;s say one day you get adventurous &amp; wish to set up your own infrastructure. No problem!</p><p>You can write your own GraphQL service, take the pain of writing resolvers, <strong>OR</strong> host <a href="https://dgraph.io/">Dgraph’s</a> open-source GraphQL database for the same GraphQL schema you defined in Slash GraphQL.</p><p>This makes Slash GraphQL so interesting, with built-in auth &amp; custom logic, Slash GraphQL is the fastest way to build apps.</p><p>Yes, there are a bunch of services out there that enable you to set up a GraphQL backend. To all which my answer is — The underlying database for Slash GraphQL is Dgraph which is open source &amp; speaks GraphQL natively. No tables. No DB management. Only GraphQL. Why settle for a translation layer?</p><p>Give it a spin maybe? Literally, you can launch a backend in autopilot mode &amp; experience the new way of building scalable apps.</p><p><a href="https://slash.dgraph.io/">Slash GraphQL</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eace9175e1a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Grow Power Users On Your Web App]]></title>
            <link>https://medium.com/swlh/grow-power-users-on-your-web-app-48b761e00c01?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/48b761e00c01</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 19:52:36 GMT</pubDate>
            <atom:updated>2020-04-29T17:51:36.999Z</atom:updated>
            <content:encoded><![CDATA[<h3>Grow Power Users On Your App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bd-yFFRKkQQXXday" /><figcaption>Photo by <a href="https://unsplash.com/@libs?utm_source=medium&amp;utm_medium=referral">Steven Libralon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Today, the Powerful User</h4><p>Who’s not a power user in 2020? Most likely you are a power user of an application you use at your workplace everyday.</p><p>Power users are generally associated with people’s skill to reap maximum gain of functionalities from a software. Over the last few years, online productive apps &amp; tools on web have altered this definition rather the path <strong><em>to become a power user </em></strong>has changed.</p><p>Fundamentally there is a difference between a power user of vim text editor &amp; a power user of Google Sheet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*i74hK_itiBh4rVgANy2zmw.png" /><figcaption>Geek’s goto text editor — VIM (Full of shortcuts)</figcaption></figure><p><strong>To be a power user</strong> of vim, you need to know shortcuts, techniques, macros &amp; what not. On the other hand Google Sheets <strong>endows power to the user</strong>. Today applications widens the users capabilities and often poorly designed web apps limits them.</p><p>Accessibility &amp; usability of your web application determines how effective users can leverage capabilities of the application. <strong>Yielding powerful users </strong>on your application ecosystem is as important as building a powerful application. Users love to work on familiar patters, it feels frictionless.</p><p>Accessibility is one key to unlock the potential of your web app. Your app must be at least accessible for your users to kick off.</p><h4>What is Web Accessibility?</h4><p>Web Accessibility is the design quotient of a website which determines the ease of use for everybody. Everyone here includes people with visual, cognitive, physical disabilities, age-related impairments and also keyboard fanatics. Accessibility support is necessary to allow assistive technology to interpret web pages and applications.</p><h4>Why Invest in building Accessible Web apps?</h4><p>Good looking web apps are not always the best. Many developers ignore accessibility mostly due to lack of awareness. Also building accessible web apps can get tough &amp; challenging.</p><p>Accessibility does not only lift the experience of users outside narrow range of the “typical” user, but also improves the visual cues of your app in general. This allows the user to relate with <strong>common design patterns &amp; behaviours </strong>which makes adoption easy especially for a complex app. Focus management becomes daunting when visual order does not overlap with the natural DOM order especially when you start using CSS grid &amp; flex.</p><p>For example, navigating through content can become pesky. Making your component fully operable through a keyboard greatly enhances the user’s productivity and saves a whole lot of time. With keyboard shortcuts added, the <strong>user can charge up their workflows.</strong></p><p><a href="http://kubric.io/">Kubric</a>’s app ecosystem is leveraged by teams across verticals composed of content creators, designers, marketeers &amp; editors etc. For building a high productivity app; making accessible components to enhance user workflows become quite important for our applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48b761e00c01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/grow-power-users-on-your-web-app-48b761e00c01">Grow Power Users On Your Web App</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sound of Software — Visual Loudness]]></title>
            <link>https://medium.com/swlh/the-sound-of-software-visual-loudness-9d33dfdffa46?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d33dfdffa46</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 16:54:38 GMT</pubDate>
            <atom:updated>2020-04-25T06:41:36.091Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Sound of Software — Visual Loudness</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*vezo8rAbGEY4xwG1EixY6g.gif" /><figcaption>RAD Colors</figcaption></figure><h4>Why do you need loudness?</h4><p>Software in 21st century doesn’t come with user manuals. They are most likely self installed on a mobile device. Nobody teaches how to operate an app.</p><p>Some apps just are just <strong>POP</strong> &amp; provide <em>natural way-finding</em>. There is no art behind this, its just quantitative analysis. Loudness needs to be tuned across the interface to help the user navigate &amp; take actions.</p><h4>Loudness is in your head!</h4><p>You don’t need to make noise(literally) to be heard. You can visually evoke loudness in the mind. Colours, contrast, position &amp; motion help digital interfaces communicate loudness. The craft is to understand how to <strong>weigh</strong> this loudness &amp; set the <em>nudges</em> for the user across the interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEKLjybsnofLb0DlU4cjcg.png" /><figcaption>See from left to right &amp; notice how the colours shifts your attention</figcaption></figure><p>Colours play a very important role in adding visual loudness naturally. In general warm colours are used infrequently which stands out among other cooler colours. Position as well matters. The corners are usual suspects for primary actions &amp; often <strong>louder</strong> places. To go one step ahead, a little animation can lift the loudness to the next level. These techniques can be built into systems through the use of <em>links</em>, buttons, &amp; <strong>promotional call-outs</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*7tlOA7NVub7C7x3ccAA3Ug.png" /><figcaption>A loudness guide illustrated in <a href="https://www.viget.com/articles/visual-loudness/">https://www.viget.com/articles/visual-loudness/</a></figcaption></figure><h4>You need a scale to measure</h4><p>Visual loudness without a scale can be disastrous. Any quantitative analysis needs a scale to measure. For visual loudness, there are no standard but there are suggested techniques &amp; parameters on which you can build your own loudness scale. You can classify components in terms of<em> volume, frequency &amp; use. </em>Volume can be . Frequency can determine if the volume assigned is appropriate, you don’t want a lot of noise a more frequently appearing component. The Use is more suggestive of justification for the cost of volume.</p><p>A good example — A <strong>Confirmation Button</strong> can have very high volume given that frequency is low &amp; the use is more encouraging . A bad example will be a <strong>Cancel Button</strong> with high volume -though the frequency is low, but the use is not encouraged (From the perspective of the Software designer).</p><p>Having a scale really helps in setting up the inventory of components used across &amp; fix the volume to bring out the POP effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCFn5UmnroiqOT2qza2n6g.png" /><figcaption><a href="https://dribbble.com/anaoku">Ana Okuntseva</a> illustrates a Loudness Scale for Buttons</figcaption></figure><p>So next time you use your favourite app, try to intercept how well loudness has been tuned &amp; observe how smartly the app nudges you to do what it wants you to.</p><p>Stay tuned &amp; follow for more stories brewing just for <em>software lovers ❤️</em>.</p><p>This is an article of a collection -<a href="https://medium.com/@thiyagaraj.t/the-sound-of-software-f7721a5178dd"><strong>The Sound of Software</strong></a><strong> 🎻</strong></p><p><em>Sources</em> —</p><ul><li><a href="https://reads.kubric.io/the-sound-of-software-visual-loudness/">The Sound of Software - Visual Loudness</a></li><li><a href="https://dribbble.com/shots/6857226-Sato-UI-Buttons-Loudness-Guide">Sato UI Buttons 🚀Loudness Guide</a></li><li><a href="https://www.viget.com/articles/visual-loudness/">Using Visual Loudness for Better Wayfinding | Viget</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d33dfdffa46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-sound-of-software-visual-loudness-9d33dfdffa46">The Sound of Software — Visual Loudness</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sound of Software]]></title>
            <link>https://thiyagaraj-t.medium.com/the-sound-of-software-f7721a5178dd?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7721a5178dd</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Thu, 02 Apr 2020 18:30:53 GMT</pubDate>
            <atom:updated>2020-04-24T17:13:53.377Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Sound of Software — Motif</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*srbPIar0d0q1SRZM" /><figcaption>Photo by <a href="https://unsplash.com/@franckinjapan?utm_source=medium&amp;utm_medium=referral">Franck V.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We are surrounded by machines doing their own <em>jingles. </em>It can be the washing machine that <em>clinks</em> when the clothes are dry or the toaster <em>dings!</em>. Companies have weaved sounds in their products to communicate information &amp; more importantly make them lively.</p><p>The sounds are functional but beyond that it is visceral. Machines try to set our mood throughout our tasks using sound.</p><p>“The person washing socks becomes the hero in a domestic drama”, — Brandon Satanek, UI/UX global manager at Whirlpool shares in an article. An appliance’s notifications provide the soundtrack support the movie, which follows an emotional arc.</p><p>Similarly, when a smart oven finishes preheating, it plays a hopeful phrase (<em>da-da-di?</em>), while a finished bake is accompanied by a triumphant <em>da-di-dum!</em> Likewise with the washer/dryer. “There are certain happy events in those situations,” Satanek said. “When you’ve finished washing your clothes, and you’re ready to smell those clean clothes, it’s a moment to celebrate. We want to reinforce those things in a really positive way with the sounds.”</p><p>Sound is visceral and induces strong stimuli in humans. Sound can help in decreasing the cognitive load on humans &amp; demand focus. This is evident with brands using sound like a hallmark for their brands, whether its Coco Cola’s <em>pop</em> sound on opening the soda bottle, Ted Talk’s <em>chime effect </em>before each video<em> </em>or the <em>god-like</em> Windows 95 starting up and closing down.</p><h4>The Silence in the Digital World</h4><p>Consumer products have made the best use of digital advancements to render better quality &amp; range of sounds to consumers but surprisingly this does not hold true for digital products.</p><p>Our relationship with digital products is much intimate than a washing machine. We carry software in our pocket, unlike a washing machine. Software is consumed at several places &amp; the idea of applications going <em>bling bang boo </em>doesn’t seem to be a great idea. But we can <em>see the sound and hear the colors</em>. Software doesn’t necessarily need to make noise to be heard. In the upcoming articles, I will be sharing how you can cut the cognitive load on the screen without making noise and establish a better recall in spatial relationships. But most importantly<em> bringing user interface to life and build a relationship with the user</em>.</p><p>Follow on medium to stay tuned and learn how modern softwares are built loud and clear.</p><h4>The Collection</h4><p><a href="https://medium.com/@thiyagaraj.t/the-sound-of-software-visual-loudness-9d33dfdffa46">Visual Loudness</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7721a5178dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Case for GraphQL]]></title>
            <link>https://codeburst.io/the-case-for-graphql-16090de30972?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/16090de30972</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[graphql-vs-rest]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Thu, 27 Feb 2020 11:47:45 GMT</pubDate>
            <atom:updated>2020-03-11T03:17:38.048Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>If all has to summarised in one line for product manager — GraphQL can </em><strong><em>Massively Impact Delivery</em></strong><em> 🚀</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*99MwmebMS8GEvDpU" /><figcaption>Photo by <a href="https://unsplash.com/@clintadair?utm_source=medium&amp;utm_medium=referral">Clint Adair</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So to cut the clutter, I will try to highlight major values &amp; challenges in three different lens -</p><h4><strong>App Centric</strong></h4><p>Significant boost to developer experience. The documentation become more of a <strong>living document</strong> &amp; allows the user to <strong>self explore</strong> documentation with limited or existing domain knowledge. Onboarding developers to use API’s will be easy. (Shopify is an early adopter which has exposed its public APIs over GraphQL)</p><p>“<em>frontend</em>” team takes the <strong>ownership</strong>. Engineering effort on the Frontend team or client app centric teams. GraphQL replaces the middleware &amp; becomes an access point for all the apps &amp; third party developers.</p><h4><strong>Platform Centric</strong></h4><p>Free from Domain model understanding. No need to be familiar with the domain models to establish relationships to <strong>deliver meaningful data</strong>.</p><p>No more <strong>over-fetching/under-fetching</strong>. This is a key value that GraphQL adds to the system. The platform doesn’t need to solve this problem anymore. Example — A storyboard can just have a list of shot ids, the GraphQL query can determine if the shots info is required by the app or not, thus the platform offloads managing fetching data from different resources to the GraphQL layer.</p><p>API Onboarding is Slow, any new API introduced needs to be on-boarded to the GraphQL layer, i.e not just configurations but also write some code!</p><p>Entry cost is high! There is a quite considerable engineering initiatives involved. It’s directly competing with REST API, clearly the benchmark is REST.</p><p>Governance &amp; management (Few solutions are being developed in this area)</p><h4><strong>Data Centric</strong></h4><p>Data access is still a blocker — The database can be still in Relational, so doesn’t reap performance benefits* (Best practices can be followed) unless there is a graph database underlying like Neo4J, DGraph, etc.</p><p>Security — This is not a solved a problem (Again, if a direct GraphQL layer is used directly over a DB)</p><h4>Principles</h4><p>Principles on which the GraphQL is evolving (at-least for now)</p><ul><li>Backward compatibility</li><li>Performance is a feature</li><li>Capabilities for new use cases</li><li>Favour no change</li><li>Simplicity &gt; Expressiveness (This is interesting)</li><li>Living Documentation</li></ul><p>The principles in my understanding gives a hope for a sustainable spec, the focus in the community is around tooling and building better developer experience. I don’t see any disruptive change can be expected in near future.</p><p>Companies involved in the <a href="https://foundation.graphql.org/">GraphQL Foundation </a>— Airbnb, Apollo, Coursera, Elementl, Facebook, GitHub, Hasura, Prisma, Shopify, and Twitter</p><p>So to sum up, if you have a platform delivering to multiple apps with different use cases, GraphQL seems to solve a lot of your problems. Definitely it’s a long term investment for creating a <strong><em>massive impact on delivery of services</em></strong>.</p><p>Also it will be interesting to see how the community evolves in this space in near future with increasing adoption in the tech space.</p><p>Originally posted on <a href="https://reads.kubric.io/the-case-for-graphql/">https://reads.kubric.io/the-case-for-graphql/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16090de30972" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/the-case-for-graphql-16090de30972">The Case for GraphQL</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write Better, More Expressive Code With Configurations]]></title>
            <link>https://medium.com/better-programming/writing-expressive-code-9330ca60c8df?source=rss-f192f15079a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9330ca60c8df</guid>
            <category><![CDATA[programming-tips]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Thiyagaraj T]]></dc:creator>
            <pubDate>Wed, 22 Jan 2020 14:10:39 GMT</pubDate>
            <atom:updated>2020-01-29T17:35:05.509Z</atom:updated>
            <content:encoded><![CDATA[<h4>Passing in objects rather than setting individual properties</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t3CuE173lO02FxHF4j8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cbarbalis?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chris Barbalis</a> on <a href="https://unsplash.com/s/photos/still-life?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This piece should not be mistaken for a design pattern. It’s about good practices you can adopt when writing functions, designing components, or even architecting a system.</p><p>The major theme is around configurations, which are generally used across many programming languages. For this article we will use JavaScript to illustrate a few examples. We will discuss this later.</p><p>For now, lets explore how configurations can improve the developer experience and rapid development.</p><h3>What is a Configuration?</h3><p>A configuration can be as simple as a JSON object with a bunch of key values or as complex as a configuration object managed by a full-blown configuration management system. There’s no right or wrong way to define or store a configuration — it’s just a representation of metadata.</p><h3>Who’s a Consumer ? Anyone</h3><p>A configuration consumer can be anything. It can be simple function, a component, or an application. There can even be multiple consumers for a single configuration. It’s just that the power lies in the consumer and not the configuration. The configuration doesn&#39;t dictate anything to the consumer — the consumer can decide what to infer. The configuration alone is just metadata.</p><h3>What Does Configuration Mean to the Consumer?</h3><p>The configuration means two things to the consumer.</p><p><strong>One</strong>: It can be treated like an execution context. The configuration can hold data which can be used by the consumer to produce results based on it.</p><p><strong>Two</strong>: It can be treated as behaviour. The configuration can be used to determine the behaviour of the consumer. Both of these sound similar don’t they? Parameters and interfaces?</p><p>Parameters passed to a function allows something to be set in the execution context. It allows the caller to pass on data to the consumer.</p><p>Interfaces determine the behaviour of the implementor. The implementor is in contract with the interface to implement a set of behaviour (functions).</p><p>A configuration can definitely be passed to a function to trickle down data to its execution data. But also it can serve an entirely different purpose to another consumer.</p><p>There is a big tradeoff for flexibility, you may notice. The author must take the responsibility of honouring the configuration — the configuration cannot alone dictate the rules to the consumer. Thus, the configuration just describes the “what” — the consumer describes the “how”. By now you should have realised that configuration allows you to practice separation of concern in your code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*-pr6jHsMV-xOcB-fjUT2Ug.png" /><figcaption>Consumers are left to interpret from the configuration</figcaption></figure><h3>Understand by Example</h3><p>Let’s assume you have to create a house object, which contains some properties, like floors and garden. Where floors could contain an array of Room objects, etc. So the first method would be to do it in an imperative way, where you based on the requirement, construct the object by creating all required sub-properties and linking these objects in the desired manner. The example below is fairly simple, done in an imperative fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKFcLJ2Gzj5W_s-oYwSFoA.png" /></figure><p>Now, what&#39;s the problem?</p><p>Some obvious deductions would be:</p><ul><li><strong>A lack of up-front information</strong>. The reader has to go through each line to understand what type of house is being constructed. Hence, you need to create some sort of mind map to make sense of the code. For example, you discover that the house contains a garden at the very end. So there can be suspense while you read code from top to bottom. Suspense is awful for the reader — it makes them more cautious and hence decisions take more time.</li><li><strong>Forced information on the reader</strong>. Not everyone is interested in the “how.” The reader probably wants to know the “what,” and, going one step ahead, maybe “why.” This code forces the reader to go line by line and leaves the reader to interpret the result. There’s some overlap between the “what” and “how” — its a liability for the reader to distinguish.</li><li>It’s a shameless abuse of the <strong>DRY</strong> principle. The code is not tangible, it&#39;s not at all reusable. If you want to create a new house, you will have to write it again, line by line. This lacks an entry point which can produce the same result.</li></ul><p>Obviously, there’s a better way to do it. Here’s a better version of it using a simple configuration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3HQR1AWAblPPS2jSFXZy-w.png" /></figure><p>Just looking at the code, we can see it’s more expressive. There are better parts of using a configuration in this simple example, discussed below.</p><h3>Consumer Agnostic</h3><p>Configuration decouples implementation detail of the consumer from the intended behaviour. Hence the behaviour can be shared by different consumers, allowing you to retain the same configuration and have multiple implementations built on top of it.</p><p>Say you have written a configuration for creating an object. There can now be multiple consumers from different vendors. For example, for the house object, there can be multiple builder functions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdbBGGx3AitIOWadpG0THg.png" /></figure><p>This is a powerful system. It gives you the flexibility to create multiple implementations over the same configuration. This should not be mistaken for interfaces. An interface is an abstraction of behaviour alone. You could say that interfaces are configuration but the opposite does not hold true.</p><p>Interfaces have a more definite purpose and are quite tightly tied up with the language itself. Configurations, on the other hand, are quite open — they can be isomorphic: shared by two entirely different systems. The serialisable nature of a configuration allows you to go one step further and use it across systems which cannot talk to each other directly.</p><p>For example, the same configuration can be consumed by a UI component, application state management level, and at service level.</p><p>Consider filters in a flight booking website. These filters can be governed by a configuration, so you don’t need to write any code. Just add a configuration, which can be consumed by the UI component, to display the new filter and determine payload for events to dispatch on click. The application state management middleware can rely on the same to determine what action to be taken on the events. At the service level, you can use it to construct the query for the database access.</p><p>A configuration is not limited to behaviour. It’s at the author&#39;s discretion to use the configuration to define behaviour or as simple input to the consumer of the configuration.</p><h3>Predictable Behaviour, Separation of Concerns</h3><p>The reader gets upfront information about what the author is trying to do. The focus shifts away from the “why” of the code towards the “what.” The decoupled behaviour and context of the consumer brings more clarity in the code. The reader knows where to find the “what” and “how” of the code.</p><p>The practice of writing configurations helps the developer evolve the mental model of coding to adopt a more declarative approach.</p><h3>Less Surface Area, Less Maintenance Weight</h3><p>The configuration becomes the source of truth. (The credibility of the configuration is still dependent on the consumer). To make any addition or change, you can always rely on the configuration to make the update.</p><p>The configuration exposes the surface area for modifying your code. You can alter the execution context or the behaviour of the consumer. Again the extent to which you can bring in variation to this code depends on the consumer. Just adding configuration will not make the consumer any good. The consumer must support the flexibility. Designing a configurable consumer itself deserves a separate blog or even a book. Again it can be a simple consumer like a utility function or also a configurable workflow system.</p><p>At <a href="http://app.kubric.io/">Kubric</a> we’ve evolved complex configurations to language to express application state, functionality and workflows in our UI. Will be sharing more about such patterns and useful home brewed techniques we have developed in the future.</p><p>Have a great day!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9330ca60c8df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/writing-expressive-code-9330ca60c8df">Write Better, More Expressive Code With Configurations</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>