3 ms·
I think your solution is the mishmash of products (to paraphrase) that the author of the article describes. It's absolutely possible to do this, and do it well
by notJim 16y ago
I think your solution is the mishmash of products (to paraphrase) that the author of the article describes.
It's absolutely possible to do this, and do it well (the company I worked for previously did it for years before finally moving to capistrano), but the point is, that means every dev team in every company is spending precious time figuring out how to do this, writing the code, testing it, debugging it etc. When the developer who wrote it gets hit by a bus, someone has to go through his/her code and learn it so that it can be maintained.
The alternative would be to have a standardized tool (like capistrano) that is commonly used.
- MartinCron 16y agoI guess that after trying to use "this will do everything for everyone" solutions (exhibit A: TFS). I am convinced that the time cobbling together a mishmash is less than the time spent fighting the backwards assumptions that the all-in-one solutions require.
- notJim 16y agoThat's kind of like saying, "Well, I tried out visual basic, but it sucked, so I decided to cobble together my own language." Pointing to a specific poor implementation of an idea does not invalidate the idea itself.
- MartinCron 16y agoThere is a huge difference between writing your own language and writing a 4 line PowerShell script. Really, the only gap I had to fill between the high quality parts that I'm already using (nUnit, TeamCity, etc.) was a tiny script to copy files + reconfigure IIS