Around 2014 I was in school and working at a bar where schedules were done by hand each week. I figured I could easily build a little web app to handle this.
The rules were impossible to encode because they didn't really exist. Building the schedule by hand allowed the manager to draw on their knowledge of everything from employee work ethic and personality to expected rushes (e.g. hockey nights) and reservations.
Are you arguing that it’s not possible to articulate all the rules? It seems as though you’ve done a good job highlighting a good number of constraints and edge cases.
Further iteration and feedback when implicit/undocumented rules are violated will get you closer. It’s not like there’s an infinite source of rules, and many of these are just general knowledge that does exist online. You can eventually get there.
If we look at traditional project roles, it's the responsibility of the Programmer to articulate the Business Logic in a way that can be interpreted by a computer (i.e. write the rules in code, using their chosen programming language).
It's the responsibility of a Business Analyst to study a work process, and articulate the rules which govern the process.
With vibe-coding, the agent is usually playing the role of a Programmer. Are they also playing the role of a Business Analyst?
If we look at iterative development, that's usually the responsibility of a Product Owner.
With agentic development, we expect AI to perform the role of developer. In this example, is the bar manager able to perform the role of BA or PO? Is the agent able to accommodate and fill in the blanks that a BA or PO would normally fill?
There may also be human edge-cases, such as "Don't schedule Dave and Brian together, they don't get on".
Agentic AI doesn't have the nuance for all these factors. Many situations (such as a bar manager or restaurant manager with a small venue) may be better off with simply having a human plan the schedule on paper.
Maps have a lengthy history of including "Trap streets" to identify copies.
Changing the value of the least-significant decimal place for a couple of points in a polygon is unlikely to significantly change the shape or reduce the accuracy so significantly that it reduces the value of the data.
The national USA average is 2.3 – 2.4 officers per 1,000 population (which is roughly in line with the UK, a little higher than Canada, a little less than the Europe average.
This regional average works out at 7.8 officers per 1,000 (including the chief, making 6 officers per 772 population).
On the other hand, small numbers make a poor comparison for ratios. To ensure 24/7 coverage, you might expect a higher ratio.
Which isn't to say there isn't an issue, but the maths don't automatically illustrate an issue.
The "prank" is that the prankster plays (a copy of) the Apple Pay chime which signals a contactless card payment, and pretends that he's taken money from the employee via a contactless payment hack.
- Shifts should be at least 4 hours
- Shifts shouldn't be more than 8 hours
- Except on festival days, where shifts can be 12 hours
- Someone who is scheduled for an evening shift shouldn't be scheduled for the morning shift the next day
- Some staff members don't work on religious holidays
- Some staff members can't work mornings / evenings / weekends
- Some days pay extra, so schedules should be reserved for preferred/long-term/permanent staff members
- Some shifts may end early if there isn't enough demand
reply