> You don't see structural engineers slapping together the first thing that works and patching the building later when parts of it fall down.
That's because if they mess up the first time people can die.
I'm guessing the likelihood of death due to a bug in most web applications is probably much less than that of a bridge :)
Software is great because it's possible to iterate quickly. But ultimately, you have a point. Developers should be willing to fix bugs they've created and/or come across in their projects. We should also try to limit the potential of bugs by releasing small chunks of functional work as often as possible. "Releasing" in this sense can mean to production or just to your qa/test/dev/stage environment. It's just important to have many eyes on the product before it's live.
That's because if they mess up the first time people can die.
I'm guessing the likelihood of death due to a bug in most web applications is probably much less than that of a bridge :)
Software is great because it's possible to iterate quickly. But ultimately, you have a point. Developers should be willing to fix bugs they've created and/or come across in their projects. We should also try to limit the potential of bugs by releasing small chunks of functional work as often as possible. "Releasing" in this sense can mean to production or just to your qa/test/dev/stage environment. It's just important to have many eyes on the product before it's live.