I work in a small team, we have ~30 active clients and other ~100 or so that are low maintenance or dormant.
We don't have an on-call rotation but I desperately want one. Because if no one is on-call - then all of us are on-call. Any one of us could be called at any time if one of our larger commerce projects falls over.
To me on-call is a necessary burden that means when I'm not on duty I am completely free to ignore my phone.
I'll certainly feel more positive about helping outside of the 9-5. I do like to be helpful, but perhaps that'll wear off like some kind of honeymoon period, juxtaposed to my current situation.
I'm always looking for more positives in such a system because I want it to work. Tuesday to Tuesday sounds great. Other comments here highlight the difference between critical fixes and patch it laters. Any other insights are welcome.
I wouldn't call those shenanigans fun, just frustrating. I know exactly the roads you're referring to. We drove that pass between SA and Vic a good 10 times in just the past 2 years and Google just couldn't figure out that it took far longer by those roads because you can't safely go at speed. There's just too many blind hills.
There's something increasingly messed up with Google's algorithm lately and there's little control. We've recently just been going up and down the east coast and it's idea of "eco" or "short" is just wild. There was an unsealed 15% grade climb over a freaking mountain, it just refused to think of a better way (the motorway that went around it).
I'd be less upset if there was more control over the options. Like a "prefer motorways" or "less turns" or "less hills". Even a "I'm towing" option.
I know it has that data to do it, why not let us use it? Hell I might even pay for it.
I remember learning A* at uni while at the same time experiencing it's quirks on our shared minecraft server.
The server was really chugging and so I ran a trace on it. I found the zombies were stuck in a loop trying to find their way into a village that we had completely secured with a large fence. Being a naive implementation (at the time) it meant they never gave up.
I recall there being a bug report with a good amount of detail about how they were going about fixing it.
My old boss used to say: "Be a chameleon. I don't want to know that I didn't write this."