Thanks, some good points in there. I just had my first conference talk, and today spoke at an internal knowledge share I was invited to, with another one planned next month.
The time between being accepted and speaking can be between a few weeks and a few months, so I can imagine not having to many in a month can be a puzzle.
How do you think about submitting a proposal when the technical part is not finished or you didn't even start on it. Do you mention it not being complete in the proposal, or sell it said it was done?
Software dev at Netflix | DC techie | Conference speaker | egghead Instructor | TC39 Educators Committee | Girls Who Code Facilitator | Board game geek | @laurieontech on twitter
Thanks, some good points in there. I just had my first conference talk, and today spoke at an internal knowledge share I was invited to, with another one planned next month.
The time between being accepted and speaking can be between a few weeks and a few months, so I can imagine not having to many in a month can be a puzzle.
How do you think about submitting a proposal when the technical part is not finished or you didn't even start on it. Do you mention it not being complete in the proposal, or sell it said it was done?
I don't normally find that it matters? You're talking about technical content. Whether you're done or not doesn't mean your learnings aren't valuable.