BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:Asia/Kolkata
BEGIN:STANDARD
DTSTART:19451014T230000
TZOFFSETFROM:+0630
TZOFFSETTO:+0530
TZNAME:IST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20250308T173409Z
UID:52021E0D-7122-4044-A95A-510A2848E63D
DTSTART;TZID=Asia/Kolkata:20250302T100000
DTEND;TZID=Asia/Kolkata:20250302T120000
DESCRIPTION:IEEE JUIT Student Branch organized an innovative and dynamic co
 ding competition\, &quot;Code Rumble\,&quot; designed to challenge not only the tech
 nical abilities of participants but also their teamwork and strategic thin
 king. Unlike traditional coding contests\, this event introduced a unique 
 twist where teams of two had to collaborate\, analyze problems of varying 
 difficulty levels (Easy\, Medium\, and Hard)\, and nominate one member to 
 solve each question.\n\nWith limited swap opportunities and high-stakes de
 cision-making\, Code Rumble pushed participants to manage pressure\, trust
  their partner’s strengths\, and execute solutions efficiently. The even
 t aimed to promote problem-solving\, enhance coding proficiency\, and enco
 urage peer-to-peer learning through a fun and competitive environment.\n\n
 IEEE JUIT Student Branch organized an exciting and strategic coding compet
 ition\, &quot;Code Rumble\,&quot; designed to test both the technical skills and tea
 mwork of participants. Unlike regular coding contests\, this event introdu
 ced a unique twist that required teams to collaborate\, plan\, and execute
  under pressure.\n\nThe competition was held in teams of two\, with each t
 eam receiving a set of problems categorized into Easy\, Medium\, and Hard 
 levels. Before the round began\, teams were given time to carefully analyz
 e all the questions and decide on a strategy.\n\nAfter the analysis phase\
 , each team had to nominate one member to stay and solve the problem while
  the other teammate stepped out of the room. This added a strategic elemen
 t\, as teams had to decide who was best suited for each problem.\n\nDuring
  the coding phase\, the nominated participant worked on solving the questi
 on within the given time. If they got stuck or felt they couldn’t comple
 te it\, they could call for a swap\, allowing their teammate to enter and 
 take over. However\, swaps were limited\, making it important to use them 
 wisely.\n\nTeams were judged based on the accuracy of their solutions\, th
 e efficiency of their code\, the number of swaps used\, and the time taken
  to complete the problems. This format not only tested coding abilities bu
 t also decision-making and teamwork.\n\nRoom: CL4\, Bldg: Academic Block\,
  Jaypee University Of Information Technology\, Solan\, Himachal Pradesh\, 
 India\, 173234
LOCATION:Room: CL4\, Bldg: Academic Block\, Jaypee University Of Informatio
 n Technology\, Solan\, Himachal Pradesh\, India\, 173234
ORGANIZER:
SEQUENCE:10
SUMMARY:Code Rumble at Murious 2025
URL;VALUE=URI:https://events.vtools.ieee.org/m/473489
X-ALT-DESC:Description: &lt;br /&gt;&lt;p class=&quot;MsoNormal&quot; style=&quot;line-height: 150%
 \; margin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-
 height: 150%\; font-family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-
 family: &#39;Times New Roman&#39;\;&quot;&gt;IEEE JUIT Student Branch organized an innovat
 ive and dynamic coding competition\, &quot;Code Rumble\,&quot; designed to challenge
  not only the technical abilities of participants but also their teamwork 
 and strategic thinking. Unlike traditional coding contests\, this event in
 troduced a unique twist where teams of two had to collaborate\, analyze pr
 oblems of varying difficulty levels (Easy\, Medium\, and Hard)\, and nomin
 ate one member to solve each question.&lt;/span&gt;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; st
 yle=&quot;line-height: 150%\; margin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;fon
 t-size: 12.0pt\; line-height: 150%\; font-family: &#39;Times New Roman&#39;\,&#39;seri
 f&#39;\; mso-fareast-font-family: &#39;Times New Roman&#39;\;&quot;&gt;With limited swap oppor
 tunities and high-stakes decision-making\, Code Rumble pushed participants
  to manage pressure\, trust their partner&amp;rsquo\;s strengths\, and execute
  solutions efficiently. The event aimed to promote problem-solving\, enhan
 ce coding proficiency\, and encourage peer-to-peer learning through a fun 
 and competitive environment.&lt;/span&gt;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; style=&quot;line-
 height: 150%\; margin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&lt;strong style=&quot;mso-bidi-fo
 nt-weight: normal\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-height: 150%\; 
 font-family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-family: &#39;Times 
 New Roman&#39;\;&quot;&gt;IEEE JUIT Student Branch&lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;font-si
 ze: 12.0pt\; line-height: 150%\; font-family: &#39;Times New Roman&#39;\,&#39;serif&#39;\;
  mso-fareast-font-family: &#39;Times New Roman&#39;\;&quot;&gt; organized an exciting and 
 strategic coding competition\, &lt;strong style=&quot;mso-bidi-font-weight: normal
 \;&quot;&gt;&quot;Code Rumble\,&quot;&lt;/strong&gt; designed to test both the technical skills an
 d teamwork of participants. Unlike regular coding contests\, this event in
 troduced a unique twist that required teams to collaborate\, plan\, and ex
 ecute under pressure.&lt;/span&gt;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; style=&quot;line-height:
  150%\; margin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; 
 line-height: 150%\; font-family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-
 font-family: &#39;Times New Roman&#39;\;&quot;&gt;The competition was held in teams of &lt;st
 rong style=&quot;mso-bidi-font-weight: normal\;&quot;&gt;two&lt;/strong&gt;\, with each team 
 receiving a set of problems categorized into &lt;strong style=&quot;mso-bidi-font-
 weight: normal\;&quot;&gt;Easy&lt;/strong&gt;\, &lt;strong style=&quot;mso-bidi-font-weight: nor
 mal\;&quot;&gt;Medium&lt;/strong&gt;\, and &lt;strong style=&quot;mso-bidi-font-weight: normal\;
 &quot;&gt;Hard&lt;/strong&gt; levels. Before the round began\, teams were given time to 
 carefully analyze all the questions and decide on a strategy.&lt;/span&gt;&lt;/p&gt;\n
 &lt;p class=&quot;MsoNormal&quot; style=&quot;line-height: 150%\; margin: 12.0pt 0cm 12.0pt 
 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-height: 150%\; font-family: &#39;
 Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-family: &#39;Times New Roman&#39;\;&quot;&gt;
 After the analysis phase\, each team had to nominate &lt;strong style=&quot;mso-bi
 di-font-weight: normal\;&quot;&gt;one member&lt;/strong&gt; to stay and solve the proble
 m while the other teammate stepped out of the room. This added a strategic
  element\, as teams had to decide who was best suited for each problem.&lt;/s
 pan&gt;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; style=&quot;line-height: 150%\; margin: 12.0pt 0
 cm 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-height: 150%\; font
 -family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-family: &#39;Times New 
 Roman&#39;\;&quot;&gt;During the coding phase\, the nominated participant worked on so
 lving the question within the given time. If they got stuck or felt they c
 ouldn&amp;rsquo\;t complete it\, they could call for a &lt;strong style=&quot;mso-bidi
 -font-weight: normal\;&quot;&gt;swap&lt;/strong&gt;\, allowing their teammate to enter a
 nd take over. However\, swaps were limited\, making it important to use th
 em wisely.&lt;/span&gt;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; style=&quot;line-height: 150%\; mar
 gin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-height
 : 150%\; font-family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-family
 : &#39;Times New Roman&#39;\;&quot;&gt;Teams were judged based on the &lt;strong style=&quot;mso-b
 idi-font-weight: normal\;&quot;&gt;accuracy&lt;/strong&gt; of their solutions\, the &lt;str
 ong style=&quot;mso-bidi-font-weight: normal\;&quot;&gt;efficiency&lt;/strong&gt; of their co
 de\, the &lt;strong style=&quot;mso-bidi-font-weight: normal\;&quot;&gt;number of swaps&lt;/s
 trong&gt; used\, and the &lt;strong style=&quot;mso-bidi-font-weight: normal\;&quot;&gt;time&lt;
 /strong&gt; taken to complete the problems. This format not only tested codin
 g abilities but also decision-making and teamwork.&lt;/span&gt;&lt;/p&gt;\n&lt;p class=&quot;M
 soNormal&quot; style=&quot;line-height: 150%\; margin: 12.0pt 0cm 12.0pt 0cm\;&quot;&gt;&amp;nbs
 p\;&lt;/p&gt;\n&lt;p class=&quot;MsoNormal&quot; style=&quot;line-height: 150%\; margin: 12.0pt 0c
 m 12.0pt 0cm\;&quot;&gt;&lt;span style=&quot;font-size: 12.0pt\; line-height: 150%\; font-
 family: &#39;Times New Roman&#39;\,&#39;serif&#39;\; mso-fareast-font-family: &#39;Times New R
 oman&#39;\;&quot;&gt;&lt;img src=&quot;https://events.vtools.ieee.org/vtools_ui/media/display/
 897ab74c-7926-4ed4-8e6c-916ee0f3fd70&quot; width=&quot;233&quot; height=&quot;267&quot;&gt; &amp;nbsp\;&lt;im
 g src=&quot;https://events.vtools.ieee.org/vtools_ui/media/display/39560709-489
 4-4c42-a870-42f2c4f06bbc&quot; width=&quot;268&quot; height=&quot;201&quot;&gt; &amp;nbsp\; &lt;img src=&quot;http
 s://events.vtools.ieee.org/vtools_ui/media/display/623bcb13-8743-4f0f-9d73
 -e6c2a5e4c2b0&quot; width=&quot;212&quot; height=&quot;159&quot;&gt;&lt;/span&gt;&lt;/p&gt;
END:VEVENT
END:VCALENDAR