Pause[x]include Tulúm México UnConference
You are probably here because you're wondering if you should attend or host a session at PauseOnError.
Rest assured, you are in the right place. First, if you are on the fence, we encourage you to jump in. This is a great opportunity to take some risks and be part of a special shared experience.
Here are a few things you should know to get started.
PauseOnError isn't like any other FileMaker conference or user group meeting. It began as a way for a group of FileMaker developers and consultants to take a break from our normal routine, hang out and share our work, ideas, problems and projects with each other.
It has traditionally been free of mass marketing because we feel it is more important that people discover PauseOnError for themselves and in the process, make a personal, informed decision to participate.
We hope you choose to participate in Pause because you feel invested in its philosophy, spirit and ideals. Commonly asked questions (with answers below) are:
1. What kinds of session can I present/host?
Sessions at this PauseX are focused on inclusiveness. Formats that have worked well in the past include: discussions, loosely scripted presentations, code reviews, brainstorms, or creative 'dialogs'. Hosts are asked to present for 10 to 20 minutes max. All other presentations should be about 5 minutes.
Not ready to present on your own? Or is someone else presenting something similar to what you want to present? Consider this a good chance to partner up and present together. If you need help syncing up with someone, find someone in Slack or at the Crowdcasts. We’ll do our best to help
2. Do I have to put my session on the schedule?
No, but it sure makes life easier.
3. Where is the session schedule?
The schedule is will be linked here, when it is close to finished.
4. Where should I do my session?
We have 1 large room that holds about 60 people, with the ability to break it into 2 rooms of about 30. In the past, sessions have been hosted in people's rooms, public parks, bars, or in hotel lobbies as an impromptu gathering around a laptop. So don’t be afraid to get creative.
5. How long is each session slot?
For Pause[x]include, we are tentatively planning on 75 minutes. Leave time for questions: some sessions are all questions. And sometimes the questions are mostly being asked by the presenter.
As this is an un-conference, you are welcome to be creative with time or place, but bear in mind that whatever structure is in place exists to help things go as smoothly as possible.
6. How do I suggest my session?
Please share your ideas in our Slack channel.
7. Can I broadcast my session?
We may be Crowdcasting the sessions, and so we ask that you don’t plan for a separate broadcast.
8. How do I get help on my session?
PauseOnError is an un-conference. That means, to the extent possible, this is a self-organizing effort. While the friendly folks on the steering committee are here to support you and provide gentle guidance, you (and your session guests) are ultimately responsible for the success of your own sessions.
9. Any tips?
"Show" rather than "tell"
Push yourself – we all want to see you succeed, so try something bold
Leave PowerPoint behind if possible. It's fine for an intro to the discussion, but not ideal for the whole thing. Ten minutes of slides is a lot.
Invite people to think about a problem with you. Listen to feedback and questions carefully and slowly
Generally avoid stuff you would do/have done for DevCon
Don’t wing it
If there is something you want to talk about / work on etc., spend some time thinking about it and be prepared to speak about it
Have some samples, talking points, or something to help guide the discussion if you can. Real work is preferable to demo files, which tend to get sanitized and pulled from context. For Pause[x]include, the human context should be included!
Pause[x] ©2019 by Pause On Error & licensed for Pause[x]include to SmallCo. Pause[x]include ©2019 by SmallCo.