Reply to thread

Message

<blockquote data-quote="jimmifett" data-source="post: 5587602" data-attributes="member: 55006"><p>Web technologies are a great thing, I write them all day long, and yes, they are relatively quicker to design and implement for, however, finding developers that know how to actually use them the right way is very difficult, needing to know to avoid the ruby-tard evangelists to the silverlight devs contemplating what to do now that MS is dumping silverlight and wpf (thanks for choosing a craptastic platform wotc). With such a customer facing product such as CB, 'minor' changes have big impact, both when they work correctly, and when they fall flat on thier faces (monster builder, looking at you). Since this is a big product, with lots of hooks into other products, you're going to have milestones, feature cutoff points, and other dates that will then have periods of testing following them before the code ever makes it to the user. When you're already a company known for failing to meet expectations of deliverables of digital products, do you keep piecemealing together small changes, or do you bundle a bunch of tested changes together and roll them at once. It's not just the devs being able to do something, it's the marketing and other 'suits' being able to say &quot;we listened, and worked hard, and now have x, y, and z ready&quot;, or to time feature updates with specifc events.</p></blockquote><p></p>

[QUOTE="jimmifett, post: 5587602, member: 55006"] Web technologies are a great thing, I write them all day long, and yes, they are relatively quicker to design and implement for, however, finding developers that know how to actually use them the right way is very difficult, needing to know to avoid the ruby-tard evangelists to the silverlight devs contemplating what to do now that MS is dumping silverlight and wpf (thanks for choosing a craptastic platform wotc). With such a customer facing product such as CB, 'minor' changes have big impact, both when they work correctly, and when they fall flat on thier faces (monster builder, looking at you). Since this is a big product, with lots of hooks into other products, you're going to have milestones, feature cutoff points, and other dates that will then have periods of testing following them before the code ever makes it to the user. When you're already a company known for failing to meet expectations of deliverables of digital products, do you keep piecemealing together small changes, or do you bundle a bunch of tested changes together and roll them at once. It's not just the devs being able to do something, it's the marketing and other 'suits' being able to say "we listened, and worked hard, and now have x, y, and z ready", or to time feature updates with specifc events. [/QUOTE]

Verification