<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Sourav Kumar</title>
    <description>The latest articles on Forem by Sourav Kumar (@sourav_codey).</description>
    <link>https://forem.com/sourav_codey</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F885116%2F3f8ee9e9-a2f0-4549-bd95-f2062403308a.jpg</url>
      <title>Forem: Sourav Kumar</title>
      <link>https://forem.com/sourav_codey</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/sourav_codey"/>
    <language>en</language>
    <item>
      <title>Good commit message V/S Bad commit message 🦾</title>
      <dc:creator>Sourav Kumar</dc:creator>
      <pubDate>Tue, 16 Jul 2024 10:43:22 +0000</pubDate>
      <link>https://forem.com/sourav_codey/good-commit-message-vs-bad-commit-message-jhi</link>
      <guid>https://forem.com/sourav_codey/good-commit-message-vs-bad-commit-message-jhi</guid>
      <description>&lt;h4&gt;
  
  
  When developers are pushing their code to VCS(Version Control System) such as Git. If you are working in any industry for production level code.
&lt;/h4&gt;

&lt;h4&gt;
  
  
  One should learn to write better commit message and make it a habit so that it is easy for co-developers to understand the code just by seeing the commit message.
&lt;/h4&gt;




&lt;blockquote&gt;
&lt;p&gt;You can use git log command to check all the commit messages, I bet you will come to see “Yep… I have absolutely no idea what I meant by ‘Fix style’ 6 months ago.” that doesn’t make any sense, what is fixed, what is the issue. 🥴&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;&lt;strong&gt;Structure of Git commit message&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Condensed&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git commit -m &amp;lt;message&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Detailed&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git commit -m &amp;lt;title&amp;gt; -m &amp;lt;description&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Tips for writing commit message&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;em&gt;Use first letter as capital and rest as lowercase &lt;strong&gt;(title case)&lt;/strong&gt;.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Use type of commit message e.g. bugfix, error, refactor, bump, config.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Commit length of body must be 50 characters and description must be at 
least 72 characters.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Be specific, don’t use worked, developed, thought, rather be direct, 
“fix”.&lt;/em&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;strong&gt;The commit type can include the following:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;feat – a new feature is introduced with the changes&lt;/li&gt;
&lt;li&gt;fix – a bug fix has occurred&lt;/li&gt;
&lt;li&gt;chore – changes that do not relate to a fix or feature and don't modify src or test files (for example updating dependencies)&lt;/li&gt;
&lt;li&gt;refactor – refactored code that neither fixes a bug nor adds a feature&lt;/li&gt;
&lt;li&gt;docs – updates to documentation such as a the README or other markdown files&lt;/li&gt;
&lt;li&gt;style – changes that do not affect the meaning of the code, likely related to code formatting such as white-space, missing semi-colons, and so on&lt;/li&gt;
&lt;li&gt;test – including new or correcting previous tests&lt;/li&gt;
&lt;li&gt;perf – performance improvements&lt;/li&gt;
&lt;li&gt;ci – continuous integration related&lt;/li&gt;
&lt;li&gt;build – changes that affect the build system or external dependencies&lt;/li&gt;
&lt;li&gt;revert – reverts a previous commit&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>github</category>
      <category>git</category>
      <category>commit</category>
      <category>development</category>
    </item>
    <item>
      <title>Library v/s Framework</title>
      <dc:creator>Sourav Kumar</dc:creator>
      <pubDate>Tue, 16 Jul 2024 10:41:54 +0000</pubDate>
      <link>https://forem.com/sourav_codey/library-vs-framework-2afd</link>
      <guid>https://forem.com/sourav_codey/library-vs-framework-2afd</guid>
      <description>&lt;h2&gt;
  
  
  Ever confused between library and frameworks ???
&lt;/h2&gt;




&lt;p&gt;Do you also get confused about these two and used these two terms interchangeably.&lt;br&gt;
Let me help you understand these two so you will have a better clarity.&lt;/p&gt;




&lt;p&gt;First, lets start with definition:&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Library&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;A collection of predefined methods, classes or interfaces used for solving common problems.&lt;br&gt;
It comes either bundled with a language or can be downloaded from internet and used.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Examples - react.js, twilio, iText, apache commons and lot more.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Benefits of using library:
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Reusability&lt;/li&gt;
&lt;li&gt;Reduces programmer's effort&lt;/li&gt;
&lt;li&gt;Allows programmer to focus on main problem&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  &lt;strong&gt;Framework&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;A collection of libraries is called framework, it provides a foundation on which we develop our code.&lt;br&gt;
It provides pre-written common logics so that developers can focus on business logic only also called components.&lt;/p&gt;

&lt;p&gt;Frameworks can be further divided into following sub categories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Frontend framework&lt;/li&gt;
&lt;li&gt;Web framework&lt;/li&gt;
&lt;li&gt;Application Development framework&lt;/li&gt;
&lt;li&gt;ORM framework &lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;Examples - angular, spring, hibernate, struts and more.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Benefits of using framework:
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Speeds up development process&lt;/li&gt;
&lt;li&gt;The code is more secured than library&lt;/li&gt;
&lt;li&gt;Forces developers to follow standard procedures and hence make our code clean and therefore is opinionated&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Difference between library and framework
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Libraries are lightweight whereas frameworks are more bulky.&lt;/li&gt;
&lt;li&gt;Libraries are more flexible than frameworks.&lt;/li&gt;
&lt;li&gt;Frameworks call our code whereas we developers call library methods or functions.&lt;/li&gt;
&lt;li&gt;Frameworks employ the concept of IoC(Inversion of Control) where framework tells developers how to write the code.&lt;/li&gt;
&lt;li&gt;Frameworks controls the flow of application but we can use force library to control the flow of application.&lt;/li&gt;
&lt;li&gt;Libraries are more flexible than frameworks.&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I hope you know the difference and advantages and disadvantages of using libraries and frameworks 🏗️.&lt;br&gt;
If, you want to develop overall architecture of an application by using best practices and standards, you can use framework but if you want to develop application at a greater pace with your own custom logics and control flow on your own, you can use library 📚.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Follow me on &lt;a href="https://x.com/thisis_souraev" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; for more.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>library</category>
      <category>framework</category>
      <category>frontend</category>
      <category>spring</category>
    </item>
  </channel>
</rss>
