tag:blogger.com,1999:blog-21332048.post8598767292198419798..comments2023-08-24T09:22:20.836-04:00Comments on Developing Upwards: How To Recognize "Software Development" Is Step OneCalvin Spealmanhttp://www.blogger.com/profile/07161631946662126734noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-21332048.post-14781028379560870512009-07-11T18:20:55.660-04:002009-07-11T18:20:55.660-04:00SwitchBL8: Don't take it so personal. If you a...SwitchBL8: Don't take it so personal. If you are able to spend the time to put the infrastructure in place and you dont need to badger the money men to budget for testing and performance analysis, you're in the right camp and don't apply to what I'm talking about. You're disgruntled attitude about what I wrote is akin to being upset that I say people who talk in movies suck, because you don't talk in movies.Calvin Spealmanhttps://www.blogger.com/profile/07161631946662126734noreply@blogger.comtag:blogger.com,1999:blog-21332048.post-51717187436890024022009-07-11T17:41:05.874-04:002009-07-11T17:41:05.874-04:00What the hell is wrong with xcopy-deployment? It&#...What the hell is wrong with xcopy-deployment? It's simple, so it sucks? And for the same matter, the people that are in an environment that has the luxury of xcopy-deployment are the same people that don't debug?<br /><br />Dude, you're assuming to much. You know what "I assume" means, don't you?<br /><br />And the comparison with cars? Ridiculous. Ever seen the maintenance statistics of Mercedes lately? It's supposed to mean something, that star on the hood, but it doesn't. Not anymore.<br /><br />And to be arbitrary: writing code includes debugging, testing and writing deployment scripts/plans. So the percentage? I'd say more than 80.SwitchBL8https://www.blogger.com/profile/10641235209802387348noreply@blogger.comtag:blogger.com,1999:blog-21332048.post-44759873712102922382009-07-11T13:59:12.191-04:002009-07-11T13:59:12.191-04:00If you are getting at something having to do with ...If you are getting at something having to do with good project config, I think that this sort of thing is still up to the developer or managing developer to set up with the least possible overhead based on previous experience. You should generally not experiement with new development, bug reporting, and release practices when starting a new contract, and if this overhead is as critical todevelop<br />ent as you say it is (I<br />and if it's done correctly then I agree with you) the costs of this overhead should be included in up-front "development costs" and is not critical to be mentioned to the client.<br /><br />Sometimes when you get into the nitpicky argument or discussions that you are mentioning it's because you aren't explaining it well enough and/or are pushing a technology that you aren't as familiar with a you think. This is a dance that I think occurs in these situations no matter what field you are in.Not Specifiedhttps://www.blogger.com/profile/06281564829886653770noreply@blogger.com