<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Maven on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/maven/</link>
		<description>Recent content in Maven on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Fri, 07 Dec 2012 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/maven/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The art of achieving perfection</title>
				<link>https://hitesh.in/2012/the-art-of-achieving-perfection/</link>
				<pubDate>Fri, 07 Dec 2012 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2012/the-art-of-achieving-perfection/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.&lt;/p&gt;&#xA;&lt;p&gt;- Antoine de Saint-Exupery&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h3 id=&#34;the-story-of-maven-is-a-journey-towards-perfection&#34;&gt;The story of Maven is a journey towards perfection.&lt;/h3&gt;&#xA;&lt;p&gt;What started as common sense, slowly evolved into a way of doing things – the Artha Shastra way. The ad-hoc, piece meal approach gave way to a structured and systematic approach to problem-solving. This was step one of removing the cruft and starting on the path to perfection.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How to build the unimaginable?</title>
				<link>https://hitesh.in/2012/how-to-build-the-unimaginable/</link>
				<pubDate>Sat, 01 Dec 2012 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2012/how-to-build-the-unimaginable/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Get started…&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Those were my thoughts when I took up the challenge of building Maven (then known as Project Andromeda).&lt;/p&gt;&#xA;&lt;p&gt;There were so many reasons not to do it, unfinished and continuously evolving specs, unknown complexity, several dependencies, no development team in place, no clear target user, unproven market, extremely aggressive deadlines, fear of running out of money etc. But there was one important reason to do it: it hasn’t been done before.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
