Hello! How are you?

If you read this, it means you think on submitting your talk. That is great!

Click here if you have any doubts.

We are interested in .NET talks related to the following topics:

  • High-performance, fault-tolerant systems
  • Memory management & GC
  • ASP.NET Core
  • .NET Core
  • Software architecture
  • Domain-driven design
  • Microservices
  • Big data
  • Development and build tools
  • Roslyn
  • CLR internals
  • Cross-platform development (Xamarin, Unity)
  • .NET libraries and frameworks
  • Dependency management
  • Continuous delivery

Submission process

Each submitted talk will be examined by at least three reviewers from the Program Committee.

Until January 22 you can submit your talk. After then you are invite to Slack in 1-2 days. Within 5 days we discuss your talk, and then we will start work on your talk. We train it, discuss and reviews at a time convenient for you. February 5 we make the final decision considering your submission, then get your talk ready for production. April 6-7 you give your talk at the conference.
Program Committee

Program committee

Vagif Abilov
Vagif Abilov Miles
Vagif is a Russian/Norwegian developer working for a Norwegian company Miles. He has about three decades of programming experience, currently...

Vagif is a Russian/Norwegian developer working for a Norwegian company Miles. He has about three decades of programming experience, currently focusing on building systems in F# and C#. Vagif is a frequent speaker on software conferences, contributor to some open source projects and maintainer of Simple.OData.Client.

Anatoly Kulakov
Anatoly Kulakov Paladyne Systems
Anatoly was studying to become an information security specialist. He was earning money like a tough C++ developer on Linux....

Anatoly was studying to become an information security specialist. He was earning money like a tough C++ developer on Linux. After getting bored of coding, he felt the urge to create and switched to C#. He has been writing in .NET since its first versions. Currently Anatoly is designing and developing business applications, distributed and fault-tolerant systems. He spends his spare time with ES, CQRS and DDD.

Igor Labutin
Igor Labutin Lanit-Tercom
An architect. 16 years ago Igor started as a C++ developer, worked with Win, Linux, QNX in areas ranging from...

An architect. 16 years ago Igor started as a C++ developer, worked with Win, Linux, QNX in areas ranging from video processing to network card drivers with a full implementation of the TCP/IP stack. 9 years ago he switched to C# and started dealing with architecture as well. His special focus is on the challenges of apps interaction (mainly on WCF stack), performance problems, as well as the convenience of developers working on complex projects.

Andrey Akinshin
MVP Reconnect member
Andrey Akinshin JetBrains
Andrey Akinshin is a senior developer at JetBrains, where he works on Rider (a cross-platform .NET IDE based on the...

Andrey Akinshin is a senior developer at JetBrains, where he works on Rider (a cross-platform .NET IDE based on the IntelliJ platform and ReSharper). His favorite topics are performance and micro-optimizations, and he is the maintainer of BenchmarkDotNet (a powerful .NET library for benchmarking supported by the .NET Foundation). Andrey is also a PhD in computer science, a Microsoft .NET MVP, a silver medalist of ACM ICPC. In his free time, he likes to study science (his primary research interests are mathematical biology and bifurcation theory).

Maxim Arshinov
Maxim Arshinov HighTech Group
The co-founder of HighTech Group, teacher in KFU and blogger. Try to google "как писать тесты" ("how to write tests"...
Maxim Arshinov

The co-founder of HighTech Group, teacher in KFU and blogger. Try to google "как писать тесты" ("how to write tests" in Russian). The first result is his article.

Previously, before founding his own company, Maxim was employed as a Web Developer, Team Leader, CTO and Head of Quality Department in various companies from Kazan, Moscow, Saint Petersburg and Antwerp, Belgium.

He is sure that technology is not a "thing in itself", but tools. The tools must suit the problem being solved. The work of an engineer is to select the right tools and create new ones.

Sasha Goldshtein
Sasha Goldshtein Google
Sasha Goldshtein is the CTO of Sela Group, Microsoft MVP and Regional Director, Pluralsight and O'Reilly author, and an international...

Sasha Goldshtein is the CTO of Sela Group, Microsoft MVP and Regional Director, Pluralsight and O'Reilly author, and an international consultant and trainer. Sasha is the author of "Introducing Windows 7 for Developers" (Microsoft Press, 2009) and "Pro .NET Performance" (Apress, 2012), a prolific blogger and open source contributor, and author of numerous training courses including .NET Debugging, .NET Performance, Android Application Development, and Modern C++. His consulting work revolves mainly around distributed architecture, production debugging and performance diagnostics, and mobile application development.

Elizaveta Golenok
Elizaveta Golenok MTS
Elizaveta is a leading developer at MTS Information Technologies. She has got experience in developing and designing systems both in...

Elizaveta is a leading developer at MTS Information Technologies. She has got experience in developing and designing systems both in C/C++ and C# ASP.NET, Mono (from navigation systems to enterprise solutions). She's into route planning and multi-agent systems, compilation, LLVM, Clang, low-level debugging of applications.

Mikhail Shcherbakov
MVP Reconnect member
Mikhail Shcherbakov KTH Royal Institute of Technology
Mikhail is a PhD student and researcher at KTH Royal Institute of Technology, an independent developer and consultant, a participant...

Mikhail is a PhD student and researcher at KTH Royal Institute of Technology, an independent developer and consultant, a participant of Microsoft Bug Bounty Programs, co-organizer of DotNet.ru, and Microsoft MVP. His professional areas are Application Security, Web Security, Static and Dynamic Code Analysis, Information Flow Security.

Natalia Ershova
Natalia Ershova JUG Ru Group
...
Natalia Ershova


Selection process
We consider talk applications according to the following guidelines:
  • The topic's relevance: you are going to discuss things that participants of the conference find useful not only yesterday but today and in the future. In addition, the topic of your talk corresponds to the theme of the conference, and the talk's content matches the stated topic.
  • Your talk dives deep into the details of the stated topic: there is no need to talk about yet another Hello World (unless you think it's a new, not widely known, but very promising technology).
  • Originality — there is technical novelty in your talk; the content of your talk either hasn't been published before or presents a well-known topic / problem in a different light.
  • Practical applicability — the talk is important from practical point of view, you not only cover the existing problems / solutions, but also share your experience.
  • Speaker's expertise and publicity.

In order to submit your talk, please, fill in the form below: we kindly ask you to pay as much attention as possible while doing that, because we'll consider your application based on the information provided below. If you require help while preparing your talk, we'll do our best to help you make a good talk.
If you've already submitted your talk, yet haven't heard from us during one week, then something went wrong. In this case, please, contact us via email program@dotnext.ru.
If you’d like to give a talk at the conference, please, read the memo for speakers.

Speaker

Talk

The title should be clear and reflect the essence of the talk. Remember: brevity is the soul of wit.
Include enough details about your talk, but be concise and clearly state: describe technologies that will be covered, purpose of the talk (problem and its solutions, etc.), target audience, audience takeaway.
About 20 points that represent main ideas of the talk.


We reserve the right to edit lexical and grammatical flaws in texts you will send.