I’m looking at my calendar and it’s day 100-something of working from home. The thing I’ve been missing most is seeing fellow developers and building software together.
That’s why I’m excited to announce that on October 13, 2020, we’re kicking off Nerd Days 1.0: Return of the Data Nerd.
What is Nerd Days 1.0?
Nerd Days 1.0 is a new, one-day conference dedicated entirely to engineers. And best of all? It’s 100% virtual and hands-on. This means you can tune in whenever and from wherever—whether it’s your home office, kitchen table, couch, or floor—as long as you have an internet connection.
That’s cool, but I built cool projects with New Relic and want to share!
The options don’t end there. For anyone interested in sharing their knowledge and passion for observability tools, we’re opening a call for proposals.
We’ve put together five tracks to choose from: Observability, Cloud Migration, Open Source, DevOps Journey, and Fundamentals. Your presentation or workshop around one of these topics will help developers better instrument and monitor their software. So let’s make what developers do more efficient, knowledge-driven, and fun.
Submit your proposal by September 1, 2020 at 11:59 PM PT and our review committee of subject matter experts will let you know if you are accepted to speak by September 30, 2020.
We built Nerd Days to support the engineers we love, who are fueled by a desire for connection, entrepreneurship, and problem-solving. Our mission is to create more perfect software with our expertise in observability tools. And that starts with us, together.
- August 17, 2020: Call for proposals opens
- September 1, 2020: Submissions due
- September 30, 2020: Decisions made
- October 13: Nerd Days
Pro-tips for submissions:
- Tailor your content to be as hands-on and interactive as possible.
- Explain what exact benefit your content offers to an engineer: will it teach them a new technique? Make their existing method easier?
- Keep it short and sweet—let us know what you hope to accomplish in less than 1,000 characters. And while you’re writing, avoid using undefined abbreviations or taking on an overly casual tone.
- Proofread! And proofread again. Ask a friend or colleague to look over your abstract before submitting.
Ready, set, build.
The views expressed on this blog are those of the author and do not necessarily reflect the views of New Relic. Any solutions offered by the author are environment-specific and not part of the commercial solutions or support offered by New Relic. Please join us exclusively at the Explorers Hub (discuss.newrelic.com) for questions and support related to this blog post. This blog may contain links to content on third-party sites. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites.