Free Trial

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #417: Evaluation of Employee Working Hours

ScottLewis
11 - Bolide

My answer, fairly elegant this time, though it does rely on a quirk of the date format (for YYYY MM DD) type formats where MM and DD have enforced 0 in the first character date minimum and string minimum are the same so you don't have to fuss with conversions.)

 

Bonus question feels like a bit of data overreach as the data set doesn't have a majority of the relevant considerations for making that decision.

 

Capture.PNG

Inactive User
Not applicable
 

My Solution: 

 

 

Spoiler

 

Bonus: IJ345 - due to all shifts being below 4 hours and the lowest amount of shifts performed.

 Results 3-13-2024.PNGWorkflow 3-13-2024.PNG

 

 

 

achisman
7 - Meteor

My Solution


Spoiler.png

 

Reesetrain2
9 - Comet
9 - Comet

All,

 

My solution:

Spoiler
Screenshot 2024-03-13 155016.png

Who should pickup more shifts:

Spoiler
Screenshot 2024-03-13 155320.png

 

olga_strubbe
11 - Bolide

Hi Akimasa, 

From what I can see, the total days are different because in the challenge solution from Nathan the total days are counted from the first day that employee worked - not all employees started work on Jan 1.  

Hope this helps :)  

sar5760
6 - Meteoroid

My solution:

 

Spoiler
Results 3-13-2024.PNGWorkflow 3-13-2024.PNG

  

pchong
8 - Asteroid

Solution for my first challenge! 

asultanov
8 - Asteroid
Spoiler
Screenshot 2024-03-14 174058.png
Powerhouse_21
10 - Fireball
Spoiler
417.png
Chris-Nienart
8 - Asteroid

If the dataset were larger, I would have reimported the start file as a csv and used the First Row Contains Field Names option.

Also, does anyone else hate percentages stated on a 0-100 scale?  

 

Spoiler
spoiler-417.PNG