<?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 Sercan REYHANLI on Medium]]></title>
        <description><![CDATA[Stories by Sercan REYHANLI on Medium]]></description>
        <link>https://medium.com/@sreyhanli?source=rss-b7afc2b447e5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LnalSQrPh856dXdTFZuK2w.jpeg</url>
            <title>Stories by Sercan REYHANLI on Medium</title>
            <link>https://medium.com/@sreyhanli?source=rss-b7afc2b447e5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:17:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sreyhanli/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[Go’s Green-Tea GC: A New Architecture for the Memory Wall]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/go-lang/gos-green-tea-gc-a-new-architecture-for-the-memory-wall-37dd5e1c1036?source=rss-b7afc2b447e5------2"><img src="https://cdn-images-1.medium.com/max/1536/1*_uK_8x2C4C7GCH2QaDf22A.png" width="1536"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://medium.com/go-lang/gos-green-tea-gc-a-new-architecture-for-the-memory-wall-37dd5e1c1036?source=rss-b7afc2b447e5------2">Continue reading on Go-lang »</a></p></div>]]></description>
            <link>https://medium.com/go-lang/gos-green-tea-gc-a-new-architecture-for-the-memory-wall-37dd5e1c1036?source=rss-b7afc2b447e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/37dd5e1c1036</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[memory-management]]></category>
            <category><![CDATA[garbage-collection]]></category>
            <dc:creator><![CDATA[Sercan REYHANLI]]></dc:creator>
            <pubDate>Sat, 01 Nov 2025 17:37:57 GMT</pubDate>
            <atom:updated>2025-11-01T18:44:59.922Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Biggest npm Supply-Chain Attack Yet: What Developers Need to Know]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://sreyhanli.medium.com/the-biggest-npm-supply-chain-attack-yet-what-developers-need-to-know-b2044e73303f?source=rss-b7afc2b447e5------2"><img src="https://cdn-images-1.medium.com/max/1536/0*385L8xCsrDVXzaSh" width="1536"></a></p><p class="medium-feed-snippet">On September 8, 2025, the JavaScript world woke up to yet another reminder of how fragile our software supply chains can be. A&#x2026;</p><p class="medium-feed-link"><a href="https://sreyhanli.medium.com/the-biggest-npm-supply-chain-attack-yet-what-developers-need-to-know-b2044e73303f?source=rss-b7afc2b447e5------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://sreyhanli.medium.com/the-biggest-npm-supply-chain-attack-yet-what-developers-need-to-know-b2044e73303f?source=rss-b7afc2b447e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2044e73303f</guid>
            <dc:creator><![CDATA[Sercan REYHANLI]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 11:58:15 GMT</pubDate>
            <atom:updated>2025-09-09T12:06:45.447Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Breaking the Sorting Barrier: A New Era for Shortest Path Algorithms]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://sreyhanli.medium.com/breaking-the-sorting-barrier-a-new-era-for-shortest-path-algorithms-7cf41725f232?source=rss-b7afc2b447e5------2"><img src="https://cdn-images-1.medium.com/max/1536/0*FQXJ-IA3KNRjMTMI" width="1536"></a></p><p class="medium-feed-snippet">How researchers beat Dijkstra&#x2019;s long-standing limit with a faster approach for directed graphs</p><p class="medium-feed-link"><a href="https://sreyhanli.medium.com/breaking-the-sorting-barrier-a-new-era-for-shortest-path-algorithms-7cf41725f232?source=rss-b7afc2b447e5------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://sreyhanli.medium.com/breaking-the-sorting-barrier-a-new-era-for-shortest-path-algorithms-7cf41725f232?source=rss-b7afc2b447e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cf41725f232</guid>
            <dc:creator><![CDATA[Sercan REYHANLI]]></dc:creator>
            <pubDate>Sun, 24 Aug 2025 23:31:01 GMT</pubDate>
            <atom:updated>2025-08-24T23:31:01.411Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Do you want to become a good Software Developer ?]]></title>
            <link>https://medium.com/teamlify-devx/do-you-want-to-become-a-good-software-developer-ff62a6447aa8?source=rss-b7afc2b447e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff62a6447aa8</guid>
            <dc:creator><![CDATA[Sercan REYHANLI]]></dc:creator>
            <pubDate>Sun, 29 Jun 2025 02:05:28 GMT</pubDate>
            <atom:updated>2025-08-24T23:54:10.654Z</atom:updated>
            <content:encoded><![CDATA[<h3>Do you want to become a good Software Developer ?</h3><p><strong>I. Foundational Knowledge &amp; Skills :</strong></p><ol><li><strong>Master the Fundamentals:</strong> Don’t chase shiny new frameworks without a solid grasp of computer science principles. You should understand:</li></ol><ul><li><strong>Data Structures &amp; Algorithms:</strong> These are fundamental building blocks. Practice implementing them.</li><li><strong>Object-Oriented Programming (OOP):</strong> Encapsulation, inheritance, polymorphism. Learn to design and structure code effectively.</li><li><strong>Basic Computer Architecture:</strong> Understand how computers work at a high level (CPU, memory, I/O).</li><li><strong>Operating Systems Concepts:</strong> Processes, threads, memory management.</li><li><strong>Databases:</strong> Relational databases (SQL) are crucial. Learn to design schemas, write queries, and understand normalization. NoSQL is increasingly important as well. There is a broad product range on market, DB selection depends on project and domain !</li></ul><ol><li><strong>Choose a Language (and Become Proficient):</strong> Select a language (Python, Java, JavaScript, C#, Go, etc.) and become proficient in it. Don’t just know the syntax; understand the language’s strengths, weaknesses, and common idioms. Master language-specific libraries and frameworks. And please don’t become FAN of language (it will block you when try to learn new language!)</li><li><strong>Version Control (Git is Your Friend):</strong> Learn Git and use it religiously. Understand branching, merging, pull requests, and resolving conflicts. Use a platform like GitHub, GitLab, or Bitbucket. This is <em>essential</em> for collaboration and managing code.</li><li><strong>Understand the Software Development Lifecycle (SDLC):</strong> Learn about different development methodologies (Agile, Waterfall, Scrum, Kanban). Knowing how software is built from requirements to deployment is crucial.</li><li><strong>Testing is NOT Optional:</strong> Learn to write unit tests, integration tests, and end-to-end tests. Understand test-driven development (TDD). Automated testing is a core skill.</li></ol><p><strong>II. Practical Development &amp; Problem Solving (The Daily Grind):</strong></p><ol><li><strong>Practice, Practice, Practice:</strong> The only way to become a good developer is to write code. Solve coding challenges on platforms like HackerRank, LeetCode, Codewars, etc. Build small projects to apply your knowledge.</li><li><strong>Learn to Debug:</strong> Master debugging techniques using your IDE or command-line tools. Learn to read stack traces, identify the root cause of errors, and use breakpoints effectively. Rubber duck debugging is surprisingly helpful.</li><li><strong>Read Code:</strong> Read open-source code, code from your team members, and code from libraries you use. This is a great way to learn new techniques, best practices, and different coding styles.</li><li><strong>Design Patterns:</strong> Learn common design patterns (Singleton, Factory, Observer, etc.) to solve recurring problems in software design. Don’t just memorize them; understand <em>when</em> to use them.</li><li><strong>Write Clean Code:</strong> Follow coding conventions, write clear and concise code, and comment your code effectively. Read “Clean Code” by Robert C. Martin.</li><li><strong>Learn to Use an IDE:</strong> Master your Integrated Development Environment (IDE). Learn its shortcuts, debugging tools, refactoring features, and other productivity-enhancing features. Popular IDEs include VS Code, IntelliJ IDEA, Eclipse, and Visual Studio.</li><li><strong>Learn to Use the Command Line (CLI):</strong> Become comfortable with the command line. It’s a powerful tool for navigating file systems, running commands, and automating tasks.</li><li><strong>Embrace the “DRY” Principle (Don’t Repeat Yourself):</strong> Avoid code duplication. Write reusable code components and functions.</li><li><strong>Refactor Regularly:</strong> Don’t be afraid to refactor your code to improve its readability, maintainability, and performance.</li><li><strong>Problem Decomposition:</strong> Learn to break down complex problems into smaller, more manageable subproblems.</li></ol><p><strong>III. Learning &amp; Growth (The Constant Evolution):</strong></p><ol><li><strong>Continuous Learning:</strong> The tech landscape changes rapidly. Stay up-to-date with the latest technologies, trends, and best practices. Read blogs, attend conferences, take online courses.</li><li><strong>Seek Mentorship:</strong> Find a mentor who can provide guidance, feedback, and support.</li><li><strong>Give Back to the Community:</strong> Contribute to open-source projects, answer questions on Stack Overflow, or write blog posts.</li><li><strong>Be Curious:</strong> Always be curious about how things work. Experiment, explore new technologies, and don’t be afraid to ask “why?”.</li><li><strong>Embrace Failure:</strong> Everyone makes mistakes. Learn from your failures and use them as opportunities to grow.</li></ol><p><strong>IV. Collaboration &amp; Communication (The Team Player):</strong></p><ol><li><strong>Communicate Effectively:</strong> Be able to communicate your ideas clearly and concisely, both verbally and in writing. Learn to listen actively and provide constructive feedback.</li><li><strong>Work Well in a Team:</strong> Software development is often a team effort. Be a team player, be willing to help others, and be open to different perspectives.</li><li><strong>Learn to Document Your Work:</strong> Write clear and concise documentation for your code, APIs, and projects. This is essential for maintainability and collaboration.</li><li><strong>Ask for Help (When You Need It):</strong> Don’t be afraid to ask for help when you’re stuck. It’s better to ask for help than to waste time struggling on your own.</li></ol><p><strong>V. Beyond the Code (The Bigger Picture):</strong></p><ol><li><strong>Understand Business Needs:</strong> Software is often built to solve business problems. Understand the business context of your work and how your code contributes to the overall business goals.</li><li><strong>Security Awareness:</strong> Learn about common security vulnerabilities and how to prevent them in your code. Security should be a primary concern.</li><li><strong>Performance Optimization:</strong> Learn how to optimize your code for performance. Understand profiling tools and techniques for identifying bottlenecks.</li></ol><p><strong>VI. Essential Soft Skills:</strong></p><ol><li><strong>Time Management:</strong> Learn to manage your time effectively and prioritize tasks.</li><li><strong>Problem-Solving Skills:</strong> Sharpen your analytical and problem-solving skills. This is core to development.</li></ol><p><strong>Why This Approach?</strong></p><p>These tips are <em>essential</em> because they focus on the core principles that underpin good software development. They build a solid foundation, promote continuous learning, and emphasize the importance of collaboration and communication. While there are countless specific technologies and techniques to learn, mastering these fundamentals will serve you well throughout your career. You’ll adapt to new languages, frameworks, and methodologies much more easily if you have a strong foundation.</p><p>Remember, becoming a skilled software developer is a journey, not a destination. Be patient, persistent, and always be learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff62a6447aa8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamlify-devx/do-you-want-to-become-a-good-software-developer-ff62a6447aa8">Do you want to become a good Software Developer ?</a> was originally published in <a href="https://medium.com/teamlify-devx">teamlify-devx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>