4 ms·
Well, sure, and ten years' experience working for some other company with their technologies and in-house legacy code, libraries, design methodologies, and idio
by SiVal 13y ago
Well, sure, and ten years' experience working for some other company with their technologies and in-house legacy code, libraries, design methodologies, and idiosyncratic ways of using even open source tools is not ten years' experience anywhere else.
A 22 year old with ten years of programming experience has ten years of experience doing what he's been doing. He may have built a Mongo-based sports statistics website for his high school. A 32 year old with ten years of corporate dev may have been creating in-house database utilities for MegaCorp's 20 year old Oracle customer database. He's had ten years of corporate database development experience. Is his experience clearly more suited to a Mongo-based startup selling hats to sports fans because his experience was corporate?
Or is it not a matter of corporate vs non-corporate experience but just how much experience doing which of the things we need someone to do?
- RussianCow 13y agoPart of the "corporate experience" is working with teams on existing code under strict deadlines. That's not something you can just learn on your own, unfortunately. I would, hands down, take the 32-year-old in this scenario (all else being equal).
- Pacabel 13y agoRegardless of age, I'd much rather take the developer with experience using one or more relational database systems. It's much easier and effective for them to downgrade their knowledge and experience to the MongoDB level than it is for somebody with only MongoDB experience to upgrade to a proper understanding of database systems.