> The problem with automapper is that it throws the compiler out the window and invites all the bugs that would normally not be there. I've seen projects when

> The problem with automapper is that it throws the compiler out the window and invites all the bugs that would normally not be there. I've seen projects when Automapper was the main reason for the cold startup of an app, which caused terribly slow "write->build->run" developer experience. So it's not only a problem of runtime exception vs compiler errors. Performance also matters. > Mapping code is still your code and should receive the same care as your fancy services. I've also seen project where all mapping code was written by hand and it was required to write unit test for it. It was also not pleasant.