Creating a simple SaaS and library for doing blocking scheduling. “Find me the next open hour for Y” - sort of like calendly but for developers with a really easy/neat callback mechanism.
I’m building it because I’m tired of being oncall for lousy delay queues, which seem to always be built in house with no docs or tests. I think I’ve seen it homebrewed at least 6 times now.
It’s the smallest possible idea I could see myself getting across the line while on paternity leave. I guess project number #1 is baby boy #2!
Thanks for posting, Loved the graphics and layout. They made for enjoyable reading. However maybe you could add or share the motivation for creating the project? Were their shortcomings of existing job scheduler solutions that you evaluated? Is there an edge case that you have that existing solutions didn't address etc?
Great idea. I was thinking about writing something like this that could be deployed to Azure Functions that could replace their Azure Scheduler, which is pretty awful
Oh yes. Any time I see code that tries to do some kind of scheduling, the first thing I ask is if they have considered using a library someone else has written. Way too many things can subtly go wrong, but new folks tend to think it should be easy, because how hard can it be to work with dates?
Thanks. Really just looking for a new routine/on-demand scheduler to run jobs with a nice interface. There might be a dependency or two, but not a lot. Also the jobs themselves are thousands of lines of code and not going to be substantially changed.
Bravo on your homepage language. A couple years back I looked into creating 'open shift management' scheduling software for caterers. It appears that you've created something similar. Though most OSMs send out a notice of available shifts. It appears you have the employee enter their availability. Either way, your approach is fresh.
Totally agree and that's why I open sourced the scheduler library and not a UI for it :) Schedule UIs should always be created specific to their usage domain otherwise they get out of control pretty quickly. Love PagerDuty by the way, but I'm not even a developer so I'm pretty sure you wouldn't want me mucking around in your code base.
I work on a meta scheduler that solves the problem of periodicity on cron - https://cylc.github.io/
It was created to manage weather forecast model runs. The new version which we are working on will have a simpler web GUI to replace its old PyGTK and Py2.
It handles o ly scheduling, and supports cyclic graphs (contrary to most workflow managers build with DAGs only).
No Python API yet, but coming in future release. So only a custom suite.rc INI style file that supports Jinja2 too.
Oh wow, that's cool. Do you know if servers currently support this? Would this mostly be useful on a network level or do you think it would also be useful for like trying to be more intelligent about scheduling?
I’m building it because I’m tired of being oncall for lousy delay queues, which seem to always be built in house with no docs or tests. I think I’ve seen it homebrewed at least 6 times now.
It’s the smallest possible idea I could see myself getting across the line while on paternity leave. I guess project number #1 is baby boy #2!
reply