<?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 Furkan Demir on Medium]]></title>
        <description><![CDATA[Stories by Furkan Demir on Medium]]></description>
        <link>https://medium.com/@dmrfurkan?source=rss-8f39e91a1518------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cgJJZQgMGZrkMaH8ScWu3A.jpeg</url>
            <title>Stories by Furkan Demir on Medium</title>
            <link>https://medium.com/@dmrfurkan?source=rss-8f39e91a1518------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:47:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dmrfurkan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How developer experience reflects the user experience?]]></title>
            <link>https://dmrfurkan.medium.com/how-developer-experience-reflects-the-user-experience-55b7e52895bd?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/55b7e52895bd</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Sat, 25 May 2024 21:26:27 GMT</pubDate>
            <atom:updated>2024-05-25T21:26:27.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Wm_MmNcYIhEehUQd.jpg" /><figcaption><a href="https://wallpapers.com/wallpapers/cowboy-bebop-edward-1920-x-1080-wallpaper-t50gko73pqjujzsr.html">Edward from Cowboy Bebop</a></figcaption></figure><p>Happy developers are more productive and motivated, which often results in better-designed and more user-friendly applications.</p><h3>Slow Feature iteration</h3><p>The flexibility and ease of the development environment directly affects the time it takes to deliver new features to the user. The slowdown also leads to building an unsustainable system, burnout and bugs. Here, in my opinion, we need to find a balance and know the velocity of the team/person well.</p><h3>Lack of Standards</h3><p>I can’t imagine a project without standards, it’s really bad for both the developer and the user. For example, imagine you are working in a project and you are constantly breaking things when you are implementing a new feature or an edit. This topic also includes software engineering practices that need to be applied. In short, if there are no standards, the user may encounter unexpected bugs as soon as they see and interact with it. This makes for a bad experience. It kills consistency.</p><h3>Poor Management</h3><p>It would be pointless to expect an unhappy and complaining employee to do a good and productive job. Therefore, we must constantly keep the company culture dynamic and if there are outdated cultural elements, we must eliminate them or introduce new ones. This is an issue with multiple factors. Due to the lack of management here, it is expected that the experience that the resulting work conveys to the user is incomplete or incorrect.</p><h3>Accessbility</h3><p>One of the things that should come to mind when we think of UX is that it should be usable and appeal to everyone and follow the rules. Tight deadlines cause developers to develop applications that are not accessible and do not give logical feedback to the user.</p><p>Just as we survey customers and take actions based on their feedback, we should do the same with teammates</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55b7e52895bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perfection]]></title>
            <link>https://dmrfurkan.medium.com/perfection-69b778e61da4?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/69b778e61da4</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Wed, 06 Dec 2023 00:20:58 GMT</pubDate>
            <atom:updated>2023-12-06T00:20:58.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3987-pVYChfKc8uzx8LLlQ.jpeg" /><figcaption><a href="https://unsplash.com/@maxa">Maxime Agnelli</a></figcaption></figure><p>When we develop a product, as developers, of course we try to make a project as sustainable and clean as we want it to be. Happy for the developers who work in this way. Everything I have written below applies to soloprenuers.</p><h4>Result</h4><p>You started developing the product with your favorite popular technologies. You’ve spent hours doing a few dynamic operations on a single page. Patterns, architectures, modern technologies etc. …. All you really need to do is come up with a solution in the simplest way possible.</p><p>Make the MVP version of the product first. It’s harder to make something simple.</p><h4>Validate</h4><p>Will your product actually be used by others? Test your work by sending it to your closest friends. Collect feedback from them because this is very important for you. You can send messages to people related to the topic of your project and ask them to try it out. No user cares about the quality and readability of the code. Welcome to Kansas.</p><h4>Useful</h4><p>If your work is useful, people will like it. They may even pay you for it.</p><blockquote>People without dirty hands are wrong. Doing something makes you right.</blockquote><h4>Time and Things to Do</h4><p>You can keep a single file of what you are going to do about the project. Since you are working alone, task management applications will not be very useful. If a product takes more than 1 week to develop, it may be something you can’t do alone. Try to collaborate with others.</p><h4>Know when to stop</h4><p>Programming is like painting: you start with a blank canvas, create with a mix of science and art, constantly revise your work, and start again when necessary. But too much detail can spoil the work.</p><blockquote>Accept that everything is a draft. It helps to get it done.</blockquote><p>What I have written above are the conclusions I have drawn from my own experience. It can change at any time. And it should be.</p><blockquote>Done is the engine of more.</blockquote><p>Influenced by Cult of Done Manifesto.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69b778e61da4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Type-Safe Pattern Matching with React]]></title>
            <link>https://dmrfurkan.medium.com/type-safe-pattern-matching-with-react-17fb057d85c3?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/17fb057d85c3</guid>
            <category><![CDATA[pattern-matching]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[rendering]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 01:30:41 GMT</pubDate>
            <atom:updated>2023-10-01T01:36:34.284Z</atom:updated>
            <content:encoded><![CDATA[<h4>As we develop new UIs, you know how difficult conditional rendering can sometimes be. Sometimes we are faced with too many nested conditions. Thanks to the pattern matching approach, we can handle this problem in a more sustainable way.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9c8ty1B8ZyCjI1aaQHCfQw.jpeg" /><figcaption>example of turkish rug with beautiful patterns</figcaption></figure><p>Pattern matching is not a fresh concept in so many languages. It’s an alternative to using long “if-else” branches and offers a succinct approach towards decision-making processes in the codebase. Let’s compare it with a traditional React conditional rendering, then illustrate how ts-pattern can offer a better solution.</p><p>Consider a straightforward case in React, an application that fetches user data from an API. Rendering depends on the data’s state, which can switch between ‘loading,’ ‘loaded,’ and ‘error.’ Typically, you would employ conditional rendering using JavaScript’s if-else statements:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/789f5d39856e9e4ac10cd64cd1064d46/href">https://medium.com/media/789f5d39856e9e4ac10cd64cd1064d46/href</a></iframe><p>Although this solution is enough for this simple case, maintaining the code in more complex scenarios, where multiple factors affect your component’s rendering, may feel like extra work. With numerous conditional branches, there’s a risk of missing a condition or improperly nesting them.</p><p>Now, let’s see how applying ts-pattern can lead to more readable and manageable code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b120345fee5107492bc50a440b49232/href">https://medium.com/media/9b120345fee5107492bc50a440b49232/href</a></iframe><p>Using the ts-pattern, the code appears cleaner and is easier to read and maintain. It has enhanced type safety because ts-pattern uses TypeScript’s static typing system to check the exhaustiveness of pattern matches at compile time.</p><p>By the way, exhaustiveness means that you’ve written code to handle all the potential values that variable can have. If you’ve covered all the cases, your code is considered exhaustive.</p><p>It reminds me of Rust.</p><p>ts-pattern allows writing clean, type-safe, and more concise code by substituting extensive conditional branches with pattern-matching. The real potential surfaces in scenarios involving more complex conditional renderings in your React application. Exploring ts-pattern can undoubtedly augment TypeScript’s power in writing robust, error-free code and aid in maintaining the codebase with more comfort and confidence.</p><p><a href="https://github.com/gvergnaud/ts-pattern">GitHub - gvergnaud/ts-pattern: 🎨 The exhaustive Pattern Matching library for TypeScript, with smart type inference.</a></p><p><a href="https://www.npmjs.com/package/ts-pattern">https://www.npmjs.com/package/ts-pattern</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17fb057d85c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On writing documentation, while making software]]></title>
            <link>https://medium.com/getir/on-writing-documentation-while-making-software-a16c667d1520?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/a16c667d1520</guid>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 20:55:29 GMT</pubDate>
            <atom:updated>2023-01-16T09:05:14.177Z</atom:updated>
            <content:encoded><![CDATA[<h4>Maximizing efficiency and minimizing errors through documentation-driven development</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*4P9mTVyOHch0ZS34" /></figure><p>Creating documentation is one of the essential parts of software development. To be honest, documenting things is hard. The main purpose is always going to be ‘getting things done’. While completing given tasks, there has to be a time frame for creating some documentation. So, why are we wasting time writing documents rather than implementing the feature?</p><p>There is an efficient and useful approach called <strong>Documentation-driven development</strong>. It dictates you prepare documentation before or alongside the actual code. You simply create documentation that contains every aspect, detail, and usage of your implementation. It helps to ensure that all stakeholders have a clear understanding of what the code is intended to do, how it should work, and how it fits into the overall project.</p><p><strong>If it’s not documented, it doesn’t exist.</strong></p><p>The team or the person who develops the product cannot be sure how the software works without having documentation while adding a feature to it or inspecting it. Well-written documentation can serve as a reference for developers as they are writing and testing the code. This can save time and effort, as developers do not have to constantly switch between the code and other materials to understand what they are working on.</p><p><strong>Single source of truth</strong></p><p>Having a single source of truth is important because it helps to ensure consistency and accuracy across all aspects of the project. By using a single, authoritative source of information, developers and other stakeholders can avoid misunderstandings and conflicts, and work together more effectively towards a common goal.</p><p>It could be the project’s design document, specifications, or other forms of documentation. It is important to keep this source up-to-date and accurate and to use it as the basis for all decisions and actions related to the project.</p><p><strong>README File</strong></p><p>A good way to start off with your code is by creating a README file. The README is an essential piece of documentation for your code, as it provides an overview of what your code is all about and its main purpose. This is important, as it can be difficult to convey the purpose of your code through code comments alone. By having a clear and concise README, you can give others a quick and easy way to understand the purpose and functionality of your code.</p><p>It shows the big picture of the software’s architecture and functionality. This document should include information about the main parts of the system, how they will work together, any important facts that will affect how the code is designed, what are the main packages or patterns of the project.</p><p><strong>Easy onboarding for newcomers</strong></p><p>If you join a company that has well-documented resources, it feels like being in heaven. Documentation-driven development can have a positive effect on the onboarding process for newcomers by providing clear, concise information about the project and how to contribute. This can help reduce the time it takes for newcomers to become productive members of the team and serve as a reference as they continue to work on the project.</p><p>So, the preferred order of operations for new features is:</p><ul><li>Write documentation</li><li>Get feedback on documentation</li><li>Test-driven development (where tests align with documentation)</li><li>Push features to staging</li><li>Functional testing on staging, as necessary</li><li>Deliver feature</li><li>Publish documentation</li><li>Increment versions</li></ul><p><strong>Documentation-driven development </strong>can help improve communication, collaboration, and understanding within a development team, which can ultimately lead to better code and a more successful project.</p><p><strong>Thanks for reading!</strong></p><p><strong>References:</strong></p><ul><li><a href="https://gist.github.com/zsup/9434452">https://gist.github.com/zsup/9434452</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a16c667d1520" width="1" height="1" alt=""><hr><p><a href="https://medium.com/getir/on-writing-documentation-while-making-software-a16c667d1520">On writing documentation, while making software</a> was originally published in <a href="https://medium.com/getir">Getir</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing an HTTP Proxy for Rest API in Next.js]]></title>
            <link>https://medium.com/better-programming/implementing-an-http-proxy-for-rest-api-in-next-js-65cdcd18fb73?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/65cdcd18fb73</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Sat, 02 Apr 2022 14:46:49 GMT</pubDate>
            <atom:updated>2022-04-05T11:11:56.577Z</atom:updated>
            <content:encoded><![CDATA[<h4>Wouldn’t be great if your back-end service is hidden from public users and other various malicious attacks? There is a way to empower your communication with back-end services from Next.js</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUS86vtcQN9mDUjddmD-Ow.png" /><figcaption>Source: undraw.co</figcaption></figure><p>Security must be one of your most important concerns when building a web application. Usually, you don’t want to expose the sensitive data of your users.</p><p>Most modern web applications authenticate with tokens. Tokens should be stored by the client to send requests after. There is plenty of way of storing a user’s token in the user’s browser. However, the most popular way to keep all types of tokens in local storage or normal cookies. Unfortunately, it’s not the safest place to store tokens.</p><p>Local storage and normal cookies both of them can be accessed from third-party scripts and browser extensions. I’ll be talking about storing the token at cookies as HttpOnly.</p><h3>Why do you have to use HttpOnly cookies to store the tokens?</h3><p>HttpOnly cookies can’t be accessed via client-side JavaScript code. Therefore, browser extensions and any JavaScript code that runs on the client-side cannot access those cookies. Thus, your JWT or something else is secure and safe. Finally.</p><p>Using an HTTP proxy doesn’t come just from secure cookies. It also provides security advantages — even if a cross-site scripting (XSS) flaw exists, and a user accidentally accesses a link that exploits the flaw, the browser will not reveal the cookie to the third party.</p><h3>Designing API Proxy</h3><p>Before we write the code I’ll share the flow with you. We are going to make two different endpoints for the BFF. The first one is only to handle login operations. The second one will be used to forward all requests to the actual API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IabxTTUntP3uO3lOuprr8A.png" /><figcaption>login flow</figcaption></figure><p>The flow above indicates how the login endpoint works. In fact, we can implement it all in a single point. It doesn’t make sense to keep all logic in a single file. Because of that, I’ve <a href="https://en.wikipedia.org/wiki/Separation_of_concerns">separated</a> login logic to somewhere else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GeDxmENNsG6lbcfBsXmjw.png" /><figcaption>communicating with BFF with proxy after authentication</figcaption></figure><h3>Implementing API Proxy</h3><p>In this step, we will add and enable the API proxy. We must create a proxy server to forward the requests to the target resource.</p><h4><strong>0. Set up environment variables</strong></h4><p>You must define some environment variables before starting. Create a file named .env in the root directory if you don’t have one. We are going to get our back-end service URL from env variables.</p><p>Note: <em>We shouldn’t prefix the env variable with NEXT_PUBLIC_* to avoid </em><a href="https://nextjs.org/docs/basic-features/environment-variables#exposing-environment-variables-to-the-browser"><em>exposing it to the browser</em></a><em>.</em></p><pre>SERVICE_URL=http://localhost:8000/api</pre><h4><strong>1. Install http-proxy and cookies package as a dependency</strong></h4><p>We need http-proxy to create a proxy server and the cookies package to deal with cookies.</p><pre>npm install http-proxy cookies</pre><h4><strong>2. Create a proxy server</strong></h4><p>You must create a proxy server instance to use API routes. Firstly, create a folder called serverin your root directory. This folder contains all your server kinds of stuff etc. Just in case, you can set up your own custom server in this folder.</p><p>After you’ve created the server folder. Create a folder called proxy.js in /server directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6cd0c445f90f316a43795ba1007f534/href">https://medium.com/media/e6cd0c445f90f316a43795ba1007f534/href</a></iframe><h4><strong>3. Implement login endpoint</strong></h4><p>You have to create an endpoint to handle login operations. I assume you have an authentication service to sign in to the users. To achieve that, create a folder called api the pages folder. This folder contains routes.</p><p>After you’ve completed these steps. You have to create a route file called login.js in your api/authfolder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/181ad8e69a2c0d420bab3a6a97b0da10/href">https://medium.com/media/181ad8e69a2c0d420bab3a6a97b0da10/href</a></iframe><h4><strong>4. Implement API proxy</strong></h4><p>We need an entry point to forward the requests to the target resource. To do that we will create a file called [..path].js under the api folder that we’ve created. This route will handle all endpoints after comes /api prefix.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/389068a217bed78472c959a3a1d77ccf/href">https://medium.com/media/389068a217bed78472c959a3a1d77ccf/href</a></iframe><p>That’s it. You are ready to use your proxy server. In fact, you can add some features to this implementation. I’ve also added a logout API route. I’ve prepared a demo. You can view it from Github.</p><ul><li><a href="https://github.com/fdemir/next-proxy">Demo Project on Github</a></li></ul><h3>Caveats</h3><p>This feature comes with all disadvantages and advantages actually. Since we’re using the proxy to communicate BFF. That leads to an increase in TTFB time. Also, the setup and maintenance of a proxy server can be costly.</p><p>Thank you for reading this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65cdcd18fb73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/implementing-an-http-proxy-for-rest-api-in-next-js-65cdcd18fb73">Implementing an HTTP Proxy for Rest API in Next.js</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>
        <item>
            <title><![CDATA[Kötü kod yazmak]]></title>
            <link>https://dmrfurkan.medium.com/k%C3%B6t%C3%BC-kod-yazmak-2e0487a5aa45?source=rss-8f39e91a1518------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e0487a5aa45</guid>
            <category><![CDATA[yazılım-geliştirme]]></category>
            <category><![CDATA[teknoloji]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[programlama]]></category>
            <category><![CDATA[kodlama]]></category>
            <dc:creator><![CDATA[Furkan Demir]]></dc:creator>
            <pubDate>Fri, 21 Jan 2022 16:30:23 GMT</pubDate>
            <atom:updated>2022-03-25T16:10:06.977Z</atom:updated>
            <content:encoded><![CDATA[<p>Her yazılımcının temel amaçlarından biri sürdürülebilir, ölçeklenebilir, anlaşılabilir ve prensiplere uygun clean(temiz) kod yazmaktır. Kötü kodun tanımını birçok şekilde yapabiliriz. Bu yazıda teknik konulara girmeden acemi geliştiriciler üzerinden neden kötü kod yazdığımızdan, bize kazançlarından ve etkilerinden bahsedeceğim.</p><p>İlk yazım olduğundan dolayı saçmalama olasılığım biraz yüksek olabilir. Aklımdakileri stream etmek başlangıçta çok mantıklı geliyor. E öyle kalsın.</p><p>Genellikle, bir işi en hızlı ve genellikle verimsiz yoldan halledebilmek için, gelecek geliştirmeleri göz önünde bulundurmadan yazılan kod parçacığına kötü kod denir. Yazılımda nadiren geleceğin ne getirebileceğini bilebiliriz. Tamamen bilseydik sıkıcı olurdu. Olayın en eğlenceli tarafı da bu!</p><p>Kötü kod yazmamızın genel sebepleri:</p><ul><li>Kullanılan teknolojiye hakim olmamak</li><li>Kullanıcıyı iyi tanıyamamak</li><li>Veri büyüklüğünü tahmin edememek</li><li>İyi kod yazmanın düşünce yapısını oturtamamak</li><li>Bilinmeyenlerin bilinmeyenleri</li></ul><p>Aslında, kötü kod yazmanız iyi bir şeydir. Bunun hakkında kötü hissetmemelisiniz. Kötü veya irite hissettmek yerine yaşayacağınız entelektüel heyecanın keyfini çıkarın. Yazdığınız kod üzerinden yaşayacağınız hatalar aslında sizin için hazırlanmış derslerden oluşur. Bu dersler sayesinde en hızlı şekilde yeni şeyler öğrenip öğrenme kapasitenizi ve kabiliyetinizi geliştirmiş olursunuz. Unutmayın, ders siz öğrenene kadar devam eder. _Sürekli olağan sabit bir öğrenme alanından bahsediyorum._</p><blockquote>Daha fazla kötü kod yazmak, daha fazla neyin mümkün olduğunu görmemi sağlıyor.</blockquote><p>Bütün acemi geliştiriciler için bir önerim var. Kod yazın, sürekli yazın, ne geliştirdiğinizin pek bir önemi yok. Yeter ki sizi değerli kılsın ve geliştiğinizi hissedin. Ne kadar kötü olduğunun bir önemi yok. Ortaya koyduğunuz ürün çok utanç verici ve kötü olabilir. Çalışır hale getirin ve daha doğru şekilde çözümlemeye çalışın.</p><h3>Sonuç</h3><p>Çok fazla kıdemli geliştirici bu konu hakkında “yapılmalı” dedikleri prensiplerden ve yöntemlerden bahsediyorlar. Fakat emin olun onlar da acemi zamanlarında inanılmaz derecede kötü kod yazdılar. Daha fazla kişinin işleri batırmaması için şu an framework(yazılım çatısı) ve çeşitli standartları ortaya koyuyorlar.</p><p>Böbürleneceğiniz bir konudan ziyade kötü veya ezik hissetmemenizi anlatmaya çalıştım.</p><figure><img alt="Keep learning!" src="https://cdn-images-1.medium.com/max/668/0*BPI6y3NuNTejKRxm.jpg" /><figcaption>Keep learning!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e0487a5aa45" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>