<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on TUTYSARA'S SPACE</title><link>https://www.tutysara.net/tags/go/</link><description>Recent content in Go on TUTYSARA'S SPACE</description><generator>Hugo</generator><language>en-EN</language><copyright>(c) 2026 tutysara</copyright><lastBuildDate>Sat, 14 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.tutysara.net/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Clean Code vs A Philosophy of Software Design</title><link>https://www.tutysara.net/posts/2026/02/14/clean-code-vs-a-philosophy-of-software-design/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.tutysara.net/posts/2026/02/14/clean-code-vs-a-philosophy-of-software-design/</guid><description>&lt;p&gt;Reading through many lines of code in Golang and Java makes for an interesting observation from the codebase which I was taking a look.&lt;/p&gt;
&lt;p&gt;There were different styles of coding and it was obvious from reading code that is written by experienced gophers.&lt;/p&gt;
&lt;p&gt;People on team who do both Java and Golang use the same Java style in Golang as well.&lt;/p&gt;
&lt;p&gt;While most Java programmers come from Clean code school of thought where functions are decomposed into many smaller functions which results in function explosion in the same file.&lt;/p&gt;</description></item></channel></rss>