<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/" 
  xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:atom="http://www.w3.org/2005/Atom" 
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
  xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>GO starter on Neeraj Sidhaye</title>
    <link>https://neerajsidhaye.github.io/tags/go-starter.html</link>
    <description>Recent content in GO starter on Neeraj Sidhaye</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&amp;copy;{year}, All Rights Reserved</copyright>
    <lastBuildDate>Mon, 10 Jul 2023 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://neerajsidhaye.github.io/tags/go-starter/index.xml" rel="self" type="application/rss+xml" />
    

      
      <item>
        <title>Go - Slice</title>
        <link>https://neerajsidhaye.github.io/posts/go/core/slice/goslicebasics.html</link>
        <pubDate>Mon, 10 Jul 2023 00:00:00 +0000</pubDate>
        
        <atom:modified>Mon, 10 Jul 2023 00:00:00 +0000</atom:modified>
        <guid>https://neerajsidhaye.github.io/posts/go/core/slice/goslicebasics.html</guid>
        <description>Small post to explain go slice basics, specially around slice length and capacity.
How an underlyig array is created in memory when we
 create a new slice create a new slice from an existing slice appending elments to a slice what happnes when underlaying array is full when we keep appending elements to slice.  Refer to code go slice basic example here
go slice visuals </description>
        
        <dc:creator>Neeraj Sidhaye</dc:creator>
        <media:content url="https://neerajsidhaye.github.io//images/posts/go/starter/go-slice-img.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>GO starter</category>
            
          
        
        
        
      </item>
      
      <item>
        <title>Go - Project Structure</title>
        <link>https://neerajsidhaye.github.io/posts/go/starter/goprojectlayout.html</link>
        <pubDate>Mon, 15 Feb 2021 00:00:00 +0000</pubDate>
        
        <atom:modified>Mon, 15 Feb 2021 00:00:00 +0000</atom:modified>
        <guid>https://neerajsidhaye.github.io/posts/go/starter/goprojectlayout.html</guid>
        <description>I am sure, how to structure a Go Project, would have been most obvious question which everybody have thought through and it is very obvious. Specially after we write some basic hello world which has only main.go or after doing workouts in Go Playground
As we step up and write more code which involve various layering, then it becomes very essential to organize the code, so that:-
 easy to understand and maintain each package purpose becomes self explanatory by it&amp;rsquo;s name reduce interdependencies in the code increase code reusability ease of collaboration  Well, you can think of more points, but the fact is, it is very important to follow a basic template which is set a as standard by various GO projects ( GO doesn&amp;rsquo;t provide any official docs on project structure as such) and later on top of that, one can evolve their own structure as needed.</description>
        
        <dc:creator>Neeraj Sidhaye</dc:creator>
        <media:content url="https://neerajsidhaye.github.io//images/posts/go/starter/goprojectlayout.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>GO starter</category>
            
          
        
        
        
      </item>
      

    
  </channel>
</rss>