- May 8, 2012
- 4,217
- 3,728
of course there is always good and bad. however you dont see the point and ignore all the facts. sure frameworks make it easy, you dont need to know what you are doing, you can produce code faster and easy, but thats not always good. sure for you its good as you dont have to spend time learning low level stuff, but it doesnt mean you produce good code just because you use framewworks.By how you search I can tell you are affected by confirmation bias. You find one article against frameworks and think it's a viable source to share, but there will be thousands of articles why you should use frameworks. The same behavior can be seen with anti-vaxxers and conspiracists.
That is why I want to know something, I google the opposite of what I think, e.g. - instead of googling "why frameworks bad", you should search "why frameworks good".
But you do you, old-timer. I've noted that guys your age thinks that they know best, and their opinion can't be affected or changed, so I will not even try. My old stepdad(graphic designer) is exactly the same. No one wants his works anymore and he says it's because he's 'overqualified' and no one can't afford him. But in reality he uses techniques used 20 years ago, well, back then he was a kickass designer tbh. Nowadays, those designs are considered outdated.
The world changes, it moves very quickly, and if one want to survive in professional consultancy business, they must change along with it.
also you assume i stopped learning 10 years ago or something. in programming you always have to keep learning, so its not like i'm using outdated technics or code. in fact i still learn new languages every now and then. the difference is i understand the underlying technology, while you just use functions other people wrote for you.