Compare output from a spoctrometer (or spectrograph) vs. eliminating outliers from an almost linear process. One will wreck your data and the other is the only correct thing to do.
Ah, well, rereading your original post I realize now this isn't necessarily painful for me. Perhaps though, the annoying aspect is seeing others use proprietary excel spreadsheets without a data lake. Conway's Law?
Does VS here mean Visual Studio? I would not call myself a data engineer, I just play one at work sometimes. Many hats, yknow?
Hah okay. I read VS different from vs. The pain, in part, is hidden functions, rarely ever inline documentation, difficult to reuse or repurpose, Windows-centric, etc.
I was curious about this position (the fact that you are upfront that you need to do a big refactor), but then the application form was very off-putting.
> Tell us about yourself in 3 KPIs, with a brief explanation and examples. (A KPI is a number that evaluate performance in a specific aspect.)
> Record and upload an unedited face-cam video (3 to 10 minutes) where you explain a problem you had this week and how you solved it on your own.
Thanks for the feedback. Indeed I don't want to get the wrong expectations & be as clear as possible. It will be a painful cleaning job at first (at least that's how refactoring is viewed by most).
And yes we do have a carefully crafted process. Those questions / requests are very meaningful for us.
Recording a video of yourself explaining something is just a non-starter for me. Maybe I'm just old and not part of the Instagram/TikTok generation, but I'd feel very self-conscious. I doubt I'm the only one.