Dave Glick@daveaglick@mastodon.socialmastodon.social

I guess I’m a #gamedeveloper now. Thanks to #godotengine and #jetbrainsrider, I made my very first pong game.

Built a very simple Enemy AI, sound effects, and scorekeeping. I also did all the graphics myself (except for the #JetBrains Rider logo).

The game logic is written in #csharp using #dotnet.

I can't begin to explain how frustrating it is when Azure _knows_ there's an outage but won't update the status page to let everyone know so you have to spelunk through random Twitter threads and other unofficial signals.

While we're on the subject of buggy stuff, looks like my laptop has suddenly forgotten how to Bluetooth. Today is going great!

Sometimes I feel bad when I discover a new bug in my own apps, but then I try to file a claim with CareFirst or book a hotel with Marriott and figure if they can build horrible buggy software, why can't I

I've said this before in the other place. But thanks @patriksvensson for the Spectre CLI library! I added it to something yesterday and it makes structuring console apps just a pleasure. #dotnet

@swimburger If you wanted to get fancy, I’d do option 1 as the de facto and then offer an optional class-based option on top like option 3, something like:

```
public abstract class PartialTranscriptHandler
: IDisposable
{
public PartialTranscriptHandler(Transcriber transcriber)
{
transcriber.OnPartialTranscript.Subscribe(HandleAsync);
}

public abstract async Task HandleAsync(PartialTranscript transcript);

// Unsubscribe on dispose
}
```

Boeing are speed running the Ship of Theseus paradox

Please, use #AI to generate tons of #content that you otherwise couldn't.

But for the love of all that is holy, pay attention to what you are putting out. Read the output. If it doesn't say exactly what you would say, edit it! Make changes. Regenerate. Go through the process of making it good.

I truly don't think people hate AI content. They hate *lazy* content.

After recent discussions about C# events and their drawbacks, prototyped a couple of alternative event APIs for a Speech-To-Text library that I'm working on.

Please let me know which one you prefer, or better alternatives.

#dotnet #csharp
https://gist.github.com/Swimburger/6f81ccbab075422c0e4f73f6d5ac99da

What the hell happened with Rebel Moon? I don’t really care about Snyder one way or another, and I’m generally a pretty easy to please movie watcher. I think I’ve given like three things a thumbs down. But this is atrocious. Like, it’s literally unbelievable. The acting is bad. The plot is bad. The cinematography and effects are bad (!?). The whole thing seems like a student film. What did Netflix spend all that money on lol? The whole thing is one long cutscene from a mediocre 90s video game.

I published an addin for the excellent #statiq site generator to add different alerts to a site

https://github.com/swissgrc/Statiq.Alerts

The params collections feature was merged into main for dotnet/roslyn last night: https://github.com/dotnet/roslyn/pull/72511

This will allow things like `void M(params ReadOnlySpan<int> values)`, as well as params on other collection like types (like IEnumerable<T>) in general.

Something that hasn’t hit me until this week is how much I miss the “universal water cooler” that was the Twitter .NET OSS community. Since Twitter became untenable to most (including me) folks have scattered to a bunch of different places, and some have left social networks altogether. We’ve lost something. At Summit it provided a virtual space alongside the physical one and helped coordinate and tie everyone together. Not sure I appreciated how much that contributed to the experience before.

Added a small example of how to use Wisp over at the GitHub repository: https://github.com/patriksvensson/wisp

Cross-platform .NET decompiler that is using @avaloniaui #dotnet https://github.com/codemerx/CodemerxDecompile

I'm a big fan of unit testing, and I've done some classic UI testing with a JS-based test runner, etc. But I'm enjoying playing with a new kind of test where I spin up a front-end *and* back-end server inside the test (one API server per test!), injecting test services like a fake database and bypass auth, and then use Playwright for orchestrating unit-style UI tests. Not sure what to call this style of testing though. I've been leaning towards "UI unit tests" but that's clunky. Suggestions?