<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-7107801460369920583</atom:id><lastBuildDate>Wed, 20 Aug 2025 11:01:30 +0000</lastBuildDate><category>ramblings</category><category>Ajax</category><category>Software Engineering</category><category>Software development</category><category>Application Architecture</category><category>Architecture</category><category>RESTFul Web Service</category><category>SQL Server</category><category>SQLServer 2005</category><category>XMLHttpRequest object</category><category>DOM</category><category>Design Principles</category><category>India</category><category>NoSQL</category><category>Note to Self</category><category>OOPs</category><category>SQLServer 2008</category><category>.NET 2.0+</category><category>.Net</category><category>Abort requests</category><category>C#</category><category>C++</category><category>C++ Project</category><category>CTE</category><category>Caching</category><category>Configuration files</category><category>CouchDB</category><category>DOM Events</category><category>Data</category><category>ExtJS</category><category>Fiddler</category><category>Handling Timeouts</category><category>Hierarchical Data</category><category>JavaScript</category><category>Microsoft Ajax Library</category><category>NILF 2010</category><category>Nasscom</category><category>People</category><category>Save our tiger</category><category>Talent</category><category>Turbo C++ 3.0</category><category>Web Application Stress Tool</category><category>XML</category><category>XSLT</category><category>cURL</category><category>commodity hardware</category><category>copy database diagram</category><category>design patterns</category><category>environment</category><category>jQuery</category><category>singleton</category><category>sysdiagrams</category><category>tab</category><category>tablet PC</category><title>Under the hood</title><description>&quot;Give me six hours to chop down a tree and I will spend the first four sharpening the axe.&quot; Abraham Lincoln</description><link>http://nestas.blogspot.com/</link><managingEditor>noreply@blogger.com (santanu)</managingEditor><generator>Blogger</generator><openSearch:totalResults>41</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5026289118656313769</guid><pubDate>Wed, 18 Mar 2015 17:58:00 +0000</pubDate><atom:updated>2015-03-18T23:28:03.619+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">.Net</category><category domain="http://www.blogger.com/atom/ns#">C#</category><category domain="http://www.blogger.com/atom/ns#">CouchDB</category><category domain="http://www.blogger.com/atom/ns#">Software development</category><title>A C# library for CouchDB</title><atom:summary type="text">I was recently working on a .NET project that uses CouchDB v 1.6.1 as its database. As part of this project, I created this library to abstract away the HTTP requests to a CouchDB. It is a work in progress, but the methods available should be sufficient for CRUD operations on a CouchDB database. 

The code&#39;s written in C# in VS 2013 Community Edition.

You can download the source at https://</atom:summary><link>http://nestas.blogspot.com/2015/03/a-c-library-for-couchdb.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-7392274955059429320</guid><pubDate>Thu, 22 Jan 2015 12:12:00 +0000</pubDate><atom:updated>2015-01-23T11:53:53.830+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">cURL</category><category domain="http://www.blogger.com/atom/ns#">Note to Self</category><category domain="http://www.blogger.com/atom/ns#">Software development</category><title>Error using cURL to POST or PUT data formatted in JSON in Windows</title><atom:summary type="text">If you use cURL in a cmd.exe shell on Windows, an attempt to POST or PUT data formatted in JSON results in an error. An example:

This is the data:
{&amp;quot;Continent&amp;quot;:&amp;quot;AS&amp;quot;,&amp;quot;ContinentName&amp;quot;:&amp;quot;Asia&amp;quot;,&amp;quot;CountryName&amp;quot;:&amp;quot;India&amp;quot;,&amp;quot;Capital&amp;quot;:&amp;quot;New Delhi&amp;quot;,&amp;quot;Iso_Alpha2&amp;quot;:&amp;quot;IN&amp;quot;,&amp;quot;Iso_Numeric&amp;quot;:&amp;quot;356&amp;quot;,&amp;quot;</atom:summary><link>http://nestas.blogspot.com/2015/01/error-using-curl-to-post-or-put-data.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-7171915319552293469</guid><pubDate>Tue, 02 Dec 2014 17:05:00 +0000</pubDate><atom:updated>2014-12-03T16:09:33.077+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Application Architecture</category><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">RESTFul Web Service</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>RESTful web service - versioning the API</title><atom:summary type="text">This is the fourth post in this series of posts on RESTful web service. 

Part 1,  Part 2, Part 3

In this post we discuss the need for versioning an API and the possible ways to do it. The need for versioning is not restricted to the REST scenario alone -  whatever is applicable to the REST scenario is also applicable to HTTP web services.

APIs don&#39;t exist for themselves - they are meant to be </atom:summary><link>http://nestas.blogspot.com/2014/12/restful-web-service-versioning-api.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5741514844885967869</guid><pubDate>Tue, 11 Nov 2014 18:51:00 +0000</pubDate><atom:updated>2014-12-03T16:21:13.403+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Application Architecture</category><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">RESTFul Web Service</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>RESTful web service - media types and resource representation</title><atom:summary type="text">This is the third in this series of posts on RESTful web service. 

Part 1,  Part 2, Part 4

In this post we will examine the role of internet media types, especially the &#39;application&#39; media type in a REST service.

The media type, to a large extent, describes the contract between the server and the client in a REST web service.

Read the full article here. 
</atom:summary><link>http://nestas.blogspot.com/2014/11/restful-web-service-media-types-and.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-1193904989943834621</guid><pubDate>Sat, 18 Oct 2014 20:04:00 +0000</pubDate><atom:updated>2014-12-03T16:21:28.148+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Application Architecture</category><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">RESTFul Web Service</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>RESTful web service - how do I design one?</title><atom:summary type="text">This is the second post of the series on RESTful Web Service. 

Part 1, Part 3, Part 4

In this post we discuss how to design and build a REST API (a collection of REST web service).

As with any design we ask ourselves what our end goals are, and then decide how we go about achieving these. I believe the questions below set out what the minimum end goals are when designing a successful REST API.</atom:summary><link>http://nestas.blogspot.com/2014/10/this-is-second-post-of-series-restful.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-4478165597948962451</guid><pubDate>Mon, 29 Sep 2014 19:05:00 +0000</pubDate><atom:updated>2014-12-03T16:15:22.019+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Application Architecture</category><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">RESTFul Web Service</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>RESTful web service - what is this?</title><atom:summary type="text">Many of us have, at some point or the other, created and consumed web services. Many of us have created and consumed RESTful (or REST) web services, because that is the trend nowadays. Or have we actually created a HTTP based web service and not really a REST web service? It&#39;s pretty easy to create a HTTP based web service with, for example, Microsoft&#39;s ASP.NET Web API 2 framework and provide the</atom:summary><link>http://nestas.blogspot.com/2014/09/restful-web-service-what-is-this.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-7046723527037427831</guid><pubDate>Sat, 03 May 2014 15:02:00 +0000</pubDate><atom:updated>2014-05-29T10:12:36.559+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Data</category><category domain="http://www.blogger.com/atom/ns#">NoSQL</category><category domain="http://www.blogger.com/atom/ns#">ramblings</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>The rise and rise of data</title><atom:summary type="text">

Even a cursory study of the history of the internet, especially after the advent of the World Wide Web, indicates the power of the medium. In terms of users, it has grown 588.4% between Dec 2000 and June 2013, from around 369 million to 2.4 billion, though only 34.3% of the world&#39;s population had access to the internet in this period [source]. The penetration is expected to grow to 45% by 2016,</atom:summary><link>http://nestas.blogspot.com/2014/05/even-cursory-study-of-history-of.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5203411378174200295</guid><pubDate>Tue, 08 Apr 2014 12:38:00 +0000</pubDate><atom:updated>2014-04-08T18:29:03.117+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">commodity hardware</category><category domain="http://www.blogger.com/atom/ns#">NoSQL</category><category domain="http://www.blogger.com/atom/ns#">ramblings</category><title>Commodity hardware</title><atom:summary type="text">

One of the USP of NoSQL databases is their ability to run on &#39;commodity hardware/ machines/ servers/ clusters&#39;. So what is commodity hardware?


My desktop PC is powered by an Intel i5 4th gen processor, has 16 GB (initially 8, upgraded later to 16) of RAM and 1 TB HDD. The hardware is reliable and affordable, even though it was built by an assembler. It is easy to upgrade when required - like </atom:summary><link>http://nestas.blogspot.com/2014/04/one-of-usp-of-nosql-databases-is-their.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-2961204789632067451</guid><pubDate>Wed, 02 Apr 2014 12:11:00 +0000</pubDate><atom:updated>2014-04-08T14:20:19.853+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ramblings</category><category domain="http://www.blogger.com/atom/ns#">Software development</category><title>Creating complex business solutions</title><atom:summary type="text">

In spite of the fact that I haven&#39;t posted on this blog for 2-2.5 years, there has been an average of 100 page views a month. I assume from this that the content has been helpful to some. Inspiration enough to start again.  


Technology has made giant strides in these few years making it possible to create very complex business solutions. Two areas get highlighted:
a. how do we maintain large </atom:summary><link>http://nestas.blogspot.com/2014/04/creating-complex-business-solutions.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-7966508133094034503</guid><pubDate>Sat, 08 Oct 2011 15:26:00 +0000</pubDate><atom:updated>2011-10-15T09:13:51.686+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ramblings</category><category domain="http://www.blogger.com/atom/ns#">Software development</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>IE&#39;s legacy browsers - will they ever go away?</title><atom:summary type="text">

“W3C publishes documents that define Web technologies. These documents follow a process designed to promote consensus, fairness, public accountability, and quality. At the end of this process, W3C publishes Recommendations, which are considered Web standards.” from Standards FAQ.


The recommendations are not binding, but as the W3C says: “W3C&#39;s role in making the Recommendation is to draw </atom:summary><link>http://nestas.blogspot.com/2011/10/ies-legacy-browsers-will-they-ever-go.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgID1GS7RLwK5FRmRomqeczSe0CArbH8xn_Ql4D748Y80ozDBpD4Q5R_J5HaZwXy7I3JiAnrp2-ULvhwnb2W50vqGwD0nxrIQaE0VxVliMbAN2g562DAF6QGMniaVcL9fcyrlxDY0O1H8g/s72-c/Table.PNG" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-2981104035252376791</guid><pubDate>Mon, 19 Sep 2011 19:20:00 +0000</pubDate><atom:updated>2011-09-20T12:24:00.172+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ramblings</category><category domain="http://www.blogger.com/atom/ns#">tab</category><category domain="http://www.blogger.com/atom/ns#">tablet PC</category><title>Why I did not buy a Samsung tab...or an iPad</title><atom:summary type="text">

Last Saturday, I walked into an electronic store to purchase a Tablet, a tab. My preference was for the Samsung 10.1;  in the store I also came across the iPad 2. And in this section was also on display an array of laptops.


Why do I need a tab? My usual practice is to surf the net after dinner, possibly read an e-book, catch up with people on Facebook or LinkedIn. I do it on a laptop </atom:summary><link>http://nestas.blogspot.com/2011/09/why-i-did-not-buy-samsung-tabor-ipad.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5233235574558758925</guid><pubDate>Sat, 10 Sep 2011 23:36:00 +0000</pubDate><atom:updated>2011-10-19T10:59:10.901+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Application Architecture</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>Weird Architecture</title><atom:summary type="text">
Sometime back the technical consultant of a customer accused me of having created a ‘weird architecture’ for her project. And this after we had completed an iteration that met agreed goals, work which was commended by the customer as ‘brilliant’.


This was a Web 2.0 application, built on the ASP.NET framework, written in C# and targeted the .NET Framework 3.5, with a SQL Server 2005 database, </atom:summary><link>http://nestas.blogspot.com/2011/09/weird-architecture.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgl4k53As-uvZGUu90u6nG2PlHUkvKtUiOaqly8sbNpyjKSojTFwGUkVB8nW22L9dSlWoq6lkCkwuvFXk3E6AYhrRTJtBVxZWC15jdOlrAujuP0smd3VO2jVuVA8zOFUg2Ra3Xc-Xj0QwsO/s72-c/Generic+Deployment1.PNG" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-8192667549254557013</guid><pubDate>Thu, 14 Jul 2011 19:36:00 +0000</pubDate><atom:updated>2011-09-13T00:03:55.586+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">People</category><category domain="http://www.blogger.com/atom/ns#">Talent</category><title>Great People, Great Teams</title><atom:summary type="text">

Bill Taylor’s post Great People Are Overrated on the HBR Blog Network has generated a lot of heat. His post was triggered by a statement Facebook CEO Mark Zukerburg made in an interview: “Someone who is exceptional in their role is not just a little better than someone who is pretty good,” he said. “They are 100 times better.” It emphasised what Marc Andreessen had told him: “Five great </atom:summary><link>http://nestas.blogspot.com/2011/07/great-people-great-teams.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-2464547276041694755</guid><pubDate>Mon, 20 Jun 2011 18:01:00 +0000</pubDate><atom:updated>2011-09-13T00:26:29.882+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>The software devlopment crisis</title><atom:summary type="text">

Some blunt observations on the state of software development practices today, and a way out.



See other Tech-Ed 2011 videos here. Of particular interest to me were those tagged as Development Practices and Architecture.

</atom:summary><link>http://nestas.blogspot.com/2011/06/software-devlopment-crisis.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-7366853756273428949</guid><pubDate>Sat, 28 May 2011 07:33:00 +0000</pubDate><atom:updated>2011-09-13T00:30:39.960+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">SQL Server</category><category domain="http://www.blogger.com/atom/ns#">SQLServer 2005</category><category domain="http://www.blogger.com/atom/ns#">SQLServer 2008</category><title>Shrink a SQL Server database</title><atom:summary type="text">

When we create a SQL Server database, it is created with a full recovery model. This grows the transaction log (the .ldf file) with every transaction we make on the database. Usually the size of the transaction file is many times more than the .mdf file.

If not maintained, the transaction log would eventually fill all the disk space that is available to the physical log files.

In a </atom:summary><link>http://nestas.blogspot.com/2011/05/shrink-sql-server-database.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5776022039050110044</guid><pubDate>Tue, 03 May 2011 17:55:00 +0000</pubDate><atom:updated>2011-09-13T00:32:56.390+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">India</category><title>Why I am bullish about India</title><atom:summary type="text">
A wonderful article by a friend that sums up the soul of India. Read it here.</atom:summary><link>http://nestas.blogspot.com/2011/05/why-i-am-bullish-about-india.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-290268485279599231</guid><pubDate>Thu, 28 Apr 2011 19:17:00 +0000</pubDate><atom:updated>2011-10-15T11:32:29.168+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Software development</category><title>Bugs!!</title><atom:summary type="text">

From Three Questions About Each Bug You Find
&quot;..Do you sometimes fix a bug, and then find another bug related to the first or to the way you fixed it? When I fix a bug, I ask myself three questions to make sure I&#39;ve thought carefully about its significance. You can use these questions to improve productivity and quality every time you think you&#39;ve found and fixed a bug...&quot;


Figure 1


Figure 1</atom:summary><link>http://nestas.blogspot.com/2011/04/bugs.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaWT8Q3Z5S4bkQyk_fDYD3yjG7UF2GrzaYu6Hg27ohXpvBqEODT_lVIzpDSGVJOwP6b12cpNSdxq9pMhwD9SLINVWsJJ7PS0hAGa1af5AvdTaTPOt1-XgP-_FPnGqeyZfHzwydoAWAULo_/s72-c/1945FirstBugLarge.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-6398071820771044268</guid><pubDate>Sat, 12 Mar 2011 07:28:00 +0000</pubDate><atom:updated>2011-09-13T00:39:48.915+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">C++</category><category domain="http://www.blogger.com/atom/ns#">C++ Project</category><category domain="http://www.blogger.com/atom/ns#">Turbo C++ 3.0</category><title>A project in C++</title><atom:summary type="text">

My son graduates high school this year. One of the subjects he has opted for is Computer Science. The major focus of this course is to provide an understanding of object oriented programming (OOP) through C++.

As a requirement of this course he needs to submit a project that covers OOP, Data File Handling, and Data Structures. His school mandates that they use Turbo C++ 3.0. 

The last few </atom:summary><link>http://nestas.blogspot.com/2011/03/project-in-c.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5969654518498304443</guid><pubDate>Wed, 26 Jan 2011 11:07:00 +0000</pubDate><atom:updated>2011-10-15T11:34:25.697+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">India</category><category domain="http://www.blogger.com/atom/ns#">ramblings</category><title>India: my pride, my shame</title><atom:summary type="text">
Today India completes 61 years as a Sovereign, Democratic and Republic state. We have been an independent nation for 64 years.

In this short span of time India has perfected the art of being corrupt. The CWG scam, the 2G scam, the Adarsh scam, $500 billion dollars of the country’s money stashed away in secret accounts abroad, bureaucrats discovered with Rs.300 crore stashed in suitcases at </atom:summary><link>http://nestas.blogspot.com/2011/01/india-my-pride-my-shame.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQRlZ94ruj4M0ErpTgfNN9r1FK7xk8am9iUA8DskMzY9aCHWzBCAYjxZ_9YEGUgR0nGuTCugyaUMkfjn7ntXpezhHcVgX8a1TDCOg90wepFzblFn4EGZ78qLu7XBn-w7rzaXHyDJ9s5gC5/s72-c/200px-Emblem_of_India.svg.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-6975500844899531406</guid><pubDate>Fri, 08 Oct 2010 18:12:00 +0000</pubDate><atom:updated>2010-10-08T23:44:55.613+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Software development</category><category domain="http://www.blogger.com/atom/ns#">Software Engineering</category><title>The privilege and responsibility of software development</title><atom:summary type="text">
From Grady Booch:
&quot;.. It is a privilege because -- in spite of some inevitable dark days -- we collectively are given the opportunity to create things that matter: to individuals, to teams, to organizations, to countries, to our civilization. We have the honor of delivering the stuff of pure intellectual effort that can heal, serve, entertain, connect, and liberate, freeing the human spirit to </atom:summary><link>http://nestas.blogspot.com/2010/10/privilege-and-responsibility-of.html</link><author>noreply@blogger.com (santanu)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-2005622962026151921</guid><pubDate>Fri, 01 Oct 2010 13:37:00 +0000</pubDate><atom:updated>2011-10-15T11:35:20.328+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">environment</category><category domain="http://www.blogger.com/atom/ns#">ramblings</category><category domain="http://www.blogger.com/atom/ns#">Save our tiger</category><title>Help...</title><atom:summary type="text">
http://www.saveourtigers.com</atom:summary><link>http://nestas.blogspot.com/2010/10/help.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVaJRgTVpIfEGdc3biyawD45bLFUWmrNBiKspLdDrX5BIJg7Rvita_qgeg8BeAvCue8pmTg5Da1R7T0yVBDbs9yvlEIRqjItN9SmJRytBKIIjaJDtLt9s8kBZBUZBJ1DxXwuu9Q8_GbmDO/s72-c/head.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-9055766878960567148</guid><pubDate>Fri, 23 Jul 2010 18:52:00 +0000</pubDate><atom:updated>2015-08-10T12:17:43.985+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ramblings</category><title>Where the mind is without fear ...</title><atom:summary type="text">&quot;Where the mind is without fear and the head is held high;
Where knowledge is free;
Where the world has not been broken up into fragments by narrow domestic walls;
Where words come out from the depth of truth;
Where tireless striving stretches its arms towards perfection;
Where the clear stream of reason has not lost its way into the dreary desert sand of dead habit;
Where the mind is led forward</atom:summary><link>http://nestas.blogspot.com/2010/07/where-mind-is-without-fear.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-2560333579643853668</guid><pubDate>Sat, 03 Jul 2010 05:57:00 +0000</pubDate><atom:updated>2011-09-26T00:54:14.892+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Design Principles</category><category domain="http://www.blogger.com/atom/ns#">OOPs</category><title>Design Principles:Don&#39;t Repeat Yourself (DRY) - A guide to its implementation</title><atom:summary type="text">&quot;DRY says that every piece of system knowledge should have one authoritative, unambiguous representation. Every piece of knowledge in the development of something should have a single representation. A system&#39;s knowledge is far broader than just its code. It refers to database schemas, test plans, the build system, even documentation.

Given all this knowledge, why should you find one way to </atom:summary><link>http://nestas.blogspot.com/2010/07/dont-repeat-yourself.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total><georss:featurename>Anand, Gujarat, India</georss:featurename><georss:point>22.560869 72.954773</georss:point><georss:box>22.521238 72.896408000000008 22.6005 73.013138</georss:box></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-5021824218885444143</guid><pubDate>Sat, 19 Jun 2010 20:18:00 +0000</pubDate><atom:updated>2011-10-15T11:38:32.904+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Design Principles</category><category domain="http://www.blogger.com/atom/ns#">OOPs</category><title>Design Principles: Program to interfaces, not implementations - A guide to its implementation</title><atom:summary type="text">One of the recommended principle of OO design/programming is to ‘program to interfaces, not implementations’.

Consider a password policy defined like this in XML:&amp;nbsp;
&amp;lt;policy&amp;gt;
 &amp;lt;password&amp;gt;
  &amp;lt;min-length&amp;gt;
   &amp;lt;administrator&amp;gt;18&amp;lt;/administrator&amp;gt;
   &amp;lt;end-user&amp;gt;8&amp;lt;/end-user&amp;gt;
  &amp;lt;/min-length&amp;gt;
  &amp;lt;expires duration=&quot;days&quot;&amp;gt;
   &amp;lt;administrator&amp;gt;60&amp;lt;/</atom:summary><link>http://nestas.blogspot.com/2010/06/program-to-interfaces-not.html</link><author>noreply@blogger.com (santanu)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7a1CokCFhEY7G0nhs_hzudD4E_M1YbZztMqmPdBs2-bPnYMN4wgmT_k076c3gE-yN0CdS9m6NA36tfOoO0_xJ5AptAC08CUHQNbf8zHJJCtrDrbZqj50tNPWB_TVkLS5d82XbhbEDnEQW/s72-c/Policy_Blog.PNG" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7107801460369920583.post-4811390374112614607</guid><pubDate>Thu, 25 Mar 2010 19:46:00 +0000</pubDate><atom:updated>2010-03-26T01:19:14.507+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Ajax</category><category domain="http://www.blogger.com/atom/ns#">XMLHttpRequest object</category><title>A for Ajax, Part 8: The XMLHttpRequest object (Part 3)</title><atom:summary type="text">In this post we modify the XHR Library.&amp;nbsp;This is now capabale of:
• &amp;nbsp;working with GET and POST requests
• &amp;nbsp;handling JSON formatted text and XML documents returned by the server
• &amp;nbsp;handling timeouts, and aborting requests

You can read the full article here.</atom:summary><link>http://nestas.blogspot.com/2010/03/for-ajax-part-8-xmlhttprequest-object.html</link><author>noreply@blogger.com (santanu)</author><thr:total>0</thr:total></item></channel></rss>