Comment by liveoneggs
2 years ago
yeah but who was getting better stuff on their resume? didn't you get the memo about perl?
Just because your throw-away 40 line script worked from cron for five years without issue doesn't mean that a seven node hadoop cluster didn't come with benefits. You got to write in a language called "pig"! so fun.
I still think that it'd be easier to maintain the script that runs on a single computer than to maintain a hadoop cluster.
The resume would look better if you used Python and Polars ;-)
Using Rust and Polars over here; am I doing this right?
1 reply →
s/he was obviously joking
maybe we should all start to add "evaluated a hadoop cluster for X applications and saved the company 1mi (in time, headcount, and uptime) a year going with a 40line perl script"
I like this idea. And something similar for evaluating blockchains and sticking with a relational database instead.
> yeah but who was getting better stuff on their resume? didn't you get the memo about perl?
That is why Rust is so awesome. It still allows me to get stuff in my resume, but still make an executable that runs on my laptop with high performance.
Id love to hear what the benefits are to using a framework for the wrong purpose
Resume entries!
Résumé-driven development and its consequences have been a disaster for the human race.
"Consistently shows disregards for costs, performance and practicality to deliver predictable increases in the team size, budget and number of direct reports"
There was a time, about 10 years ago, when Hadoop/Spark was on just about every back-end job post out there.
I was in the field at the time and I agree. I thought it had to be what the big boys used. Then I realized that my job involves huge amounts of structured data and our MySQL instance handled everything quite well.