I've just used Spectre.Console in my project to parse arguments and present the progress of a long-running async operation instead of printing "Please wait...". It was the first time I've used it and just loved how easy and well-thought the API is. Matched it with IProgress<T> interface and the experience was delightful. I wanted to learn more so ended up here. Thank you Patrik!

Flavor of the month shit

People using Microsoft are idiots

the moment I saw tau=2.0*pi I knew this would be legit <3

Serious skills, love a topic about coding for oneself. ❤️👍

Excellent watch, fact rich and engagingly presented. Thanks Richard!

22:30 - It should be obvious - Darkly is super easy to implement in code and super easy to use, not to mention the other stuff.

Excellent presentation. I will be sharing this with my team.

42:17 Love the suggestions features AND the suggestion to use this. My preference is to provide an example but also to link to the relevant documentation or good blog article This turns the review comment into targeted learning.

21:33 Nits should be fixed by the PR author to help reduce the later occurance rate of similar nits. Of course, automate first :) Great talk, thanks for sharing. Packed with useful ideas.

Amazing talk, Blazor is amazing! Thanks for sharing.

Does anyone know what happened to this book? was it abandoned in favour of making it a presentation?

This is the most sensible review of. CQRS(and programming in general) available. Thank you Oskar! Looking forward to exploring your website.

awesome, is the CLI slides code available online? so cool

Thanks Oskar for cool talks. Do you have those example in github what to take a look out of corner of my eyes?

Git workflow, when using short-lived branches and rebases, isn't an issue. Trunk-based development is handy at the start of a project when you both need to e.g. extend the domain model or you both need to work on the same modules (records/classes) I don't like feature toggles as it instantly creates technical debt in both code and unit/integration tests and also it increases complexity. I don't say I hate trunk-based but saying that it is a silver bullet when using git, and git workflow is bad is just ridiculous

Unit tests are cancer.

at 9:31 min cherrypicking the Bugfix into the Hotfixbranch. doesn’t this potentially cause new Bugs and introduces unreleased features from ongoing trunk dev. ?? or does cherrypick refer only to that particular bugfix without other trunk improvements ?

Love this talk. So far the best I have watched here. I used to use git flow(the very first version). Caused lots of problems. One of the big problem is the long lived branches. It’s a nightmare. Finally, we ditched that. Our way is similar to trunk based development model with minor differences, it’s been working great.

another great tutorial that ends in the send method cannot be called if the connection is not active. thanks, gerald.

I love this guys humor - thanks for the great talk!

When we are committing in main trunk, is it necessary to create tags for every commit. When we are going for a release, shall we cut a branch out of it or just tag??

this guy is Jimmy Bogard on steroids

Can someone explain how kzbin.info/www/bejne/nn2UgI2cnNSNfc0 is not a feature branch?

Wow, what a wonderful talk.

Nice video shot, keep it up, thanks for sharing it with us :)

Nice talk. Didn't expect to see actual Func<_>s in a csharp talk, that's like the most overlooked ways to abstract out implementation details! I feel like this is what is lacking in most of the talks: simplicity.

I have my own in C++, but if I knew yours , I ll not make mein, waste too much time . NOW I GOING TO MAKE IT FOR C AND ASM.

dude, use sixel to show your picture

Dotnet agggg

Are the slides available somewhere? It would help a lot, since the camera doesn’t focus in on every slide or so often.

Also, feature toggles makes code unclear at all. It breaks a lot of common programming rules like don't create zombie code or zombie comments. What will happen if 3-5 developers left the company and their features are in the intermediate, non-working state? Nobody can understand what they were trying to do and what was the idea. Or the implementation way could be wrong. And all this code we have in master branch! Each reader of this branch should spend time on trying to understand fired developers' thoughts until he comes to the idea that it was a wrong implementation of smth.

Please, don't share this shit (trunk based cherry picks from 10:00). It's not only doesn't work in real life as you described, it makes a nightmare which ruins all merge, deploy and development life cycles with unpredictable results with unstable master branch. Cherry picking is a took which has to be hidden as far as possible from real developer. It ruins history, it forces you to re-resolve conflicts, it can overwrite all the work. All you need here is an every day rebase of long-refactoring branch onto your master branch, or better not to do a long refactoring branches at all, while you develop features. Because it's not a refactoring. It's already a payment of the technical and architecture debts. It's not the refactoring - a thing developer must do each time he adds a new feature or fixes a bug (M. Fowler). In case of the debt payment and serious change of architecture you must stop development of the features. So, the right tools should be selected for the right issues. And trunk based + cherry picking to allow long technical debt payment is not the right combination.

How to create a presentation like this one?

Amazing, he make console to work almost as worpad.

Awesome, Thanks.

great talk

Gerald Versluis as always valuable content! Thanks !! <3

I really wish I'd seen this earlier. We are still using feature branches and it's not working for us. I immediately shared this with my team and we are already in the process of adapting our processes.

Its always possible to do trunk based changes, even when using feature branched for other stuff. So that negates any argument in favor of CI, let alone CD. Really I hate these videos made by amateurs, trying to solve problems that already have working solutions. Just because they stumbled and messed up in obvious ways before using one method, does not mean another is somehow superior. I only see downsides to CI, let alone CD, not even customers want it (they hate constant change). It simply cannot work for most kinds of projects, every showcase is about an existing product undergoing insignificant changes. Not because they are broken up in small pieces, but because they really are that insignificant.

Dear Gerald, could you, please make a distinct solution or link a video if exists only(!) about .NET MAUI Blazor with SignalR? For me it is not clear how should I exactly create a project in that case, that is not the normal Blazor web assembly solution or Maui with SignalR.

I only know trunk based development.

very helpful

You said a benefit of Trunk based development is that it "encourages refactoring" but never explained how that could be so. From everything I've seen and experienced, smaller and quicker prs to the main branch do exactly the opposite. All in all, though, I found this talk very informative.

Great presentation *ThumbsUp

thank you for a single place overview

Man, that was a rough crowd. Thanks for the great presentation

Thx Patrik for presentation. It looks amazing :)

19:00 "and the descript version of Java - JavaScript", no despite the name JavaScript the language has nothing to do with Java at all except the name.

Wouldn't it possible to validate the SKU in the constructor for the record? Records can have constructors.