3 ms·

Thank you for this - it's a great example of how to do it properly and on how to choose the right tools for the job. Unfortunately the organisation I currently

by bwarp 15y ago

Thank you for this - it's a great example of how to do it properly and on how to choose the right tools for the job. Unfortunately the organisation I currently work for managed to screw it royally. Firstly, we mandated .Net as the technology paltform (which is the most unscriptable and obtuse platform ever in the history of time). Secondly, we made the deployment too complicated (one deployment is 30+ VMs and about 20 SQL server databases!). Thirdly, we wrote our own tooling entirely (there is a lot of Not Invented Here in the .Net space). Fourthly, we let management in on the process (who don't know arse from elbow).

vyrotek 15y ago
Hey now. There's probably a bit more blame on .Net than there needs to be :) I agree though, there seems to be quite a few wannabe .Net architects who design unmaintainable behemoth deployments just because they can. In fact I'm helping one company completely replace their old system because all the developers who built it left in a hurry and no one now knows how to run the custom deployment. But that's not the language's fault. There really are some good companies out there doing awesome things with .Net