4 ms·
Alternatively, many c# programmers use the default stack because they don't treat their client/employer as their personal playing field to try out the latest bu
by adamconroy 13y ago
Alternatively, many c# programmers use the default stack because they don't treat their client/employer as their personal playing field to try out the latest buzz.
- PommeDeTerre 13y agoIt wasn't that long ago that ASP.NET MVC, EF, and WCF, for example, were new technologies. How were the early adopters of those unproven technologies not "treating their client/employer as their personal playing field to try out the latest buzz"?
- spamizbad 13y agoThere are actually many Microsoft shops that still consider the stuff you listed as too new/unproven. In general, .NET shops are more risk adverse than "open source" shops. Some reasons are cultural, some are business. I think Microsoft is trying to change this as they're clearly growing tired of their own developer base being reluctant to adopt their own technologies.
- adamconroy 13y agoThe point is that as an architect you can be very confident that those frameworks will be solid, well maintained and documented and quite importantly well integrated with everything else in the default stack now and in the future. You can also be confident that in the future you will be able to find developers with experience using the default stack. I could bore you with quite a few personal anecdotes that back up my opinions. Of course there are going to be exceptions to this but as a general rule, taking into account all dimensions of the decision, the default stack is the rational choice.
- adamconroy 13y agoCase closed (pun intended) : http://www.twilio.com/blog/2013/07/billing-incident-post-mortem.html http://www.twilio.com/blog/2013/07/billing-incident-post-mor...