I must admit I'm a little confused at this (but not downvoting), I think the speed of development is probably equivalent but with the benefit that as the codeba

I must admit I'm a little confused at this (but not downvoting), I think the speed of development is probably equivalent but with the benefit that as the codebase grows you at least have types to make scaling easier but having not tried Django I can't really give a fact-based view. Without knowing what exactly was being implemented it's hard to assess. However I think any halfway decent .NET developer can probably stand up a low-medium complexity MVC app in a couple of weeks. Granted you could go full OO-brain and use all sorts of patterns, service layers, onion architecture etc. to bloat the code. But you don't have to, if it's a quick throwaway you could simply do data access directly in the controllers (even using EF to abstract away any SQL writing). Can you expand some more on what exactly the bloat is that you feel slows .NET development down?