This was a good talk. I liked how he covered a lot of topics and get always got right to the point(s). There are a lot of little tips like these that we could share, but I think he included a good mix of items. Because he covered so many topics the talk never got boring or repetitive. Kudos.

00:00:00 - Introduction and Talk Overview
00:00:30 - Target Audience and Talk Structure
00:01:28 - Goals of the Talk
00:01:50 - Speaker Introduction
00:03:28 - Framing the Discussion: The Challenge of Complexity in Software
00:05:14 - Feature Folders (Organizing Code)
00:09:42 - Treat Warnings as Errors
00:10:43 - Logging Best Practices
00:14:20 - Differentiating Logs, Metrics, and Audits
00:21:40 - Global Authorization via Fallback Policy
00:24:03 - Validation with Fluent Validation
00:28:24 - Remove the Server Header
00:31:11 - Alternative to IOptions for Configuration
00:33:11 - Code Smells: Early Returns and Indentation
00:36:46 - Generic Code Smells: Method/Class Length and Regions
00:38:08 - Modern Solution Files (SLNX)
00:40:09 - HTTP Security Headers
00:42:02 - Build Once, Deploy Many Times (Trunk-Based Development)
00:44:05 - Validate on Build (DI Container)
00:46:56 - Importance of Automated Tests
00:49:29 - Checkov's Gun Applied to Automated Tests
00:52:25 - Central Package Management
00:53:38 - Bonus: Entity Framework SQL Query Logging
00:54:33 - Bonus: CI/CD Pipelines and Confident Green
00:56:14 - Bonus: Feature Toggles
00:56:45 - Bonus: Work in Small Batches
00:57:13 - Real-World Benefits and Key Takeaways
00:58:07 - Conclusion and Contact Information

"Trunk-based Development" - Ahh, how we've come full-circle back to the tried and true methods of the 1990s-2000s.  Glad you brought this up.

thanks! you give me the idea to add the Server header "Kestrel" on my React website :P

Didn't know about the fallback policy feature!

This was awesome... real practical advice from real work experience.

Thank you, some things are more about personal preferences, but the header... I was not aware of this, thank you! This is really a crime MS leave such trap in the code which is about to be deployed. But it is a deeper thing, we can discuss to death if OOP approach is right, or maybe functional, less or more abstractions, closed source, or open source, but IMHO above all the absolutely the most important thing is a mindset. If team/company acts like "under influence" nothing really will save you, using given framework will always be like a war, struggle, it will be a constant source of problems. Sadly, the list of non-trustworthy libraries is getting longer and longer.

Really good talk, thanks!  One thing that would be great is considering approval for your unit tests instead of assertions.  this is something that saved us so many time over the years.

I like fluent validation for some things, more complex scenarios, but if used everywhere it seems like a lot of extra keystrokes

Amazing lecture thank you very much for sharing your knowledge and best practices!

Good presentation Scott, thanks.

Good presentation.  A large subset of these points apply to pretty much all development environments.  Would recommend for all developers.  Senior devs as well, as we could all benefit from having these concenpts re-enforced.

Great Video. Thank you very much.

I think SQL Server System Versioned Temporal Tables is worth mentioning when discussing keeping a journal of table changes for auditing purposes.

This is great content. thank you for sharing.

Super!!!

Curious take on the model+validation living together, being a no-go. I usually keep validations as close to the domain model as possible, to encapsulate invariants and state transitions.

I clicked this video after seeing don't use IOption, I was curious if anything else came😊. It's better to say use IOption in better way. Because we still using IOption the place we changed to handle in better way. thanks for presentation it was so informtive.

A couple of reasons I encountered that stopped us from doing CD all the way to prod all the time:
- sometimes a new feature needs to be tested by another external service and approved in DEV/INT before moving forward to higher environments
- company has a policy of "PRO updates only on Mondays", you have to submit a request ticket with all the details and changes the week before, that has to be approved by a release management team

I went to Oslo for the lutefisk and lefstze. 😅