Nebraska.Code AI Guidelines:
- Regardless of how your presentation was created you are personally responsible for everything in it. If you have a slide that says "Using X tool resulted in 87% decrease in bugs" you need to be able to state where you got that number. If it was a study by a team at a University you need to link to that study and be able to talk a bit about the methodology of the study. If it was an internal study at your organization then you should have exact numbers, dates, criteria, etc. that lead to that number. Don't state a fact or use a number that you can't back up.
- If you let it, your favorite LLM will write a script for you for your presentation. DO NOT STAND IN FRONT OF AN AUDIENCE READING A SCRIPT FROM AN LLM. I'm going to repeat it because I've seen it happen too many times lately. DO NOT STAND IN FRONT OF AN AUDIENCE READING WHAT IS ESSENTIALLY THE RESULTS FROM A PROMPT YOU GAVE AN LLM. Your audience is highly technical and perfectly capable of creating their own prompts. They are not at Nebraska.Code to listen to a human read the results of a prompt.
- There are ways to use AI to add value to your presentation. LLM's are great at organizing a talk and creating an outline that flows well. They can do research and suggest areas that you can go more in-depth. If you are not graphically inclined AI can help make a pleasing looking slide deck, although if you are not careful it will have an AI sheen to it.
- The audience is here to listen to your thoughts and experiences. That is where the value of the conference comes from. While AI is creeping into every aspect of our lives, getting together, in-person, can be a quiet act of human defiance. I love in-person events and I want them to continue to play an integral role in the tech industry.
What we look for:
- Content above all else - we're looking for topics that will be of interest to our attendees, regardless of who submits them.
- Sessions on all aspects of software creation (design, development, management, etc) on any technology stack are welcome!
- We take great pride in the number of sessions that we offer, so getting a good variety of different topics is very important.
What you need to know:
- Spotlight Sessions are 25 minutes, Breakout sessions are 60 minutes and Workshops are 6 hours
- Workshops are on Wednesday, June 23rd, 2027
Submission Guidelines
- Title - Make sure your title makes it clear what your session is about. While it is tempting to go for the pun/attention-grabbing statement it is important to remember that attendees are quickly scanning titles when making their decisions on which sessions to attend. * ex. Bad - "Your Javascript is dirty, BRO!!!!" Much Better - "Implementing SOLID Principals in Javascript"
- Description / Abstract - Be descriptive and complete. Your description should make it clear what value an attendee will receive for attending your session. It is highly recommended that you include a concise summary that describes the attendee take-aways. * ex - "Attendees will leave with a much better understanding of the tools, techniques, and libraries available to write higher quality and more maintainable Javascript"
If you are selected
- Out-of-town speakers will have their hotel rooms covered.
- All speakers receive complimentary admission to the event
- You will receive a speaker guide with all you need to know about the event, including venue location, hotel information, projector resolutions, room sizes, travel information, etc... Please read it thoroughly.
Speaker Travel Expenses: We do cover stay at the hotel and in certain special circumstances will cover T&E for speakers. If you need your travel covered by the conference reach out before submitting your sessions. Any travel reimbursement needs to be approved BEFORE session selection.
Workshop Speaker Remuneration: We know how much work and effort goes into creating a full-day workshop. Workshop speakers will receive $20/attendee in their workshop.