|
|
|
|
|
by jerf
5468 days ago
|
|
"The fact is that making things easier doesn't necessarily mean improvement." Untrue, and if you're a programmer you ought to know better. Making something that works the exact same way, only easier, is definitely an improvement. Now it takes less of your finite mental reserves to accomplish a task, and you can now go further in the same amount of time. Making something that abstracts away some things and makes the rest easier is often an improvement, when the advantage of being easier outweighs the loss of control. Or are you still programming in raw machine language? Programmers live in such a rich ecosystem of things that are improvements merely because they are easier that it is easy to take that process for granted without understanding it. How many orders of magnitude less effective would I be in machine language? Certainly more than one, almost certainly more than two (working on a network + manual memory management = security fail). |
|
A simple example, it took months to write a simple browser with a little less features than the browsers available during the Win 9x era. Does it take weeks now? I doubt so.
Ok, to put it more simply, what I meant was improvement in the time required not as in the thing that was produced. Uh, get what I mean?