I know exactly how this occurs because I recently met a "Senior Web Developer" at an established business who was basically their acting architect because he was the their first coder and therefor his non-technical bosses regarded him as some kind of genius because he knows how to unjam the office printer. He didn't know a lick of Unix, didn't understand load balancing, and had very weak SQL skills. He was your typical framework junky who couldn't imagine writing even the simplest web app without a framework to do all the heavy lifting. All he wanted was for me to recommend an even simpler web framework so he wouldn't have to write any SQL at all. No doubt some day his code will be generating headlines like this one, and he will no doubt blame whatever framework he used and his bosses will simply mandate that they switch to a more secure framework pronto, and they'll promote this boob as their Senior Architect to lead the project.
That actually sounds like the right way to do it to me. He shouldn't be writing frameworks. Frameworks are reviewed by a lot of people, and there is a far greater chance of them being bug free than something home-rolled.
I've met hundreds of these boobs in IT shops around the world. There's a huge skills gap between IT and software devs. IT guys are not given the time nor resources to learn and implement all this stuff. Also, they often don't have the skills or curiosity to figure it out themselves. So they really do need a framework that takes care of it all easily.
