2 ms·
There are two (related) problems that I've experienced here. 1. Most of what we make (in software) is invisible to the user. So when they see a shiny GUI they
by Jtsummers 6y ago
There are two (related) problems that I've experienced here.
1. Most of what we make (in software) is invisible to the user. So when they see a shiny GUI they think that's it, they don't see the 10 million SLOC underneath it making everything work across dozens or hundreds of servers of all kinds. If you make a change that makes the whole thing more stable or slightly faster, but doesn't impact the presentation, they think you've done nothing but remove, their conception of, a sleep(1000) from the code somewhere.
2. Our code is, hopefully not the entirety of, our design but also our implementation. As we add things we have to change the design because of a realization ("Oh! This is redundant, I could collapse this into a common class or template and then specialize for these 4 cases, I've just removed 40k lines of code and made maintenance a crap ton easier!") or a change in requirements ("The customer needs us to store phone numbers and send reminder calls based on appointments, how do we want to do that?"). In other engineering disciplines you (generally) spend a lot more time on the design before you get to the implementation. You don't build half a bridge while finishing the design for the other half. But our software does seem to come out in that fashion because requirements aren't fixed, or it's hard to delineate between prototype and final product.
These things, combined, account for most of the issues I've had trying to explain schedules and delays to people, or why we had to scrap 10k lines of code ("You wasted three months writing that!").
- geon 6y ago> You don't build half a bridge while finishing the design for the other half. But our software does seem to come out in that fashion because requirements aren't fixed The analogy is flawed, because ”building” the software is the job of the compiler. Programming is all design. And many bridges can be built using the same design, possibly with some parameters adjusted. When the same thing is done with software, it is so trivial to recompile that it doesn’t “count”. So you get fully custom software design compared to routine “compiles” of bridge blueprints.