3 ms·
>> The level of sacrifice required is dropping, and it's dropping like a rock. What have changed , just ruby on rails type frameworks , or something beyond ?
by hershel 13y ago
>> The level of sacrifice required is dropping, and it's dropping like a rock.
What have changed , just ruby on rails type frameworks , or something beyond ?
- potatolicious 13y agoEmployers. It was never that difficult to become a novice developer, but convincing anyone to hire you was the hard part. No CS degree (or math, or engineering) was a death sentence to any resume at the vast majority of companies. The new model is to skip the CS fundamentals and instead crash-course you on frameworks and languages that are being used in-industry, then toss you into the deep end. If you float, you've now got the "experience" part of the dreaded "experienced required" part of any job posting. The hard part was getting employers to buy into the scheme. "We've got this guy who has next to no idea about algorithms and data structures, but will do fine as a low-level Rails grunt" didn't sound very attractive before, but considering how hard engineering hiring is right now, some companies are biting. I for one am intrigued at the inversion of priorities and curious to see how this will play out. Up until now our educational process has been to fill your head full of theory and leave the practical application up to your own time. This has meant truckloads of CS graduates who aren't actually capable of performing real-life engineering. The new scheme is to get you working first and foremost, and assume that the fundamentals and theory you missed out on will be filled over time. As someone who never got their CS degree to begin with, I'm rather partial to the latter approach.
- malbs 13y agoGood old vocational education.