ohcnetwork / admission_task

Global Digital Corps - Software Engineering Test Problem | Priority list

Global Digital Corps - Software Engineering Test Problem | Priority list

https://fullstack.gdc.network

This repo contains the starting templates for all supported languages in the challenge.

Please note that this repository is not meant for collaboration. While we appreciate issues and pull requests, we cannot guarantee any response — we may close issues and PRs without explanation.

---

Kindly desist from sharing your solution privately or publicly. This is because the programming task is not complex for those who've written non-trivial amount of code before. But for beginners, solving this can be quite instructive - frustrating at times, but rewarding in the end.

But if you share your solution with them - through a GitHub repo, or by circulating in your private networks, you're only robbing them of a rewarding experience that would have helped them grow as programmers.

It is trivial to detect copy-cat code submissions and students who submit plagiarized code will be unable to find a place among the limited seats in the course. It is just that it'll take us a few more moments to read through the code and tag it. A lose-lose proposition for all concerned.

---

That said, we hope you find the challenge interesting. We've found more students who've worked through the problem diligently and have written in about the magic of programming than what any of us hoped to, when we first announced the course.

The seats in this particular course are limited - but that shouldn't deter you - there is no limit to how much you can grow if you continue to enjoy programming and work at it.

We wish you best of luck and look forward to reading your code submissions!

Base Project Setup with Starter Packs

This repository provides pre-built starter packs for various programming languages, helping you quickly set up a base project. Each starter pack comes with a pre-configured environment, including the necessary files and documentation to get you started.

Available Starter Packs

The following starter packs are available:

• C: fellowship-c.zip
• C++: fellowship-cpp.zip
• JavaScript: fellowship-javascript.zip
• Ruby: fellowship-ruby.zip
• Python: fellowship-python.zip
• Java: fellowship-java.zip

How to Use a Starter Pack

Step 1: Select the Appropriate Zip File

Choose the zip file that corresponds to the programming language you wish to use:

• If you are working in C, download fellowship-c.zip.
• If you are working in C++, download fellowship-cpp.zip.
• If you are working in JavaScript, download fellowship-javascript.zip.
• If you are working in Ruby, download fellowship-ruby.zip.
• If you are working in Python, download fellowship-python.zip.
• If you are working in Java, download fellowship-java.zip.

Step 2: Unzip the Starter Pack

Extract the contents of the selected zip file into your project directory. For example, if you are using the JavaScript starter pack, run:

unzip fellowship-javascript.zip -d your-project-directory

Step 3: Follow the Included README Instructions

Each starter pack includes a README.md file with language-specific instructions. Once you have unzipped the starter pack, open the README.md file in your project directory and follow the instructions to get your project up and running.

For example:

• C Starter Pack: Instructions on compiling and running C programs.
• JavaScript Starter Pack: Instructions on setting up and running a Node.js environment.
• Python Starter Pack: Instructions on setting up a Python environment and running scripts.

Step 4: Build Your Task Manager

Use the starter pack as a base to build your task manager. You can add the required features as per the requirements and test your implementation using the Makefile in your starter pack.

License

This project is licensed under the MIT License. See the LICENSE file for more details.

admission_task's Issues

Suggestions

Don't use priority as an identifier

I suggest avoiding the use of task priority as the identifier to pick a todo item. In any real-world-ish implementation, the priority is bound to be stored separately from any identifier.

Allow multiple TODO items to have the same priority

Again, in real world implementations, it's common to have multiple todo items in a list that share the same priority.

So instead of using priority as an identifier, let's use that to sort the output of the program? For example, here's a sample scenario:

./tasks add 2 "A thing I need to do"
# Added task: "A thing I need to do" with priority 2

./tasks add 2 "Another thing I need to do"
# Added task: "Another thing I need to do" with priority 2

./tasks add 4 "A not-so-important thing I need to do"
# Added task: "A not-so-important thing I need to do" with priority 4

./tasks add 1 "Quite an important todo item"
# Added task: "Quite an important todo item" with priority 1

./tasks ls
# 1. Quite an important todo item [1] 
# 2. A thing I need to do [2] 
# 3. Another thing I need to do [2] 
# 4. A not-so-important thing I need to do [4]

./tasks done 2
# Marked "A thing I need to do" as done

./tasks report
# Pending: 3
# 1. Quite an important todo item [1] 
# 2. Another thing I need to do [2] 
# 3. A not-so-important thing I need to do [4]
#
# Completed: 1
# 1. A thing I need to do

Note how the identifier is basically just indexing of an array sorted by priority.

Admission_task

admission_task

No explanation of problem is provided and no platform to solve the problem