Skip to content

A solo attempt at creating a soul crushingly difficult exam (not only is it mentally demanding, but tedious as well)

Notifications You must be signed in to change notification settings

AryanChand753/one-embedded-problem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 

Repository files navigation

The One Problem Embedded Programming Exam

Author: Aryan Chand

Tip

This is a psychopathic1 exam to take.

Welcome to the public release of my One Problem Embedded Programming Exam. This repository is designed so anyone can fork, attempt, and submit their own solution. Whether you're practicing, teaching, or just testing your engineering discipline, this challenge is meant to to be rigorous.

Note

Please recognize this is my first attempt at creating a such exam; and while I could create test casing and automate failing solutions, I would have to read through the solutions regardless to verify if the rules have been followed to the fullest.

Overview

This exam presents a single programming problem that evaluates:

  • Algorithmic reasoning
  • Code clarity and maintainablility
  • Correctness and edge-case handling
  • Ability to design modular, testable solutions
  • Documentation and explaining skills

The problem statement, rules, and instructions are included in the repository in pdf form (exam.pdf) or through the markdown file exam/readme.md

How

  1. Read the full problem statement
  2. Fork the repository
  3. Implement your solution
    • Place your solution files in the solutions/ directory within a folder with your github username.

      [!TIP] Feel free to copy the __sample_user/ directory and rename it before starting.

  4. Provide explanations
    • In your solution folder, create a markdown file for your explanations. You may either include a separate markdown file for the follow-up questions or keep it in one document.
    • If you copied the sample user directory, there are template documents provided already in __sample_user/docs/.
  5. Add sample inputs and outputs
    • This will vary by solution
  6. Submit your attempt
    • If you would like your solution to be public, simply open a pull request with a submission tag

Repository Structure

/                                     # ... the repo ...
|-- exam/
|   |-- exam.pdf
|   |-- Instructions.md
|   |-- readme.md
|   └-- Rubric.md
|-- img/                              # This is for the repository README file
|-- solutions/
|   |-- __sample_user/            # ! # DO NOT EDIT THIS DIRECTORY
|   |   |-- docs/
|   |   |   |-- explanations.md       # Explain your solution
|   |   |   └-- follow_up.md          # Answer the follow up questions
|   |   |-- src/
|   |   |   └-- main.c                # sample starter ( literally has nothing lol )
|   |   |-- test/                     # User-defined test cases ( optional )
|   |   |   └--test.md                # Optional
|   |   └-- readme.md                 # Basic Information ( optional )
|   └-- YOUR_USERNAME/
|       └-- "                         # INSERT YOUR SOLUTION
|-- .gitignore                        # Ignorance is bliss
└-- README.md                     # ! # YOU ARE HERE

RULES

  • Your work MUST be your own.
  • AI-generated code is NOT allowed.
  • You may submit multiple attempts.
  • If you are attempting to produce a solution with lightened constraints, please specify it in your pull request AND the readme of your submission directory

Contributing

This repository is intentionally open. You are welcome to:

  • Submit your attempt
  • Discuss in the discussions tab
  • Suggest improvements to the exam ( use enhancement or bug labels in issues )
  • Add public test cases ( Feel free to put it in the discussions tab )

If you enjoyed this challenge

Consider starring the repo to help others discover it. You can also share your solution and compare it to others'

Footnotes

  1. This exam is cancer in exam form - tedious and draining.

About

A solo attempt at creating a soul crushingly difficult exam (not only is it mentally demanding, but tedious as well)

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages