<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Nicollet.Net</title>
	<link>http://www.nicollet.net</link>
	<description>Everyone Loves Me</description>
	<lastBuildDate>Mon, 23 Jan 2012 16:55:59 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress" -->

	<item>
		<title>OCaml Submodule Pattern</title>
		<description><![CDATA[My code is quite large for an OCaml project. The main RunOrg repository alone contains 46212 lines of OCaml code (plus an additional 5631 lines of OCaml mli files) — and then, there&#8217;s the web framework code and the independent plugins code. It&#8217;s is Better™ to have many short files than a few long ones. [...]]]></description>
		<link>http://www.nicollet.net/2012/01/ocaml-submodule-pattern/</link>
			</item>
	<item>
		<title>freedom.txt</title>
		<description><![CDATA[Francis suggested the freedom.txt idea in early January. It&#8217;s catching on. I think this is a good idea, although I do not agree with the wording of the message, so here&#8217;s mine. You might not understand what I am rambling about in the two sentences above. What is going on? Until recently, humans were fairly [...]]]></description>
		<link>http://www.nicollet.net/2012/01/freedom-txt/</link>
			</item>
	<item>
		<title>Frameworks, Libraries, Conventions</title>
		<description><![CDATA[Funkatron came up with the MicroPHP Manifesto : I am a PHP developer I am not a Zend Framework or Symfony or CakePHP developer I think PHP is complicated enough I like building small things I like building small things with simple purposes I like to make things that solve problems I like building small [...]]]></description>
		<link>http://www.nicollet.net/2012/01/frameworks-libraries-conventions/</link>
			</item>
	<item>
		<title>Consensus and Compromise</title>
		<description><![CDATA[Working on a start-up involves many decisions — how features should work, how pages should look like, how advertising should be written&#8230; and making decisions is a difficult process when working as a team. Even in the tightest-knit team of two, disagreements happen. Sometimes, on the less important decisions, you might get out of it [...]]]></description>
		<link>http://www.nicollet.net/2011/12/consensus-and-compromise/</link>
			</item>
	<item>
		<title>Two-way bindings</title>
		<description><![CDATA[Quick : how would you design a function that opens a file handle that auto-closes whenever execution leaves a certain scope, even if an exception happens ? The C++ solution is quite straightforward : have a destructor that closes the file handle, and create the handle as an auto variable: std::ofstream out = std::ofstream("out.txt"); out [...]]]></description>
		<link>http://www.nicollet.net/2011/12/two-way-bindings/</link>
			</item>
	<item>
		<title>How to Annoy People</title>
		<description><![CDATA[Here is a hypothetical situation : The kingdom is in trouble, and the King must enact a new law. Of course, such a law will make many people happy for years, but some people will be annoyed by it for a few days. He has two possible choices : Law A will make 20% of the [...]]]></description>
		<link>http://www.nicollet.net/2011/12/how-to-annoy-people/</link>
			</item>
	<item>
		<title>Basic Patterns for Everyday Programming</title>
		<description><![CDATA[Lakshen Perera provides a list of basic patterns for everyday programming, illustrated in Javascript and Ruby. I thought it would be interesting to provide an OCaml illustration as well, and perhaps a handful of additional patterns as well. Verify object&#8217;s availability before calling its methods or properties In many languages, there is a possibility for [...]]]></description>
		<link>http://www.nicollet.net/2011/11/basic-patterns-for-everyday-programming/</link>
			</item>
	<item>
		<title>Comment Branches</title>
		<description><![CDATA[Your development job is making changes in your software. Writing, testing and debugging those changes takes some time. If your job is anywhere as hectic as mine, you will have to fix and deploy urgent patches, even when your application code is in a half-written, half-debugged state because of the feature of the month. This is [...]]]></description>
		<link>http://www.nicollet.net/2011/11/comment-branches/</link>
			</item>
	<item>
		<title>The Three Components of Negotiation</title>
		<description><![CDATA[We negotiate several times a day, even if we do not recognize those occurences as such — « accept or walk away » is a fairly instinctive, if somewhat inefficient, negotiation strategy, and it goes hand in hand with the modern « take it or leave it » strategy employed by most mass consumer shops. [...]]]></description>
		<link>http://www.nicollet.net/2011/11/the-three-components-of-negotiation/</link>
			</item>
	<item>
		<title>Annealing Constraints</title>
		<description><![CDATA[Of all the existing constraint-solving algorithms out there, my favourite is simulated annealing. To use it, you need a mutation function that randomly and slightly alters a solution, and a fitness function that lets you compare two solutions. Based on these, the algorithm is simple : Start with an arbitrary solution. Mutate the solution : [...]]]></description>
		<link>http://www.nicollet.net/2011/10/annealing-constraints/</link>
			</item>
</channel>
</rss>

