Except you might want different error handling for different error codes. For example, our validation errors return a JSON object as well but with 422.
So treating "get a response" and "get data from a response" separately works out well for us.
There's only a 6 hour different between the East coast and Hawaii. You can't entirely avoid a night shift, so you might as well have them all work from the same location.
If I was making edits more often, I might run into sync conflicts. But I mostly edit on my PC, then might make small edits to recipes while I'm working in the kitchen.
> Being able to hover a line, having the message of the commit which last changed it, and be able to say "ah ok, it was for this" is quite useful.
Honestly, this just sounds like we need better integrations with JIRA into dev tools. I'm not going to rewrite tickets in commits / PRs. That ticket has its own history, linked tickets, acceptance criteria, epics, related bug tickets, etc.
The first is solvable with a PR check. You can do whatever you want with the submodule on your branch, but if you want it to merge to `main`, then your changes to the submodule have to merged to its `main`.
We have a check that makes sure the referenced commits is on `main`, and not older than 10 PRs.
They have to get the books recorded and printed without overproducing and losing money while also not getting a worse deal with a smaller print + miss out on sales. Same thing for merchandise. All of it needs to be warehoused until it's ready for delivery. Plus probably other things I'm unaware of.
A major publisher already has all this infrastructure to take a gamble on new books while paying with current sales. Dragonsteel is still very small.
We don't use it on our Node app because it would be too noisy. Another noisy library was the AWS SDK for .NET. In that case, I actually use a wildcard version range `3.7.*` to always have the latest patch release and cut down on Dependabot noise.
We have it on for everything else (.NET/Nuget, Ruby, Docker, GitHub Actions, Git Submodule). It's great at keeping us up to date with little effort. For major (and some minor) releases, I'll read release notes to see if there's anything to watch out for.
It's especially useful for updating the git repo we use as a submodule in 5 other repos. Submodules were a source of frequent merge conflicts before as different developers updated it in their PRs. Now we pretty much don't think about it, and Dependabot keeps it up to date with our latest database models and shared libraries.
edit: We have it set to weekly for everything but the submodule, which is daily.
But either way, thank you for using noscript only for the counter and not to blank out the entire page! So many websites these days don't load at all without JavaScript.