<?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 ilaydaGundogdu on Medium]]></title>
        <description><![CDATA[Stories by ilaydaGundogdu on Medium]]></description>
        <link>https://medium.com/@gundogduilayda04?source=rss-091a6f690f4b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lT0IfraHQBGNsPsxErrolw.jpeg</url>
            <title>Stories by ilaydaGundogdu on Medium</title>
            <link>https://medium.com/@gundogduilayda04?source=rss-091a6f690f4b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:55:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gundogduilayda04/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[What is SDLC? what are its characteristics, and what should we keep in mind?]]></title>
            <link>https://medium.com/@gundogduilayda04/what-is-sdlc-what-are-its-characteristics-and-what-should-we-keep-in-mind-1707fc295ebd?source=rss-091a6f690f4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1707fc295ebd</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[sdlc-model]]></category>
            <category><![CDATA[waterfall-model]]></category>
            <category><![CDATA[incremental-development]]></category>
            <category><![CDATA[sdlc]]></category>
            <dc:creator><![CDATA[ilaydaGundogdu]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 07:20:34 GMT</pubDate>
            <atom:updated>2026-08-21T07:08:05.972Z</atom:updated>
            <content:encoded><![CDATA[<p>If you want to build a project from scratch like me, and your mentor asked you “Have you decided on the SDLC type?” don’t panic at all. I’ll explain it to you in a very simple way. :)</p><h3>1- What is SDLC?</h3><p>SDLC (Software Development Life Cycle) is a roadmap that describes the process a software goes through from the idea stage to reaching the user and then its maintenance. It is similar to building a house: first you plan, design, build, check, deliver and then maintain it. The steps in software follow the same logic. The only difference is that each model has its own rules and you need to choose the path that best fits your project. That’s all.</p><h3>2-Why is SDLC important?</h3><p>Starting to code without SDLC is like driving a car to a city without knowing the way. If you don’t know where you’re going, you can both waste time, run out of fuel and end up in the wrong place. There are many possible bad scenarios.</p><p>Thanks to these steps, a team knows in advance what to do when to do it and what it needs. Errors are noticed at the beginning rather than at the end of the work and that is why fixing them is much cheaper. Since everyone follows the same plan, confusion is reduced and tasks don’t overlap with each other.</p><p>Also, the customer or user knows where they are in the process before seeing something concrete in their hands. So they don’t experience surprises. In short, software can be developed without SDLC but generally the work progresses in a disorganized way, errors are noticed late and in the end both time and money are lost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*eocVnZHJCemijE3XW0mW_g.png" /></figure><h3>3-SDLC consists of seven main stages:</h3><p><strong>1-Planning </strong>— The purpose, scope, and budget of the project are determined. The foundation of the work is laid here.<br>2- <strong>Requirements analysis</strong> — What the system should do is clarified. The user and customer are talked to, and the needs are listed.<br> 3-<strong>Design</strong> — The collected requirements are turned into a technical plan. How the architecture will be, how the database will be built and how the interface will look are decided here.<br>4- <strong>Coding</strong> — The stage where the actual software is written. The design comes off the paper and turns into real code.<br>5- <strong>Testing</strong> — The written system is tested, errors are found and fixed. It is checked whether everything complies with the requirements.<br>6- <strong>Deployment</strong> — The system is now made available to real users.<br>7- <strong>Maintenance</strong> — After use begins, errors that arise are fixed and small improvements are made when necessary.</p><h3>4-SDLC Models:</h3><p><strong><em>1-Waterfall model</em></strong></p><p>It is the oldest and most strict model. Planning, requirements analysis, design, coding, testing and delivery move in one direction. You don’t move to the next stage before finishing the current one and going back is almost not possible. At the end of each stage a lot of documentation is created which makes it easier to follow the project. It is generally preferred for small projects where the requirements are clear from the beginning and are not likely to change.</p><ul><li><em>Advantage:</em> It is easy to understand and manage. Who will do what and when is clear from the beginning and budget and time can be estimated clearly.</li><li><em>Disadvantage:</em> If the requirements change, the cost can become very high. Since testing is done at the end, big errors may be noticed late. The customer cannot see the product during the process.</li></ul><p><strong><em>2- V-Model</em></strong></p><p>It keeps the basic structure of Waterfall but takes one thing more seriously: testing. A testing stage is placed opposite each development stage to check it. For example, requirements analysis matches with acceptance testing, and design matches with system testing. Because of this, it is preferred for critical projects such as medical devices and flight systems where the chance of error needs to be almost zero and an error at the end of the project can cause serious problems.</p><ul><li><em>Advantage:</em> Quality control is very strong and errors can be found early. Since every development stage has a matching test stage, responsibilities are clear.</li><li><em>Disadvantage:</em> It is not flexible like Waterfall. There is a lot of testing and documentation which increases the cost.</li></ul><p><strong><em>3- Incremental Model — a model I really like using</em></strong></p><p>The entire system is not produced all at once. it is produced in functional pieces (increments). Each piece is delivered as a working, usable product on its own. then new pieces are added on top of it. In other words, the customer starts to see something in their hands before the entire system is finished.</p><ul><li><em>Advantage:</em> A working product appears at an early stage since risks are divided into small pieces, one major error does not affect the entire project. It is easier to fix the system as errors are found.</li><li><em>Disadvantage:</em> If the system architecture is not designed well from the beginning. the pieces may become disconnected from each other; if the overall scope is unclear, management can become difficult.</li></ul><p><strong><em>4- Iterative Model — another flexible model I like, and it can usually be used together with the one above</em></strong></p><p>It is close to Incremental, but its purpose is different. Here, the goal is not delivery in pieces but continuously improving the same product through repeated cycles. The requirements aren’t clear from the beginning. They become clearer with each cycle and the product takes shape accordingly. In practice, it is often used together with Incremental because one answers the question“What will I deliver?” while the other answers “How will I make it more mature?”</p><ul><li><em>Advantage:</em> It allows requirements to become clearer over time. The risk of going in the wrong direction is reduced through early feedback.</li><li><em>Disadvantage:</em> The total time and cost cannot be predicted precisely from the beginning, continuous change can cause the scope to grow uncontrollably (scope creep).</li></ul><p><strong><em>5- Spiral Model</em></strong></p><p>It’s a more cautious and more corporate version of Iterative. Before entering each cycle, a risk analysis is always performed — technical risk, budget risk, time risk, and so on. As the cycles progress, the project expands like a spiral. It is designed for large-budget, high-risk, enterprise-scale projects.</p><ul><li><em>Advantage:</em> Risk management is very strong and provides early warning in large projects. it can also adapt to changing requirements.</li><li><em>Disadvantage:</em> Risk analysis requires expertise and is expensive. it is unnecessarily heavy and complex for a small project.</li></ul><p><strong><em>6- Prototype Model</em></strong></p><p>Before writing the real system a draft or prototype is prepared that the user can try and comment on. The goal isn’t to finish the product but to turn the user’s unclear request into something concrete. The user gives feedback, the prototype is improved and this cycle continues until the requirements become clear.</p><ul><li><em>Advantage:</em> Unclear or abstract user needs are revealed early and concretely.</li><li><em>Disadvantage:</em> It requires continuous active user involvement. sometimes the user may mistake the prototype for the real system and develop incorrect expectations.</li></ul><p><strong><em>7-RAD (Rapid Application Development)</em></strong></p><p>It aims to produce a fully functional product in a very short time (usually within a few months) using ready-made components, reusable code pieces, and intensive user involvement. It’s similar to Prototype in spirit, but its purpose is different. the goal here isn’t just to test an idea but to actually produce a deliverable product.</p><ul><li><em>Advantage:</em> It provides very fast development. thanks to continuous user involvement the product comes out close to user expectations.</li><li><em>Disadvantage:</em> It only works for systems that can be made modular, intensive expert/user involvement may not be possible in every project.</li></ul><p><strong><em>8-Agile Model -one of the most famous models-</em></strong></p><p>It adds another culture on top of Iterative. Work is done in short cycles (sprints, usually 1–4 weeks), a working piece is delivered at the end of each cycle and the customer is continuously involved in the process. Not only the product but also the way of working itself is reviewed and improved in every cycle</p><ul><li><em>Advantage:</em> It adapts quickly to changing requirements. value emerges early through frequent deliveries. transparency is high.</li><li><em>Disadvantage:</em> It requires continuous and intensive stakeholder involvement. scope and budget may not be predictable precisely from the beginning and documentation may remain weak.</li></ul><p><strong><em>9- DevOps -important!!!-</em></strong></p><p>It is actually not a development sequence but a working culture. It brings the development and operations teams together under the same roof with continuous integration and continuous deployment (CI/CD) tools. updates are released automatically and very frequently (sometimes several times a day). While other models focus on the question “How do I build the product?” DevOps focuses on the question “How do I keep this product running and up to date continuously?”</p><ul><li><em>Advantage:</em> Very fast and frequent deployments can be made; automation reduces human error. the disconnect between development and operations is eliminated.</li><li><em>Disadvantage:</em> It requires a strong automation infrastructure and investment in tools. since it requires a cultural transformation, it can create unnecessary complexity in small teams.</li></ul><p><strong><em>10- Big Bang</em></strong></p><p>It’s the model at the extreme end. Development begins directly with whatever is available without serious planning. The process is based on trial and error. there is no formal structure or clear roadmap.</p><ul><li><em>Advantage:</em> It is very simple with no bureaucracy. it provides a quick start for small and experimental work.</li><li><em>Disadvantage:</em> Unpredictability and risk are very high. it is not suitable for large or critical projects.</li></ul><h3>5. Criteria to Consider When Choosing the Right Model:</h3><ul><li><strong>&gt;Clarity of requirements:</strong> If they are clear from the beginning, Waterfall/V-Model; if they become clear over time, Iterative/Agile.<br> <strong>-&gt;Project size and risk:</strong> If it is large and risky, Spiral; if it is small and experimental, Big Bang.<br> <strong>-&gt;Level of user/stakeholder involvement:</strong> If continuous involvement is possible, Agile/RAD/Prototype; if limited, Waterfall/Incremental.<br> <strong>-&gt;Time pressure:</strong> If fast delivery is required, RAD/Agile; if there is a long-term and planned process, Waterfall/Spiral.<br> <strong>-&gt;Error tolerance:</strong> If an almost zero margin for error is required, V-Model.<br> <strong>-&gt;Team experience and infrastructure:</strong> Models such as DevOps require strong automation/tool infrastructure.<br> <strong>-&gt;Budget flexibility:</strong> If the budget is fixed, predictable models (Waterfall); if it is flexible, Agile/Iterative is more suitable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KV-GEPJRKZUny-xtil45jQ.png" /></figure><p>This article was written based on my own research and notes. I want to improve my English through my writing. I hope I’ve explained the topic clearly enough. Sometimes I had to use a translator but I still tried to write it myself. I hope you enjoy it. I’d be very happy to receive your feedback, both on the topic and on my English.Thank you in advance :))</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1707fc295ebd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting React and .NET Web API:How They Talk To Each Other??]]></title>
            <link>https://medium.com/@gundogduilayda04/connecting-react-and-net-web-api-how-they-talk-to-each-other-4921e3bfc547?source=rss-091a6f690f4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4921e3bfc547</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[ilaydaGundogdu]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 18:07:02 GMT</pubDate>
            <atom:updated>2026-02-12T18:07:02.631Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*6cGNjfjqOiDZgxUxZL_0zw.png" /></figure><p>When I first started learning web development, I thought that connecting a frontend to a backend was like magic. You click a button, and suddenly data appears. But as I built my first projects using <strong>React</strong> and <strong>.NET Web API</strong>, I realized there is a very logical “bridge” between them.</p><p>In this post, I want to share what I’ve learned about how these two worlds talk to each other. If you are a student like me, this guide will help you understand the big picture.</p><h3>1. The Big Picture: Client vs. Server</h3><p>In a modern web app, we usually separate the “face” of the app from its “brain.”</p><p><strong>-&gt;React (The Client):</strong> This is the frontend. It lives in the user’s browser. It is responsible for the buttons, the forms, and the overall look.</p><p>-&gt; <strong>.NET Web API (The Server):</strong>This is the backend. It lives on a server. It handles the database, security, and complex calculations.</p><p>They talk to each other using the <strong>HTTP protocol</strong>. Think of it like a conversation: React asks a question (Request), and .NET gives an answer (Response).</p><h3>2. The Language They Speak: HTTP Methods And Json</h3><p>To make sure they understand each other, they use specific “action words” called HTTP methods. Each one has a purpose:</p><ul><li><strong>GET:</strong> “Can you show me the list of products?”</li><li><strong>POST:</strong> “I have a new user here, please save this to the database.”</li><li><strong>PUT / PATCH:</strong> “The user changed their email, please update it.”</li><li><strong>DELETE:</strong> “The user wants to remove this post.”</li></ul><p><strong>!!!</strong>The data itself is usually sent in <strong>JSON</strong> format. One common mistake here is a “naming mismatch.” For example, if React sends userName but .NET expects UserName, you might get null values. Matching these names is like a contract between the frontend and backend. !!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*ZsdrXPj1-h5uCgEk0E0Zeg.png" /></figure><h3><strong>3. The Famous CORS Policy</strong></h3><p>If you are building this for the first time, you <em>will</em> see a red error in your console called <strong>CORS (Cross-Origin Resource Sharing)</strong>.</p><p>Don’t panic! It’s not because your code is bad. It’s a security feature of the browser. Browsers don’t allow a website at localhost:3000 to talk to a server at localhost:5001 unless the server says it is okay. To fix this, you need to go to your .NET Program.cs file and add a &quot;CORS Policy&quot; to allow your React URL.</p><h3>4. Keeping it Safe with JWT (Authentication)</h3><p>We don’t want just anyone to access our API. We need a “security guard.” Most React and .NET projects use <strong>JWT (JSON Web Token)</strong>.</p><p>-When you log in, the server gives you a secret “ticket” (the token).</p><p>-React saves this ticket in the browser.</p><p>-Every time you ask for data, you send this ticket in the <strong>HTTP Header</strong>.</p><ul><li>The server checks the ticket. If it’s valid, you get the data.</li></ul><h3>5. Managing the “Wait”: Loading and Errors</h3><p>In a perfect world, the internet is always fast. In the real world, it’s not. As developers, we must handle three states in our React components:</p><p><strong>Loading State:</strong> Show a “spinner” or a loading text so the user doesn’t think the app is broken.</p><p><strong>Success State:</strong> Render the data once it arrives from the API.</p><p><strong>Error State:</strong> If the server is down or the data is wrong, show a friendly message like <em>“Sorry, we couldn’t load the data right now.”</em></p><h3>6. Helpful Tools</h3><p>While building this bridge, I found two tools very helpful:</p><p><strong>-&gt; Swagger:</strong> .NET usually has this built-in. It lets you test your API endpoints in the browser without even using React.</p><p><strong>-&gt; Postman:</strong> Great for testing different HTTP requests and seeing exactly what the server returns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*V0P0LNEPZ6LGxM5sB4Ix9w.png" /></figure><h3>Conclusion</h3><p>Building a full-stack application with React and .NET is a great learning journey. It teaches you how data flows across the internet and how to keep that data secure. It might feel complicated at first, but once you understand the HTTP “bridge,” everything starts to make sense.</p><p><strong>What about you?</strong> What was the most annoying error you faced when connecting your frontend to your backend? Let’s talk in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4921e3bfc547" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Veritabanına Dokunmadan SQL Yazmak: Entity Framework ile İlk Adım]]></title>
            <link>https://medium.com/@gundogduilayda04/veritaban%C4%B1na-dokunmadan-sql-yazmak-entity-framework-ile-i%CC%87lk-ad%C4%B1m-48164e1f88f2?source=rss-091a6f690f4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/48164e1f88f2</guid>
            <category><![CDATA[database-first]]></category>
            <category><![CDATA[code-first]]></category>
            <category><![CDATA[entity-framework]]></category>
            <category><![CDATA[dotnet-orm]]></category>
            <category><![CDATA[entity-framework-beginner]]></category>
            <dc:creator><![CDATA[ilaydaGundogdu]]></dc:creator>
            <pubDate>Fri, 24 Oct 2025 22:19:28 GMT</pubDate>
            <atom:updated>2025-10-24T22:19:28.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yb6BO3q0J1ak2bqKfA9vyQ.png" /></figure><h3>Entity Framework Nedir?</h3><p>Entity Framework, Microsoft’un geliştirdiği bir <strong>Object Relational Mapper (ORM)</strong> aracıdır. ORM kavramı, veritabanı ile uygulama kodu arasında bir köprü görevi görür. Normalde SQL sorguları yazarak yaptığımız işlemleri, Entity Framework nesneler üzerinden yapmamızı sağlar.</p><p>Örneğin bir ürün tablosuna yeni kayıt eklemek için “INSERT INTO” komutu yazmak yerine, bir Product nesnesi oluşturup kaydedersiniz. EF bu işlemi arka planda SQL’e dönüştürür ve veritabanına uygular.Bu sayede hem kod okunabilirliği artar hem de veritabanına bağımlılık azalır.</p><p>Entity Framework yalnızca <strong>.NET ekosistemi</strong> içinde, yani C#, VB.NET veya F# gibi dillerde çalışır. Java, Python veya JavaScript gibi diller kendi ORM araçlarını (Hibernate, SQLAlchemy, Sequelize gibi) kullanır.</p><h3><strong>Entity Framework Nasıl Çalışır?</strong></h3><p><em>Entity Framework’ün çalışma mantığı üç temel bileşene dayanır:</em><strong><em>Model</em></strong><em>, </em><strong><em>Context</em></strong><em> ve </em><strong><em>Migration</em></strong><em>.</em></p><p><strong>Model:</strong><br> Veritabanındaki tabloların temsilidir. Örneğin “Product” adında bir tablo varsa, bunun C# tarafında Product adında bir sınıfı bulunur. Her sütun, sınıfın bir özelliğine (property) karşılık gelir.</p><pre>public class Product<br>{<br>    public int Id { get; set; }<br>    public string Name { get; set; }<br>    public decimal Price { get; set; }<br>}</pre><p><strong>DbContext:</strong><br> Uygulama ile veritabanı arasındaki bağlantıyı yönetir.<br> Bu sınıf üzerinden tabloya erişir, yeni veriler eklersiniz, sorgular çalıştırırsınız.EF için oldukça önemlidir.</p><pre>public class AppDbContext : DbContext<br>{<br>    public DbSet&lt;Product&gt; Products { get; set; }<br>}</pre><p><strong>Migration:</strong><br> Kodda oluşturulan modelleri alıp veritabanına uygular.</p><pre>Add-Migration InitialCreate   //EF&#39;ye hangi tabloların oluşturulacağını söyler<br>Update-Database               //fiziksel olarak veritabanına yazar</pre><p>Bu yapı, <strong>Code First yaklaşımı</strong> olarak adlandırılır; yani önce kod, sonra veritabanı gelir.</p><h3>Entity Framework’ün Yaklaşımları</h3><p>Entity Framework’te üç ana yaklaşım vardır:</p><p><strong>1-Code First:</strong>Önce C# modelleri yazılır, EF bu modellerden veritabanı oluşturur.En esnek ve en yaygın kullanılan yöntemdir.</p><p><strong>2-Database First:</strong>Önce veritabanı hazırlanır, EF mevcut tabloları kod tarafına aktarır.<em>Halihazırda bir veritabanı varsa </em>tercih edilir.</p><p><strong>3-Model First:</strong>Veritabanı diyagramı görsel olarak oluşturulur, EF hem kodu hem veritabanını buradan üretir.Artık nadiren kullanılır.</p><h3>Entity Framework’ün Avantajları</h3><p>1-Kodun temiz ve anlaşılır olmasını sağlar.</p><p>2-Proje büyüdükçe veri işlemlerini yönetmek kolaylaşır.</p><p>3-Eğer SQL bilmiyorsanız,tek satır SQL yazmadan tablo oluşturabilir, güncelleyebilir veya silebilirsiniz.</p><p>4-LINQ sorguları sayesinde verilerle güçlü, okunabilir sorgular yazabilirsiniz.</p><p>5-Farklı veritabanlarına geçiş yapmak için yalnızca bağlantı cümlesini değiştirmeniz yeterlidir.</p><h3>Olası Dezavantajlar</h3><p>Her araç gibi EF’nin de bazı zorlukları vardır:</p><p>1-Çok karmaşık veya büyük veritabanlarında, performans açısından manuel SQL sorguları kadar hızlı olmayabilir.</p><p>2-Otomatik migration bazen dikkat edilmezse tablo yapısında istenmeyen değişiklikler yapabilir.</p><p>3-Geliştiricinin veritabanı yapısını temel seviyede anlaması yine de önemlidir.</p><h3>Kaynakça</h3><p><a href="https://learn.microsoft.com/en-us/ef/core/">Microsoft Docs — Entity Framework Core</a></p><p><a href="https://github.com/dotnet/efcore">Entity Framework GitHub</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48164e1f88f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redux Toolkit Nedir? Modern React Uygulamaları İçin State Yönetimi Rehberi]]></title>
            <link>https://medium.com/@gundogduilayda04/redux-toolkit-nedir-modern-react-uygulamalar%C4%B1-i%CC%87%C3%A7in-state-y%C3%B6netimi-rehberi-930a3451c900?source=rss-091a6f690f4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/930a3451c900</guid>
            <category><![CDATA[redux-toolkit]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[ilaydaGundogdu]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 20:34:49 GMT</pubDate>
            <atom:updated>2025-09-30T20:34:49.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lf8jlfYGMeuJFgqWt5h4mg.png" /></figure><p>React projeleri büyüdükçe, uygulama içindeki state (durum) yönetimi en büyük zorluklardan biri haline gelir. Kullanıcı verileri, formlar, API’den gelen içerikler derken state yapısı giderek karmaşıklaşır.</p><p>İşte bu noktada <strong>Redux</strong> devreye girer. Ancak klasik Redux yaklaşımı bolca boilerplate kod, ayrı dosyalar (action, reducer, types) ve karmaşık yapısıyla geliştiriciler için zaman zaman yorucu olabilir.</p><p>Bu sorunu çözmek için geliştirilen <strong>Redux Toolkit (RTK)</strong>, Redux’un resmi ve modern versiyonudur. Daha az kod, daha kolay kullanım ve standart bir yapı sunar.</p><p>Bu yazıda Redux Toolkit’in avantajlarını ,temel kavramlarını,adım adım kullanımını ve asenkron işlemler için sunduğu kolaylıkları ele alacağız.</p><h3>1. Redux Toolkit’in Avantajları</h3><p>Redux Toolkit kullanmanın öne çıkan faydaları şunlardır:</p><p>Daha az <strong>boilerplate kod</strong><br> Slice yapısıyla <strong>düzenli dosya yapısı</strong><br> Asenkron işlemleri yönetmek için <strong>createAsyncThunk</strong><br> Performans optimizasyonları<br> Redux DevTools desteği<br> Modern ve anlaşılır bir API</p><p>Kısacası RTK, Redux’u daha erişilebilir ve keyifli hale getirir.</p><h3>2. Redux Toolkit Temel Kavramları</h3><h4>a) Store</h4><p>Store, uygulamanın tüm state’ini saklar. RTK ile “<em>configureStore”</em> fonksiyonunu kullanmak yeterlidir:</p><pre>// store.js<br>import { configureStore } from &quot;@reduxjs/toolkit&quot;;<br>import counterReducer from &quot;./counterSlice&quot;;<br><br>export const store = configureStore({<br>  reducer: {<br>    counter: counterReducer,<br>  },<br>});</pre><h4>b) Slice</h4><p>Klasik Redux’ta <em>action</em> ve<em> reducer</em> ayrı dosyalarda yazılırken, <strong>RTK slice</strong> ile ikisini tek dosyada toplar. Böylece hem dosya sayısı azalır hem de mantıksal bütünlük korunur.</p><pre>//counterSlice.js<br>import { createSlice } from &quot;@reduxjs/toolkit&quot;; <br><br>export const counterSlice = createSlice({<br>  name: &quot;counter&quot;,<br>  initialState: { value: 0 },<br>  reducers: {<br>    increment: (state) =&gt; { state.value += 1 },<br>    decrement: (state) =&gt; { state.value -= 1 },<br>  },<br>});<br><br>export const { increment, decrement } = counterSlice.actions;<br>export default counterSlice.reducer;</pre><h4>c) Provider ile Store’u Bağlamak</h4><p>React uygulamasının tamamında store’a erişebilmek için, <em>Provider</em> ile en üst bileşeni sarmalamamız gerekir. Böylece tüm alt bileşenler state’e erişebilir.</p><pre>// main.jsx<br>import React from &quot;react&quot;;<br>import ReactDOM from &quot;react-dom/client&quot;;<br>import { Provider } from &quot;react-redux&quot;;<br>import { store } from &quot;./store&quot;;<br>import App from &quot;./App&quot;;<br><br>ReactDOM.createRoot(document.getElementById(&quot;root&quot;)).render(<br>  &lt;Provider store={store}&gt;<br>    &lt;App /&gt;<br>  &lt;/Provider&gt;<br>);</pre><h4>d) State’e Erişim ve Güncelleme</h4><p><em>useSelector</em> state’e erişim, <em>useDispatch</em> ise state güncellemek için kullanılır:</p><pre>// Counter.jsx<br>import { useSelector, useDispatch } from &quot;react-redux&quot;;<br>import { increment, decrement } from &quot;./counterSlice&quot;;<br><br>export default function Counter() {<br>  const count = useSelector((state) =&gt; state.counter.value);<br>  const dispatch = useDispatch();<br><br>  return (<br>    &lt;div&gt;<br>      &lt;h1&gt;{count}&lt;/h1&gt;<br>      &lt;button onClick={() =&gt; dispatch(increment())}&gt;+&lt;/button&gt;<br>      &lt;button onClick={() =&gt; dispatch(decrement())}&gt;-&lt;/button&gt;<br>    &lt;/div&gt;<br>  );<br>}</pre><h3>3. Asenkron İşlemler</h3><p>Gerçekte çoğu zaman kullanıcıdan form alırız, API’dan veri çekeriz veya dış servislerle haberleşiriz. İşte bu noktada asenkron işlemler devreye girer.</p><p>Klasik Redux’ta async işlemleri yönetmek için <strong><em>middleware</em></strong> (örneğin redux-thunk) eklemek gerekiyordu. Bu hem ekstra konfigürasyon ister, hem de kodun okunabilirliğini zorlaştırırdı.</p><p>RTK bu noktada <strong>createAsyncThunk</strong> fonksiyonunu sunar.</p><pre>// dataSlice.js<br>import { createAsyncThunk, createSlice } from &quot;@reduxjs/toolkit&quot;;<br><br>export const fetchData = createAsyncThunk(<br>  &quot;data/fetchData&quot;,<br>  async () =&gt; {<br>    const res = await fetch(&quot;https://jsonplaceholder.typicode.com/posts&quot;);<br>    return res.json();<br>  }<br>);<br><br>const dataSlice = createSlice({<br>  name: &quot;data&quot;,<br>  initialState: { items: [], status: &quot;idle&quot; },<br>  reducers: {},<br>  extraReducers: (builder) =&gt; {<br>    builder<br>      .addCase(fetchData.pending, (state) =&gt; { state.status = &quot;loading&quot; })<br>      .addCase(fetchData.fulfilled, (state, action) =&gt; {<br>        state.items = action.payload;<br>        state.status = &quot;succeeded&quot;;<br>      })<br>      .addCase(fetchData.rejected, (state) =&gt; { state.status = &quot;failed&quot; });<br>  },<br>});<br><br>export default dataSlice.reducer;</pre><p>Artık async işlemleri çok daha temiz bir şekilde yönetebilirsiniz.</p><h3>4. Redux Toolkit Kullanımında İpuçları</h3><p>Redux Toolkit, işleri oldukça kolaylaştırsa da, projeler büyüdükçe doğru bir yapı kurmak önemlidir. İşte işinizi kolaylaştıracak birkaç pratik ipucu:</p><p><strong>1-Slice mantığını benimseyin</strong>: Her özelliği (feature) ayrı bir slice olarak tasarlayın. Bu sayede kodunuz modüler ve okunabilir olur.<br> <strong>2-Klasör yapısına dikkat edin</strong>: Küçük projelerde tüm slice dosyaları aynı yerde durabilir, ama orta ve büyük ölçekli projelerde her feature için ayrı bir klasör (ör. features/user/userSlice.js) çok daha düzenli bir yapı sağlar.<br><strong> 3</strong>-<strong>Redux DevTools’u aktif kullanın</strong>: State değişimlerini adım adım görmek, debug sürecinde inanılmaz kolaylık sağlar. RTK, DevTools entegrasyonunu hazır olarak getirir.<br> 4-<strong>createAsyncThunk</strong> ile async işlemleri standart hale getirin.</p><h3>5. Sonuç</h3><p>Redux Toolkit, Redux’un öğrenmesi zor ve karmaşık yanlarını ortadan kaldırarak modern React projelerinde state yönetimini çok daha kolay hale getiriyor.Artık daha az kodla, daha düzenli bir yapıyla işlemleri gerçekleştirebilirsiniz.</p><p>Küçük projeler için bile kullanılabilir, büyük projelerde ise standart bir yapı ve sürdürülebilirlik sağlar.</p><p>Eğer React ile ciddi projeler geliştirmeyi düşünüyorsanız, Redux Toolkit öğrenmeniz gereken en önemli araçlardan biri.</p><h3>Kaynaklar &amp; Daha Fazlası</h3><p><a href="https://redux-toolkit.js.org/">https://redux-toolkit.js.org/</a></p><p><a href="https://github.com/reduxjs/redux-devtools">https://github.com/reduxjs/redux-devtools</a></p><p><a href="https://redux.js.org/introduction/why-rtk-is-redux-today">https://redux.js.org/introduction/why-rtk-is-redux-today</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=930a3451c900" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Projelerinde i18next ile Çoklu Dil Desteği]]></title>
            <link>https://medium.com/@gundogduilayda04/react-projelerinde-i18next-ile-%C3%A7oklu-dil-deste%C4%9Fi-521e7d909cb6?source=rss-091a6f690f4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/521e7d909cb6</guid>
            <dc:creator><![CDATA[ilaydaGundogdu]]></dc:creator>
            <pubDate>Sat, 13 Sep 2025 20:47:13 GMT</pubDate>
            <atom:updated>2025-09-13T20:47:13.904Z</atom:updated>
            <content:encoded><![CDATA[<p>Günümüzde geliştirdiğimiz uygulamalar sadece tek bir ülke ya da tek bir kullanıcı kitlesiyle sınırlı kalmıyor. Kullanıcı deneyimini güçlendiren en önemli noktalardan biri de uygulamanın farklı dillerde kullanılabilir olması. Örneğin, Türkiye’de yaşayan bir kullanıcı arayüzü Türkçe görmek isterken, Almanya’daki bir kullanıcı aynı uygulamayı Almanca kullanmak isteyebilir. Eğer uygulamamız çok dilli desteğe sahipse, bu geçişi kolayca sağlayabiliriz.</p><p>React ekosisteminde bu ihtiyacı karşılamak için en çok tercih edilen kütüphanelerden biri <strong><em>react-i18next</em></strong><em>.</em> Bu yazıda size, sıfırdan başlayarak React projenize i18n desteğini nasıl ekleyeceğinizi adım adım göstereceğim. Kurulum, yapılandırma ve dil değiştirme işlemlerini birlikte yapacağız. Yazının sonunda siz de kendi projelerinizde çok dilli desteği kolayca hayata geçirebilecek düzeye geleceksiniz.</p><h3>1. Kurulum</h3><p>İlk olarak gerekli paketleri yükleyelim:</p><pre>npm install react-i18next i18next </pre><h3>2. Dil Dosyalarını Hazırlama</h3><p>Çeviri metinlerimizi JSON dosyalarında tutacağız. Projede src/locales klasörü oluşturup her dil için ayrı bir dosya ekleyelim. Örneğin ben Türkçe ve İngilzce dil desteği sağlamak istiyorum.</p><p><em>src/locales/eng.json</em></p><pre>{<br>  &quot;welcome&quot;: &quot;Welcome to my app&quot;,<br>  &quot;change_language&quot;: &quot;Change Language&quot;<br>  &quot;hello&quot; : &quot;Hello&quot;<br>}</pre><p>Şimdi aynı adımı Türkçe için de yapmamız gerekiyor.</p><p><em>src/locales/tr.json</em></p><pre>{<br>  &quot;welcome&quot;: &quot;Uygulamama hoş geldiniz&quot;,<br>  &quot;change_language&quot;: &quot;Dili Değiştir&quot;,<br>  &quot;hello&quot; : &quot;Merhaba&quot;<br>}</pre><h3><strong>3. i18n Yapılandırması</strong></h3><p>JSON dosyalarımızı kurduktan ve kodumuzda bulunan kelimeleri belirleyip JSON dosyamızda belirledikten sonra bir i18n.jsx dosyası oluşturalım. Burada hem dillerimizi tanımlayacağız hem de i18n’in nasıl çalışacağını ayarlayacağız:</p><pre>import i18n from &#39;i18next&#39;;<br>import { initReactI18next } from &#39;react-i18next&#39;;<br>import tr from &#39;./locales/tr.json&#39;;     // JSON dosyalarımızı import ediyoruz<br>import eng from &#39;./locales/eng.json&#39;;  <br><br>const resources = {   // Dillerimizi resources içinde tanımlıyoruz<br>  tr: {<br>    translation: tr  <br>  },<br>  en: {<br>    translation: eng <br>  }<br>};<br><br>i18n<br>  .use(initReactI18next) // React ile entegrasyon<br>  .init({<br>    resources,         <br>    lng: &#39;en&#39;,         // varsayılan dil (şimdilik İngilizce seçtik)<br>    fallbackLng: &#39;en&#39;, <br>    interpolation: {<br>      escapeValue: false <br>    }<br>  });<br><br>export default i18n;</pre><h3>4. Provider Kullanımı</h3><p>Şimdi <em>index.jsx</em> dosyasında i18n’i uygulamaya dahil etmeliyiz:</p><pre>...<br>import App from &quot;./App&quot;;<br>import &quot;./i18n&quot;;<br>...</pre><p>Artık uygulama içinde <strong>useTranslation</strong> hook’unu kullanabiliriz:</p><pre>import { useTranslation } from &quot;react-i18next&quot;;<br><br>function Home() {<br>  const { t } = useTranslation();<br><br>  return (<br>    &lt;div&gt;<br>      &lt;h1&gt;{t(&quot;welcome&quot;)}&lt;/h1&gt;<br>      &lt;h1&gt;{t(&quot;hello&quot;)}&lt;/h1&gt;<br>    &lt;/div&gt;<br>  );<br>}<br><br>export default Home;</pre><p>Burada dikkat etmemiz gereken nokta:</p><p>Ekranda gösterilecek her metin artık <strong><em>{t(“…”)} </em></strong>formatında çağrılmalı.</p><p>t(“welcome”) ifadesi eng.json dosyasında tanımlı “welcome” anahtarının karşılığını getirir.</p><p>Dil değiştiğinde, <strong><em>t </em></strong>fonksiyonunu kullandığımız için metinler otomatik olarak güncellenir.</p><p>Ayrıca uygulamamızın çok dilli çalışabilmesi için sadece çeviri dosyaları eklemek yetmez. Kullanıcıya da <strong>hangi dili seçmek istediğini</strong> gösterecek bir arayüz sunmamız gerekir. Bunun için basit bir dil değiştirme butonu ekleyebiliriz.</p><h3>5.Dinamik Parametreler</h3><p>Son olarak, i18n’in dinamik parametreler özelliğine bakalım. Bazen metinler sabit olmayabilir ve içerisine değişken değerler eklememiz gerekebilir. Örneğin kullanıcı adını göstermek isteyebiliriz.</p><p><em>tr.json</em></p><pre>{<br>  &quot;hello_user&quot;: &quot;Merhaba {{name}}&quot;<br>}</pre><p><em>React componentinde kullanım</em></p><pre>function Greeting() {<br>  const { t } = useTranslation();<br><br>  return &lt;p&gt;{t(&quot;hello_user&quot;, { name: &quot;Ayşe&quot; })}&lt;/p&gt;;<br>}</pre><p>t(“hello_user”, {name: “Ayşe”}) ifadesi, JSON dosyasındaki {{name}}parametresini “Ayşe” ile değiştirir.</p><p>Böylece metinler <strong>dinamik olarak güncellenebilir</strong>, örneğin kullanıcı farklıysa isim de değişir. Bu özellik, uygulamanızın çevirilerini daha esnek ve kullanıcı odaklı hale getirir.</p><p>React projelerinize <strong>react-i18next</strong> ile çoklu dil desteği eklemek hem kolay hem güçlü bir yöntemdir. Bu yazıda: paket kurulumu, JSON çevirilerin hazırlanması, i18n yapılandırması, Provider tanımlaması ve <strong>useTranslation</strong> hook’unun kullanımı gibi temel adımları öğrendik.</p><p>Artık kullanıcılarınıza basit bir dil değiştirici ekleyerek tüm arayüz dilini anında değiştirebilirsiniz. Bu yaklaşım, uygulamanızın erişilebilirliğini artırır ve hem yerel hem global kullanıcı kitlenize hitap etmenizi sağlar.</p><h3>References</h3><p><a href="https://react.i18next.com/">Introduction | react-i18next documentation</a></p><p><a href="https://react.i18next.com/">https://react.i18next.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=521e7d909cb6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>