All the submissions will happen through PR sent by you to this repo which will be evaluated, make sure to add your names for identification
Please refer to the following rules as any violation(s) or noncompliance will result in negative grading:
- Document any and every step throughout your tasks. Refer section Rules.1
- Provide a link to every resource you have used for your research or code-generation.
- Use of LLMs is allowed but the chats must be shared in the report.
- Please ensure to work only on the task provided to you. Refer section Rules.2
- Expect to be questioned for every line within your report. Refer section Rules.3
Every step taken in a task must be documented. The document doesn't have any specific formatting requirements but must adhere to the following constraints:
- Every line written in the document must be inferred or obtained from research, resources or code.
- In Extension to Rules.1.1, every line of code must be inferred in accordance to your report.
- The document is not a formal report. The document is expected to contain your reasoning and approach. Example: Instead of writing "16 bit integers were used to save space", mention in brief as "My initial idea was to use integers to save space as opposed to strings and within integers, I started with 32-bit fixed integers but later realized (also mention what you realized and how) that the 16 bits from MSB were useless so I used 16-bit integers"
Every candidate is provided with a unique task amongst 3 available tasks. Ensure to only participate in the task provided to you.
- The tasks under category 3 are common for every candidate and is the sole exception to this rule.
- Bonus points are awarded for breaking your system uniquely in category 3 tasks - refer to category 3 - Task 3.3
The questioning are designed to test the following:
- Your understanding and not testing your memorization of the report for word-to-word.
- Your style of thinking and methods to approach problems.
- Your reasoning behind solutions and problems.