3 ms·
I've seen this happen so many times, it feels like the norm. I guess it's inevitable though, it's more interesting to work on something "new" and "cool" than ad
by jamesu 12y ago
I've seen this happen so many times, it feels like the norm. I guess it's inevitable though, it's more interesting to work on something "new" and "cool" than adjust your mindset to year old design decisions.
Would be interesting to know if there is a relationship between years of experience in programming and how likely you are going to inject the latest "cool" design pattern / framework into code. Personally I have become far more cautious about this stuff. I'd rather adapt what is already present than subject anyone else to an abstract monstrosity I just cooked up after reading the latest hacker news post on the latest hype.
- acveilleux 12y agoI think it's more a matter of as programmer mature/learn, they overly disparage old code and idioms. It's not the new orthodoxy... I've seen in with RPC calls (hand-coded HTTP -> Hessian -> Protobufs), serialization languages (XML -> Json -> Protobufs/Bson), ad nauseam. I think this kind of changes is the natural state of multi-year development efforts. On a 10-15 years old code base, you'll see all sorts of things like that cropping up and it's incredibly hard to steer clear of these kinds of things. What are the alternatives? Wholesale replacement of all uses? Wasteful in resources! Not introducing new technologies? Offends the sensibilities of the devs...
- rumcajz 12y agoIt also has to do with the fact that programmers are often ignorant about the problem domain and frequently don't even try to understand it. That makes them unable to solve the domain problems. They just follow the spec written by business analyst. With no interesting problems to solve they get bored and look for "new" and "cool" technologies to make their work more palatable.