Scheduler Proof of Concept
by Julian RubischThe backbone of the app is starting to shape. I managed to craft a reactive prototype of a workload distribution solution.
Getting the distribution right due to quantized (rounded) precision (the prototype is working with quarter hours, but this will be customizable) was challenging, but the groundwork is done.
The scheduler will take a date range, an amount of hours and a workload type (hill, valley, increasing, decreasing) and allot time automatically, ensuring that time is optimally distributed along the date range.
-
1
Have you thought about expanding more on "Determine the optimal time allocation over a given timespan.". It looked like an interesting concept, but the only explanation I've seen was a simple static image (which wasn't enough for me in order to understand this whole concept).
-
1
Thank you for your reply! Honestly I'm a bit new to the whole IndieHackers Experience, and sometimes it acts a bit surprising... so it is entirely possible you didn't find this info because I posted it in the wrong places.
That said, have you read these blog posts of mine?
https://www.crowsnestapp.com/data-science/2020/09/24/the-science-behind-crows-nests-burn-rate-types/
https://www.crowsnestapp.com/product/2020/08/30/hidden-overbookings-freelancers-fast-lane-to-burn-out/Maybe they can provide more clarity.
And I'm 100% with you that an introductory video would be great, which is why I'm preparing a Proof of Concept right now... the one linked here already has a short video: https://twitter.com/julian_rubisch/status/1313110983330672643?s=20
-