BoostCon/C++Now! Talk: How I Code and Why

I talked about this last year, and this year I've submitted the proposal, so If you volunteered last year (and are still interested) and/or are interested in helping with a particular/peculiar talk at BoostCon/C++Now this year, then read on, and contact me offline: I'm planning on giving a talk, entitled "How I Code and Why". It is not meant to be presumptuous and tell you how *you* should code, but instead just explains how I code - day-to-day - and how I came to these patterns/conclusions. But who cares just about how *I* code, people want to hear how other members of the Boost community - people they've come to know and respect via the boost lists - code. So I'm hoping to have a few co-conspirators on stage with me, and have each explain a fundamental guiding principle that they follow in their every day code, how they came to adopt this principle and why they find it valuable. For example, I will tell the simple story ('epiphany') of why my favourite comment word is 'otherwise', and how this relates to advice you may have heard or read before. I like the flavour of [ simple, real world, specific ] ---> [ general principle ] The goal is to bring a more real world down to earth picture to the sometimes lofty fundamentals found in books and lectures. Instead of a book explaining how a guiding principle makes sense *in theory*, it would be great (I think) to hear how respected members of the community apply these principles in real life. So, if you want to participate, email me, and we will see what we can figure out. (And/or I might just have to track you down based on promises made last year!) Not sure how many people we need. I'm thinking 5-15 mins per 'principle', and I think you only need to present one (I think the weight of picking *just one* principle makes it all the more interesting). Anyhow, we can work out the details as we go along. Tony PS. this is not (yet?!) an accepted talk, but I have a bit of chicken/egg thing here: ie it would help to have a few people on board to show that the talk is viable, and thus be accepted.

On Mon, Feb 13, 2012 at 7:30 AM, Gottlob Frege
I talked about this last year, and this year I've submitted the proposal, so
Do you mean "talked about" it on the mailing list, or "talked about" it as in presented a talk? If the latter can you supply a link to your previous talk?
[...snipped lots...]
This sounds potentially interesting, but I'm not really sure I understand what you mean! Can you give an example, so I can better understand what you're getting at? Thx, - Rob.

On 2/13/12, Robert Jones
On Mon, Feb 13, 2012 at 7:30 AM, Gottlob Frege
wrote: I talked about this last year, and this year I've submitted the proposal, so
Do you mean "talked about" it on the mailing list, or "talked about" it as in presented a talk? If the latter can you supply a link to your previous talk?
I mean talked about on the list (and in person with a few people at boostcon11, but not as part of a talk). I can supply a link to my previous discussion, I suppose: http://boost.2283326.n4.nabble.com/Boost-Talk-quot-How-I-Code-quot-td3320509...
[...snipped lots...]
This sounds potentially interesting, but I'm not really sure I understand what you mean! Can you give an example, so I can better understand what you're getting at?
Well, I don't want to give away the punch line, but in one slide I could present the code that lead me to the guideline "my favourite comment word is 'otherwise'". That leads to a general discussion of good vs bad commenting, "self documenting code", etc. But I find the "otherwise" mantra an easy way to explain and remind people about the principles involved. So, the interesting part to me would be to try to summarize your coding style into a single fundamental/essential trait - ie if I had to pick one thing to follow/remember. (For me it isn't actually commenting style; it would probably be "separation of concerns", but I'm not sure I have the "Reader's Digest" explanation for that yet.)
Thx,
- Rob.
Hope that helps, Tony

On Tue, Feb 14, 2012 at 7:14 AM, Gottlob Frege
On 2/13/12, Robert Jones
wrote: On Mon, Feb 13, 2012 at 7:30 AM, Gottlob Frege
wrote: [...snip...]
I can supply a link to my previous discussion, I suppose:
http://boost.2283326.n4.nabble.com/Boost-Talk-quot-How-I-Code-quot-td3320509...
[...snipped lots...]
Well, I don't want to give away the punch line, [..snip..]
Ok, that's fairly helpful, mainly the alternative title "Nuggets of Experience", and I see I chipped-in to that thread too. Sadly I can't be at BoostCon, but I shall be interested in the suggestions that come forward, especially your championing of 'otherwise' in comments. I feel quite tempted to put forward my experience nugget as 'code slowly', but that might not be the most career-advancing suggestion! Thx - Rob.

On Tue, Feb 14, 2012 at 3:54 AM, Robert Jones
I feel quite tempted to put forward my experience nugget as 'code slowly', but that might not be the most career-advancing suggestion!
:) Maybe a better way to phrase it would be to borrow the old carpenter's mantra of "measure twice, cut once" ? -- Chris Cleeland

On Tue, Feb 14, 2012 at 1:45 PM, Chris Cleeland
On Tue, Feb 14, 2012 at 3:54 AM, Robert Jones
wrote: I feel quite tempted to put forward my experience nugget as 'code slowly', but that might not be the most career-advancing suggestion!
:) Maybe a better way to phrase it would be to borrow the old carpenter's mantra of "measure twice, cut once" ?
Ah, the beauty of language! They do as much to divide us to unite us. My broader point, obviously very badly made, was the more subtle suggestion that sometimes the wisdom and behaviour learnt from real experience, while valid and valuable, may be at odds with the more superficial, less informed behaviours that we are 'required' to champion. To say that is not particularly to criticise any or all organisations, merely to recognise that group wisdom, aka mob rule, is necessarily the product of the lowest common denominator of experience. I'll get my coat. - Rob.
participants (3)
-
Chris Cleeland
-
Gottlob Frege
-
Robert Jones