#automapper#dotnet#solidprinciples
429K subscribers • 62 videos on Hallway
Intermediate. Assumes working knowledge.
124K views3 years ago2 recommendations
Software designTools and practiceDesign patternsRefactoring and legacy codePerformance and optimization
Nick Chapsas argues against using AutoMapper in .NET, highlighting performance issues and violations of SOLID design principles.
Use code DOCKER15 and get 15% off the brand new Docker course on Dometrain: dometrain.com/course/from-zero-to-hero-docker Become a Patreon and get source code access: patreon.com/nickchapsas Hello, everybody, I'm Nick, and in this video of LinkedIn Advice Police Department (LAPD) I will take a look at three bad pieces of advice and try to give you good advice based on them. My mappers video: youtube.com/watch?v=U8gSdQN2jWI Workshops: bit.ly/nickworkshops Don't forget to comment, like and subscribe :) Social Media: Follow me on GitHub: bit.ly/ChapsasGitHub Follow me on Twitter: bit.ly/ChapsasTwitter Connect on LinkedIn: bit.ly/ChapsasLinkedIn Keep coding merch: keepcoding.shop #csharp #dotnetWhat people say. Recommended for understanding the architectural and performance drawbacks of using AutoMapper in .NET applications.
u/BlazorPlatein r/dotnet • Recommends
On “Do you think the software architect should have a say in if the team uses AutoMapper or not”
u/mikkolukasin r/dotnet • Mentions
On “Does anyone use explicit operator instead of using AutoMapper?”