notnotmike

Around two years ago I was on a really small team, just two or three developers, and the other developer decided they wanted us to use Rider. Because I didn't have a preference, I used Rider and rather enjoyed it. However, that developer has since moved teams and now it is just me (for the time being).

So I was considering moving back to Visual Studio or even switching to Visual Studio Code, but I wanted to see some arguments against this.

Here is my list so far, but it's probably out of date since I haven't used Visual Studio in a long time.

Pros of Rider:

• Much faster than using ReSharper
• Less sharp interface with a better font
• I'm used to it at this point
• I have a Nyan cat loading bar which is kind of fun

Cons of Rider:

• Enterprise license is expensive (probably)
• New versions of C# aren't immediately supported
• Refactorings are becoming less necessary with the rise of AI assistants
• Don't really like their source control manager

Wanted to hear what other users think. What keeps you using Rider?

Oh and banned for rule 1 if you disagree

The Praying to the Gods achievement requires you to kill the fanatic 10 times "without drinking any potion which restores prayer" and without leaving the wilderness. Simple solution is to pray on the nearby Chaos Altar or to take the obelisk down to a less busy altar near Ferox.

However, do you think the spaghetti code takes into account Stat Restore Pot Share or butterflies? Could you cheese this one with a friend?

I would recommend everyone try this. Just sit down, bend your knees, throw a blanket over, and show them the entrance. Just be warned they will not leave unless you make them

My favorite way to develop applications is microservices, or at least smaller services that can separate concerns a little bit. In our current application, there is an API we've created with an OAS document and an auto-generated .NET SDK based on the document. We then have a web console that makes calls to the backend API using the SDK and, ideally, customers would also use the SDK.

So my question to everyone is: what is the best "flow" to develop a NuGet package?

Currently, we have pipelines which publish the NuGet package of the SDK to our internal NuGet repository on every commit within a merge request. We have a manually incrementing semver with an additional build number tacked on (for example 1.2.3+abc123).

Now this works pretty well, but we often run into problems where a tester's NuGet doesn't pull down the latest version based on the build number if it detects it has the proper semver number. For example, if we create 1.2.3+abc456 NuGet won't pull down this version as long as it has the original 1.2.3+abc123 in its .nuget/packages directory. Testers and developers have to manually delete the version from the packages directory and do a fresh restore.

So, is there a better way to do build numbers? Or should I be deleting the NuGet package from the private repository every time (doesn't sound ideal...)?

The other part of this question is what is the best way to develop and test NuGet packages locally?

My current flow is a PowerShell script which will create the new .nupkg file, publish it to a local/filesystem NuGet directory with some random semver number (i.e., 9.9.9), update the .csproj with the version (temporarily), and then do a fresh dotnet restore on the target project. However, this can be cumbersome and feels like something that should be built into the dotnet command. Am I missing something, or is this really the best way to develop locally?

You can add Ecosia as a search engine to Firefox Android by going to Settings - Default Search Engine - Add then entering the following:

• Name - Ecosia
• Search URL - https://ecosia.org/search?q=%s
• Complete URL - https://ac.ecosia.org/autocomplete?q=%s&type=list

This will also allow you to use the Firefox Search widget on your home screen to search Ecosia.

I tried using the Addon to no avail, so I had to manually add the search myself.

Thanks for creating the community! I had forgotten to use Ecosia on Android for a while now. So much missed opportunity

https://d2l.ai/

The book was written originally by a group of Amazon engineers and strives to be a resource on getting started with deep learning.

Even if you have no interest in developing models, you should be aware of how they work under the hood.

For the AI enthusiasts, it makes them more interesting. For the AI doomists, it makes them less scary.

The book being online and an easy to remember URI makes this a great reference book that you can access from any device with an internet connection. You could read the whole thing with cURL if you were feeling wacky. You can also clone the repo and host it locally if you want to "own" a copy.

They are releasing a physical book in English this week, so for you collectors out there can have something for your shelves.

Get good loot from a toolbox in Fallout? Gotta check them all now