I’ve stumbled across this article, by @adactio, and it resonated with me, as I’ve had a similar discussion with my colleagues some time ago. The main point is that, since it’s easier to write and talk about new technologies, patterns and frameworks, we got to a state where what you read in articles, newsletters or what you hear at conferences doesn’t really reflect the actual state of the industry. I don’t think I’ve seen more than 10 talks or articles about Objective-C, or with code samples in Objective-C for a few years now. There are very few articles or talks about Core Data (I’ve written a bit about that in the intro to Issue 265). Almost every week you see articles and talks about “fixing MVC”, proposing new architectures and flows, even though I’m sure that the majority of the apps still use (in one way or another) MVC, Core Data is still used by a lot of developers and there’s still a lot of Objective-C out there. I’m not saying that’s bad, or that there should be more content about the “proven” technologies that people use. The role of newsletters, articles and conference talks is to inform and show alternatives. I just want to reiterate the article’s conclusion: don’t feel bad if what you read about or what you see doesn’t match you do. Whether you use those new technologies and follow the trends is your (or your team’s) decision, and it should be made taking into account a variety of factors. There are many other in your situation, and just because your code doesn’t use X or Y or Z it doesn’t mean it’s bad. The important thing, in my opinion, is to always try to improve, and always keep learning.