I keep writing up talk submissions for conferences. They get accepted. And I give talks.
Yet it occurs to me that this is the “if I build it, they will come” approach to speaking. I’m going to turn it around. This is a request for requests.
Is there some topic on which you’d come to see me speak? Is there some topic on which you want me to weigh in? Do I hold some controversial position that you want me to either support or repudiate? Is there anything that I’ve done that you’d like to see me do more?
Also, some of these topics may turn into blog entries.
It takes me a while, but eventually I learn: ask the customer. So, customer, how could I best help you with whatever matters most to you?
I'd love to see you describe effective hiring and interview practices. You touched on it once in a conversation, and I'm curious to see what it would look like fully baked.
There are a bunch of really commonly used frameworks that are really poor on testability — web frameworks, phone frameworks, and javascript codebases spring to mind. Is there anyone pointing toward a more testable design for these, or can you walk through how you'd take something like, say, Rails, or frontend javascript development and redesign the ecosystem for testability?
Please elaborate on why you consider estimations to be a waste. At LESS 2010 I asked you the same question and you mentioned a podcast where you talked more about it (seems I've lost the link – what was it again?), but it would be nice to have a more in-depth article and/or presentation about the topic, or is there one somewhere already?
Thanks for the great suggestions. Some of these would make great blog entries. Others would make good talks. I may do both for some.