<?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 Ali Raza on Medium]]></title>
        <description><![CDATA[Stories by Ali Raza on Medium]]></description>
        <link>https://medium.com/@thealiraza?source=rss-2f4ef1372d9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r0NQcIkNNbprpv9FnlXTNA.png</url>
            <title>Stories by Ali Raza on Medium</title>
            <link>https://medium.com/@thealiraza?source=rss-2f4ef1372d9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:26:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thealiraza/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[Yes, you can prevent the use of stolen JWTs]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://thealiraza.medium.com/yes-you-can-prevent-the-use-of-stolen-jwts-9d9ebbf8f634?source=rss-2f4ef1372d9b------2"><img src="https://cdn-images-1.medium.com/max/1456/0*VCWwy1g1uNpFG8sc.png" width="1456"></a></p><p class="medium-feed-snippet">We all know that OAuth access tokens are stateless, bearer credentials, and anyone who possesses them can perform the permissions granted&#x2026;</p><p class="medium-feed-link"><a href="https://thealiraza.medium.com/yes-you-can-prevent-the-use-of-stolen-jwts-9d9ebbf8f634?source=rss-2f4ef1372d9b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://thealiraza.medium.com/yes-you-can-prevent-the-use-of-stolen-jwts-9d9ebbf8f634?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d9ebbf8f634</guid>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 09:32:00 GMT</pubDate>
            <atom:updated>2026-08-09T09:32:00.085Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to transition from frontend to backend development: A complete roadmap.]]></title>
            <link>https://levelup.gitconnected.com/how-to-transition-from-frontend-to-backend-development-a-complete-roadmap-e061228aef23?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e061228aef23</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[backend]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Mon, 17 Mar 2025 21:33:54 GMT</pubDate>
            <atom:updated>2025-03-19T13:37:34.942Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog was originally published on my <a href="https://solutionsarchitect.substack.com/p/how-to-transition-from-frontend-to">substack blog.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*jbRyqgU4s6hvX-jxLl1GEw.png" /></figure><p>You are a front-end developer who wants to learn and build backend systems and become a full-stack developer.</p><p>I am writing a step-by-step guide with topics at each level and projects you should build instead of bombarding you with backend terms and topics.</p><p>By following this guide, you will know the important topics at each stage, such as beginner and medium level, and what projects to build to implement theoretical concepts.</p><blockquote><em>At my job, I have trained tens of interns and transitioned front-end developers into back-end engineers.</em></blockquote><h3>So, how do we do it?</h3><ol><li>I will first enlist the topics you need to learn and the subtopics. You can use YT boot camps, courses, and books of your own choice, but I have shared my suggestions at the end.</li><li>A project with implementation will be mentioned at the beginner and intermediate levels so that you know what to build in the beginning.</li><li>New and slightly advanced concepts will be introduced gradually so that you can learn those and implement them in existing projects.</li></ol><p>Before moving ahead, I assume you are already skilled in JavaScript as a front-end developer.</p><h3>Roadmap</h3><p>You first need to learn some basic concepts related to backend development. These concepts will remain the same irrespective of the programming language or framework.</p><h3>General Backend Concepts</h3><ol><li>HTTP/HTTPS</li><li>SSL/TLS Encryption</li><li>TCP vs UDP</li><li>How does the server work?</li></ol><h3>Overview of APIs</h3><ol><li>What are RESTful APIs?</li><li>CORS</li><li>HTTP methods.</li><li>Status codes</li><li>Idempotency</li><li>OpenAPI Specification</li><li>API payload validation</li><li>API Versioning</li></ol><h3>Security</h3><ol><li>Concept of Authentication and Authorization</li><li>OAuth 2.0: overview, what it is, and how it works?</li><li>JWT: What it is and how it works?</li><li>Understanding of Session Cookies</li><li>HTTP-only cookies</li><li>Encryption</li><li>Hashing</li></ol><p>By now, you have understood some concepts. Now, let’s move to <strong>Node.js</strong> to get our hands dirty.</p><h3>Why choose Node.js to write the first backend code?</h3><p>As you are already familiar with JavaScript, it will be much easier and more more convenient to implement the concepts you learn across.</p><p>If another programming language is chosen, it will take you some time to learn the syntax and concepts. So, we will skip all those steps here.</p><h3>Node.js essentials concept</h3><ol><li>Basics of Node.js</li><li>Spinning up a Node.js server</li><li>Create an API endpoint, send some dummy JSON responses, and call your first API from Postman.</li></ol><p>Congratulations. You have achieved something meaningful now.</p><p>Let’s now move to databases.</p><h3>Database</h3><ol><li>Basics of DB, what it is, etc.</li><li>Pick MongoDB or PostgreSQL and read a little bit about it.</li><li>Learn concepts of schemas, relationships, unique constraints, indexing, etc.</li><li>Overview of commands for operations such as insert, update, delete, and get and play with these in the database console.</li><li>Add the database to your project; add services for CRUD operations.</li></ol><h4>Create a basic user management service</h4><p>Now, we will build a minimal user service to implement the authentication and authorization, encryption, and hashing concepts we have learned.</p><ol><li>Install JWT in the project.</li><li>Add an API for creating users and hash passwords and save them in the database.</li><li>On login, return the JWT.</li></ol><p>For read, update, and delete endpoints, create a middleware and verify the JWT.</p><h4>Build a task to-do list project</h4><ol><li>Design a DB model/schema for your project without taking help from the internet for objects, at least.</li><li>Create CRUD endpoints for to-do list items and add them to the database.</li><li>Implement middleware for payload validation and authorization.</li><li>Implement sign-up and sign-in support.</li></ol><p><strong>Congratulations!</strong> You have built the basic backend of an app that can be integrated with the frontend.</p><p>Before moving ahead, build a lot of APIs using the stuff you have learned so far. Some of the projects are:</p><p><strong>URL shortener</strong></p><ol><li>CRUD APIs.</li><li>Dashboard for analytics</li><li><strong>Expense tracker</strong></li></ol><p>After building these projects, I hope that you have fully grasped the basic concepts.</p><p>Now, we will move ahead and learn some new concepts on top of existing knowledge.</p><h3>APIs</h3><ol><li>GraphQL APIs and comparison with RESTful ones.</li><li>Rate-limiting and throatling-related concepts and implementations</li><li>Pagination &amp; filtering</li><li>RBACs: Role-Based Access Controls</li></ol><h3>Architectural Patterns</h3><ol><li>concurrency, parallelism and Multi-threading</li></ol><h3>Caching</h3><ol><li>Concepts of caching</li><li>Strategies such as Cache-Aside, Write-Through, Write-Behind, Read-Through</li><li>Redis: data structures and their usage</li><li>Cache eviction strategies</li></ol><h3>Database</h3><ol><li>ACID properties</li><li>Transactions</li><li>Query Optimizations</li><li>ORMs</li></ol><h3>Real-time data</h3><ol><li>Server-Sent Events</li><li>Websockets</li><li>Polling</li><li>Webhooks</li></ol><h3>Monitoring &amp; Logging</h3><ol><li>APM: Overview</li><li>Monitoring &amp; SLAs: What are 999999s, etc?</li><li>Explore Sentry and other open-source tools such as Grafana and Prometheus.</li></ol><h3>Cloud &amp; Networking</h3><ol><li>IP Addressing &amp; Subnetting (IPv4, IPv6)</li><li>DNS Basics (How domain names resolve)</li><li>Sockets &amp; Ports (How services communicate)</li><li>Firewalls &amp; NAT (Basic security and network translation)</li><li>Network Performance Optimization (Keep-Alive, Pipelining, QUIC)</li></ol><h3>Deploying the App</h3><ol><li>Overview of CI/CD process</li><li>Basics of docker</li><li>Image creation</li><li>Running docker container</li><li>Deploying on Heroku/Render</li></ol><p>Hopefully, you have understood these concepts by now and have practised a little bit. But now, you will build some projects to implement the concepts.</p><p>By this time, you can add Express/Nest to your project as the Node.js framework.</p><h3>e-commerce store</h3><p><strong>Storefront</strong></p><ol><li>implement pagination and filtering.</li><li>introduce OAuth using Google or Facebook Sign-in</li><li>Add cart and checkout functionality with database transactions and ACID properties.</li><li>Optimize the listing and get single product API queries.</li><li>Write a rate-limiting middleware in your app to restrict API usage.</li></ol><p><strong>Store Management</strong></p><ol><li>CRUDs for store owners to add products</li><li>Implement RBAC for different roles, such as admin, read-only, etc.</li><li>Save randomly fetched data in Redis and with caching strategies as per the use case.</li><li>Provide support for a merchant to fetch or upload details in CSV files and implement a child thread in Node.js to perform some operations on the files.</li><li>Any e-commerce application use case you can think of.</li><li>Containerize your app and deploy on Render/Heroku.</li></ol><h3>Realtime Chat Application</h3><ol><li>Implement WebSockets for messaging</li><li>Add JWT or OAuth 2.0 for AuthN/AuthZ.</li><li>Save messages in Redis.</li><li>Use Redis for leaderboard analytics for any use case, such as someone who gives instant replies.</li><li>Containerize your app and deploy on Render/Heroku.</li></ol><p>For monitoring and logging, I will suggest sticking with <strong>Sentry,</strong> as it’s a managed service with a free trial available.</p><p>Congratulations on reaching this point! You have learned and implemented essential concepts of backend development, from security to database to deployment.</p><p>Before moving ahead, I will suggest building the projects and APIs using the tech we have just discussed.</p><p><em>It’s time to introduce some advanced concepts and patterns.</em></p><h3>Event-driven Approach</h3><ol><li>Overview of event-driven approach</li><li>Understanding of producers and consumers</li><li>Event Brokers and Queues</li><li>Architectural approaches</li><li>Pub/Sub Model</li><li>CQRS (Command Query Responsibility Segregation)</li></ol><p>I suppose that you have been using a service-based approach while calling different sub-services.</p><p>Now, we will replace the synchronous approach with an event-based approach and make these modifications to your project.</p><h4>Replace synchronous flows with an event-based approach in the projects</h4><h4>1. e-commerce</h4><p>There are multiple services in your e-commerce project, such as:</p><ol><li>cart</li><li>products</li><li>checkout</li><li>customers</li></ol><p>to name a few.</p><p>Here, we will implement a basic consumer/producer pattern.</p><p>When a customer checks out, the events should be pushed to product and customer service to update the inventory and customer purchase history.</p><p>You can implement other use cases, such as payment notifications, abandoned carts, etc.</p><h4>2. URL Shortener</h4><p>You can implement analytics using the event-driven approach that whenever a URL is opened, the user performs some action or closes, you can trigger a notification and show it in analytics.</p><p>By this time, you have got your hands dirty on the surface of most of the things.</p><p>Now, before moving any further, you need to build some more projects around it and implement all that you have learned so far.</p><p>Let’s move to some advanced concepts. I am pretty sure you will be getting these used in actual jobs and production environments with real users.</p><h3>Architectural Styles</h3><ol><li>Monolith</li><li>Modular Monolith</li><li>Microservices and its patterns</li><li>Serverless Architectures</li></ol><h3>Scalability</h3><ol><li>Horizontal vs vertical scaling</li><li>Loadbalancing: concept, algorithms and tools</li><li>Database</li><li>Sharding</li><li>Partitioning</li><li>Replication and related use cases</li><li>CAP Theorem</li></ol><h3>Fault Tolerance and High Availability</h3><ol><li>Circuit Breaker Patterns</li><li>Choas Engineering</li><li>Auto-scaling principles</li></ol><h3>Misc.</h3><ol><li>gRPC, protobuf</li><li>Intrusion Detection &amp; Prevention system with SEIM</li><li>Service Mesh</li><li>DDoS Mitigation Techniques</li></ol><h4>You can build the following projects to implement your learning.</h4><ol><li>Notification systems like Instagram and LinkedIn.</li><li>Real-time trading systems</li><li>Personalization/Recommendation Engines</li><li>AI-based chatbots with LLM</li></ol><p>Once you have built these projects, you have learned enough of the backend concepts to think and build something on your own.</p><p>Although these will be some basic projects, they will help you to transition to backend projects easily.</p><h3>When should I learn a new language?</h3><p>Once you have mastered these concepts using Node.js and built projects, then you can transition to Python or preferably Golang.</p><h3>Courses and tutorials I recommend:</h3><ol><li><a href="https://www.udemy.com/course/nodejs-the-complete-guide/?couponCode=ST11MT170325G1">NodeJS — The Complete Guide (MVC, REST APIs, GraphQL, Deno)</a></li><li><a href="https://www.udemy.com/course/understanding-nodejs-core-concepts/">Understanding Node.js: Core Concepts</a></li><li><a href="https://www.udemy.com/course/fundamentals-of-backend-communications-and-protocols/?couponCode=ST11MT170325G1">Fundamentals of Backend Engineering</a></li><li><a href="https://www.nodejsdesignpatterns.com/">Node.js Design Patterns</a></li></ol><p>Cheers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e061228aef23" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/how-to-transition-from-frontend-to-backend-development-a-complete-roadmap-e061228aef23">How to transition from frontend to backend development: A complete roadmap.</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Mechanical Engineer to Software Architect within 5 years]]></title>
            <link>https://javascript.plainenglish.io/from-mechanical-engineer-to-software-architect-within-5-years-6b436ba87664?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b436ba87664</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 24 Dec 2023 11:08:48 GMT</pubDate>
            <atom:updated>2023-12-28T15:16:24.216Z</atom:updated>
            <content:encoded><![CDATA[<h3>How did I transition into the software engineering field after graduating from mechanical engineering?</h3><figure><img alt="From Mechanical Engineer to Software Architect within 5 years" src="https://cdn-images-1.medium.com/max/1024/1*QmqwIrCNht26mVMxch-t_g.png" /></figure><p>I am currently working as a software architect at and leading <a href="https://www.xstak.com/xpay">Xstak XPay</a>, a cutting-edge payment orchestration platform, building a universal API for payments.</p><p>I studied mechanical engineering at the university and later switched my career to software engineering.</p><p><strong><em>And it all started with a Google search.</em></strong></p><h3>Motivation behind transition</h3><p>Five years ago, in late 2018, I wanted to build a mobile app and thought it was some super technical stuff. I just did a Google search, only to find that all it needs is an Android Studio and a programming language.</p><p>I was dissatisfied with the opportunities available in the local market for mechanical engineers.</p><p>So, I decided to give a shot to software engineering for ample growth and learning opportunities.</p><blockquote>I have an attitude and belief that I can learn anything from any field by studying and putting in hours.</blockquote><p>In this article, I will share my journey and how you can grow in your career.</p><h3>My roadmap towards becoming a Software Engineer</h3><p>So, I started exploring software engineering and found that it is easier to get with the MERN stack.</p><p><strong>I did two things to make a learning path:</strong></p><ol><li>Enlisting all the important topics and concepts related to technologies such as HTML, CSS, JavaScript, React, Node, etc.</li><li>Go through the interview questions and note down the topics and levels of difficulty.</li></ol><p><strong>I learned all the concepts this way:</strong></p><ol><li>First, learn the basics of the topic.</li><li>Practice and build using that knowledge.</li><li>Learn advanced concepts related to that topic.</li></ol><p>Following this path, I built basic webpages, then added interaction using JS and moved to more complex projects such as building clones, etc.</p><h4>I used the following resources:</h4><h4><strong>HTML/CSS courses:</strong></h4><ol><li><a href="https://www.udemy.com/course/design-and-develop-a-killer-website-with-html5-and-css3/">https://www.udemy.com/course/design-and-develop-a-killer-website-with-html5-and-css3/</a></li><li><a href="https://www.udemy.com/course/advanced-css-and-sass/">https://www.udemy.com/course/advanced-css-and-sass/</a></li></ol><p><strong>JavaScript courses:</strong></p><ol><li><a href="https://www.udemy.com/course/the-complete-javascript-course/">https://www.udemy.com/course/the-complete-javascript-course/</a></li><li><a href="https://www.udemy.com/course/modern-javascript-from-the-beginning/">https://www.udemy.com/course/modern-javascript-from-the-beginning/</a></li><li><a href="https://www.udemy.com/course/javascript-advanced/">https://www.udemy.com/course/javascript-advanced/</a></li><li><a href="https://www.udemy.com/course/understand-javascript/">https://www.udemy.com/course/understand-javascript/</a></li></ol><p><strong>ReactJS courses:</strong></p><p>Honestly, I didn’t know anything about React or any other library until I started looking for gigs and freelance projects.</p><ol><li><a href="https://www.udemy.com/course/react-the-complete-guide-incl-redux/">https://www.udemy.com/course/react-the-complete-guide-incl-redux/</a></li><li><a href="https://www.udemy.com/course/react-redux/">https://www.udemy.com/course/react-redux/</a></li></ol><p>So, I started learning React and found it quite easier than JavaScript.</p><p><strong>NodeJS courses:</strong></p><ol><li><a href="https://www.udemy.com/course/the-complete-nodejs-developer-course-2/">https://www.udemy.com/course/the-complete-nodejs-developer-course-2/</a></li><li><a href="https://www.udemy.com/course/advanced-node-for-developers/">https://www.udemy.com/course/advanced-node-for-developers/</a></li></ol><blockquote>As I got work, I gained more experience and worked on web apps, chatbots, digital marketing, and Shopify apps, to name a few.</blockquote><h3>Hands-On Experience</h3><p>As soon as I knew I could do some basic web development, I started looking for work and did some projects.</p><p>Over time, due to client requirements, I learned a lot of skills, such as GraphQL, chatbot development, etc., irrespective of my experience and skillset in that regard.</p><p>By gaining industry experience, my confidence boosted, and I was able to identify more areas to grow in this domain.</p><h3>Journey from software developer to architect</h3><p>Three years ago, I joined my current company as a senior software engineer, and looking backward and connecting the dots, it was one of the best decisions I have ever taken.</p><p>I started my team as one of the developers in a team of 8–10 developers. I had no background in CS, so I put in more effort and worked harder.</p><p>To set context, during my job, I gradually got promoted to these roles in just three years:</p><ol><li>Project Lead: 3 months</li><li>Team Lead: 6 months</li><li>Principal Software Engineer: 2 years</li><li>Software Architect: officially for 3 months</li></ol><p>Before we move further, it is important to understand that every software engineer is an architect in some capacity.</p><h3>Hard and technical skills got me promoted, and so can you.</h3><h4>1. Learned niche-specific skills</h4><p>I started with a frontend development role and later moved to backend development as a developer and architect. I learned these hard skills and improved my domain-specific knowledge.</p><p>Every project is built on the frontend, backend, database, cloud, and DevOps.</p><h4>2. Mastering software architecture fundamentals</h4><p>The fundamentals of every architecture are the same, with the same requirements. I mastered these concepts:</p><ol><li>Performance.</li><li>Scalable</li><li>Security</li><li>Reliability</li><li>Problem-solving</li></ol><h4>3. Understanding different architecture types</h4><p>Architecture starts with a project structure, connectivity between different components, and the pattern used to build the project. And it’s unique for each project. So, in this domain, you need to understand different architecture topics:</p><ol><li>Event-driven</li><li>Monolith vs Microservices</li><li>Modular monoliths</li><li>Service-oriented architecture</li></ol><h4>4. Practicing building architecture of different apps</h4><p>I practice building the architecture of famous products and the problems I face with existing services like ticket booking apps, airline search engines, payment systems, etc. It allows me to explore and learn a multitude of skills, architecture patterns, and ways to improve problem-solving.</p><h3>The soft skills and qualities that elevated my career and can do your’s</h3><p>Everyone knows technical stuff, but the real puzzle is how to complement that with soft skills and your solution-building capabilities.</p><h4><strong>1. Love what you do.</strong></h4><p>I loved to be a software engineer, and it became my passion over time. I would spend weekends and leisure time learning new technology and upgrading my skillset. Accumulating vast skills allowed me to lead and manage different projects. As a software engineer, you need to find your passion in any niche or subdomain of software engineering and keep building the stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*dpGwygtHPLheKsLBbAy6WQ.png" /></figure><h4><strong>2. Don’t limit yourself.</strong></h4><p>I never limited myself to a specific skill and built my identity on that. If you limit yourself to a specific tech stack and don’t take on new tasks requiring a new skillset and level, you will never explore new horizons.</p><p>I was given the same advice by my manager, the CTO, when I asked him how I could reach his position.</p><p>To be able to lead multiple teams and build solutions, you need to have skills and experience in multiple technologies and the mindset to be willing to learn new skills.</p><h4><strong>3. Become a go-to person.</strong></h4><p>In your company, become the go-to person for a specific product or feature. You will interact with different teams while understanding the requirements and building a network inside your company.</p><p>I followed this path initially at my current job. I was the go-to person for integrating checkout into the projects for a headless e-commerce CMS. Then, when I moved to a sister product-based SAAS startup, I took charge of XAP, an admin panel for customers, and was the go-to person for all requirements and implementations.</p><p>This allowed me to build my reputation and further grow in the higher hierarchy. It will do the same for you as well.</p><h4>4. Being at the right place at the right time.</h4><p>I think and plan long-term. When my colleagues were switching jobs for a quick raise, I stuck to my position and outperformed my competition with management and leadership skills. I found and availed of the opportunities in my current company, which grew my position and influence. In fact, my current experience amazes the recruiters.</p><p>You need to think long-term if you want to reach higher positions. I doubt if any company will hire you for higher positions if you continuously switch jobs.</p><h4>5. Learn to sell yourself.</h4><p>We live in a free market where we trade our skills for money. So to make a better deal, you need to master marketing and selling yourself.</p><p>So you need to put forward your efforts in front of your managers and their managers in standups, regular meetings, etc. If there is a technically difficult task that no one is willing to take on, work on that.</p><p>Do quarterly sessions with your manager or lead and take their feedback on improvements and work on that.</p><h4><strong>6. Ownership</strong></h4><p>Always take 100% ownership of your task and project. Put in 100 percent effort with integrity, and always deliver a WOW experience.</p><h4>7. Work Hard</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FdASZbvqqAgRkvE9" /><figcaption>Photo by <a href="https://unsplash.com/@whitfieldjordan?utm_source=medium&amp;utm_medium=referral">Jordan Whitfield</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I can&#39;t say enough.</p><h4>8. Find mentor at your job</h4><p>I consider myself lucky to have had my first manager as my mentor, who actually taught me the art of leading people, managing multiple projects simultaneously, and pointing out the flaws in my leadership skills. In my first year, I learned all the skills required to work in top positions.</p><h3>Conclusion</h3><p>I have shared all the hard and soft skills that got me promoted despite transitioning from mechanical to software engineering. To get promoted, you need to work hard and smart, think long-term, and always strive to do your best.</p><p>Thanks for reading.</p><p>Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">Linkedin</a>.</p><h3><a href="https://plainenglish.io/">PlainEnglish.io</a> 🚀</h3><p><em>Thank you for being a part of the In Plain English community! Before you go:</em></p><ul><li><em>Be sure to </em><strong><em>clap</em></strong><em> and </em><strong><em>follow</em></strong><em> the writer</em><strong>️</strong></li><li><em>Learn how you can also </em><a href="https://plainenglish.io/blog/how-to-write-for-in-plain-english"><strong><em>write for In Plain English</em></strong></a><em>️</em></li><li><em>Follow us: </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>X</em></strong></a><strong><em> | </em></strong><a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><strong><em> | </em></strong><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><strong><em> | </em></strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong><em>Discord</em></strong></a><strong><em> | </em></strong><a href="https://newsletter.plainenglish.io/"><strong><em>Newsletter</em></strong></a></li><li><em>Visit our other platforms: </em><a href="https://stackademic.com/"><strong><em>Stackademic</em></strong></a><strong><em> | </em></strong><a href="https://cofeed.app/"><strong><em>CoFeed</em></strong></a><strong><em> | </em></strong><a href="https://venturemagazine.net/"><strong><em>Venture</em></strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b436ba87664" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/from-mechanical-engineer-to-software-architect-within-5-years-6b436ba87664">From Mechanical Engineer to Software Architect within 5 years</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building predictable, reliable, resilient, and retriable APIs with Idempotency]]></title>
            <link>https://levelup.gitconnected.com/building-predictable-reliable-resilient-and-retriable-apis-with-idempotency-4dd3fc0bf01f?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dd3fc0bf01f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 17 Sep 2023 18:53:43 GMT</pubDate>
            <atom:updated>2023-09-18T13:30:20.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wq_WeZlk5RfSErk6P1ZtTQ.png" /></figure><p><em>This post is originally from </em><a href="https://zerotoarchitect.substack.com/"><em>Zero To Architect</em></a><em>, a free newsletter available on Substack from </em>Ali Raza, a versatilist software architect who believes that anyone can be a software architect.</p><p>Developers want their APIs to be reliable and resilient.</p><p>But there is an area that is often overlooked: are your APIs predictable and retriable?</p><p>Let’s explore some examples.</p><h3>Customers getting double charged: A classic example</h3><p>A customer is using your payment APIs, and as soon as the process is initiated, there is a network issue on the customer’s end, and he is unable to receive a response. As soon as the network is back, they click on the pay button again. What should happen now?</p><p>If the payment process is restarted, the customer will be double-charged. Which will dent the credibility of the payment processor.</p><h3>Order and Inventory Management Systems</h3><p>Similarly, let’s say you have an e-commerce OMS app. The store owners process some orders but, for some reason, again perform the same actions. The system should not reprocess but instead, return the original response.</p><p>These problems can be resolved by introducing idempotency in the APIs.</p><h3>What is idempotency?</h3><p>Idempotency is a mathematical and computer science concept that refers to the quality of some operations or functions in which performing them several times has the same effect as performing them once.</p><blockquote><em>An idempotent operation can be repeated an infinite number of times and still provide the same outcome.</em></blockquote><p>Idempotent APIs enable API users to retry calls in the event of a network outage or other problems without having to worry about producing duplicate rows in a database or charging the client several times.</p><h3>HTTP Methods ensuring idempotency</h3><p>HTTP methods such as PUT, DELETE, and GET are idempotent in nature.</p><ol><li><strong>GET:</strong> Repeating a GET request will return the same resource representation without changing the resource on the server.</li><li><strong>HEAD:</strong> The HEAD method, like GET, obtains metadata about a resource but not the resource itself. It can be used to check for the existence of a resource, get headers, or find the last change date without modifying the resource itself.</li><li><strong>PUT:</strong> If the resource at the specified URL already exists, a PUT request will replace it with the new representation sent in the request body. PUT will build the resource if it does not already exist. <em>PUT is idempotent in the sense that repeating the same PUT request with the same data does not affect the resource in any way other than the initial request.</em></li><li><strong>DELETE:</strong> When you issue a DELETE request, the server deletes the resource if it exists, and it simply provides a successful answer if it does not. Multiple DELETE operations on the same resource will not have different outcomes beyond the first deletion, making it an idempotent operation.</li></ol><h3>How can a developer build idempotent APIs?</h3><p>A developer can add idempotency in various ways.</p><h3>1. Idempotency Keys</h3><p>Idempotency keys are the building blocks of idempotent keys. A key, preferably a UUID, is used to identify a request. Whenever the API is called again with the same key, it will return the original response.</p><p>The keys are either external or internal.</p><ul><li><strong>External Idempotency Keys: </strong>If the API is integrated into 3rd-party apps, then that system can pass the key to be identified as the idempotency key.</li><li><strong>Internal Idempotency Keys: </strong>If the system generates a key against each request and attaches that on the basis of an ID, then that key will be called an idempotent key.</li></ul><h4>Saving Idempotency Keys</h4><p>The idempotency keys are usually short-lived and can be reused with new requests after a specified time.</p><ol><li><strong>Redis:</strong> Redis or other caching solutions can be used to save short-lived idempotency keys.</li><li><strong>TTL indexing: </strong>Time-to-live indexes are often used to save a value in a database to be deleted later after a given time interval.</li></ol><h3>2. Using HTTP Methods</h3><p>Using HTTP methods such as GET, PUT, and DELETE will ensure that the API resources are by default idempotent.</p><h3>Let’s write some code</h3><p>Here’s an example of how to utilize the Express.js framework to create an idempotent API endpoint in Node.js, including the use of an idempotency key to ensure that repeated requests do not have unintended consequences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*93B0zE6HJOyi3sIx.png" /></figure><ul><li>For upgrading a user’s email address, we establish an Express.js application and configure a POST request endpoint (/users/:userId/email).</li><li>To uniquely identify each request, we develop and employ an Idempotency-Key header. If you use the same idempotency key in many requests, the server will recognize it as a duplicate and reply accordingly.</li><li>The server determines whether the idempotency key has previously been processed. If it has, the server responds with a response indicating that it has already handled the request.</li><li>To prevent duplicate processing of the same key, processed idempotency keys are placed in a Set.</li></ul><h3>Final Thoughts</h3><p>It is critical to consider the probability of failure in a distributed system and how to address it while developing APIs that are both resilient and predictable. Retry logic on clients and server idempotency are two strategies that can help achieve this goal and are reasonably easy to implement in any technological stack.</p><p>Here are a few fundamental principles to remember while building clients and APIs:</p><ol><li>Ensure that failures are dealt with consistently. Request that clients retry activities on remote services. Failure to do so may result in inconsistent data, which may cause problems in the future.</li><li>Make certain that failures are handled in a safe manner. Allow clients to pass a unique value and retry requests as needed by using idempotency and idempotency keys.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dd3fc0bf01f" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/building-predictable-reliable-resilient-and-retriable-apis-with-idempotency-4dd3fc0bf01f">Building predictable, reliable, resilient, and retriable APIs with Idempotency</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This post is originally from Zero To Architect, a free newsletter available on Substack from Ali…]]></title>
            <link>https://thealiraza.medium.com/this-post-is-originally-from-zero-to-architect-a-free-newsletter-available-on-substack-from-ali-edf8bb59a454?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/edf8bb59a454</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 10 Sep 2023 16:38:16 GMT</pubDate>
            <atom:updated>2023-09-10T16:38:16.963Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to measure your and your team’s productivity as a developer, manager and engineering lead.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_dOVEJzftuO5C3d0aEAn0Q.jpeg" /></figure><p><em>This post is originally from </em><a href="https://zerotoarchitect.substack.com/"><em>Zero To Architect</em></a><em>, a free newsletter available on Substack from </em>Ali Raza, a versatilist software engineer who believes that anyone can be a software architect.</p><p>Productivity is contextual and subjective. It can’t be generalized.</p><p>I manage and lead 8 to 10 engineers on average across different teams and use different measures to determine their performance and productivity instead of one rule that fits all.</p><p>Let’s start.</p><ol><li>Year of experience in a specific tech stack</li><li>Difficulty level of new tech stack for a new task</li><li>Relevance of tasks with the tech stack</li><li>Ability to learn any new skill to fulfill the job</li><li>Knowledge of relevant tech ecosystems</li></ol><h3>Example 1: Experience and task in the same tech stack</h3><p>Let’s say there is a developer with three years of experience in JavaScript and React. Xe is assigned a task of five-story points, which is relatively fair and expected to be completed if no blockers occur.</p><p>If the task is completed within the timeframe, then the developer is performing well.</p><p>But if the random tasks are taking more time, then there needs to be a discussion.</p><h3>What is to be discussed here?</h3><p>As a lead or manager, I will first sit down and evaluate what went wrong here. There are chances that</p><ol><li>There was tech debt that needed to be cleared first.</li><li>But who created that in the first place? Was it some other developer?</li><li>The feature affected other parts of the code and needed to be handled, and it took more time than anticipated earlier.</li><li>Was the codebase not scalable?</li><li>How can we ensure that it doesn’t happen in the next feature implementation?</li><li>The person took more time.</li></ol><p>The first two options clearly illustrate that the developer might not be wrong and could be given leverage. But in the last one, the performance is quite low.</p><h3>Example 2: A developer is assigned a task of an overlapping tech stack</h3><p>A backend developer with an Express.js and Node.js tech stack can be expected to take over Nest.js with ease, and his task estimates can be extended from 10% to 25%. However, if the same engineer takes double the time, then it means either he lacks basic JS OOP skills or is a slow learner.</p><p>The latter is acceptable, but the former is not and will directly fall under poor performance, and the developer should be considered less productive.</p><h3>Example 3: You are given a task above your skill level</h3><p>Assume you have average database skills and know the syntax and APIs to work with. Your next task is implementing sharding and partitioning with eventual consistency and maintaining connection pooling.</p><p>It’s a difficult task that requires thorough knowledge of the internals of the database.</p><h4>What to do as an engineer</h4><ol><li>First, discuss with your manager that you don’t have the current skillset for this task, but you will learn it and finish it.</li><li>Discuss the timeline. If a person with the required skillset needs two weeks, then it should be four for you.</li><li>Set expectations earlier to avoid any confusion and delivery delays later.</li><li>This will ensure that, as a developer, your performance level is as per your skillset, with room to improve.</li></ol><h4>What to do as an engineering lead and manager</h4><ol><li>Understand the situation and skill level of your resources.</li><li>Set expectations for the deliverable accordingly.</li><li>Even if the candidate is able to deliver 50–70%, it means xe performed well and couldn’t be deemed a non-productive engineer.</li></ol><h3>Tangible criteria to judge an engineer</h3><p>Irrespective of any task, the developers must be following these practices:</p><ol><li>Clean code practices being followed</li><li>Unit and integration testing</li><li>Scalable code</li><li>Number of bugs and issues reported</li><li>Git standards being followed</li></ol><p>With different use cases, I have tried to establish that it is not that easy to evaluate even one developer under different scenarios.</p><p>So, interact more with your team and ensure that you understand their side of the story before evaluating performance and productivity.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edf8bb59a454" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The developer’s productivity can’t be measured in McKinsey’s way. An Analysis.]]></title>
            <link>https://levelup.gitconnected.com/the-developers-productivity-can-t-be-measured-in-mckinsey-s-way-an-analysis-4d81924279ae?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d81924279ae</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 03 Sep 2023 13:56:33 GMT</pubDate>
            <atom:updated>2023-09-05T09:39:40.581Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3j8k71NVKf0hFviU" /><figcaption>Photo by <a href="https://unsplash.com/@schmaendels?utm_source=medium&amp;utm_medium=referral">Andreas Klassen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I have been managing and leading different teams for the last two and a half years and analyzing the productivity and performance of teammates with different backgrounds.</p><p>McKinsey published a <a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity">report</a> and laid down some productivity indicators to build a framework for tech companies.</p><p>As soon as I read this report, the first question I asked myself was, Do I measure the productivity of my team members? If so, do I use one generalized approach for all? The answer is no.</p><h3>Is it important to measure the productivity of software developers?</h3><p>Yes, every company needs the best talent and wants to replace the least productive engineers with the most productive ones. However, the productivity parameters of one developer completely differ from those of the other.</p><p>It is impossible to apply one formula that fits all and expect accurate results. It will be disruptive.</p><p>Let’s say there are three developers, A, B, C, and D, working in a team and putting in 100% effort.</p><p>Developer A is working on new features and delivering them regularly.</p><p>Developer B is reducing tech debt by optimizing code for scalability and paving the way for new feature development at a rapid pace.</p><p>Developer C is blocked most of the time due to third-party dependencies and couldn’t get it delivered.</p><p>Developer D is building with a completely new stack, and the development pace is slow, but things are getting done as per contractual expectations.</p><p>Who will get more recognition and be considered more productive in typical C-level meetings? Does it mean, by any standard, that one is less productive than the others? A person solving bugs or reducing tech debt might seem less productive than one delivering features in a typical tech company.</p><h3>A summary of the McKinsey report</h3><p>McKinsey thinks they have a solution to measure the developer’s productivity.</p><p>This article explores the significance of measuring software developer productivity and proposes a novel method for doing so. It emphasizes that, in contrast to other corporate operations, software development has generally been undermeasured. However, because most businesses now rely substantially on software, it is critical to analyze and optimize developer performance.</p><p>Given the complexity and collaboration required in software development, the essay acknowledges the difficulties in assessing developer productivity.</p><p>The article’s innovative technique involves assessing production at three levels: system, team, and person, using DORA and SPACE metrics and Opportunity-focused metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*q9MhSmAXr1TNTrZSWbT83g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*vO1fgBt_bk2t8Tqxtuk6DQ.png" /></figure><p>It introduces new measures, including deployment frequency, change lead time, and contribution analysis, to evaluate performance and find areas for improvement.</p><p>The essay emphasizes the need to avoid measurements that are unnecessarily simplistic, such as lines of code, and encourages organizations to move beyond antiquated mindsets that imply software engineering cannot be measured.</p><p>The article concludes with suggestions for getting started with measuring developer productivity, such as learning about software development, assessing existing systems, developing a plan, and understanding that measuring productivity is contextual and aimed at improving the entire development environment. The goal is to boost developer productivity and overall corporate performance by increasing openness and insight.</p><h3>An analysis from a developer’s and engineering lead’s perspective</h3><p>The report is more focused on building a framework for C-level managers than considering the software development lifecycle and the developer’s journey from building to delivery.</p><h4>1. A non-engineering person gauging developers&#39; productivity and influencing decisions</h4><p>This is where the problem starts.</p><p>It’s just a button or an API connected to the database.</p><p>To a non-techie, it might look like just a feature, but the concepts of tech debt, architectural decisions, and feature implementation are naive.</p><p>The question is, when the CTO is spearheading the technical side, shouldn’t he be calling the shots and firing and hiring developers based on their performance?</p><p>Not to mention non-engineering people, I have witnessed leads and managers struggling with developers working on the other tech stack. I have witnessed backend leads who don’t understand how a page loads on browsers and, out of ignorance, rank frontend developers low.</p><blockquote><strong><em>Learn the basics.</em></strong> All C-suite leaders who are not engineers or who have been in management for a long time will need a primer on the software development process and how it is evolving.</blockquote><p>It’s a welcoming statement, but not all tech companies are building the same product. R&amp;D, architectural decisions, and overhead vary. The developer and software lifecycles in a fintech startup are different from those in a typical SAAS. So the question is: are C-level managers willing to learn from the context of their product?</p><h4>2. Entire focus on coding</h4><blockquote>From both a productivity and personal-experience standpoint, maximizing the amount of time developers spend in the inner loop is desirable: building products directly generates value <em>and </em>is what most developers are excited to do.</blockquote><p>The document thinks that the more code a developer writes, the more productive he or she is. The irony is that it indirectly insists on building a coder mindset in organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TCWA8r_dVxvmlFVZ" /><figcaption>Photo by <a href="https://unsplash.com/@cbpsc1?utm_source=medium&amp;utm_medium=referral">Clint Patterson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There is no mention of how much different aspects of software engineering, such as building a system design, taking architectural decisions, and discussing scalability, influence the course of the product.</p><h4>3. The outer loop is completely generalized for all developers</h4><p>The absence of platform engineering and DevOps standardization will impede development progress and make developers focus less on their jobs.</p><p>It makes sense that the developers should be unblocked for CI/CD pipelines and deployments, but excluding meetings, security, and compliance from a developer’s activity is rather a generalization.</p><p>It’s true for most tech companies, where unnecessary prolonged meetings and standups happen and should be reduced to a point where developers just attend meetings where they are actually required.</p><p>A developer working in Fintech and Banking is considerate of security and compliance. If development evolves the product, then obviously these factors come into play. Who will then implement those features?</p><h4>4. No mention of automated and manual QAs or DevOps engineers</h4><p>Productivity can vary from developer to developer, depending on the job description.</p><p>Developers are not the only ones building the product and need to be productive. The QA team and DevOps play equal roles. Here, no indicator is defined to measure their productivity.</p><p>The manual QAs and the ones doing automation need different criteria, as do the DevOpsers.</p><h4>5. Developer Velocity Index</h4><p>DV, in fact, adds to the efficiency of a developer’s and the overall software development cycle. The developer’s productivity will fall to zero if they get stuck in CI/CD pipelines, manual unit testing, tedious code promotion strategies, etc.</p><h4>6. Overlooking non-coding contributions of developers</h4><blockquote>For example, one company found that its most talented developers were spending excessive time on noncoding activities such as design sessions or managing interdependencies across teams. In response, the company changed its operating model and clarified roles and responsibilities to enable those highest-value developers to do what they do best: code.</blockquote><p>The company went wrong here, and this model is not a viable one.</p><p>It can be assumed that the most talented developers should know the ins and outs of the product and the internal dependencies overlapping across the teams. Who is supposed to take the lead, create, or assess designs and system designs? Are those talented developers or others hired for these specific roles? Were those developers completely turned into coding bots?</p><p>Let’s say there is a major feature implementation that requires ongoing communication between the teams. It’s a common practice that managers, with the help of developers, handle this and point out the shortcomings and successes of the integrations and implementations.</p><p>Creating a separate role for this creates only friction rather than good code and products.</p><h4>7. The framework doesn’t address contextuality</h4><blockquote><strong>Remember that measuring productivity is contextual. </strong><em>The point is to look at an entire system and understand how it can work better by improving the development environment at the system, team, or individual level.</em></blockquote><p>It’s a welcome point in the report, and it’s true.</p><p>At my job, my manager gauges my productivity and performance in a different context than I do for my team members on a different tech stack.</p><p>At the team level, my developers get blocked for a couple of days due to an external issue, although a feature has been completed. When they get unblocked, they might have to change a feature implementation due to a third-party requirement, and the delivery gets delayed. In this context, the team is not a non-productive one. But if it is clearly monitored, the team is indeed productive, as they have delivered the feature in the time required to do all the work.</p><p>To some C-level managers, the developer might look non-productive as the feature is getting delayed, but the reason is not the productivity issue.</p><p>Similarly, if the team or developer underestimates the ETA and there are no blockers, they fail to defend against delays, and productivity and performance issues will come into the spotlight.</p><p>It’s easier to gauge performance with a given set of points, such as clean code, unit testing, number of bugs, tech debt accrued, etc.</p><h4>8. The impact of the developer on the team is greater than the coding</h4><p>This is one of the most important aspects of an outstanding developer, but there seems to be no mention of it. If you are a senior developer on the team, you will be expected to help out the juniors, review code, and suggest solutions. The amount of time spent coding will not be a big factor in your assessment.</p><p>The greater your impact, the more productive and exceptional you will be considered.</p><h3>Summary</h3><p>It’s a very welcoming report, but it comes with some basic flaws. Every manager wants to know the productivity level of his or her team and how to improve it. But it can’t be generalized and applied across organizations. Every developer or team has different tasks and circumstances. Similarly, each developer comes with different strengths and weaknesses, which have an impact on the product being built. Some are good at unblocking teammates and building solutions, while others write exceptional and optimized code. Those who implement this framework will produce more coders than software engineers who build solutions.</p><p>Thanks for reading.</p><p>Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d81924279ae" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/the-developers-productivity-can-t-be-measured-in-mckinsey-s-way-an-analysis-4d81924279ae">The developer’s productivity can’t be measured in McKinsey’s way. An Analysis.</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The wrong DevOps strategy can undermine your startup and product.]]></title>
            <link>https://levelup.gitconnected.com/the-wrong-devops-strategy-can-undermine-your-startup-and-product-2ae8a3a01d2d?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ae8a3a01d2d</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Sun, 11 Jun 2023 23:24:49 GMT</pubDate>
            <atom:updated>2024-03-04T15:47:16.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vRYUOBWW7d-BycS2fYbMbQ.png" /><figcaption>The wrong DevOps strategy can undermine your startup and product.</figcaption></figure><p>You can subscribe to my newsletter @ <a href="https://solutionsarchitect.substack.com/">https://solutionsarchitect.substack.com/</a></p><p>DevOps is an integral part of the technology behind your industry-disrupting startup. The decisions for DevOps strategies—which servers, machines, and tech to use for individual services—directly make or break your product.</p><p>This is often one of the most overlooked domains in early-stage startups, as deliverables are to be shipped as soon as possible, and building a solid foundation takes some time. But one wrong decision will sabotage expectations and even cause customer loss.</p><p>Hardly anyone talks about it.</p><p>The product I was leading fell prey to the wrong DevOps decisions, slowly becoming a source of suffering for me, management, and customers.</p><h3>My experience: How did choosing EKS over CloudFront become a nightmare?</h3><p>We had five individual products, and it was decided to bring them under one roof. Each product had separate admin panels, AuthN &amp; AuthZ, etc.</p><p>So, to run all different admin panels under one domain and SSO, I created a micro frontend-based solution: save the build of each admin panel in the individual subdirectory and do redirection from one product to another. At that moment, it was the quickest and best solution.</p><p>It was to be done via a function that redirects customers to the product’s dashboard based on the request URL. AWS Lambda seemed like the best solution, as it can be linked to a CloudFront distribution, which provides additional benefits such as cache, and code pipelines for each product, etc.</p><p>But, guess what? EKS was used for this implementation. The function was added to the root React project, which runs the apps and redirects all the users to the relevant app. All the projects were to be placed under the same root build, and on each code push, all six React apps were to be built, which increased pipeline time to 30–50 minutes. There was no caching, and as each request has to first connect with EKS and bring a response each time, the app load took anywhere from 5 to 20 seconds.</p><blockquote>React apps were deployed in EKS instead of S3 + CloudFront.</blockquote><p>It was a complete disaster and I had to listen to complaints from management to the sales team and customers, etc.</p><p>I knew that only Lambda and CloudFront were the solutions. So, I created a Lambda function, a CloudFront registry, and an S3 bucket hosting all apps in subfolders. <em>As soon as the implementation was done, the same app switching that had been taking 5 to 10 seconds went down to 200 ms.</em></p><p>And everyone took a sigh of relief.</p><p>And all the pain went away with correct decision-making.</p><h3>What is in it for developers?</h3><p>I always argue that every developer should learn DevOps, at least in relation to his or her job description.</p><p>What are the best ways to host your application, which service will decrease latency, etc.?</p><p>Provide those suggestions to DevOps and stick to that stack, as you are the one responsible for everything related to the product. Don’t succumb.</p><p>A programmer should be able to code, deploy, and publish his project in the best possible way.</p><p>You can read about it in my article.</p><p><a href="https://levelup.gitconnected.com/every-developer-should-learn-devops-in-2023-1154ec261b46">Every developer should learn DevOps in 2023</a></p><h3>What is in it for DevOpsers?</h3><p>There are multiple ways of doing one thing. But not all are the best.</p><p>The frontend and backend need different sets of technologies to host and deploy the apps. What is true for one app can’t be applied to other apps.</p><p>For instance, AWS Amplify provides the built-in solution to host Next.js apps, but choosing another stack will require more work and might affect performance.</p><p>So, it is important to consult the relevant development team about the deployment and hosting requirements and what the best solution will be.</p><p>So, always do right by DevOps.</p><p>Thanks for reading. Follow for more amazing content.</p><p>Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">LinkedIn</a> and <a href="https://twitter.com/nowaliraza">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ae8a3a01d2d" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/the-wrong-devops-strategy-can-undermine-your-startup-and-product-2ae8a3a01d2d">The wrong DevOps strategy can undermine your startup and product.</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Lambda Response Stream: Optimize the app response and experience]]></title>
            <link>https://aws.plainenglish.io/aws-lambda-response-stream-optimize-the-app-response-and-experience-344ee444d66a?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/344ee444d66a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Tue, 18 Apr 2023 07:11:26 GMT</pubDate>
            <atom:updated>2023-04-25T17:24:34.703Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS Lambda Response Stream: Optimize the app response and user experience</h3><figure><img alt="AWS Lambda Payload Response Stream — Ali Raza" src="https://cdn-images-1.medium.com/max/1024/1*XisITLKwCS9Qh08s669nQw.png" /></figure><p>AWS Lambda has announced streaming of response payloads. The new invocation pattern known as “response streaming” allows functions to send back response payloads to clients in a steady trickle.</p><p>Lambda response payload streaming enables the continuous delivery of response data to callers. Web and mobile app performance may benefit from this. With response streaming, you may create functions that return more substantial payloads and execute lengthy tasks while reporting intermediate results.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAxMtqgb7z4Y%3Fstart%3D24&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAxMtqgb7z4Y&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FAxMtqgb7z4Y%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/34cdb6586a4f5f4e8fd62fafa132eb68/href">https://medium.com/media/34cdb6586a4f5f4e8fd62fafa132eb68/href</a></iframe><h3>What is the traditional AWS Lambda Response Model?</h3><p>Typically, when using request-response models, the response must be fully created and delayed before being sent back to the client. Because the client must wait for the server to create the answer, TTFB performance may suffer.</p><p>The time to first byte (TTFB) and page load speed are extremely important for web applications. The time-to-first-byte (TTFB) latency can be reduced to the millisecond range by using the response streaming feature. This can boost web apps’ search engine rankings and user satisfaction.</p><blockquote>Time to First Byte (TTFB) monitors how long it takes a web server to react to a request and transmit the first byte of data to the client’s browser.</blockquote><h3>How it works?</h3><pre>exports.handler = awslambda.streamifyResponse(<br> async (event, responseStream, context) =&gt; {<br>     responseStream.setContentType(&quot;text/plain&quot;);<br>     responseStream.write(&quot;Hello, Medium Users!&quot;);<br>     responseStream.end();<br> }<br>);</pre><p>The invocation event’s stringified form may be found in the requestStream. <em>The responseStream is a stream object that may be written to. Any data that is written to the responseStream object will be sent to the client as a stream.</em></p><p>The item used as context remains unchanged.</p><h3>How to access AWS Lambda Streaming Response?</h3><ol><li>The AWS SDK (JavaScript SDK v3, Go SDK, or Java SDK v2) allows you to get streaming responses from Lambda functions.</li><li>Any HTTP client that supports streaming answers may be used with Lambda Function URL.</li></ol><h3>How and where to use it? And what are advantages?</h3><ol><li>Apps may have substantial data to transfer, such as multimedia files, lengthy texts, or database results. Without storing the complete payload in memory, response streaming allows you to send it back to the client.</li><li>If your answer is going to be greater than Lambda’s 6 MB response payload limit, you may utilize response streaming to transmit it. The limit is softly set at 20 MB.</li><li>Streaming response to requests improves time-to-first-byte (TTFB). Sometimes this is useful. For instance, returning video or audio. The client can show the user multimedia stuff sooner by streaming it.</li><li>This functionality can stream incremental updates for long-running tasks, which are usually handled via web sockets.</li></ol><h3>Support for AWS Lambda Payload Response Streaming</h3><ol><li>The current version of Node.js that is compatible with response streaming is 14.x.</li><li>The Lambda API, AWS SDK, and Lambda function URLs may all be used as an Amazon CloudFront origin to stream replies.</li></ol><h3>Pitfalls</h3><h4>1. Size restriction on payload</h4><p>The default size restriction is 20 MB, and maximum data transfer rates are capped at 2 MB per second, or 16 Mbps.</p><h4><strong>2. ALB</strong></h4><p>The ALB Lambda integration does not support streaming replies.</p><h4><strong>3. Only Node.js is supported</strong></h4><p>The response streaming is only accessible in the Node.js SDK; however, a custom Lambda runtime supporting additional languages can implement it.</p><h4>4. Runtime limitation</h4><p>It only supports the node14.x, node16.x, and node18.x runtimes.</p><p>Thanks for reading. Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">LinkedIn</a> and <a href="https://twitter.com/nowaliraza">Twitter</a>.</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>. Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Join our </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>Discord</em></strong></a><em> community and follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a>, <a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><em> and</em><strong><em> </em></strong><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><strong><em>.</em></strong></p><p><strong><em>Learn how to build awareness and adoption for your startup with </em></strong><a href="https://circuit.ooo/?utm=publication-post-cta"><strong><em>Circuit</em></strong></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=344ee444d66a" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/aws-lambda-response-stream-optimize-the-app-response-and-experience-344ee444d66a">AWS Lambda Response Stream: Optimize the app response and experience</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every developer should learn DevOps in 2023]]></title>
            <link>https://levelup.gitconnected.com/every-developer-should-learn-devops-in-2023-1154ec261b46?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1154ec261b46</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Mon, 27 Mar 2023 00:40:54 GMT</pubDate>
            <atom:updated>2023-03-27T00:40:54.591Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RHqi2Xht2g8yVsy80OQX-A.png" /></figure><p>Over the last one and a half years, I am working as a tech lead/architect and most of my time is spent on taking decisions and building scalable solutions. Besides, domain-related hard skills, the working knowledge of DevOps and AWS helps me out while creating the best solutions.</p><p>I am convinced that every developer should know about DevOps and at least can manage the Ops related to his domain.</p><p>In this article, we will learn about what DevOps is, what are different parts of it and what should you learn and how will it help you further in your career. Even, the basic of DevOps is also required in the job description nowadays.</p><h3>What is DevOps?</h3><p>DevOps is a set of practices and cultural beliefs that emphasize collaboration and communication between software developers and IT operations professionals. Its goal is to automate the software delivery process and increase the speed, quality, and dependability of software releases.</p><p>DevOps integrates software development, testing, deployment, and operations into a single continuous process, allowing for faster and more efficient software development and deployment. It also includes the use of tools and technologies that automate the various stages of the software delivery process, such as version control, continuous integration and deployment, monitoring, and infrastructure as code.</p><h3>DevOps technologies and concepts you must know.</h3><h4>1. Docker</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1_DPKrr5x_5KXzEY" /><figcaption>Photo by <a href="https://unsplash.com/@rubaitulazad?utm_source=medium&amp;utm_medium=referral">Rubaitul Azad</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Docker is a containerization platform that lets developers deploy their apps consistently and portable.</p><p>Docker lets developers create container images with all the software dependencies, libraries, and configuration files needed for their applications. Users can share these images. To ensure software consistency across development, testing, and production environments, these images can be shared and used.</p><p>A Docker client tool interacts with the Docker daemon, which manages images and containers. Docker’s command-line and graphical interfaces can manage and deploy containers.</p><h4>2. Kubernetes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IB4k4Pnd4QnNzsan" /><figcaption>Photo by <a href="https://unsplash.com/@growtika?utm_source=medium&amp;utm_medium=referral">Growtika</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Kubernetes (K8s), an open-source container orchestration platform, automates containerized application deployment, scaling, and management.</p><p>Developers can deploy their apps in lightweight, portable containers with Kubernetes. Kubernetes manages and scales these containers efficiently across a cluster of nodes.</p><p>Kubernetes uses a master and multiple worker nodes. The cluster’s master node schedules worker node containers. Workers run containers and receive updates and instructions from the master node.</p><p>Kubernetes provides:</p><ol><li><strong>Automatic scaling:</strong> Kubernetes scales containers based on demand to ensure applications have enough resources.</li><li><strong>Self-healing:</strong> Kubernetes can detect and replace unhealthy or unresponsive containers, ensuring application availability.</li><li><strong>Load balancing:</strong> Kubernetes distributes traffic across containers for responsive applications.</li><li>Controlled application update rollouts and rollbacks reduce downtime and error risk with Kubernetes.</li><li><strong>Storage orchestration:</strong> Kubernetes manages container storage to give applications access to data.</li></ol><h4>3. Infrastructure as code (IaC)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lN_7F_FSaSW-once" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Infrastructure as code (IaC) uses code to automate and manage infrastructure. Instead of manually configuring servers, networks, and databases using a GUI or CLI, it defines them in declarative code.</p><p>IaC benefits include:</p><ol><li><strong>Consistency:</strong> IaC consistently provisioned and configured infrastructure, reducing human errors and misconfigurations.</li><li><strong>Reusability:</strong> IaC code can be shared across teams and environments, making infrastructure provisioning faster and easier.</li><li><strong>Scalability:</strong> IaC quickly and easily scales infrastructure to meet application and user needs.</li><li><strong>Version control:</strong> Developers and infrastructure teams can collaborate on IaC code using version control systems.</li><li><strong>Auditability:</strong> IaC tracks infrastructure changes, making troubleshooting and debugging easier.</li></ol><p>Terraform and CloudFormation allow declarative code descriptions of infrastructure components that can be versioned, tested, and deployed automatically. Dependency management, variable support, and modularity simplify infrastructure management.</p><h4>4. Continuous Integration/Continuous Delivery (CI/CD) Pipelines</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o0VPbr4gnFNgWBqX" /><figcaption>Photo by <a href="https://unsplash.com/@jjying?utm_source=medium&amp;utm_medium=referral">JJ Ying</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Continuous Integration/Continuous Delivery (CI/CD) allows developers to automate software building, testing, and deployment to production.</p><p>CI/CD pipelines automate code building, testing, and deployment. Developers start the pipeline by committing changes to version control.</p><p>The pipeline then executes:</p><ol><li>Code creation: The pipeline compiles code from the version control system.</li><li>Testing the code: The pipeline runs a suite of tests to check for bugs and regressions after code changes. Unit, integration, and functional tests.</li><li>The pipeline packages the code and dependencies into a deployable artifact like a container image or ZIP file.</li><li>The pipeline deploys code changes to a staging environment for testing before deploying to production.</li><li>Monitoring code: The pipeline checks the staging application for errors.</li><li>The pipeline promotes code changes to production if the staging environment is stable and error-free.</li><li>CI/CD pipelines speed up and improve software delivery to production.</li></ol><p>Automating the building, testing, and deployment process reduces manual errors and downtime and improves visibility and control over the software delivery process.</p><h4>5. Deployment Strategies</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mPIkcH5wBGwOsRtJZMFcqQ.png" /><figcaption>source: <a href="https://spinnaker.io/concepts/">https://spinnaker.io/concepts/</a>)</figcaption></figure><p>Software modifications are released and deployed to production environments using deployment strategies. Speed, risk, and complexity vary with deployment strategy. Deployment methods include:</p><ol><li><strong>Blue-Green Deployment: </strong>This technique maintains two identical environments for production and staging. The staging environment hosts the new application, which is tested and certified before traffic is moved to it.</li><li><strong>Rolling Deployment:</strong> This technique involves releasing changes to a small group of production servers, checking that they function, and then gradually rolling out the changes to the other servers.</li><li><strong>Canary Deployment:</strong> This method deploys changes to a limited group of users or servers in the production environment while keeping the rest of the traffic on the old version. After validation, traffic is gradually switched to the updated version.</li><li><strong>A/B Testing:</strong> This method involves deploying two versions of the application, A and B, and routing a percentage of traffic to each version. Both versions are compared, and the superior one is maintained.</li><li><strong>Immutable Deployment:</strong> Instead of upgrading the environment, each deployment creates a new one. This makes the environment consistent and trustworthy and decreases the possibility of errors caused by changes between environment versions.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BGdocBfsXKjCKqXDeZUrw.png" /><figcaption>source: <a href="https://spinnaker.io/concepts/">https://spinnaker.io/concepts/</a>)</figcaption></figure><p>Each deployment approach has pros and downsides, and the ideal one depends on the organization’s needs. The application’s size and complexity, risk tolerance, resources, and deployment speed should be considered while choosing a deployment method.</p><h4>6. Site Reliability Engineering</h4><p>Site Reliability Engineering (SRE) integrates software development and operations to construct and run reliable, scalable, and efficient software systems. SRE teams monitor system uptime, latency, and error rates.</p><p>SRE relies on numerous fundamentals:</p><ol><li>SRE teams monitor system performance, including uptime, latency, and error rates. This data helps uncover issues and inform system improvements.</li><li>Automate everything: SRE teams automate to eliminate human error, and boost efficiency, and consistency. Automated testing, deployment, and issue response.</li><li>SLOs and SLAs: SRE teams set SLOs and SLAs to guarantee system performance meets user needs.</li><li>Perform blameless post-mortems: SRE teams investigate incidents to determine what happened, why, and how to avoid it from happening again. Instead of blaming, learn from mistakes and improve the system.</li><li>SRE teams experiment to test new ideas and improve the system. A/B testing, canary deployments, and other methods are used to test changes before implementing them.</li><li>SRE teams collaborate with development, testing, and operations to ensure system reliability and efficiency. Sharing information, resources, and best practices.</li><li>SRE is a mentality and practices for designing and running reliable, scalable, and efficient software systems. SRE teams can increase system reliability, performance, and user experience by following these guidelines.</li></ol><h4>7. Cloud Services</h4><p>Cloud services are internet-delivered services from cloud computing providers. These services offer computation, software, and storage. Cloud services are usually subscription-based and accessed via a browser or client application.</p><p>The most popular cloud service is, AWS. Its most useful services are EC2, S3, Lambda, RDS, Secret Manager, and more.</p><h3>How will learning these DevOps concepts and tools help you as a developer?</h3><h4>1. Better technical solution</h4><p>A developer can create more resilient, scalable, and solid technical solutions. Knowing how different parts of tech work can help in taking better decisions. For example, the decision when to use Lambda vs deploying a service on EC2 with respect to speed and cold-starts can only be made when you have got to know in and out of these techs. And this can only be possible if you have some background in DevOps and AWS.</p><h4>2. Production Debugging</h4><p>DevOps can help developers debug production difficulties. Debug production issues using DevOps principles with these steps:</p><ol><li>Monitor production difficulties with monitoring tools. Monitoring can help you catch problems early. DevOps monitoring is automated and combines with other technologies to give real-time application visibility.</li><li>Reproduce: Use your DevOps process to replicate an issue in a development or testing environment. Reproducing the problem helps diagnose and solve it.</li><li>Collaborate with operations teams to understand the production environment and identify configuration or infrastructure issues that may be causing the problem. Use DevOps concepts to collaborate and communicate with operational teams to fix the issue.</li><li>Fix: Use your DevOps process to push the fix to production after finding the issue. Continuous delivery and automated testing can assist deploy the patch quickly and safely.</li><li>Monitor again: After delivering the fix, monitor the production environment again to confirm the issue is repaired and no new issues arise. This verifies your repair and production stability.</li></ol><p>Developers can reduce downtime and improve user experience by debugging production issues using DevOps techniques.</p><h4>3. Better approach toward development</h4><p>Developers can improve their development methods with DevOps:</p><ol><li><strong>Agile Development:</strong> DevOps encourages rapid iteration, collaboration, and continuous improvement. Developers can respond to changing needs, provide features faster, and get stakeholder input by working in Agile.</li><li><strong>Collaboration:</strong> DevOps encourages collaboration between developers, operations, and other software development stakeholders. Developers can better understand the production environment and design deployable, operable software by engaging with operations teams.</li><li>DevOps emphasizes monitoring and feedback throughout development. Developers can enhance their code by analyzing production application performance and availability.</li></ol><h3>Conclusion</h3><p>To summarize, it can be said that DevOps is a necessary tool for developers to learn as it will help them in debugging, developing better solutions, and an improved skill set to match the market demand.</p><p>Thanks for reading. Follow for more amazing content.</p><p>Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">LinkedIn</a> and <a href="https://twitter.com/nowaliraza">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1154ec261b46" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/every-developer-should-learn-devops-in-2023-1154ec261b46">Every developer should learn DevOps in 2023</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Source Map 101: What Developers Should Know About This Security Risk]]></title>
            <link>https://javascript.plainenglish.io/source-map-101-what-developers-should-know-about-this-security-risk-b7e69ee38a82?source=rss-2f4ef1372d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7e69ee38a82</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Ali Raza]]></dc:creator>
            <pubDate>Mon, 30 Jan 2023 14:16:29 GMT</pubDate>
            <atom:updated>2023-01-30T14:16:29.599Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdvXgO2iamB2Hf706p3DiA.png" /></figure><p>What could be a developer&#39;s worse nightmare than having their app&#39;s source code exposed? If you are a front-end developer, you should be more concerned, as there are various ways your app’s source code will be exposed, and one of the most overlooked ways is “source mapping.&quot;</p><h3>What is a source map?</h3><p>A source map is a file that maps a file’s original source code (such as a JavaScript file) to its generated version (such as code that has been compiled and minified).</p><p>The source map file has the names of the files, the line numbers, and a map of the code that has been compiled from the original source code. By displaying the original source code, the source map assists developers in troubleshooting built programs.</p><p>Web developers use source mapping to translate, shrink, and bundle JavaScript code to make websites run faster, but this makes it harder to find bugs. Source mapping can help debug and create CSS, graphics, and other programs.</p><h3>Is a source map necessary?</h3><p>Source maps are important because they let developers troubleshoot their original source code while working with the generated version. This makes the code easier to read and understand.</p><p>Source maps let you connect the original source code to the code that was made, which solves the problem. When a developer is debugging compiled code, they can use the source map to view the original source code, which makes it easier to identify and resolve errors.</p><p>Source maps also let developers debug code on a live website or app. They can use the browser&#39;s developer tools to look at the original source code and set breakpoints, just like they would when developing locally.</p><h3>Source map and security implications</h3><p>A source map is obviously helpful for debugging, but it also raises security concerns. It can expose a program’s or website’s original source code, which may reveal things like passwords or private data.</p><ol><li>The information included in a file’s source code, such as passwords or other secrets, could be exposed if a source map were to be used to read the file.</li><li>An attacker who is hunting for vulnerabilities may find source maps helpful because they show the structure and organisation of the software.</li><li>A misconfigured source map could expose the original source code to attackers or harmful third parties.</li><li>When an attacker obtains a source map, they can use it to reconstruct the original programs, which could lead to the discovery of security flaws or other private details.</li><li>With the help of source maps, attackers can insert malicious code into legitimate files, potentially granting them execution privileges on the victim’s computer.</li></ol><h3>How to not generate a source map in production?</h3><p>The process for avoiding the creation of a source map during the building and compiling of your code will vary depending on the tool or framework you employ. Some instances are as follows:</p><pre>// Webpack<br>module.exports = {<br>  devtool: &#39;none&#39;,<br>  // ...<br>};</pre><pre>// Babel<br>babel --sourceMaps false script.js</pre><pre>//typescript<br>{<br>    &quot;compilerOptions&quot;: {<br>        &quot;sourceMap&quot;: false,<br>        //...<br>    },<br>    //...<br>}</pre><pre>//Rollup<br>export default {<br>  input: &#39;src/index.js&#39;,<br>  output: {<br>    file: &#39;dist/bundle.js&#39;,<br>    format: &#39;cjs&#39;,<br>    sourcemap: false<br>  }<br>};</pre><h4>How to not generate a source map for React application?</h4><ol><li>Set “GENERATE SOURCEMAP=false” in your <strong>.env file</strong> in the root of your project directory.</li></ol><p>2. Change React scripts command</p><pre>// package.json<br>&quot;build&quot;: &quot;GENERATE_SOURCEMAP=false react-scripts build&quot;</pre><p>3. You can use the webpack config as discussed above.</p><h3>Is there a way to save source maps securely and access them?</h3><p>Source maps can be protected against unauthorised access and disclosure of important data by being stored in external, password-protected files.</p><p>Following these instructions will allow you to securely store your source maps in external files:</p><ol><li>Take advantage of a build tool that gives you control over where the source map file is written. The dev tool option in webpack, for instance, lets you set where the source map file is written.</li><li>Protect the original map file by uploading it to a file hosting service that offers encryption. The source map file, for instance, can have its rights restricted using AWS S3 so that only certain people can access it.</li><li>Use an authorization tool to limit who can access the source map file, such as JSON Web Tokens (JWT).</li><li>Utilize Content Security Policy (CSP): CSP is a security feature that aids in detecting and mitigating specific attacks, such as Cross-Site Scripting (XSS) and data injection attacks. It can be used to restrict who can access the source map file by specifying which sources are authorised to load content in the browser.</li></ol><p>It’s worth noting that these measures can aid in securing the source map file, but cannot ensure the entire security of the source code. Reviewing the codebase and expunging private details is a recommended best practice.</p><h3>How to debug your code without a source map?</h3><ol><li><strong>Pretty-print the code:</strong> Some minifiers and transpilers include white spaces and comments to make the code more legible. This simplifies code comprehension and debugging.</li><li><strong>Set breakpoints and step through code with a debugger:</strong> Many recent browsers feature built-in developer tools. The debugger can help you comprehend the code flow and find bugs even if it’s not as readable as the original source code.</li><li><strong>Use a decompiler: </strong>A decompiler can turn compiled code into readable code. The resulting code may be simpler to comprehend and troubleshoot.</li><li>Knowing the code structure may help you understand it without a source map. Even if the code is minified, you may be able to discover and debug a method that handles a feature.</li><li><strong>Logging:</strong> Use console.log commands to output variable values to understand the code flow and discover faults.</li></ol><p>Thanks for reading. Follow for more tips and content.</p><p>Let’s connect on <a href="https://www.linkedin.com/in/thealiraza/">LinkedIn</a> and <a href="https://twitter.com/nowaliraza">Twitter</a>.</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>. Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a>, <a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><em>, </em><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><em>, and </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>Discord</em></strong></a><strong><em>.</em></strong></p><p><strong><em>Interested in scaling your software startup</em></strong><em>? Check out </em><a href="https://circuit.ooo/?utm=publication-post-cta"><strong><em>Circuit</em></strong></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7e69ee38a82" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/source-map-101-what-developers-should-know-about-this-security-risk-b7e69ee38a82">Source Map 101: What Developers Should Know About This Security Risk</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>