107 karma · joined March 13, 2014
https://web.archive.org/web/20161003115800/https://blog.mozi...
#!/usr/bin/dotnet run
https://devblogs.microsoft.com/dotnet/announcing-dotnet-run-...https://andrewlock.net/exploring-dotnet-10-preview-features-...
So treating "get a response" and "get data from a response" separately works out well for us.
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.
But I've been using the website for over a year and don't feel like I'm missing out.
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.
Every developer can control how those tabs are rendered to their preference.
I'd rather use something like https://crontab.guru/ to verify my syntax, thus I have it bookmarked for the 1-2 times a year it comes up.
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 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.
The way other projects can access these services is by using the project's helper to register them all in the DI container by their interface. That way I can be sure no one is directly using the classes and make breaking changes to the constructors (like swapping loggers or api clients), but still access them from tests.