I find that when you read a script, or rewrite something, or look at something that's been gone over, you can tell, like rings on a tree, by how bad it is, how long it's been in development.
Sentiment: NEGATIVE
The longer you work on something, the more you don't really want to know what the world is going to tell you.
Yet we still see continuous reports of bugs.
About every year or two, there is a moment of truth where there's some new development in the marketplace, some new technology, some sort of existential crisis. You just have to be vigilant about looking out for those moments.
You can theorize as much as you want about what you think you're seeing, but until you get out there and dig, you can't tell exactly what it is.
I believe one can gauge a book's impact only after about 10 years.
The problem is, in software design, often the consequences of your decisions don't become apparent for years.
I guess we guess our way through life. How many times do we really know for sure?
When I write and develop things myself, I might work for a while on a script from a book, and then I go back and read the book and go back into it to see if I lost something: is there something there?
When we assess the impact of technological changes, we tend to downplay things that happened a while ago.
I only know from my own personal experience, and I personally feel that there's a cyclical nature to things, so you don't want to start making generalizations about how bad things have become in comparison to the old days.