<?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[Agentic Engineering - Medium]]></title>
        <description><![CDATA[Tips and tricks, best practices, learning around Agentic Engineering and Best Practices - Medium]]></description>
        <link>https://medium.com/ispeakjs?source=rss----cf85e88c7d6---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Agentic Engineering - Medium</title>
            <link>https://medium.com/ispeakjs?source=rss----cf85e88c7d6---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:32:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ispeakjs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Good one, bookmarked!!]]></title>
            <link>https://medium.com/ispeakjs/good-one-bookmarked-925fc1e96dd0?source=rss----cf85e88c7d6---4</link>
            <guid isPermaLink="false">https://medium.com/p/925fc1e96dd0</guid>
            <dc:creator><![CDATA[Anoop Gupta]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 05:02:43 GMT</pubDate>
            <atom:updated>2020-09-11T05:02:43.448Z</atom:updated>
            <content:encoded><![CDATA[<p>Good one, bookmarked!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=925fc1e96dd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ispeakjs/good-one-bookmarked-925fc1e96dd0">Good one, bookmarked!!</a> was originally published in <a href="https://medium.com/ispeakjs">Agentic Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Precise, concise and useful. Nicely articulated Pavan Podila]]></title>
            <link>https://medium.com/ispeakjs/precise-concise-and-useful-nicely-articulated-pavan-podila-e4c1aaa29c25?source=rss----cf85e88c7d6---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4c1aaa29c25</guid>
            <dc:creator><![CDATA[Anoop Gupta]]></dc:creator>
            <pubDate>Sat, 09 Nov 2019 11:28:02 GMT</pubDate>
            <atom:updated>2019-11-09T11:28:02.765Z</atom:updated>
            <content:encoded><![CDATA[<p>Precise, concise and useful. Nicely articulated <a href="https://medium.com/u/fc769b8e3de6">Pavan Podila</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4c1aaa29c25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ispeakjs/precise-concise-and-useful-nicely-articulated-pavan-podila-e4c1aaa29c25">Precise, concise and useful. Nicely articulated Pavan Podila</a> was originally published in <a href="https://medium.com/ispeakjs">Agentic Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git commands and tips, I use frequently]]></title>
            <link>https://medium.com/ispeakjs/git-commands-and-tips-i-use-frequently-915c59170cdd?source=rss----cf85e88c7d6---4</link>
            <guid isPermaLink="false">https://medium.com/p/915c59170cdd</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Anoop Gupta]]></dc:creator>
            <pubDate>Sun, 18 Mar 2018 16:49:28 GMT</pubDate>
            <atom:updated>2018-03-18T22:19:54.432Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part- 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P66WqtgUc6l6Rh9rIwbMLg.jpeg" /></figure><p>I have been using Git for almost four years and kept my day to day Git commands and tips in a document to just copy and use as and when required.</p><p>I just want to share my compilation of git commands and tips, I use in my day to day workflow. Hope it will help.</p><p><strong>Git Aliases</strong></p><p>This is not a command but if you are tired of writing a full git command, Git Aliases can make your life very easy. You can easily setup an alias for any Git Command. Treat it as a git shortcut.</p><p>For example:</p><p>Instead of “git checkout”, I use “git co”. So how you can set it up ?</p><p>Here we go, just write below line in your teminal</p><pre>$ git config --global alias.co checkout</pre><p>Here</p><p>$ git config --global telling git to update global configuration file</p><p>alias.co defining your alias name</p><p>checkout is your main git command</p><p>You can set as many as aliases based on your requirements. I generally use for check last commit, complex logging, checking differences visually etc.</p><p>If you want to <a href="https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases">read more</a> about aliases, please <a href="https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases">click here</a>.</p><h3>Advance Git Commands</h3><p>Other than aliases here are some git commands, I use in my day to day activities. Today I will focus on viewing the commit history.</p><p>Have you used “git log”. What a pretty bored B/W output.</p><p>Instead of a black and white log of your commits, use below for a colourful, more visible log</p><blockquote><em>$ git log --graph --pretty=format:&#39;%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset&#39; --abbrev-commit</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-TvTBlYzsQ15d5vtqJ_nw.png" /><figcaption>The colorful git log</figcaption></figure><p>Above command seems very complex. Isn’t it?</p><p>Why don’t you use git alias for that. Copy and paste below line in your teminal</p><pre>git config --global alias.lg &quot;log --color --graph --pretty=format:&#39;%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset&#39; --abbrev-commit&quot;</pre><p>Woo hoo…now, what you all need to do is, use “git lg” to see your colourful logs</p><pre>git lg</pre><p>If you want to see, the log of lines changed, jus use</p><pre>git lg -p</pre><p>You can use other log options along with above alias.</p><p>For example:</p><p>-p</p><p>Show the patch introduced with each commit.</p><p>--stat</p><p>Show statistics for files modified in each commit.</p><p>--shortstat</p><p>Display only the changed/insertions/deletions line from the — stat command.</p><p>--name-only</p><p>Show the list of files modified after the commit information.</p><p>--name-status</p><p>Show the list of files affected with added/modified/deleted information as well.</p><p>--abbrev-commit</p><p>Show only the first few characters of the SHA-1 checksum instead of all 40.</p><p>--relative-date</p><p>Display the date in a relative format (for example, “2 weeks ago”) instead of using the full date format.</p><p>--graph</p><p>Display an ASCII graph of the branch and merge history beside the log output.</p><p>--pretty</p><p>Show commits in an alternate format. Options include oneline, short, full, fuller, and format (where you specify your own format).</p><p>--oneline</p><p>Shorthand for --pretty=oneline --abbrev-commit used together.</p><p>You can read more about git logging by clicking at below reference.</p><p>Reference: <a href="https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History">https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History</a></p><p>Thats it for today. I will share some more useful git commands in this series.</p><p>Till then, have a great weekend.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915c59170cdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ispeakjs/git-commands-and-tips-i-use-frequently-915c59170cdd">Git commands and tips, I use frequently</a> was originally published in <a href="https://medium.com/ispeakjs">Agentic Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oops! OO Patterns vs OO Principles vs OO Programming Systems]]></title>
            <link>https://medium.com/ispeakjs/oops-oo-patterns-vs-oo-principles-vs-oo-programming-systems-bab8619fca59?source=rss----cf85e88c7d6---4</link>
            <guid isPermaLink="false">https://medium.com/p/bab8619fca59</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[object-oriented]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Anoop Gupta]]></dc:creator>
            <pubDate>Fri, 03 Nov 2017 14:25:23 GMT</pubDate>
            <atom:updated>2019-09-11T21:10:15.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="OOPS" src="https://cdn-images-1.medium.com/max/686/1*E0d3l_ykyHg_odPaFNf1Bw.jpeg" /></figure><p>Preface: That blog is all about a basic introduction to OOPS, Design Patterns, and Principles. It is not meant for learning OOPS concepts in detail :)</p><p>Last evening I was spending my quality time after office hours with some of my colleagues including some junior team members.<br>I read somewhere that “Girls want attention and women want respect” and to extend that statement in men’s world. “ Men want a beer and drunk men want a discussion and on the top of that “Drunk techie men want to discuss OOPS”. isn’t it ironic? At least with me, it happens quite often.</p><p>Anyways, to spoil that evening one of my teammates asked a very simple question. “<strong>What’s the full form of OOPS</strong>”?<br>What do you think?</p><p>Here are some answers, you have to choose:<br><strong>A. Object Oriented Principles<br>B. Object-Oriented Patterns<br>C. Object-Oriented Programming System<br>D. An exclamation word in English used to show recognition of a mistake</strong></p><p>You won’t believe Option D was my answer. That was: Oops! A fight is going to start.</p><p>In order to stop that discussion, I pitched in and asked a question for question.<br><strong>What do you understand by Principles and Patterns?</strong><br>I got some mixed answers and then started giving my explanation and kept aside OOPS.<br>In plain English, the main difference between a Pattern and Principle is:<br><strong>Pattern</strong>: Pattern is a general solution to a commonly occurring problem.<br><strong>Principle</strong>: Principle is a set of guidelines to implement any pattern.<br>In <strong>Object-Oriented Programming Systems</strong>, yes you got it right, (that’s a full form of OOPS) or in software engineering, there are different concepts of Design Patterns and Design Principles, given as follows:<br><strong>Design Pattern</strong>: By definition, a Design Pattern is a general reusable solution to a commonly occurring problem within a given context in software design.<br>Example: Factory, Singleton etc which come under a superset of design patterns commonly known as <strong>Gang of Four</strong><br><strong>Design Principles</strong>: Design principles represent a set of guidelines that help us to avoid having a bad design and direct to implement a better solution.<br>For example: <strong>SOLID</strong> principles of OOPS<br><strong>S.O.L.I.D stands for:</strong><br>When expanded the acronyms might seem complicated, but they are pretty simple to grasp.<br>S — Single-responsiblity principle<br>O — Open-closed principle<br>L — Liskov substitution principle<br>I — Interface segregation principle<br>D — Dependency Inversion Principle</p><p>We can learn more about design patterns and principles in my upcoming blog.<br>Let’s discuss <strong>OOPS</strong> — Object Oriented Programming System<br>In this world, everything (living or nonliving) is an Object, a real-world entity such as book, tv, chair, table etc. <br>Object-Oriented Programming System is a methodology to design a software solution using classes and objects. It simplifies the software development by providing some concepts known as elements of Object Oriented Development.<br>1. Object<br>2. Class<br>3. Inheritance<br>4. Polymorphism<br>5. Abstraction<br>6. Encapsulation</p><p>I will provide a detailed blog about <strong>Elements of Object Oriented Programming</strong>.</p><p>I tried my best to explain little things in a better way and thanks to my teammate who asked that question because “If you want the answer — ask the question.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bab8619fca59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ispeakjs/oops-oo-patterns-vs-oo-principles-vs-oo-programming-systems-bab8619fca59">Oops! OO Patterns vs OO Principles vs OO Programming Systems</a> was originally published in <a href="https://medium.com/ispeakjs">Agentic Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>