<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>sunilshenoy.com</title><link>http://www.sunilshenoy.com/</link><description>I’m Sunil Shenoy, founder of Float Gravity Web Studio.Programmer, Traveller, Movie buff</description><item><title>WHAT DOES IT MEAN TO BE SIMPLE?</title><link>http://www.sunilshenoy.com/2012/04/15/what-does-it-mean-to-be-simple</link><guid isPermaLink="false">/2012/04/15/what-does-it-mean-to-be-simple</guid><pubDate>Sun, 15 Apr 2012 01:00:00 IST</pubDate><description>&lt;blockquote&gt;
  &lt;p&gt;All designers say simplicity is important, but what does it really mean to make something simple? Most of the time we think it means less, that by removing stuff we achieve simplicity. We think by keeping content above the fold we’re helping people focus, or by using bullets instead of paragraphs more people will read it, or by cutting text in half it becomes more clear. But simple doesn’t mean “less”. A better definition would be “just enough”.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Worth a read. &lt;a href="http://52weeksofux.com/post/21026021557/what-does-it-mean-to-be-simple"&gt;WHAT DOES IT MEAN TO BE SIMPLE?&lt;/a&gt;.&lt;/p&gt;
</description></item><item><title>Throw it all away if you know you can do it better</title><link>http://www.sunilshenoy.com/2012/04/14/throw-it-all-away-if-you-know-you-can-do-it-better</link><guid isPermaLink="false">/2012/04/14/throw-it-all-away-if-you-know-you-can-do-it-better</guid><pubDate>Sat, 14 Apr 2012 08:31:00 IST</pubDate><description>&lt;blockquote&gt;
  &lt;p&gt;8) Throw it all away if you know you can do it better&lt;/p&gt;
  
  &lt;p&gt;Don’t be afraid to throw it all away and start over if you can afford to. The best designers and developers in the world don’t get “it” right the first time, rarely get it right the second time and maybe get it right the third time. As an example, Flud designed and launched four web apps privately, and we’ve continually thrown them all away because they weren’t creating the right experience. We finally have something that works and it will be launching soon. It is far from perfect, but it is an experience our team believes in.&lt;/p&gt;
  
  &lt;p&gt;Startups are hard, hard work (thank you captain obvious) but the force is with you if you choose it to be.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;via &lt;a href="http://bobbyonboard.com/8-startup-lessons-i-learned-the-hard-way-so-you-don-t-have-to" title="link to blog post on bobbyonboard.com"&gt;@ghoshal&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A great advice, but often ignored in the rush to launch things as soon as possible. Always launch with the version the team feels is right. Might not always be the first version developed.&lt;/p&gt;
</description></item><item><title>Bootstrapping a Software Product</title><link>http://www.sunilshenoy.com/2012/04/06/bootstrapping-a-software-product</link><guid isPermaLink="false">/2012/04/06/bootstrapping-a-software-product</guid><pubDate>Fri, 06 Apr 2012 17:10:00 IST</pubDate><description>&lt;p&gt;A presentation about the lessons learned through both the good and bad decisions &lt;a href="https://twitter.com/garrettdimon"&gt;Garrett Dimon&lt;/a&gt; made while bootstrapping &lt;a href="http://sifterapp.com/"&gt;Sifterapp&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://speakerdeck.com/u/garrettdimon/p/bootstrapping-a-software-product"&gt;Bootstrapping a software product&lt;/a&gt;.&lt;/p&gt;
</description></item><item><title>Lessons from a 40 year old</title><link>http://www.sunilshenoy.com/2012/04/01/lessons-from-a-40-year-old</link><guid isPermaLink="false">/2012/04/01/lessons-from-a-40-year-old</guid><pubDate>Sun, 01 Apr 2012 11:00:00 IST</pubDate><description>&lt;iframe src="http://player.vimeo.com/video/38463833?title=0&amp;amp;byline=0&amp;amp;portrait=0" width="400" height="300" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen&gt;&lt;/iframe&gt;

&lt;p&gt;&lt;br&gt;&lt;br&gt;
&lt;a href="http://a.wholelottanothing.org/2012/03/my-webstock-talk.html"&gt;Transcript of the talk is available here&lt;/a&gt;.&lt;/p&gt;
</description></item><item><title>Yesterday you said tomorrow</title><link>http://www.sunilshenoy.com/2012/03/31/yesterday-you-said-tomorrow</link><guid isPermaLink="false">/2012/03/31/yesterday-you-said-tomorrow</guid><pubDate>Fri, 20 Apr 2012 08:25:00 IST</pubDate><description>&lt;p&gt;&lt;img src="http://mlkshk.com/r/EVI0" alt="Yesterday you said tomorrow" /&gt;&lt;/p&gt;
</description></item><item><title>→ Newsblur</title><link>http://www.sunilshenoy.com/2012/03/26/newsblur</link><guid isPermaLink="false">/2012/03/26/newsblur</guid><pubDate>Mon, 26 Mar 2012 22:22:31 IST</pubDate><description>&lt;p&gt;The only web based RSS feed reader I have enjoyed using.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.newsblur.com"&gt;Newsblur&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Also being developed in the open &lt;a href="https://github.com/samuelclay/NewsBlur"&gt;on github&lt;/a&gt;&lt;/p&gt;


&lt;p&gt;&lt;a href="http://www.YOURDOMAINHERE.com/2012/03/26/newsblur"&gt;&amp;#8734; Permalink&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Moved away from Posterous</title><link>http://www.sunilshenoy.com/2012/03/01/moving-away-from-posterous</link><guid isPermaLink="false">/2012/03/01/moving-away-from-posterous</guid><pubDate>Mon, 26 Mar 2012 00:00:00 IST</pubDate><description>&lt;p&gt;After reading the &lt;a href="http://blog.posterous.com/big-news"&gt;Posterous acquisition by Twitter&lt;/a&gt;, I have been wanting to move away from Posterous.&lt;/p&gt;

&lt;p&gt;Why? Because acquisition almost always mean the end of the service when the acquisition is for the talent. This means, that the product stops being developed. Also, in their blog post about being acquired Posterous did mention about service being affected in the future.&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;We&amp;#8217;ll give users ample notice if we make any changes to the service. For users who would like to back up their content or move to another service, we’ll share clear instructions for doing so in the coming weeks.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Rather than waiting to move the blog later, I had a few hours free this weekend. Plus gives me a good reason to try &lt;a href="http://www.marco.org/secondcrack"&gt;Second Crack&lt;/a&gt;.&lt;/p&gt;
</description></item><item><title>Done by Tomorrow</title><link>http://www.sunilshenoy.com/2012/01/09/done-by-tomorrow</link><guid isPermaLink="false">/2012/01/09/done-by-tomorrow</guid><pubDate>Mon, 09 Jan 2012 10:08:02 IST</pubDate><description>&lt;p&gt;Client: When will it be done by?&lt;br&gt;
Programmer: Give me a couple of days and I should have it ready.&lt;/p&gt;

&lt;p&gt;Prospective Client: &amp;quot;Is this difficult to build? Have you built such an system before?&amp;quot;&lt;br&gt;
Programmer: I haven&amp;#039;t done it before, but I would assume this is easy to build&lt;/p&gt;

&lt;p&gt;If you are a programmer, you have been part of such conversations before. You have made promises to your client or yourself to get a certain thing done, without having thought so much about the complexity of the problem or if you do in fact have the time to get it done tomorrow. &lt;/p&gt;

&lt;p&gt;I have had these moments, a lot last year while working on multiple projects. A requirement to build a simple Image gallery in PHP/MySQL would have me giving out a time-frame of 3-4 days. Would it really take 3-4 days? No, it would take me less time to build it. What made that timeline 3-4 days is the fact, that I had other things going on, which also needed attention while the Image Gallery was being built.&lt;/p&gt;

&lt;p&gt;Most people I meet want things completed as soon as possible. Often their decision of working with you involves you having the required time to get things completed at the earliest. It&amp;#039;s tough saying &amp;quot;no&amp;quot; to &amp;quot;can I get it back tomorrow&amp;quot; requests. The client assumes there is something wrong when you say it would take 2 days to add a simple feature. &lt;/p&gt;

&lt;p&gt;Communication, I have learnt is really important as I spend more time working through projects. Done by tomorrow conversations have now been replaced by &amp;quot;Done by {date}&amp;quot;. The {date} I arrive upon, after having looked through the work involved that week and letting the client know that I have other things to attend to between today and {date}.&lt;/p&gt;

&lt;p&gt;It&amp;#039;s important to have a good work-life balance. Burning the mid night oil cannot go on a long time.&lt;/p&gt;
</description></item><item><title>→ A great way to hire programmers</title><link>http://www.sunilshenoy.com/2012/01/03/a-great-way-to-hire-programmers</link><guid isPermaLink="false">/2012/01/03/a-great-way-to-hire-programmers</guid><pubDate>Thu, 01 Mar 2012 22:22:31 IST</pubDate><description>&lt;blockquote&gt;
  &lt;p&gt;I think programming riddles, games, and brain teasers are a great way to hire. First one to say &amp;#8220;fuck this&amp;#8221; and walk out gets the job.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;via &lt;a href="https://twitter.com/#!/holman/status/154986236640112641" title="link to holmans tweet on twitter"&gt;@holman&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I never got the need to solve puzzles during the interview process. How about focusing on the persons previous projects and code samples. Now that&amp;#8217;s a change, I hope more companies consider.&lt;/p&gt;


&lt;p&gt;&lt;a href="http://www.YOURDOMAINHERE.com/2012/01/03/a-great-way-to-hire-programmers"&gt;&amp;#8734; Permalink&lt;/a&gt;&lt;/p&gt;</description></item><item><title>JSFoo</title><link>http://www.sunilshenoy.com/2012/01/03/jsfoo</link><guid isPermaLink="false">/2012/01/03/jsfoo</guid><pubDate>Mon, 23 Jan 2012 22:22:31 IST</pubDate><description>&lt;p&gt;Saturday was quiet an eventful day.The first conference, first time I took a 4:40 AM train and the first time I went to Pune by train. All this because there is always more to learn out there.&lt;/p&gt;

&lt;p&gt;And learn I did. As the name suggests, JSFoo is a Javascript conference which covered a wide range of topics from Node.js , WebSockets, Test Driven Development , Behavior Driven Development and how to handle errors better for Javascript. I also learn&amp;#8217;t how it is important to write unit tests even for Javascript. I never thought I needed unit tests for Javascript.&lt;/p&gt;

&lt;p&gt;My favorite talks of the 6 that I attended has to be from Rakesh Pai and Sunil Pai. I enjoyed how they made their talk fun to listen to and had funny meme&amp;#8217;s in their presentation. We all like meme&amp;#8217;s don&amp;#8217;t we :)&lt;/p&gt;

&lt;p&gt;Errorception was the product Rakesh Pai demonstrated and quite an interesting product it is. Helps you catch JS errors at the client end, in cases where the error&amp;#8217;s did not show up during your tests.&lt;/p&gt;

&lt;p&gt;Sunil Pai, urged all front end developer&amp;#8217;s to &amp;#8220;own the browser&amp;#8221;, write JS templates, use javascript MVC frameworks and write &amp;#8220;unit tests&amp;#8221; for all new features and bugs. His presentation slide is here http://www.slideshare.net/threepointone/amplify-your-stack-jsfoo-chennai-2012&lt;/p&gt;

&lt;p&gt;My take away from the conference has to be to start writing unit tests and start using MVC frameworks even for Javascript. The web just got more exciting for me.&lt;/p&gt;
</description></item></channel></rss>

