Define "in depth"? Any talk at a conference will fail to give a thorough understanding of a subject no matter the length. Educational research shows that "lecture style" education is the worst way to teach anything, people need to hands on experience. This is even more true in the technology world because we all learn something new every day through reading and experience.
A talk can do a lot, it can excite you about something you didn't know, it can explore the third rails of a particular area of technology imparting shared experience on the audience. When talks are best they provide something to think about and discuss *after* the talk, in the hallways and at the parties after speaking. I think about it this way; even if you can't teach someone something in a talk, but you can teach them *why* they would want to learn it. In most cases, the shorter the better. Also, the NodeConf programme is unlike anything you've seen at a conference. Maybe I'm too ambitious, but each day of NodeConf will have a theme and the speaker content will walk linearly through a beginning, middle and an end. I'm using the reverse call for speakers to build that programme and i'll work with every speaker individually to make sure the content has a flow throughout the entire day. So, you, and all the spakers, won't be on the hook for presenting everything there is to know about Streams. You'll bite off the chunk that fits you best and you'll know where that fits in the larger programme. Yes, this is very different. No, I don't know that it's been done before, but I'm confident I can make it work. -Mikeal On Mar 16, 2012, at March 16, 20122:42 PM, Marco Rogers wrote: > Hmmm, not sure how I feel about this. I won't argue because I'm positive it > won't do much good. But do you see as the venue for people who want more in > depth talks about node? I think the community needs that as well. > > Either way, I have some ideas about how to make an awesome 20 minutes about > streams. > > :Marco > > On Thursday, March 15, 2012 4:35:52 PM UTC-7, Mikeal Rogers wrote: > yes, it's a talk, not a tutorial. > > btw, TED talks are all between 10 and 20 minutes :) > > On Mar 15, 2012, at March 15, 20124:33 PM, Stewart Mckinney wrote: > >> Wait; is that for real? ( 20 minute limit? ) >> >> On Thu, Mar 15, 2012 at 6:53 PM, Mikeal Rogers <[email protected]> >> wrote: >> All talks are 20 minutes this year :) >> >> On Mar 15, 2012, at March 15, 20123:38 PM, Marco Rogers wrote: >> >>> The call for speakers is open for NodeConf 2012. I want to talk about >>> streams in node. Last year I only got a half hour to cover a large topic. >>> This may be a simliar situation. But at a high level you an vote for any or >>> all of these. >>> >>> - What do we mean by streams? require('stream'). How these relate to net >>> sockets and fs streams. >>> - What are some best practices for working with streams? >>> - How to take advantage of custom streams to do cool things in node without >>> breaking things or ruining efficiency >>> - How to add stream compatibility to your module >>> - How to maintain state across streams. When would you even want to do >>> this? See https://github.com/polotek/procstreams >>> >>> Feel free to suggest others. Dont forget to fill out the form. >>> >>> http://www.nodeconf.com/ >>> >>> :Marco @polotek >>> >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: >>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
