5 ms·

I worked in software development within companies for 20+ years. The "why does it take so long" conversation has come up a lot. So on one hand, I see the argum

I worked in software development within companies for 20+ years. The "why does it take so long" conversation has come up a lot. So on one hand, I see the argument. Simply opening unknown code, and making a change no matter how small, is a risky game. You need to research the impacts, test, and walk slowly through a deployment you haven'y done in ages. I totally get that. But I also see the other side. Why DOES it take 8 hours to do a simple one-line code change? That's ridiculous. Somehow, we've developed these fragile systems. We've trapped ourselves in processes that add 7 hours to any change we make, no matter how small. The status quo does not need to remain. It should be easier to make small changes. It should be cheaper to respond to simple requests. The client is actually right to question us when they just want an email to appear a day earlier and it costs them $1500.

bobblywobbles 7y ago
Our needs are complex, and constantly changing. If our needs weren't complex, it would be easier to make a change.
rafiki6 7y ago
I'm not sure what companies you've worked with, but the answers to your questions are very easy and come with experience. There's a universe of testable things. You'll never have 100% coverage (this is a software development law). Even if you were to do everything right, and build incredible automated deployment and testing systems, at best you'll end up reducing but never entirely eliminating fragility. To even get to that level of perfection would require a tremendous amount of overhead and time that most enterprises don't want to invest in the systems they build. It's akin to trying to constantly remodel/add additions to a building. You may decide that you want new floors, but when you tear up the carpet you realize there's tons of water damage that was being covered.
notatoad 7y ago
>But I also see the other side. Why DOES it take 8 hours to do a simple one-line code change? That's ridiculous. you might be right, but if you're not in a position to help make it take less time, that's not a helpful discussion to have. the reality is that it takes that long, and complaining doesn't make it faster. The procedures that take time exist for a reason, and i'm sure in every organization there are opportunities to make the process faster. But when somebody who wants a change says "why does it take that long", they aren't looking for helpful ways to improve the process, they're looking for an exception to the process be made so their specific change gets out faster.
zoomablemind 7y ago
What's crucial here is that someone previously set the expectation of "one-line change" Maybe a savvy client, maybe a happy dev. Most likely this situation happened not for the first time.
bo1024 7y ago
Very much agree -- this is a good chance to step back and ask how software practices can improve. It feels like we are a long way from optimal.

bobblywobbles 7y ago

Our needs are complex, and constantly changing. If our needs weren't complex, it would be easier to make a change.

rafiki6 7y ago

I'm not sure what companies you've worked with, but the answers to your questions are very easy and come with experience. There's a universe of testable things. You'll never have 100% coverage (this is a software development law). Even if you were to do everything right, and build incredible automated deployment and testing systems, at best you'll end up reducing but never entirely eliminating fragility. To even get to that level of perfection would require a tremendous amount of overhead and time that most enterprises don't want to invest in the systems they build. It's akin to trying to constantly remodel/add additions to a building. You may decide that you want new floors, but when you tear up the carpet you realize there's tons of water damage that was being covered.

notatoad 7y ago

>But I also see the other side. Why DOES it take 8 hours to do a simple one-line code change? That's ridiculous. you might be right, but if you're not in a position to help make it take less time, that's not a helpful discussion to have. the reality is that it takes that long, and complaining doesn't make it faster. The procedures that take time exist for a reason, and i'm sure in every organization there are opportunities to make the process faster. But when somebody who wants a change says "why does it take that long", they aren't looking for helpful ways to improve the process, they're looking for an exception to the process be made so their specific change gets out faster.

zoomablemind 7y ago

What's crucial here is that someone previously set the expectation of "one-line change" Maybe a savvy client, maybe a happy dev. Most likely this situation happened not for the first time.

bo1024 7y ago

Very much agree -- this is a good chance to step back and ask how software practices can improve. It feels like we are a long way from optimal.