I Built a Project-Based Job Scheduler for Developers

Many development projects eventually accumulate scripts that need to run for a long time or run repeatedly. Things like: data processing pipelines machine learning training jobs automation scripts maintenance tasks build or deployment utilities In practice, these are often managed with a mix of cron jobs, shell scripts, and long-running terminal sessions. It works, but over time it becomes difficult to answer simple questions: What jobs are currently running? What failed recently? Where can I see logs? Which tasks belong to which project? I kept running into this problem, so I built a tool called Husky. The Idea: Project-Based Scheduling Most scheduling tools are system-centric. For example, cron schedules tasks at the system level, which means jobs from different projects get mixed together. But in reality, developers usually think about tasks in terms of projects, not systems. So Husky takes a different approach: project-based scheduling. Each project defines its own tasks, and Husky