4 ms·

Iterating without improvement is just making a different wheel, if you know what I mean. It gives the impression of progress without actually making progress.

Iterating without improvement is just making a different wheel, if you know what I mean. It gives the impression of progress without actually making progress. This is also why I got tired being a programmer after doing it for many years. First version is always super nice. Then you add features, and refactor. Doing this is slower and slower the bigger your software gets. At the end, your software is filled with complexity and you want to rewrite it from scratch. So you do, and you are back with a nice version. Until again, more features need to be added. Now, does this example above mean the developer is innovating? Are we getting somewhere? No. At the end, his product is going to be replaced by other products that does the job better - until they also meet the same fate.

tomnipotent 8y ago
> No. At the end, his product is going to be replaced by other products that does the job better - until they also meet the same fate. Yes, this is the very definition of innovation. Just because what you're working on is going to be replaced, doesn't mean it's not innovative. Of course it's going to be replaced, that's the whole purpose. Hopefully we get better and smarter along the way. Sometimes something that seems trivial to you as an engineer is mind blowing to a layman with domain expertise that goes on to leverage your software to help make the company more money in ways no one was expecting (or maybe save money). In other words, innovating.