My company is setting up a whole Hadoop/Spark infrastructure ..
For less than 60 gb of data. If anyone dares do anything other than agree with the CTO that this is a great idea, they get fired.
Do they offer redundancy? Getting fired over this might be your best option.
I'm buying some vintage ZX Spectrums from the flea market and soon I'll setup a big-data environment handling 6Mb of data! The stock market doesn't stand a chance B-)
You know what Chipper? He's doing that for his resume. It's dumb to fight that even though it will certainly be a waste of money if not an outright failure. It will look great on your resume and it will help you get a new job when the shit hits the fan.
The key is moving at the right time...
After getting the experience
Before the shit hits the fan
More than 6 months
Less than 18
I'm not sure if I agree with the looks great on your resume statement. It's only great if it's something you want to continue doing in the future at another company (or if you're starving and desperate for a job). I'm not a programmer, but I've left CAD systems I've used off my resume because I hated modeling in them. Some of them were trendy at the time.
Yup, Sangamon's got the time frame right.
Those keywords are a gold mine at the moment. Be a team player lol...
Yeah, it's a hot skill set. The question is if you want to do more of that in the future.
A colleague of mine called Big Data an "engineering wasteland". After working with these tools for a few months, I kind of see what he's talking about. Testing as part of the development process tends not to happen (TDD). This particular project is in "get 'er done" mode but there has been no effort at architecture or design, so we're basically just rewriting a bunch of SQL in a new framework.
Personally I could see myself going back to full stack development or something less specialized. But it's good to have the exposure to Spark/Hadoop - I guess.
"He's doing that for his resume."
But that is software engineering today. We have lots of sh!ty frameworks, programming languages reinventing the same sh!t, lots of unneeded faux domains of expertise, etc, etc. Everyone has to have a (not so) hidden agenda of creating resume fluff to stay employable.