<?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 T_DasanthaEdirisinghe on Medium]]></title>
        <description><![CDATA[Stories by T_DasanthaEdirisinghe on Medium]]></description>
        <link>https://medium.com/@t.dasanthaedirisinghe?source=rss-16f0aadac7f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mYgnWd4wjsGmmLUy</url>
            <title>Stories by T_DasanthaEdirisinghe on Medium</title>
            <link>https://medium.com/@t.dasanthaedirisinghe?source=rss-16f0aadac7f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:37:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@t.dasanthaedirisinghe/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[AI Can Write Your API Code. So Why Isn’t That Enough?]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/ai-can-write-your-api-code-so-why-isnt-that-enough-2ef58daa1725?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ef58daa1725</guid>
            <category><![CDATA[open-api]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[ai-in-engineering]]></category>
            <category><![CDATA[developer-experience]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Sat, 04 Apr 2026 04:51:19 GMT</pubDate>
            <atom:updated>2026-04-04T04:51:19.711Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is a continuation of my previous post on <a href="https://medium.com/@t.dasanthaedirisinghe/stop-writing-manual-api-services-moving-toward-a-type-safe-automated-future-c9bd15758cf5">building Tenon-Link </a>— where I explored eliminating manual API services through automation. If you haven’t read that yet, I recommend starting there for full context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKFwDUwSVlNtJADZYRM5Zw.png" /><figcaption>Generated by Gemini</figcaption></figure><h3>Why we’re still dealing with broken integrations in the age of Autocomplete.</h3><p>We’re living in a time where tools like Claude, ChatGPT, Gemini and GitHub Copilot can generate API calls in seconds. Paste an endpoint, ask for a TypeScript function, and — <em>done</em>.</p><p>At first glance, it feels like the problem of API integration is solved. So why are we still dealing with broken integrations, mismatched types, and runtime errors?</p><blockquote>Because AI solves the <strong>symptom</strong> — not the <strong>system</strong>.</blockquote><h3>The Illusion of “Done”</h3><p>Let’s say you prompt an AI: <em>“Generate a TypeScript function for GET /users.”</em> You get something like this:</p><p>TypeScript</p><pre>const getUsers = async (): Promise&lt;User[]&gt; =&gt; {<br>  const res = await fetch(&#39;/users&#39;);<br>  return res.json();<br>};</pre><p>Looks clean. Feels productive. But here’s the catch: <strong>That code is based on patterns, not reality.</strong></p><ul><li>Does /users actually return User[]?</li><li>Are the field names exactly what the backend emits?</li><li>What happens when a field becomes optional tomorrow?</li></ul><p>AI doesn’t know. It guesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvWfqYAKVxUaGFJSqHtMBg.png" /><figcaption>Generated By Gemini</figcaption></figure><h3>1. AI Has No Source of Truth</h3><p>The biggest problem with AI-generated API code is that it is not connected to your backend. Your API is a living thing: fields get renamed, responses change shape, and new validation rules appear.</p><p>AI doesn’t automatically update your code. When the backend evolves, you have to go back, re-prompt, re-generate, and re-check. You haven’t eliminated manual labor; you’ve just replaced <strong>manual coding</strong> with <strong>manual prompting</strong>.</p><h3>2. You Still Own the Bugs</h3><p>AI can speed things up, but it doesn’t take responsibility. If your API returns { &quot;user_id&quot;: &quot;123&quot; } but your AI-generated code expects { &quot;id&quot;: &quot;123&quot; }, you’ll hit the classic: Cannot read property &#39;id&#39; of undefined.</p><p>Now you’re debugging the same issue you were trying to avoid. <strong>AI didn’t break your app</strong> — but it didn’t protect it either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0aIsoVfmCgg1Qor_SA0W1g.png" /><figcaption>Generated by Gemini</figcaption></figure><h3>3. Type Safety Isn’t Real (With AI Alone)</h3><p>AI-generated TypeScript looks type-safe, which is the dangerous part. Unless that code is generated from a real schema, you’re operating on <strong>false confidence</strong>. And false confidence is worse than no safety at all, because you stop looking for the errors that are inevitably there.</p><h3>4. AI Doesn’t Scale Across Teams</h3><p>Using AI individually is great. Using it across a team is where things break down. Everyone writes prompts differently, code styles vary, and API layers become inconsistent. There’s no shared contract — no guarantee that two developers are integrating the same endpoint the same way.</p><h3>The Real Problem: API Integration Is Still Manual</h3><p>AI didn’t remove the workflow; it just made one step faster. You still have to think about types, verify responses, and handle mismatches. The <strong>“manual API tax”</strong> is still there — it’s just slightly disguised.</p><h3>What a Real Solution Looks Like</h3><p>To truly solve API integration, you need <strong>infrastructure</strong>, not just an assistant. This is why I’ve been working on <strong>Tenon-Link</strong>.</p><p>A real solution requires:</p><ul><li><strong>A single source of truth:</strong> Your API spec (OpenAPI/Swagger).</li><li><strong>Deterministic generation:</strong> Code generated directly from that spec — not guessed.</li><li><strong>Guaranteed alignment:</strong> If the backend changes, the frontend types break at compile-time, not runtime.</li></ul><h3>AI vs. Infrastructure: When to Use Each</h3><p>AI is an incredible tool, but we need to be honest about where it belongs in the stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uo-2y6zBRPUCoZjM9lJS8Q.png" /><figcaption>Generated by Gemini</figcaption></figure><h3>Use AI for:</h3><ul><li>Writing complex business logic.</li><li>Building UI components.</li><li>Learning new patterns or refactoring code.</li></ul><h3>Use Tenon-Link for:</h3><ul><li>Standardizing your API integration layer.</li><li>Ensuring 100% type safety between FE and BE.</li><li>Scaling a consistent codebase across a large team.</li></ul><p><strong>Tenon-Link</strong> is currently in its early stages.</p><p>The current version is a <strong>prototype</strong>. While the full production suite is being polished for its official release.</p><ul><li><strong>Visit the Site: </strong><a href="https://sites.google.com/iit.ac.lk/tenon-link1/home">https://sites.google.com/iit.ac.lk/tenon-link1/home</a></li></ul><p><strong>I need your feedback.</strong> Drop a comment below or reach out through the site — let’s build an API-first future that actually works.</p><h3>Final Thought</h3><p>AI is an assistant. But API integration is <strong>infrastructure</strong>.</p><p>Infrastructure shouldn’t depend on how well you phrase a prompt or how much of the documentation you can fit into a context window. It should be deterministic, repeatable, and — frankly — boring.</p><p><strong>AI helps you write code faster. Tenon-Link helps you not have to write that code at all.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ef58daa1725" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Writing Manual API Services: Moving Toward a Type-Safe Automated Future]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/stop-writing-manual-api-services-moving-toward-a-type-safe-automated-future-c9bd15758cf5?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9bd15758cf5</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[open-api]]></category>
            <category><![CDATA[swagger]]></category>
            <category><![CDATA[type-safety]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Sat, 04 Apr 2026 04:30:04 GMT</pubDate>
            <atom:updated>2026-04-04T04:30:04.530Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Monday Morning Problem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TLwH7RuUR94VzCj54gxnMg.png" /><figcaption>Monday Morning Problem Illustration Generated by Gemini</figcaption></figure><p>It’s Monday morning.</p><p>Your backend team just shipped five new endpoints. Everything is documented (kind of) in Swagger. Now it’s your turn.</p><p>You open your editor and start the ritual:</p><ul><li>Define TypeScript interfaces</li><li>Write Axios/fetch calls</li><li>Map responses</li><li>Handle edge cases</li></ul><p>Three hours later, you’ve written code that <em>feels</em> like progress — but deep down, you know the truth:</p><p>You didn’t build anything meaningful. You just wired things together.</p><p>And worse? A single typo in a property name can crash your UI.</p><h3>There’s a better use of your brain.</h3><p>Frontend developers should be focused on <strong>UX, performance, and logic</strong> — not repetitive plumbing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4M3ShkBtStaD7eCsyjgN1Q.png" /><figcaption>Better use of Frontend Developers Day Generated by Gemini</figcaption></figure><h3>The Hidden Cost: The “Manual API Tax”</h3><p>Let’s call it what it is: a tax on your time.</p><h3>1. Maintenance Nightmare</h3><p>Your backend changes user_id → userId.</p><p>Now what?</p><p>You’re searching across your entire codebase, hoping you didn’t miss a single reference. If you did, congrats — you’ve just introduced a bug that TypeScript <em>won’t catch</em>.</p><h3>2. The Sync Gap</h3><p>Your Swagger docs say one thing.<br> Your backend returns something slightly different.</p><p>This drift happens more often than we admit.</p><p>And suddenly, your “source of truth” isn’t actually the truth anymore.</p><h3>3. When TypeScript Lies</h3><p>We trust TypeScript to protect us.</p><p>But here’s the uncomfortable reality:</p><p>If you manually define your interfaces, you can accidentally lie to the compiler.</p><pre>type User = {<br>  id: string;<br>  name: string;<br>};</pre><p>Looks fine… until the backend sends:</p><pre>{ &quot;user_id&quot;: &quot;123&quot;, &quot;full_name&quot;: &quot;John&quot; }</pre><p>Now you’re debugging:</p><pre>Cannot read property &#39;name&#39; of undefined</pre><p>Type safety? Gone.</p><h3>Enter Tenon-Link</h3><p>What if your API layer could write itself?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_A_o54PyCzAUX2o8eGQl1g.png" /><figcaption>Manual Vs Tenon-Link API bridge Generated by Gemini</figcaption></figure><p><strong>Tenon-Link</strong> is designed to bridge the gap between your OpenAPI/Swagger specification and your TypeScript codebase.</p><h3>The idea is simple:</h3><ul><li>Read your API spec</li><li>Generate fully typed API clients</li><li>Eliminate manual boilerplate</li></ul><p>No more hand-written fetch calls.<br>No more mismatched interfaces.</p><h3>What You Get</h3><ul><li><strong>True type safety</strong> (directly from your API spec)</li><li><strong>Zero boilerplate API code</strong></li><li><strong>Full IntelliSense &amp; autocomplete</strong></li><li><strong>Automatic sync with backend changes</strong></li></ul><p>You write less code — and trust it more.</p><h3>The Workflow Shift</h3><p>Let’s compare.</p><h3>The Old Way</h3><pre>Update API Spec<br>   ↓<br>Write TypeScript Interfaces<br>   ↓<br>Write API Service Functions<br>   ↓<br>Debug mismatches<br>   ↓<br>Finally Done</pre><h3>The Tenon-Link Way</h3><pre>Update API Spec<br>   ↓<br>Run Generator<br>   ↓<br>Done</pre><p>This isn’t just faster — it’s <strong>safer, cleaner, and scalable</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ERTBB0SCRgbIu_MLqYWA4A.png" /></figure><h3>Transparency: Where This Is Today</h3><p>Tenon-Link is currently in <strong>active development</strong>.</p><p>The current website is a <strong>quick prototype {Link:- </strong><a href="https://sites.google.com/iit.ac.lk/tenon-link1/">https://sites.google.com/iit.ac.lk/tenon-link1/</a><strong>}</strong>— built to share the vision, not the final product. A more robust platform is coming as the system matures.</p><h3>I Need Your Feedback</h3><p>I’m building Tenon-Link to solve a real problem I’ve personally faced over and over again.</p><p>Now I want to hear from you:</p><ul><li>Does this solve a pain point in your workflow?</li><li>What features would make this indispensable for you?</li><li>What would make you switch from your current setup?</li></ul><p>If this resonates with you, I’d love for you to:</p><ul><li>Join the waiting list</li><li>Share your thoughts</li><li>Help shape the roadmap</li></ul><h3>Closing Thoughts</h3><p>Tenon-Link is being built on a simple belief:</p><blockquote><em>Our tools should work for us — not the other way around.</em></blockquote><p>We’re still in the lab, refining the engine.</p><blockquote>But the goal is clear:<br> <strong>Make API integration invisible.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9bd15758cf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most Asked Question in ReactJS]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/most-asked-question-in-reactjs-53928ce6b63c?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/53928ce6b63c</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[questions]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Sat, 03 Aug 2024 15:36:39 GMT</pubDate>
            <atom:updated>2024-08-03T15:36:39.330Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0lejKWqYBQFNGqWi" /><figcaption>Photo by <a href="https://unsplash.com/@jontyson?utm_source=medium&amp;utm_medium=referral">Jon Tyson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What is a module?</h3><p>In JavaScript, a module is a self-contained unit of code that encapsulates related functionalities. It’s like a building block that can be reused in different parts of your application. Modules promote code organization, reusability, and maintainability.</p><h3>What is package?</h3><p>A package is a collection of related modules and assets that are bundled together for distribution and installation. It’s a higher-level abstraction than a module. Think of a package as a toolbox containing various tools (modules) that can be used together to build something.</p><h3>What is the difference between a module and a package.</h3><ul><li><strong>Module:</strong> A single unit of code with specific functionalities.</li><li><strong>Package:</strong> A collection of modules and other resources distributed as a single unit.</li></ul><h3>What is NPM?</h3><p>NPM (Node Package Manager) is a default package manager for JavaScript that allows you to install, share, and manage packages of code. It’s a vast repository of open-source packages that can be easily integrated into your React projects.</p><h3>What is Webpack?</h3><p>Webpack is a powerful build tool for modern JavaScript applications. It takes your code and dependencies and bundles them into optimized files for the browser. It’s essential for managing complex React projects with multiple files and dependencies.</p><h3>How do you create a new React project?</h3><p>You can create a new React project using the following command:</p><pre>npx create-react-app my-app</pre><p>Replace my-app with your desired project name. This command sets up a basic React project structure with necessary files and dependencies.</p><h3>What are the files and folders inside a project folder?</h3><ul><li><strong>package.json:</strong> Contains metadata about the project, including dependencies, scripts, and project information.</li><li><strong>package-lock.json</strong> or <strong>yarn.lock:</strong> (Depending on the package manager) Locks down the exact versions of dependencies to ensure consistent builds.</li><li><strong>.gitignore:</strong> Specifies files and directories that Git should ignore.</li><li><strong>node_modules:</strong> Contains all installed packages and their dependencies.</li><li><strong>public:</strong> Contains static assets like index.html, favicon.ico, and other files that will be served directly to the client.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53928ce6b63c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JSX: The power behind ReactJS]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/jsx-the-power-behind-reactjs-57edc532272e?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/57edc532272e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Thu, 01 Aug 2024 15:57:42 GMT</pubDate>
            <atom:updated>2024-08-01T15:57:42.100Z</atom:updated>
            <content:encoded><![CDATA[<p>JSX, a syntax extension for JavaScript, has revolutionized the way we build user interfaces. By blending HTML-like structure with JavaScript’s power, it offers a clean and efficient approach to component development. In this blog, we’ll explore the core concepts of JSX syntax, providing practical examples to help you master this essential skill for React development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tn-F7rwOTI0nMi26" /><figcaption>Photo by <a href="https://unsplash.com/@rahuulmiishra?utm_source=medium&amp;utm_medium=referral">Rahul Mishra</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>JSX, a syntax extension for JavaScript, simplifies the creation of user interfaces by allowing HTML-like structures within JavaScript code. Unlike traditional HTML, JSX offers the power of JavaScript for dynamic content and logic. While it resembles HTML, it’s not a string but rather a template syntax transformed into JavaScript objects. This transformation is handled by tools like Babel, which convert JSX into standard JavaScript code that browsers can understand. By eliminating the need for createElement calls, JSX promotes cleaner and more expressive component development in frameworks like React.</p><p>See the JSX code below.</p><pre>// we don&#39;t need to use quotes with JSX<br><br>const jsxElement = &lt;h1&gt;I am a JSX element&lt;/h1&gt;<br>const welcome = &lt;h1&gt;Welcome to JSX Blog!&lt;/h1&gt;<br>const data = &lt;small&gt;Written by Tharindu Edirisinghe&lt;/small&gt;</pre><p>The above code seems like JavaScript but it is not JavaScript and it seems like HTML but not completely an HTML element. It is a mix of JavaScript and an HTML elements. JSX can allow us to use HTML in JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pUoqszeXxmtVg_cK" /><figcaption>Photo by <a href="https://unsplash.com/@casparrubin?utm_source=medium&amp;utm_medium=referral">Caspar Camille Rubin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>JSX Element</h3><p>JSX element could be a single HTML element or many HTML elements wrapped in a parent HTML element.</p><pre># This JSX element has only one HTML element which is h1.<br>const jsxElement = &lt;h1&gt;I am a JSX element&lt;/h1&gt;</pre><p>What if we need to create an element with multiple HTML elements inside. We can do it without any problem but remember every HTML element should be wrapped by an outer HTML element to create a valid JSX element.</p><pre>const header = (<br>  &lt;header&gt;<br>    &lt;h1&gt;Welcome Blog on JSX&lt;/h1&gt;<br>    &lt;h2&gt;This is a code block with &lt;/h2&gt;<br>    &lt;h3&gt;Multiple HTML elements in one variable&lt;/h3&gt;<br>  &lt;/header&gt;<br>)</pre><p>By understanding the fundamentals of JSX syntax, you’ve taken a significant step towards mastering React development. JSX’s ability to seamlessly blend HTML-like structure with JavaScript’s power makes it an invaluable tool for crafting dynamic and interactive user interfaces.</p><p>Remember, while JSX might appear similar to HTML, it’s essential to grasp its underlying nature as a JavaScript syntax extension. By comprehending how JSX is transformed into JavaScript objects, you’ll gain a deeper appreciation for its role in the React ecosystem.</p><p>As you continue your React journey, explore advanced JSX features like conditional rendering, lists, and keys to unlock the full potential of this powerful syntax. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57edc532272e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is React?]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/what-is-react-5d29b0ea83e3?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d29b0ea83e3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Thu, 01 Aug 2024 15:38:58 GMT</pubDate>
            <atom:updated>2024-08-01T15:38:58.145Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKxgipQAiegTrvspQvhZ9Q.jpeg" /></figure><p>ReactJS has taken the web development world by storm. Its component-based architecture and ability to create dynamic, interactive user interfaces have made it a top choice for developers worldwide. But what exactly is ReactJS, and how does it work? Let’s dive in.</p><p>React is a powerful JavaScript library that’s transformed how we craft interactive web applications. Born in the creative labs of Facebook in 2013, it’s become a cornerstone for building complex UIs with ease. Forget wrestling with the DOM directly; React introduces a clever virtual DOM, which acts like a blueprint. When changes happen, React intelligently updates only the necessary parts, resulting in lightning-fast performance. This component-based approach means you create reusable building blocks, making your code efficient and maintainable.</p><h3>Why React?</h3><p>React has undeniably captured the attention of the developer community, solidifying its position as a leading JavaScript library in recent years. Countless developers and businesses have embraced React for its efficiency in constructing intricate user interfaces. This rapid ascent to prominence is mirrored in the library’s substantial and ever-growing community. To quantify its popularity, metrics like GitHub repository stars, watchers, and forks offer valuable insights. A comparative analysis of these figures across the most popular JavaScript libraries paints a clear picture of React’s dominance in the field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*2KXGf5fqs6xEiVbc.png" /></figure><p>Why we choose to use React ? We use it because of the following reasons:</p><ul><li><strong>fast</strong></li></ul><p>React’s performance is exceptional. Its use of a virtual DOM significantly optimizes rendering by updating only the necessary components. This means smoother interactions, quicker load times, and an overall enhanced user experience.</p><ul><li><strong>modular</strong></li></ul><p>React’s component-based architecture promotes modularity, allowing developers to break down complex UIs into smaller, reusable pieces. This improves code organization, maintainability, and efficiency, as components can be easily shared and reused across different parts of an application.</p><ul><li><strong>scalable</strong></li></ul><p>React’s ability to handle complex and large-scale applications is unparalleled. Its component-based structure and efficient rendering make it ideal for building applications that can grow and adapt to changing requirements without compromising performance.</p><ul><li><strong>flexible</strong></li></ul><p>React offers incredible flexibility, accommodating a wide range of project types and complexities. Whether you’re building a simple single-page application or a sophisticated enterprise-level system, React can adapt to your needs.</p><ul><li><strong>big community and popular</strong></li></ul><p>With a massive and active community, React benefits from extensive support, resources, and third-party libraries. This rich ecosystem accelerates development, problem-solving, and staying up-to-date with the latest trends.</p><ul><li><strong>open source</strong></li></ul><p>As an open-source project, React is freely available for anyone to use, modify, and contribute to. This fosters innovation, collaboration, and a thriving community dedicated to improving the library.</p><ul><li><strong>High job opportunity</strong></li></ul><p>The popularity of React has led to a surge in demand for developers with React skills. This translates into abundant job opportunities and competitive salaries for those proficient in this technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*7gRJ5MdX_yAuLofz.jpeg" /></figure><p><strong>In conclusion</strong>, React has revolutionized web development by providing a robust, efficient, and flexible framework for building dynamic user interfaces. Its component-based architecture, combined with the virtual DOM, ensures high performance and maintainability. The vast and active community, coupled with its open-source nature, guarantees continuous growth and development. With its ability to handle complex projects, scale effortlessly, and offer a plethora of job opportunities, React stands as a compelling choice for developers seeking to create cutting-edge web applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d29b0ea83e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Java Class Fundamentals: Building Blocks of Object-Oriented Programming]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/classes-and-objects-0110de9e9182?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0110de9e9182</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[oop]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[concept]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Mon, 17 Jun 2024 18:09:59 GMT</pubDate>
            <atom:updated>2024-06-17T18:10:58.265Z</atom:updated>
            <content:encoded><![CDATA[<p>Looking to build robust and efficient code? Then Object-Oriented Programming (OOP) is a concept you must master. At its core, OOP is all about creating scalable and reusable code by using classes, objects, and other key structures. However, these foundational concepts can be tricky to understand at first. So why don’t we break down the fundamentals of classes and objects with simple examples and explore the world of Object-Oriented Programming. So at the end we can have a deep understanding of OOP concepts and apply them to our next coding project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*wydoIP3ZjAT4VXnc7YRqKg.jpeg" /></figure><h3>What is a class?</h3><p>A class is a blueprint or a template for creating objects. Classes are a fundamental concept in Object-Oriented Programming (OOP) that bundles data and behaviours into a single unit. Objects are instances of classes, and they represent real-world entities in the program.</p><p>So first lets dive into the key characteristics of a **Java class**. Java, being an object-oriented programming language, relies heavily on classes to define objects and their behaviours. A Java class has several key components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZ12geoB2gYRveKJBY5SIw.png" /></figure><h3>Fields</h3><p>Firstly, fields aka attributes represent the properties or characteristics of an object. They serve as containers for the distinctive features of the object. Imagine a car is a Java class, things that include essential details such as manufacturer, model and production year are attributes of the car. By bundling those important details inside the fields we not only create a structured representation of the objects characteristics but also it helps seamless integration of functionalities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*lYcUI9MLtHK_2elv4AlWpA.jpeg" /></figure><h3>Methods</h3><p>The second vital aspect of a Java class is its methods or behaviours. Methods define the actions that the object can perform. If we look at a car, the things car can preform like starting, driving forward, braking, taking a turn and stopping are methods of the car object. These methods bundles or in OOP language encapsulate the functionalities associated with the object so we can interact with it seamlessly.</p><h3>Constructors</h3><p>Next main thing we have is known as a constructor, which is a special method that tells or initializes how to create the object. In java constructors has the same name as the class. Constructors set the starting state of the object, allowing us to define how the object should configured.</p><h3>Access Modifiers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*aeJ-oSb3lOITDFazYAl6TA.png" /></figure><p>We cannot talk about classes without talking about access modifiers. Access modifiers are keywords that control the visibility and accessibility of classes, fields, methods and constructors. In other words they determine who can use or access these components within a program. There are three main access modifiers.</p><ul><li><strong>public</strong> — Components with public modifiers are accessible by any other class or code in the program. Which means they can be accessed from anywhere. For example, a public method can be called from another class, allowing it to be used by different parts of the program. It is commonly used for methods and fields required to be accessed from outside the class.</li><li><strong>private</strong> — Components with private modifiers are only accessible within the same class. They cannot be accessed or modified by any other class or code outside the class in which they are declared. private access is often used to encapsulate the internal implementation details of a class and hide them from external sources. It reinforces the principle of encapsulation, enhancing the security and integrity of the code. private fields can still be accessed through getter and setter methods, allowing controlled access to the data.</li><li><strong>protected</strong> — Components marked as protected are accessible within the same class, subclasses, and other classes in the same package. They are not accessible outside the package unless a subclass inherits from the class. This access modifier allows for controlled access to certain methods and fields while maintaining the encapsulation principle. protected access is commonly used in scenarios where class inheritance is involved and certain components need to be accessible to both parent and child classes.</li></ul><p>The access modifiers are important for maintaining code integrity, security, and encapsulation. By carefully choosing the appropriate access modifier for each component, we can establish clear boundaries and ensure the desired behaviours of the class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*ugYINItjfeyzPx4hF-F32A.png" /></figure><p>Mastering these key characteristics is crucial for understanding the full power of object-oriented programming. By understanding the concepts of fields, methods, constructors and access modifiers you can design efficient, scalable, and maintainable applications that adhere industry best practices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0110de9e9182" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Background Check on Databases]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/background-check-on-databases-c5f25d426ddc?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5f25d426ddc</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[background]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Wed, 03 Apr 2024 18:57:57 GMT</pubDate>
            <atom:updated>2024-04-03T18:57:57.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10w1Rl085BACdXf0xvUDqA.jpeg" /></figure><p>Hey guys CS50 iswhere I started my journey in tech. In CS50 I learned basics of C language and get a solid understanding of Algorithms and Data Structures. Since then I came a long way and so did the Course.</p><p>So I found out recently that there is a new course out called SC50 SQL about Database Management. Databases are one of the most interesting parts of the tech world for me, so today I went all in and started the course. I finished first 30 mins of the first video and decided to write this blog to give you guys a general idea about what I learned so far. Next blog I’ll go into the technical details for today I’ll stop at the background details.</p><h3>Why Learn SQL Database</h3><p>2024 is a peak of the information age, Information age is the time where everything depends on the data. If we take a look around us today everything extremely depends on data, If we go to YouTube they always look for most liked video, what video has the most comments, which comment has most likes so they save everything in a data base and the people decide everything on that data. Not only YouTube, but also big companies like google and Facebook heavily depends on the amount of data they have. So right now is the best time to learn data and be better at data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXPQ9cHIOUCk0CqDg6dHFg.jpeg" /></figure><h3>What is data and how we save it?</h3><p>In ancient times people use this thing called tables to store data. Each table has some columns that store data and rows that store different attributes or sub data of individual data. And then present day huge companies develop this normal tables into a electronic more efficient form of tables called spreadsheets. As examples we have<br>- Apple Numbers<br>- Google Sheet<br>- Microsoft Excel<br>- …..<br>And many more.</p><p>But if we have these Spreadsheets to store and manage data why do we need different type of databases and learn languages to manage them. That seems pretty pointless to me. That’s until I realize that some times these spreadsheets lack three things databases have.</p><h3>Advantages of using Databases</h3><p>Comparing to spreadsheets databases have three main advantages. first in the list is the Scale. Yes spreadsheets are good, graphical, beautiful but they are not made to handle large data sets. If you have around 100 units of data then yes spreadsheet can handle your dataset pretty easily. But when it comes to the database of the YouTube, Google or Facebook, then your average spreadsheet has no chance competing. That’s where the databases shine. Databases can hold and manage pretty easily millions of data with ease.<br>Not only the scale when it comes to the frequency you need to use the data in the database, an SQL database is way better than a spreadsheet. Unlike a spreadsheet a database can execute multiple lines of code and give out multiple data in seconds. Which comes to the third point speed. I don’t have to tell you if you have used a spreadsheet you know finding and changing data form a spreadsheet is not the fastest thing to do in the world. But databases have a completely different take on this, you can change or find data with the speed of light using databases.</p><h3>So what is a Database and What is a DBMS ?</h3><p>Database is simply a collection of data organized for CRUD operations. I know, I know. You are probably asking what is a CRUD operations. Well CRUD stand for Create, Read, Update and Delete. Which are the four things you can do with a database. You can create a brand new data in a database. You can find and update a existing data in a database and you can Read the existing data. Not only that you can delete the existing data form the database.</p><h4>So then what is the DBMS….?</h4><p>DBM stands for database Management System, which is a software to interact with a database. There are multiple database management systems out there some are open source and some are feature rich and have more properties. Some examples for DBMS are <br>- MySQL<br>- Oracle<br>- PostgreSQL<br>- SQLite<br>and there are many other DBMS out there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Adq1T298Ab0dPjz5oHTExQ.jpeg" /></figure><p>So with that I think I said everything I learned about the background of Databases and SQL. In next blog lets find out about the basics of SQL shall we? <br>Till then Sayonara mi amigos…..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5f25d426ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QA Testing Methodologies]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/qa-testing-methodologies-f28a52362e39?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f28a52362e39</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[trending]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Tue, 02 Apr 2024 19:00:15 GMT</pubDate>
            <atom:updated>2024-04-02T19:00:15.105Z</atom:updated>
            <content:encoded><![CDATA[<p>QA stands for the term Quality Assurance, which is a critical field that ensures software applications work and function smoothly and meet user expectations. I am a total noob for the field so I search every where and find out things. So here’s some information I found when I search around to be better at QA.</p><h3>Testing Methodologies</h3><p>Testing methodologies are the different approaches testers use to make sure the software functions correctly. There are three main popular methods — manual testing, exploratory testing and finally my favourite automation testing.</p><p><strong>Manual Testing</strong></p><p><strong>Strengths</strong><br>Manual testing is really good when it comes to handling complex test scenarios and user interactions, which are really difficult to automate. And not like in other testing methods in manual testing, testers can identify usability issues and asses the overall user experience effectively. And also Manual testing can easily adapts to changings and requirements during the development process.</p><p><strong>Weaknesses</strong><br>Unlike other testing types no matter how useful or powerful it is, manual testing is always time consuming than the other testing types. Not only that we need to test everything over and over again every time even after proven work to make sure old functionalities haven’t broken with new changes. And also results might vary depending on the tester performing the tests.</p><p><strong>Exploratory Testing</strong></p><p>Exploratory testing is a software testing method that emphasizes learning, test design and execution all happening at the same time</p><p><strong>Strengths</strong><br>This method encourages thinking outside the box, which uncover unexpected issues. This method helps early bug detection which means effective in finding bugs early in the development cycle. Not only that testers can adjust their tests based on findings, making it ideal for complex or evolving softwire’s.</p><p><strong>Weaknesses</strong><br>Even this method is really useful but it lacks a predefined test plan, making it difficult to track progress or repeat tests. not only that this have a limited scope which means this may miss certain areas not explored during testing.</p><p><strong>Automation Testing</strong></p><p><strong>Strengths</strong><br>Automation testing is really fast and efficient, automating repetitive tasks, saving time and resources. And also this is ideal for regression testing, ensuring existing functionalities remain intact. Not only that automated tests are consistent and produce reliable results.</p><p><strong>Weaknesses</strong><br>Automated scripts need maintenance as the software evolves. Automation may not be suitable for all test scenarios, especially those requiring human judgment or complex interactions. not only that but also Setting up an automation Framework requires an initial investment in time and resources.</p><p>The best approach often involves a combination of these methodologies. Here’s a general guideline:</p><p>- Manual testing is ideal for usability testing, exploratory testing sessions, and edge-case scenarios.<br>- Exploratory testing is valuable in early development stages and for uncovering unexpected issues.<br>- Automation testing is efficient for regression testing, repetitive tasks, and areas with well-defined test cases.</p><p>By understanding the strengths and weaknesses of each methodology, you can choose the most appropriate approach for a particular project and ensure comprehensive software quality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f28a52362e39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build Your Vitae: What exactly is a CV?]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/build-your-vitae-what-exactly-is-a-cv-075ce199c9c1?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/075ce199c9c1</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[cv]]></category>
            <category><![CDATA[professional]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[resume]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Tue, 31 Oct 2023 04:15:54 GMT</pubDate>
            <atom:updated>2023-10-31T04:15:54.227Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you a individual looking for a career jumpstart or do you want to make a impression by showcasing your skills and experience while standing out from other applicants. Then look no further the best way to present your qualifications is through a CV.<strong> But what is a CV?</strong></p><p>A CV, short for Curriculum Vitae (pronounced like “curry your tea” but without the “your”), is like your life’s resume. It’s a document that shares all of the amazing things you’ve done academically and professionally. The fancy Latin translation for “Curriculum Vitae” is “course of life,” but we promise it’s not as intimidating as it sounds.</p><h3>CV Vs Resume</h3><p>You’re on a journey to find a better job, and your trusty weapon is your professional document. But what document should you choose a CV or a resume? Let’s find out what is the best document for the job hunt.</p><h4>Length and Content</h4><ul><li><strong>CV:</strong> Think of this as the director’s cut of your professional life story. It’s got room for all the details: education, career history, awards, research — the whole nine yards. Your CV is your academic and research bio, several pages long and ready for an in-depth exploration.</li><li><strong>Resume: </strong>If you want something shorter, snappier, and to the point, the resume is your go-to. It’s the movie trailer of your professional life. Typically just one or two pages — your best skills and most relevant work experiences. It’s perfect for jobs outside the academic universe.</li></ul><h4>Purpose</h4><ul><li><strong>CV:</strong> If you’re are gearing up for a career in academia, a CV is your trusted sidekick. It’s the go-to choice when applying for academic positions, research grants, or anything that’s academic.</li><li><strong>Resume:</strong> The resume is your all-purpose tool for job hunting in pretty much any field.</li></ul><h4>International Usage</h4><p>Imagine a world where they call both your CV and resume by the same name — “CV”, then you got Europe. But if you are in US or Canada, they tend to say “CV” when they mean the longer academic version and “resume” for the snappier job-hunting version.</p><p>Conclution, both CVs and resumes are your professional passports, but they come in different shapes and sizes depending on where you are and what kind of adventure you’re on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=075ce199c9c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Blogging Style: Cultivating Your Unique Voice and Navigating Criticism]]></title>
            <link>https://medium.com/@t.dasanthaedirisinghe/mastering-blogging-style-cultivating-your-unique-voice-and-navigating-criticism-688c04a8caf7?source=rss-16f0aadac7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/688c04a8caf7</guid>
            <category><![CDATA[top-10]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[writting]]></category>
            <dc:creator><![CDATA[T_DasanthaEdirisinghe]]></dc:creator>
            <pubDate>Tue, 06 Jun 2023 17:57:26 GMT</pubDate>
            <atom:updated>2023-06-06T17:57:26.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*ORGU5-eLa-Hd31PxgILFcw.jpeg" /></figure><p>In the world of blogging, your writing style plays a pivotal role in capturing readers’ attention and building a loyal following. Developing a unique and recognizable tone sets you apart from the crowd. In this article, we will explore how to cultivate your blogging voice, maintain integrity, and handle criticism with grace.</p><h3>Cultivating Your Voice</h3><p>Your blogging voice is more than just what you write — it’s how you write. To develop your voice, read other blogs and observe how successful bloggers communicate with their audience. Experiment with different writing styles and techniques to find what resonates with you and your readers. Infuse your writing with passion and enthusiasm, as the posts we love to write are often the ones that resonate most with our audience.</p><h3>Writing Passionate Posts</h3><p>To create captivating content, pay attention to what grabs your attention as a reader. Identify topics that genuinely excite you and make a lasting impression on your audience. However, be cautious not to turn passionate posts into rants. Instead, choose a specific point to discuss and develop a well-organized argument. This approach maintains clarity and helps readers connect with your perspective.</p><h3>Maintaining Integrity</h3><p>Maintaining high standards of integrity is essential for building trust and credibility with your audience. Ensure that your blog reflects truth and accuracy by diligently verifying information and getting your facts straight. Take responsibility for any mistakes and promptly correct them. Demonstrating fairness is also crucial — credit your sources appropriately and consider the potential impact of your posts on individuals and communities.</p><h3>Embracing Independence</h3><p>Transparency with your readers fosters trust and loyalty. Be open about your perspectives, affiliations, and any potential biases. Your independence as a blogger allows you to present diverse viewpoints and explore a range of topics. Engage in honest conversations and invite respectful dialogue among your readers.</p><h3>Handling Criticism</h3><p>As a blogger, it’s important to have a thick skin and navigate criticism constructively. Remember that it takes courage to share your thoughts and ideas. Monitor your comments section and learn from constructive feedback. Weigh both the positive and negative feedback, using it to improve and refine your content. However, it’s crucial not to engage with trolls or individuals seeking to provoke negativity. Recognize the privilege of having a blog and use it responsibly to create positive impact.</p><p>Developing a unique blogging voice and maintaining integrity are essential elements of a successful blog. Cultivate your voice by reading other blogs, experimenting with different styles, and injecting passion into your writing. Uphold high standards of truth, accuracy, fairness, and independence to build trust with your readers. Embrace criticism as an opportunity for growth and learning, while also recognizing the privilege and responsibility that comes with having a blog. Let your voice shine through, create meaningful connections with your audience, and continue to make a positive impact through your blog. Happy writing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=688c04a8caf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>