<br><br><div class="gmail_quote">On Wed, May 9, 2012 at 10:54 AM, Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org" target="_blank">eli@barzilay.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">Three hours ago, Laurent wrote:<br> ><br> > I'd be very interested in what your rules are. Could you expand a<br> > little please?<br> <br> </div>A bunch of things that would take a lot of verbiage to specify, and<br> might lead to unnecessary flamage...</blockquote><div><br>Hopefully we're all grown-ups here.<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> At the high level there's not<br> much that will be surprising, maybe except for how much I'll invest in<br> avoid things like duplicated code etc.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><br></div>Well, if you ever feel like writing them down, I'd be happy to read that, and I'm pretty sure I'd learn a lot.<br> Btw, you'd be surprised how unsurprising things can be surprising. I caught myself "discovering" quite recently a common coding style rule that I used most of the time unconsciously but forgot from time to time. Now that's it's consciously set in my mind, I use it consistently or, if I break it, I must have a good reason to do so and be ready to make it a rule too, not just be lazy.<br> (the rule is "always put spaces around operators" in infix languages, but that's not the point.)<br><br>Laurent<br>