4 ms·
So much so that I don't think "refactoring" should even be a concept - that's what coding is. Every feature, bug fix or change should take into account the new
by thinkloop 9y ago
So much so that I don't think "refactoring" should even be a concept - that's what coding is. Every feature, bug fix or change should take into account the new relationships and structure of the model. Leaving refactoring for later is ignoring the fundamental required task of coding.
- iovrthoughtthis 9y agoEh, refactoring is distinct from feature developement, prototyping and testing. They are different modes of thought.
- ataturk 9y agoThe problem is that 99.9% of MBA types don't understand what you just said. Worse, they will probably NEVER understand it. In their world, your code is part of an investment. The products in their world, be they software, or whatever, have a cost and that cost is incurred to generate revenue for the company. They don't view software as a living organism, they see it as a cost with a fixed $ attached to it. Maintenance is not a capital expense. If you begin to understand the world in their terms, you realize why our world is so fucked up. You can also maybe approach them with solutions (at times). The other problem with MBA types is that it's all about them and their personal arc and career. They routinely take full credit for any of your success while shifting blame at all times to you. This is how the world is. This is why being a software engineer is an exercise in cognitive dissonance.