3 ms·
>> Alpha: No. Since we have little time, it is important that you complete one powerpoint screen at a time and NOT go back to it. When it is done it is DONE. I
by YeGoblynQueenne 6y ago
>> Alpha: No. Since we have little time, it is important that you complete one powerpoint screen at a time and NOT go back to it. When it is done it is DONE. I absolutely do not want to hear that you are rewriting code that has already been completed.
This reminded me of something an acquaintance had once said, about "the least productive workers", by which they meant programmers. It seems this is a common theme among non-technical co-workers at tech companies. Basically, there is a sense that programmers somehow overcomplicate things and that everything would go so much more smoothly if only programmers learned to do the simple thing that everyone else can see is so easy to do. Common sense, innit.
The same spirit is behind requests to do something "simple" that "doesn't need much work". "It's just a few lines in SQL, you can do it real quick". Of course, it never is. But if you say, "yeah, it's easy, I'll do it" (because you haven't learned yet) it will take a lot of work, you will take much more than a little time and they will be displeased with you because you're "taking so long for something that is so easy".
- ownagefool 6y agoActually, it is that easy. Then you do it again. Then again. Then some more. Suddenly it's not that easy anymore.
- cryptonector 6y agoAbstractions leak, bad interactions occur, you have to refactor, or work around bugs or -worse- design flags in various interfaces, and now the simple thing ain't.
- larrywright 6y agoI once sat in a meeting where a high up person was giving us requirements for a new feature she wanted to add to our application. It was adding a button to the screen, and when the user clicked the button it would initiate some complex logic and actions that would be invisible to the user. When we gave her the estimate for the change, she went nuts. She couldn’t understand why it was going to take so long and cost so much. No matter how I tried to explain it to her, all she said over and over was “It’s just a button!”.
- _ZeD_ 6y ago"so, you want just a button? or a button that works?"
- Jtsummers 6y agoThere 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.