CLRium # 7: Practical. Seminar, homework with verification, mentoring

April 18, 2020 in St. Petersburg and May 16 in Moscow largest .NET platform seminar will be held CLRium # 7 on which we will continue the topic of multi-threading: this time in terms of practice. The main topics of the seminar (the program is being formed):

  • Parallel Code Architecture
  • Testing parallelized code, algorithms, and synchronization primitives
  • Debugging Parallel Code

And this time the seminar will be, in a sense, two weeks:

  • The workshop itself will go the day;
  • After which you will receive homework and within two weeks we will solve them together, check and give advice on how to improve them (a group in Telegram will also be created to discuss them dynamically);

It is also possible to work in the format of interviews with a personal mentor

Practice and homework

Attending conferences does not guarantee experience: after all, experience is primarily a practice. At conferences there are a lot of interesting topics, a lot of food for thought, but gradually everything disappears from memory … But what experienced people tell us: in order for information to settle, you must first repeat it, and secondly, try it in practice.

Therefore, I decided to make a new evolutionary round of the seminar. Work at the seminar is implied in 3 or 4 stages:

Stage 1: By purchasing tickets for CLRium # 7, you additionally get access to CLRium # 6 videos: Concurrency & Parallelism, in which we told you all the layers of multithreading: from the processor level to the async / await level. You can study his materials immediately after purchasing a ticket.

Stage 2: Attendance at CLRium # 7 Workshop. It will contain a number of reports related to the practice of developing multi-threaded code.

Stage 3: at the end of the seminar, you will receive many tasks for the development and correction of existing code. In essence – to realize the knowledge you have gained.

Here we are still thinking: most likely this stage will consist of two: when everyone gets the decision of the other participant and will review it, gaining experience in analyzing multi-threaded code (written essentially by a beginner). The second stage is the analysis by us as curators: at the same time you send the tasks for verification, and we give recommendations for fixing them (once, but capaciously). Resending tasks to us for verification will lead to a shorter answer. Either everything is fine, or a couple of comments. But not capacious. The answer will be short.

Thus, you will receive three checks: by the community – 1 time and 2 times – by us.

Stage 4 (optional): if you wish, we can go through mentor interviews together. More details about them are below.

Mentor Interviews

To consolidate knowledge thoroughly, we introduced another interaction format. You buy a separate type of ticket and agree to receive a slot from the schedule of interviews. In total, two interviews are available:

Primarywhen the mentor interrogates you on the topic of multithreading, gives suggestive questions, and after that describes your gaps and gives links + a list of literature and reports for study

Secondarywhen mastering the material, you call up and consolidate the experience gained.

The format of the interview is excellent in that it helps to prepare for a change of work, as well as simply consolidate the knowledge gained when communicating with the mentor: after all, this is a full 5 hours of communication.

Due to the fact that time is not rubber, and we are also working somewhere on our tasks, the number of slots for mentoring interviews is limited: 150 tickets for both cities. Here you need to decide in advance.

Contacts

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *