Whether you're a programmer or a seamstress, it's all about new techniques, simplifying old techniques, and consolidating steps. Making things go faster - but not worse.
Sentiment: POSITIVE
Experience has taught me that you have to improve all the time-little bit by little bit-and not keeping starting everything from new.
Unless you're doing a feature piece, which is going to be longer, and you have more time to get into stuff.
Progress is more of a challenge for the cynic but also more important and urgent, since for the optimist things aren't that bad and are bound to get better anyway.
Architecture is changing faster than some other professions.
Practice quality, and you get better at quality. But quality takes time, so by working solely on quality, you end up losing something else that's important - speed.
I have a great respect for incremental improvement, and I've done that sort of thing in my life, but I've always been attracted to the more revolutionary changes. I don't know why. Because they're harder. They're much more stressful emotionally. And you usually go through a period where everybody tells you that you've completely failed.
It's a big, big advantage because understanding what changes we might make takes time and it takes time to work out settings and to understand everything about the new machine.
But part of the enjoyment I take in it is finding the most efficient way to do it, which doesn't mean the corrections aren't made. I like to have a feeling of the whole task before I start, even if it changes.
I have to be an optimist and say that it might get better.
Here's a very simple, common sense idea - if you practice something more, you get better at it; if you can't complete everything you need to do, take more time.
No opposing quotes found.