<?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 Saurabh Asthana on Medium]]></title>
        <description><![CDATA[Stories by Saurabh Asthana on Medium]]></description>
        <link>https://medium.com/@saurabhasthana?source=rss-fc126a95c9f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7_sM-PYTPMGSNxkAG3Y7Tw.jpeg</url>
            <title>Stories by Saurabh Asthana on Medium</title>
            <link>https://medium.com/@saurabhasthana?source=rss-fc126a95c9f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:26:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saurabhasthana/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[The Ultimate Linux Cheat Sheet for Devops: Your Go-To Guide for Everyday Commands]]></title>
            <link>https://saurabhasthana.medium.com/the-ultimate-linux-cheat-sheet-for-devops-your-go-to-guide-for-everyday-commands-bcb6b05aff64?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcb6b05aff64</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cheet-sheets]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Thu, 06 Mar 2025 07:15:28 GMT</pubDate>
            <atom:updated>2025-03-06T07:15:28.081Z</atom:updated>
            <content:encoded><![CDATA[<p>Mastering Linux is a game-changer for anyone working in DevOps, cloud computing, or software development. Whether you’re a beginner or an experienced pro, having a solid grasp of essential Linux commands can streamline your workflows and boost productivity. Let’s break down the must-know commands, organized by category, to keep handy as you navigate your terminal like a boss.</p><h3>📂 1. Basic File &amp; Directory Commands</h3><ul><li>pwd — Print current directory</li><li>ls — List files and directories</li><li>ls -l — Long format listing</li><li>ls -a — Show hidden files</li><li>ls -lh — Human-readable sizes</li><li>cd &lt;dir&gt; — Change directory</li><li>cd .. — Move up one level</li><li>cd - — Switch to the previous directory</li><li>mkdir &lt;dir&gt; — Create a new directory</li><li>rm &lt;file&gt; — Remove a file</li><li>rm -r &lt;dir&gt; — Remove a directory and its contents</li><li>cp &lt;source&gt; &lt;destination&gt; — Copy files/directories</li><li>mv &lt;old&gt; &lt;new&gt; — Move or rename files</li></ul><h3>🔐 2. Managing File Permissions &amp; Ownership</h3><ul><li>ls -l — View file permissions</li><li>chmod 755 &lt;file&gt; — Set file permissions</li><li>chmod u+x &lt;file&gt; — Add execute permission for the user</li><li>chown &lt;user&gt;:&lt;group&gt; &lt;file&gt; — Change ownership</li><li>chown -R &lt;user&gt;:&lt;group&gt; &lt;dir&gt; — Recursive ownership change</li></ul><h3>🔍 3. Searching for Files</h3><ul><li>find &lt;dir&gt; -name &quot;&lt;pattern&gt;&quot; — Find files by name</li><li>find &lt;dir&gt; -type f -size +100M — Find large files</li><li>locate &lt;file&gt; — Locate files using an indexed database</li><li>updatedb — Update the locate database</li></ul><h3>📦 4. File Compression &amp; Archiving</h3><ul><li>tar -czvf archive.tar.gz &lt;files&gt; — Create a compressed archive</li><li>tar -xzvf archive.tar.gz — Extract a compressed archive</li><li>zip archive.zip &lt;files&gt; — Zip files</li><li>unzip archive.zip — Unzip files</li></ul><h3>🛠 5. Process Management</h3><ul><li>ps aux — List running processes</li><li>top — Show real-time system processes</li><li>kill &lt;PID&gt; — Kill a process</li><li>kill -9 &lt;PID&gt; — Force kill a process</li><li>nohup &lt;command&gt; &amp; — Run a command in the background</li></ul><h3>💾 6. Disk Usage &amp; Management</h3><ul><li>df -h — Show disk usage</li><li>du -sh &lt;dir&gt; — Show directory size</li><li>lsblk — List block devices</li><li>mount /dev/sdX /mnt — Mount a partition</li><li>umount /dev/sdX — Unmount a partition</li></ul><h3>👥 7. User Management</h3><ul><li>whoami — Show current user</li><li>adduser &lt;username&gt; — Add a new user</li><li>passwd &lt;username&gt; — Change user password</li><li>usermod -aG &lt;group&gt; &lt;user&gt; — Add user to a group</li><li>deluser &lt;username&gt; — Delete a user</li></ul><h3>🌐 8. Network Commands</h3><ul><li>ip a — Show IP addresses</li><li>ping &lt;host&gt; — Test network connectivity</li><li>traceroute &lt;host&gt; — Trace route to a host</li><li>netstat -tulnp — Show listening ports</li><li>curl -I &lt;url&gt; — Fetch HTTP headers</li></ul><h3>📦 9. Package Management</h3><ul><li><strong>Debian/Ubuntu:</strong></li><li>apt update — Update package lists</li><li>apt install &lt;package&gt; — Install a package</li><li><strong>RHEL/CentOS:</strong></li><li>yum install &lt;package&gt; — Install a package</li><li>rpm -i &lt;package.rpm&gt; — Install an RPM package</li></ul><h3>📜 10. Log Management</h3><ul><li>cat /var/log/syslog — View system logs</li><li>journalctl -xe — View systemd logs</li><li>dmesg — View kernel logs</li></ul><h3>🔑 11. SSH &amp; Remote Access</h3><ul><li>ssh user@host — Connect to a remote server</li><li>scp &lt;file&gt; user@host:/path — Copy file to a remote server</li><li>rsync -av &lt;src&gt; &lt;dest&gt; — Sync files</li></ul><h3>📝 12. Text Processing</h3><ul><li>grep &quot;pattern&quot; &lt;file&gt; — Search for patterns in a file</li><li>awk &#39;{print $1}&#39; &lt;file&gt; — Print the first column</li><li>sed &#39;s/old/new/g&#39; &lt;file&gt; — Replace text in a file</li><li>sort &lt;file&gt; — Sort lines in a file</li><li>cut -d&#39;:&#39; -f1 &lt;file&gt; — Extract fields</li></ul><h3>🕒 13. Task Scheduling with Crontab</h3><ul><li>crontab -e — Edit cron jobs</li><li>crontab -l — List cron jobs</li><li>Example cron job:</li><li>0 * * * * /path/to/script.sh — Run script every hour</li></ul><h3>📊 14. System Monitoring</h3><ul><li>uptime — Show system uptime</li><li>free -h — Show memory usage</li><li>iostat — Show CPU and disk I/O stats</li><li>watch -n 1 &lt;command&gt; — Run a command every second</li></ul><h3>🔥 15. Firewall &amp; Security</h3><ul><li>ufw status — Check firewall status (Ubuntu)</li><li>iptables -L — List firewall rules (RHEL/CentOS)</li><li>passwd -l &lt;user&gt; — Lock a user account</li><li>fail2ban-client status — Check Fail2Ban status</li></ul><h3>🧠 16. Kernel &amp; System Info</h3><ul><li>uname -r — Show kernel version</li><li>hostnamectl — Show system hostname and details</li><li>lsmod — List loaded kernel modules</li></ul><h3>⚡ 17. System Shutdown &amp; Restart</h3><ul><li>shutdown -h now — Shutdown immediately</li><li>shutdown -r now — Restart the system</li><li>reboot — Reboot the system</li></ul><h3>🛠️ 18. Disk Partitioning</h3><ul><li>fdisk -l — List all partitions</li><li>mkfs.ext4 /dev/sdX1 — Format a partition as ext4</li><li>fsck /dev/sdX — Check and repair a filesystem</li></ul><h3>🌿 19. Environment Variables</h3><ul><li>echo $PATH — Show system PATH</li><li>export VAR=value — Set an environment variable</li></ul><p>This Linux cheat sheet is a living document — keep it handy and update it as you discover new commands that speed up your workflow. The more comfortable you get with the terminal, the more powerful you become as a DevOps engineer or developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcb6b05aff64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to DevOps]]></title>
            <link>https://saurabhasthana.medium.com/introduction-to-devops-cdc201ea3c06?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdc201ea3c06</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 09:16:27 GMT</pubDate>
            <atom:updated>2023-06-13T09:30:48.989Z</atom:updated>
            <content:encoded><![CDATA[<p>“DevOps is the union of people, process, and products to enable continuous delivery of value to our end users.” — According to Donovan Brown in <a href="https://www.donovanbrown.com/post/what-is-devops">What is DevOps?</a></p><p>Below topics will be very helpful while going through your Devops journey and to follow a correct Devops roadmap.</p><ul><li>How to plan for DevOps.</li><li>Use source control.</li><li>Scale Git for an enterprise.</li><li>Combine artifacts.</li><li>Design a dependency management strategy.</li><li>Manage secrets.</li><li>Implement continuous integration.</li><li>Implement a container-build strategy.</li><li>Design a release strategy.</li><li>Set up a release management workflow.</li><li>Implement a deployment pattern.</li><li>Optimize feedback mechanisms.</li></ul><h3>What is the DevOps transformation journey?</h3><p>The DevOps transformation journey is a series of 9 learning paths. It familiarizes you with Azure DevOps and GitHub. Also, learn its many services, features, and integration with tools to support your DevOps process.</p><h3>What is DevOps?</h3><p>The contraction of “Dev” and “Ops” refers to replacing siloed Development and Operations. The idea is to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications. DevOps is a constant journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*3dPyDw9JDY_mJiTk.png" /></figure><h3>Understand your cycle time</h3><p>Let us start with a basic assumption about software development. We will describe it with the OODA (Observe, Orient, Decide, Act) loop. Originally designed to keep fighter pilots from being shot out of the sky, the OODA loop is an excellent way to think about staying ahead of your competitors. You start with observing business, market, needs, current user behavior, and available telemetry data. Then you orient with the enumeration of options for what you can deliver, perhaps with experiments. Next, you decide what to pursue, and you act by delivering working software to real users. You can see all occurring in some cycle time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*O88kxxSqRWO7IE31.png" /></figure><h3>Become data-informed</h3><p>We recommend you use data to inform what to do in your next cycle. Many experience reports tell us that roughly one-third of the deployments will have negative business results. Approximately one-third will have positive results, and one-third will make no difference. Fail fast on effects that do not advance the business and double down on outcomes that support the business. Sometimes the approach is called pivot or persevere.</p><h3>Strive for validated learning</h3><p>How quickly you can fail fast or double down is determined by your cycle time. Also, in how long that loop takes, or in lean terms. Your cycle time determines how quickly you can gather feedback to determine what happens in the next loop. The feedback that you collect with each cycle should be factual, actionable data. We call it validated learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*DqS9IbsFT7bdTSz7.png" /></figure><h3>Shorten your cycle time</h3><p>When you adopt DevOps practices:</p><ul><li>You shorten your cycle time by working in smaller batches.</li><li>Using more automation.</li><li>Hardening your release pipeline.</li><li>Improving your telemetry.</li><li>Deploying more frequently.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*7BHI0vTtiWMGZZEV.png" /></figure><h3>Optimize validated learning</h3><p>The more frequently you deploy, the more you can experiment. The more opportunity you have to pivot or persevere and gain validated learning each cycle. This acceleration in validated learning is the value of the improvement. Think of it as the sum of progress that you achieve and the failures that you avoid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*vVNswqTXCddW8lPO.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdc201ea3c06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ChatGPT recommended top 100 python programs]]></title>
            <link>https://saurabhasthana.medium.com/chatgpt-recommended-top-100-python-programs-9f1f00994533?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f1f00994533</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[python-programming]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Sun, 05 Mar 2023 16:53:28 GMT</pubDate>
            <atom:updated>2023-03-05T16:53:28.278Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>ChatGPT recommended top 100 python programs</strong></p><p>I asked ChatGPT to give me a list of top 100 python programs that will make me a python expert :)</p><p>So the list goes</p><p>1. Hello World program</p><p>2. Arithmetic operations</p><p>3. Printing the Fibonacci sequence</p><p>4. Finding the largest number in a list</p><p>5. Calculating the factorial of a number</p><p>6. Checking if a number is prime or not</p><p>7. Reversing a string</p><p>8. Counting the occurrences of a character in a string</p><p>9. Converting Celsius to Fahrenheit</p><p>10. Generating random numbers</p><p>11. Calculating the area and perimeter of a rectangle</p><p>12. Calculating the area and circumference of a circle</p><p>13. Sorting a list of integers</p><p>14. Merging two sorted lists</p><p>15. Searching for an element in a list</p><p>16. Removing duplicates from a list</p><p>17. Calculating the sum of digits in a number</p><p>18. Checking if a string is a palindrome</p><p>19. Generating a random password</p><p>20. Implementing a stack using a list</p><p>21. Implementing a queue using a list</p><p>22. Converting a decimal number to binary</p><p>23. Converting a binary number to decimal</p><p>24. Calculating the power of a number</p><p>25. Implementing binary search</p><p>26. Implementing linear search</p><p>27. Calculating the GCD and LCM of two numbers</p><p>28. Calculating the square root of a number</p><p>29. Calculating the factorial of a large number using recursion</p><p>30. Converting a string to uppercase or lowercase</p><p>31. Generating a random number within a range</p><p>32. Sorting a list of strings</p><p>33. Implementing bubble sort</p><p>34. Implementing insertion sort</p><p>35. Implementing selection sort</p><p>36. Implementing merge sort</p><p>37. Implementing quick sort</p><p>38. Implementing heap sort</p><p>39. Calculating the distance between two points</p><p>40. Calculating the area of a triangle</p><p>41. Calculating the perimeter of a triangle</p><p>42. Implementing a binary tree</p><p>43. Implementing a binary search tree</p><p>44. Implementing a linked list</p><p>45. Implementing a doubly linked list</p><p>46. Implementing a circular linked list</p><p>47. Implementing a hash table</p><p>48. Implementing a priority queue</p><p>49. Implementing Dijkstra’s algorithm</p><p>50. Implementing the A* algorithm</p><p>51. Implementing the BFS algorithm</p><p>52. Implementing the DFS algorithm</p><p>53. Implementing the Kruskal’s algorithm</p><p>54. Implementing the Prim’s algorithm</p><p>55. Implementing the Bellman-Ford algorithm</p><p>56. Implementing the Floyd-Warshall algorithm</p><p>57. Implementing the K-means algorithm</p><p>58. Implementing the SVM algorithm</p><p>59. Implementing the decision tree algorithm</p><p>60. Implementing the KNN algorithm</p><p>61. Implementing the Naive Bayes algorithm</p><p>62. Implementing the logistic regression algorithm</p><p>63. Implementing the linear regression algorithm</p><p>64. Implementing the neural network algorithm</p><p>65. Implementing the backpropagation algorithm</p><p>66. Implementing the gradient descent algorithm</p><p>67. Implementing the perceptron algorithm</p><p>68. Implementing the random forest algorithm</p><p>69. Implementing the ensemble learning algorithm</p><p>70. Implementing the AdaBoost algorithm</p><p>71. Implementing the bagging algorithm</p><p>72. Implementing the PCA algorithm</p><p>73. Implementing the LDA algorithm</p><p>74. Implementing the Q-learning algorithm</p><p>75. Implementing the DQN algorithm</p><p>76. Implementing the SARSA algorithm</p><p>77. Implementing the REINFORCE algorithm</p><p>78. Implementing the TD-learning algorithm</p><p>79. Implementing the actor-critic algorithm</p><p>80. Implementing the policy gradient algorithm</p><p>81. Implementing the Monte Carlo algorithm</p><p>82. Implementing the simulated annealing algorithm</p><p>83. Implementing the genetic algorithm</p><p>84. Implementing the ant colony optimization algorithm</p><p>85. Implementing the particle swarm optimization algorithm</p><p>86. Implementing the Tabu search algorithm</p><p>87. Implementing the hill climbing algorithm</p><p>88. Implementing the beam search algorithm</p><p>89. Implementing the alpha-beta pruning algorithm</p><p>90. Implementing the minimax algorithm</p><p>91. Implementing the Expectimax algorithm</p><p>92. Implementing the Monte Carlo tree search algorithm</p><p>93. Implementing the policy iteration algorithm</p><p>94. Implementing the value iteration algorithm</p><p>95. Implementing the SARIMAX algorithm</p><p>96. Implementing the ARIMA algorithm</p><p>97. Implementing the exponential smoothing algorithm</p><p>98. Implementing the autoregressive model algorithm</p><p>99. Implementing the moving average model algorithm</p><p>100. Implementing the long short-term memory (LSTM) algorithm.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f1f00994533" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn GIT — Part 2]]></title>
            <link>https://saurabhasthana.medium.com/learn-git-part-2-d2fa71240053?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2fa71240053</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Sat, 04 Mar 2023 04:35:02 GMT</pubDate>
            <atom:updated>2023-03-04T04:35:02.447Z</atom:updated>
            <content:encoded><![CDATA[<h3>Learn GIT — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*BCZkmZR1_YzDZy22Vn4uUw.png" /></figure><p>Git is a powerful tool that allows developers to manage code versioning and collaborate with others on a codebase. One of the essential concepts of Git is the Git add and Git commit commands. In this article, we will explore Git add and Git commit in detail and understand how they work together to help manage code versioning.</p><h3>Git Add</h3><p>The Git add command is used to add changes to the staging area, which is a temporary area where you can prepare your changes before committing them. The staging area allows you to review and organize your changes before making a commit, which helps ensure that your commits are focused and organized.</p><p>The basic syntax for Git add is as follows:</p><pre>git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p]<br>	  [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--sparse]<br>	  [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize]<br>	  [--chmod=(+|-)x] [--pathspec-from-file=&lt;file&gt; [--pathspec-file-nul]]<br>	  [--] [&lt;pathspec&gt;…​]</pre><h3>EXAMPLES</h3><p>Adds content from all *.txt files under Documentation directory and its subdirectories:</p><h4>$ git add Documentation/\*.txt</h4><ul><li>Note that the asterisk * is quoted from the shell in this example; this lets the command include the files from subdirectories of Documentation/ directory.</li></ul><p>Considers adding content from all git-*.sh scripts:</p><h4>$ git add git-*.sh</h4><ul><li>Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not consider subdir/git-foo.sh</li></ul><h4>$ git add .</h4><ul><li>This can be used stage all the files at the current location.</li></ul><p>These are the basic steps required for working with git add command, For advance concepts please refer to <a href="https://git-scm.com/docs/git-add">https://git-scm.com/docs/git-add</a>.</p><p>After running the Git add command, your changes will be added to the staging area. You can review your changes by running the following command:</p><h4>$ git status</h4><pre>git status [&lt;options&gt;] [--] [&lt;pathspec&gt;…​]</pre><p>This command will display the changes that have been added to the staging area and any changes that have not yet been added.</p><p>For advance concepts please refer to <a href="https://git-scm.com/docs/git-status">https://git-scm.com/docs/git-status</a></p><h3>Git Commit</h3><p>Once you have added your changes to the staging area, you can create a commit using the Git commit command. A commit is a snapshot of the codebase at a particular point in time. Each commit has a unique identifier that can be used to track changes over time.</p><p>The basic syntax for Git commit is as follows:</p><pre>git commit [-a | --interactive | --patch] [-s] [-v] [-u&lt;mode&gt;] [--amend]<br>	   [--dry-run] [(-c | -C | --squash) &lt;commit&gt; | --fixup [(amend|reword):]&lt;commit&gt;)]<br>	   [-F &lt;file&gt; | -m &lt;msg&gt;] [--reset-author] [--allow-empty]<br>	   [--allow-empty-message] [--no-verify] [-e] [--author=&lt;author&gt;]<br>	   [--date=&lt;date&gt;] [--cleanup=&lt;mode&gt;] [--[no-]status]<br>	   [-i | -o] [--pathspec-from-file=&lt;file&gt; [--pathspec-file-nul]]<br>	   [(--trailer &lt;token&gt;[(=|:)&lt;value&gt;])…​] [-S[&lt;keyid&gt;]]<br>	   [--] [&lt;pathspec&gt;…​]</pre><p>Create a new commit containing the current contents of the index and the given log message describing the changes. The new commit is a direct child of HEAD, usually the tip of the current branch, and the branch is updated to point to it (unless no branch is associated with the working tree, in which case HEAD is “detached” as described in <a href="https://git-scm.com/docs/git-checkout">git-checkout[1]</a>).</p><p>The content to be committed can be specified in several ways:</p><ol><li>by using <a href="https://git-scm.com/docs/git-add">git-add</a> to incrementally “add” changes to the index before using the <strong>commit</strong> command (Note: even modified files must be “added”);</li><li>by using <a href="https://git-scm.com/docs/git-rm">git-rm</a> to remove files from the working tree and the index, again before using the <strong>commit</strong> command;</li><li>by listing files as arguments to the <strong>commit</strong> command (without — interactive or — patch switch), in which case the commit will ignore changes staged in the index, and instead record the current content of the listed files (which must already be known to Git)</li><li>by using the -a switch with the <strong>commit</strong> command to automatically “add” changes from all known files (i.e. all files that are already listed in the index) and to automatically “rm” files in the index that have been removed from the working tree, and then perform the actual commit.</li><li>by using the — interactive or — patch switches with the <strong>commit</strong> command to decide one by one which files or hunks should be part of the commit in addition to contents in the index, before finalizing the operation. See the “Interactive Mode” section of <a href="https://git-scm.com/docs/git-add">git-add</a> to learn how to operate these modes.</li><li>The --dry-run option can be used to obtain a summary of what is included by any of the above for the next commit by giving the same set of parameters (options and paths).</li></ol><p>If you make a commit and then find a mistake immediately after that, you can recover from it with <strong>git reset</strong>.</p><h3>Best Practices</h3><p>Here are some best practices for using Git add and Git commit effectively:</p><ol><li>Keep your commits focused: Try to make each commit focused on a single change. This makes it easier to track changes over time and understand what has changed.</li><li>Write clear commit messages: A good commit message should be descriptive and concise, explaining the changes you have made in a way that others can understand.</li><li>Review your changes before committing: Use the staging area to review your changes before committing them. This helps ensure that your commits are organized and focused.</li><li>Commit often: It is generally a good practice to commit frequently, especially if you are working on a large codebase. This helps track changes over time and makes it easier to collaborate with others.</li><li>Use branching and merging: Git allows you to create branches, which are separate code paths that can be worked on independently. Branching and merging can help manage complex changes and make it easier to collaborate with others.</li></ol><h3>Conclusion</h3><p>In conclusion, Git add and Git commit are essential commands for managing code versioning with Git. Git add allows you to add changes to the staging area, while Git commit creates a snapshot of the codebase at a particular point in time. By following best practices, such as keeping your commits focused and writing clear commit messages, you can use Git add and Git commit effectively to manage your codebase and collaborate with others. With practice and experience, you can become proficient in using Git to manage code versioning and collaborate effectively with others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2fa71240053" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn GIT — Part 1]]></title>
            <link>https://saurabhasthana.medium.com/learn-git-f550da077665?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f550da077665</guid>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Thu, 16 Feb 2023 16:43:42 GMT</pubDate>
            <atom:updated>2023-02-19T07:49:45.305Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKNIJHFYH4sKRK696134Mg.jpeg" /></figure><p>Learning git can be a very useful skill for managing your code and collaborating with others. Here&#39;s a possible roadmap to follow when learning git:</p><p>Understand the basics: Start by understanding what git is, how it works, and why it is important. Learn about the different terms and concepts such as repository, commit, branch, and merge.</p><h3><strong>Install Git</strong></h3><p>You&#39;ll need to install Git on your computer to use it. Git is available for all major operating systems, including Windows, macOS, and Linux.</p><p>Instructions to install Git on different operating systems:</p><h4>Windows</h4><ol><li>Go to the official Git website (<a href="https://git-scm.com/downloads">https://git-scm.com/downloads</a>) and download the Git installer for Windows.</li><li>Run the downloaded installer and follow the prompts. On Windows, you may need to confirm that you want to allow the installer to make changes to your computer.</li><li>Choose the installation directory and the components you want to install. The default options should be sufficient for most users.</li><li>During the installation, you’ll be asked to choose your preferred text editor and the default branch name. You can leave these as the default options if you’re not sure.</li><li>Once the installation is complete, you can verify that Git is installed by opening a command prompt and typing “git — version”. This should display the version of Git that you just installed.</li></ol><h4>Mac</h4><ol><li>If you have Homebrew installed, open a terminal and type “brew install git”. If you don’t have Homebrew installed, you can download and install it from the official Homebrew website (<a href="https://brew.sh/">https://brew.sh/</a>), and then follow the previous command.</li><li>If you don’t want to use Homebrew, you can go to the official Git website (<a href="https://git-scm.com/downloads">https://git-scm.com/downloads</a>) and download the Git installer for Mac.</li><li>Run the downloaded installer and follow the prompts.</li><li>Once the installation is complete, you can verify that Git is installed by opening a terminal and typing “git — version”. This should display the version of Git that you just installed.</li></ol><h4>Linux</h4><p>The exact steps to install Git on Linux will depend on the specific distribution you’re using. Here are instructions for some popular distributions:</p><h4>Ubuntu/Debian</h4><ol><li>Open a terminal and type “sudo apt-get update” to update the package list.</li><li>Type “sudo apt-get install git” to install Git.</li><li>Once the installation is complete, you can verify that Git is installed by typing “git — version” in the terminal.</li></ol><h4>CentOS/Fedora</h4><ol><li>Open a terminal and type “sudo yum install git” to install Git.</li><li>Once the installation is complete, you can verify that Git is installed by typing “git — version” in the terminal.</li></ol><h4>Arch Linux</h4><ol><li>Open a terminal and type “sudo pacman -S git” to install Git.</li><li>Once the installation is complete, you can verify that Git is installed by typing “git — version” in the terminal.</li></ol><p>That’s it! You should now have Git installed on your computer, regardless of the operating system you’re using.</p><p><strong>Set up Git</strong>: Configure your name and email in Git, so that your commits can be attributed to you. You can do this by running the &quot;git config&quot; command in your terminal.</p><p>here’s a brief guide on how to set up Git on different operating systems:</p><p><strong>MacOS:</strong></p><ol><li>Open the Terminal app.</li><li>Type the following command to install Homebrew: /bin/bash -c &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)&quot;</li><li>Type the following command to install Git: brew install git</li><li>Verify that Git is installed by running the command: git --version</li></ol><p><strong>Windows:</strong></p><ol><li>Download the Git installer for Windows from the official Git website: <a href="https://git-scm.com/download/win">https://git-scm.com/download/win</a></li><li>Run the installer and follow the prompts to complete the installation.</li><li>Verify that Git is installed by opening the Command Prompt and running the command: git --version</li></ol><p><strong>Linux (Ubuntu):</strong></p><ol><li>Open the Terminal app.</li><li>Type the following command to update the package list: sudo apt-get update</li><li>Type the following command to install Git: sudo apt-get install git</li><li>Verify that Git is installed by running the command: git --version</li></ol><p>These are the basic steps to install Git on different operating systems. Once installed, you can configure Git and start using it to manage your source code and collaborate with other developers.</p><p><strong>Create a repository</strong>: Create a new Git repository to work with. You can do this by running the &quot;git init&quot; command in your terminal, which initializes an empty repository.</p><p><strong>Create a new Git repository:</strong></p><p>Create a new directory on your local machine where you want to store the repository. Open a terminal or command prompt and navigate to the directory using the cd command.</p><p>Once you are inside the directory, run the following command to initialize a new Git repository:</p><ul><li>git init</li></ul><p>This will create a new .git directory in your project folder, which is where Git will store all the version control information. Next, create some files in your project directory, or copy over some existing files that you want to version control.</p><p>We will continue to learn more about GIT in next part.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f550da077665" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of Container Architecture]]></title>
            <link>https://saurabhasthana.medium.com/overview-of-container-architecture-cddd093fb139?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cddd093fb139</guid>
            <category><![CDATA[redhat-openshift]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[redhat-linux]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Sat, 30 Apr 2022 08:32:56 GMT</pubDate>
            <atom:updated>2022-04-30T08:32:56.031Z</atom:updated>
            <content:encoded><![CDATA[<h3>Objectives</h3><p>After completing this section, you should be able to:</p><ul><li>Describe the architecture of Linux containers.</li><li>Describe the podman tool for the managing containers.</li></ul><h3>Introducing Container History</h3><p>Containers have quickly gained popularity in recent years. However, the technology behind containers has been around for a relatively long time. In 2001, Linux introduced a project named VServer. VServer was the first attempt at running complete sets of processes inside a single server with a high degree of isolation.</p><p>From VServer, the idea of isolated processes further evolved and became formalized around the following features of the Linux kernel:</p><p><strong>Namespaces</strong></p><p>A namespace isolates specific system resources usually visible to all processes. Inside a namespace, only processes that are members of that namespace can see those resources. Namespaces can include resources like network interfaces, the process ID list, mount points, IPC resources, and the system’s hostname information.</p><p><strong>Control groups (cgroups)</strong></p><p>Control groups partition sets of processes and their children into groups to manage and limit the resources they consume. Control groups place restrictions on the amount of system resources processes might use. Those restrictions keep one process from using too many resources on the host.</p><p><strong>Seccomp</strong></p><p>Developed in 2005 and introduced to containers circa 2014, Seccomp limits how processes could use system calls. Seccomp defines a security profile for processes, whitelisting the system calls, parameters, and file descriptors they are allowed to use.</p><p><strong>SELinux</strong></p><p>Security-Enhanced Linux (SELinux) is a mandatory access control system for processes. Linux kernel uses SELinux to protect processes from each other and to protect the host system from its running processes. Processes run as a confined SELinux type that has limited access to host system resources.</p><p>All of these innovations and features focus on a basic concept: enabling processes to run isolated while still accessing system resources. This concept is the foundation of container technology and the basis for all container implementations. Nowadays, containers are processes in the Linux kernel making use of those security features to create an isolated environment. This environment forbids isolated processes from misusing system or other container resources.</p><p>A common use case of containers is having several replicas of the same service (for example, a database server) in the same host. Each replica has isolated resources (file system, ports, memory), so there is no need for the service to handle resource sharing. Isolation guarantees that a malfunctioning or harmful service does not impact other services or containers in the same host, nor in the underlying system.</p><h3>Describing Linux Container Architecture</h3><p>From the Linux kernel perspective, a container is a process with restrictions. However, instead of running a single binary file, a container runs an image. An image is a file-system bundle that contains all dependencies required to execute a process: files in the file system, installed packages, available resources, running processes, and kernel modules.</p><p>Like executable files are the foundation for running processes, images are the foundation for running containers. Running containers use an immutable view of the image, allowing multiple containers to reuse the same image simultaneously. As images are files, they can be managed by versioning systems, improving automation on container and image provisioning.</p><p>Container images need to be locally available for the container runtime to execute them, but the images are usually stored and maintained in an image repository. An image repository is just a service — public or private — where images can be stored, searched, and retrieved. Other features provided by image repositories are remote access, image metadata, authorization or image version control.</p><p>There are many different image repositories available, each one offering different features:</p><ul><li><a href="https://registry.redhat.io/">Red Hat Container Catalog</a></li><li><a href="https://hub.docker.com/">Docker Hub</a></li><li><a href="https://quay.io/">Red Hat Quay</a></li><li><a href="https://cloud.google.com/container-registry/">Google Container Registry</a></li><li><a href="https://aws.amazon.com/ecr/">Amazon Elastic Container Registry</a></li></ul><h3>Managing Containers with Podman</h3><p>Containers, images, and image registries need to be able to interact with each other. For example, you need to be able to build images and put them into image registries. You also need to be able to retrieve an image from the image registry and build a container from that image.</p><p>Podman is an open-source tool for managing containers and container images and interacting with image registries. It offers the following key features:</p><ul><li>It uses the image format specified by the <a href="https://www.opencontainers.org/">Open Container Initiative</a> (OCI). Those specifications define a standard, community-driven, non-proprietary image format.</li><li>Podman stores local images in the local file system. Doing so avoids unnecessary client/server architecture or having daemons running on the local machines.</li><li>Podman follows the same command patterns as the Docker CLI, so there is no need to learn a new toolset.</li><li>Podman is compatible with Kubernetes. Kubernetes can use Podman to manage its containers.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cddd093fb139" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginning of Data Science Journey]]></title>
            <link>https://saurabhasthana.medium.com/beginning-of-data-science-journey-d46ec3a4ee49?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d46ec3a4ee49</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data-scientist]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Sun, 24 Jan 2021 19:41:07 GMT</pubDate>
            <atom:updated>2021-01-25T18:19:20.096Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A3UAmyPVyrzhlvRJnd3rNA.jpeg" /></figure><p><strong>Hello</strong> everyone, I have been working in IT industry for around 10 years, specializing in leading high-performing and multi-disciplinary teams from product development through successful product launches. Accustomed to managing multiple projects and priorities in fast-paced environments. I am committed to maintaining cutting edge technical skills and up-to-date industry knowledge.</p><p>In past few years I have tried to learn coding in Python, Java, C and C++ but it did not go through and stopped after a point.</p><p>This is the beginning of a hopeful 2021, leaving behind all the odds of 2020 I want to accelerate my learning. In past few months I have learned few things that I wouldn’t imagine knowing 6 months before. I know that self learning is very challenging but at the same time it can be fun also. The amount of knowledge now available over the internet is just amazing. Now we don’t have to pay for learning most of the things. The experiences and knowledge which people now share over the internet is undoubtedly one of the most useful resource for self learners.</p><p>I am a beginner in Data Science and trying to learn on my own, taking one step at a time. I want to share my journey with everyone as i move along. I feel sharing my journey and the challenges that i face, will be a great motivation for myself in learning something new and sharing with everyone.</p><p>I will also be sharing my progress on my <a href="https://github.com/asthanas"><strong>GitHub</strong></a><strong> </strong>updating it frequently to track progress.</p><p>So I will start by asking a very simple question.</p><h4>What should be our approach towards learning and mastering anything ?</h4><p>According to me there are 5 most effective approach, which are :</p><ol><li>Read</li><li>Listen</li><li>Build</li><li>Communicate</li><li>Network</li></ol><p>📚<strong>Read</strong>: According to me reading is one of the most important approach which one should have. Reading not only helps in learning new skills but also helps in personal growth. But it is very important to choose right books, articles and other reading resources in order to reach your desired goal. With the amount of resources now available over the internet its very easy to get caught up and waste a lot of time. So it becomes very necessary to have a good library, that will help you to solve problems while working on any project.</p><p><em>“The more that you read, the more things you will know. The more that you learn, the more places you’ll go.” </em><strong><em>— Dr. Seuss</em></strong></p><p>👂<strong>Listen</strong>: Without a doubt, one of the most important skill is having a good listening ability. Listening is the key to all effective communication. Listening is the ability to accurately receive and interpret messages in the communication process. Without the ability to listen effectively, messages are easily misunderstood. As a result, communication breaks down and the sender of the message can easily become frustrated or irritated.</p><p><em>“The most basic of all human needs is to understand and be understood. The best way to understand people is to listen to them.” </em><strong><em>— Ralph Nichols</em></strong></p><p>🔧🔨<strong>Build</strong>: Practice…Practice and Practice. Build projects, even the smallest one. Let it fail, learn from your mistake, ask for feedback from others and work on it. Getting your hands dirty is the best way to reach your goal. This will help you in applying theoretical concepts and improve your problem solving skills.</p><p><em>“If you don’t practice, you don’t deserve to win.” — </em><strong><em>Andre Agassi</em></strong></p><p>📢<strong>Communicate: </strong>Being able to communicate effectively is perhaps the most important of all life skills. It is what enables us to pass information to other people, and to understand what is said to us. For a Data Scientist its extremely important to communicate his ideas and present in front of an audience.</p><p><em>“To effectively communicate, we must realize that we are all different in the way we perceive the world and use this understanding as a guide to our communication with others.” — </em><strong><em>Anthony Robbins</em></strong></p><p>👨‍👩‍👧‍👦<strong>Network</strong>: Networking, most important approach of modern world. Create your LinkedIn profile, join group discussion. Create blogs, go to events. Don’t hesitate in expressing yourself, you may not be right every time, but you will be once you come to know about your mistake. Get out of your comfort zone. Follow people on medium, linkedin and other social networking sites. To stand out from the crowd, you have to market yourself and network is the best market.</p><p><em>“Networking is marketing. Marketing yourself, your uniqueness, what you stand for.” </em><strong><em>-- Christine Comaford-Lynch</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d46ec3a4ee49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Science]]></title>
            <link>https://saurabhasthana.medium.com/data-science-ed1dee9ef834?source=rss-fc126a95c9f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed1dee9ef834</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Saurabh Asthana]]></dc:creator>
            <pubDate>Sun, 17 Jan 2021 05:25:28 GMT</pubDate>
            <atom:updated>2021-01-17T19:08:05.124Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Over the past few years we have seen very significant changes in the business infrastructure, that has completely changed the ability to collect data. Terabytes and Petabytes of data getting generated within matter of seconds. Each and every aspect of business is now dependent on data, starting from very small to biggest business decisions. With increasing infrastructure, information is now widely available on each and every event happening around us such as financial trends, business competition and news. This broad availability of data has led to the use of various methods to extract useful information from the huge amount of data. These useful informations are then used to solve several business problems.</p><p>With vast amount of data available, companies are trying to exploit that data for a competative advantage. One of the most important thing to note here is that, that data has always been there. Earlier statisticians use to analyze those data manually using various quantitive methods. With the evolution of technology two things that has contributed to increase in exploitation of data are :</p><ol><li>Ability to store huge amount of data.</li><li>Increased processing speed of hardware.</li></ol><p>In addition to this, development of advanced algorithms, advanced tools and community support across the globe has greatly contributed to a deeper analysis of data with huge volume and variety, which was not possible using manual statistical methods.</p><p>So next the big question…</p><h3>What is Data ?</h3><p>Data are characteristics or information, usually numerical, that are collected through observation. In a more technical sense, data are a set of values of qualitative or quantitative variables about one or more persons or objects, while a datum (singular of data) is a single value of a single variable.</p><p>I will be discussing more about data in my next post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed1dee9ef834" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>