Warning
Developed for unix OS.
This software is NOT official from 42 Network, use it at your own risk.
For informational purposes only.
You’ve probably had to calculate the days you have for each milestone and even after asking around, you still might not have everything clear. Well, that’s what happened to me, so I decided to create a pace-date calculator to know where I stand and how I’m doing.
I named it "42 Deadlines", and is a personal side project to practice what I’ve learned and, I hope, to be useful for anyone working under the "pace system."
Of course, it’s not an official application from 42 School and it in no way replaces the information you receive from the Staff or any official documents from the 42 network.
The information you get is only a guideline based on the kickoff date you input, so it might not match your actual times, especially if you’ve gone through a freeze, bonus days, etc...
I’ll try to keep it updated, but any help is welcome if you’re interested.
git clone https://github.com/LLuisPP/deadlines42Public.git deadlines42
Navigate to cloned folder:
cd deadlines42
Compile program in your terminal:
make
Use correct syntax, for example:
./deadlines 22-09-15 5 18
Handle instructions:
milestone | 8 mths | 12 mths | 15 mths | 18 mths | 22 mths | 24 mths |
---|---|---|---|---|---|---|
0 | 8 | 13 | 18 | 24 | 30 | 45 |
1 | 24 | 35 | 42 | 48 | 58 | 73 |
2 | 22 | 33 | 41 | 49 | 60 | 60 |
3 | 36 | 53 | 67 | 80 | 98 | 128 |
4 | 51 | 77 | 96 | 115 | 141 | 141 |
5 | 71 | 107 | 134 | 162 | 197 | 197 |
6 | 32 | 47 | 59 | 70 | 86 | 86 |
(244 d) | (366 d) | (458 d) | (549 d) | (671 d) | (732 d) |
milestone | 8 mths | 12 mths | 15 mths | 18 mths | 22 mths | 24 mths |
---|---|---|---|---|---|---|
0 | 8 | 13 | 18 | 24 | 30 | 45 |
1 | 32 | 48 | 60 | 72 | 88 | 118 |
2 | 54 | 81 | 101 | 121 | 148 | 178 |
3 | 90 | 134 | 168 | 201 | 246 | 306 |
4 | 141 | 211 | 264 | 316 | 387 | 447 |
5 | 212 | 318 | 398 | 478 | 584 | 644 |
6 | 244 | 365 | 457 | 548 | 670 | 730 |
Tip
Key concepts: timestamp
leap_year
epoch
Note
If you find an error and you want to contribute:
Fork the repository
- Create a pull request
- Create a new branch:
git checkout -b ErrorBug
- Make your changes and commit them:
git commit -m 'Error description'
- Push the changes to your branch:
git push origin ErrorBug