3 ms·
I've done too little SQL to be traumatized by it, but I experienced it plenty of times doing more complex data processing on the backend. I would e.g. spend a
by TeMPOraL 4y ago
I've done too little SQL to be traumatized by it, but I experienced it plenty of times doing more complex data processing on the backend.
I would e.g. spend a week on first discussing a solution, then researching both theoretical background and relevant libraries, and finally writing code to do the math and render the answers (probability distributions). I eyeball them, they seem to all match expectations, so I declare victory, post some nice screenshots to team Slack, and close the ticket.
Feeling high on success, I expect the weekend to start nicely - except, winding down on that Friday evening, I follow that little thought at the back of my head, that I realize was there since the start, quietly poking for my attention. I run one more sanity check, different from the ones I did before. The results come out completely wrong. Only then it dawns on me that I made a terrible mistake early on - I misunderstood how to implement certain step and forgot about a theoretical assumption that must hold. And so, instead of a relaxed weekend, I now dread having to explain to everyone on Monday that a) I actually need another week for this, and b) the nicely looking graphs they saw are all pure bullshit, and the things that looked correct only seemed so, and only by accident.
After a few such cases - including one where the higher-ups were nonplussed, because after I corrected the mathematical errors someone made a long time ago, the pretty graphs that looked nice on the demo stopped looking so nice - I learned to sanity-check my understanding of the problem as early as possible, and then also sanity-check the code I'm writing, and then keep testing as I go. It's all too easy to write "trivial" code that "obviously" does what you think it does, only to realize some time later that it's throwing out an entire dimension of the input data, and nobody noticed because test examples are too trivial, results look roughly correct, and no one is paying attention.
- Micoloth 4y agoThat’s a great writeup of what it’s like to learn to do this job ahaha. Everbody goes through this I think (Arguably I’m still going through this…)
- fifilura 4y agoI feel the pain. Programming back-end code in an IDE takes you very far from working with the numbers on front of you. Is it possible to prototype in notebooks and add the results and input to unit tests?
- 2fast4you 4y agoYour anecdote gave me an idea. What if we use AI to enhance the communication between people instead of replacing the people? Imagine you give a problem statement to the LLM, then it tried to find all the subtleties, confusing parts, room for interpretation, etc. All of the people involved revise the problem statement to make it more clear and give it back to the LLM. Iterate like that until satisfied
- kulahan 4y agoAsking the right question is surprisingly hard sometimes. I'd love a tool I could converse with to come up with a question at the core of my thoughts.
- nickpeterson 4y agoRubber Duck AI chat bot, you explain your problem and it critiques your wording leading you sharpen your argument.
- noobermin 4y agoI really don't know why you think an AI as we currently have it could do this when it can't get these queries exactly right.
- 2fast4you 4y agoI really don’t know why you feel the need to point this out when I made no claims about feasibility. I think it’s worth exploring even if our current tech isn’t up to it.
- boredemployee 4y agoLol, countless times that I ended up with the right solution in my head while taking a shower or the day after, because after chillin my mind found that the previous code was wrong.
- harvey9 4y agoI've been there except instead of explaining to everyone on Monday, I didn't spot my mistake for two weeks _and none of the report users did either_. Nobody died but it wasn't my finest hour.
- comboy 4y agoWhen I was dealing with something similar and I didn't know how the result should even look like, something I did a few times was to separate some sample data, implement the idea using different technology than I was using for that project and then compare the numbers. Helps with debugging too.
- MonkeyClub 4y ago> b) the nicely looking graphs they saw are all pure bullshit, and the things that looked correct only seemed so, and only by accident. They’re not “bullshit” per se, they’re just “prototypes” for further refinement :) The road to success is trodden in stumbling half-drunken steps on the pebbles of failures.
- roenxi 4y agoThe traumatising experience of SQL is that the scenario you describe being scale-invariant. The smallest question and the largest question both have the potential to be completely wrong for any inane reason. Often turns out that metrics the company has been using for months are totally bogus too in my experience, which is not a fun conversation to have. So the life of an SQL analyst in their early days (it gets better as they learn to trust nothing) is either continuously pumping out garbage or constantly needing to go back and, very awkwardly, correct and redo work that people thought was finished (and those people were often happy with a bad result because it looked like something interesting was going on). This article is highly misleading, approx. none of the time an analyst spends is working on writing 5 line queries. The analyst is the person who knows that the data table for the series A and B rounds has different semantics depending on the data round because someone screwed up the table design beyond recovery and therefore a plain COUNT(*) will give incorrect results. This tool would let people who don't understand that pump out garbage faster. That might be a win regardless, most analytics requests cannot possibly be value-add.
- fifilura 4y agoThis is very on point. As an Analyst your asset is to own the data and know all the odds and quirks. Very similar to how developers need to own their codebase. Yes you can ask chatGPT to write a complex function. But your job as a developer is to see how it fits in with the rest of the framework. The logic is the simple part. As many pointed out you also need to be brutally honest with the numbers and also the problems you may have caused or fixed. Trying to hide any problems will very quickly throw you downhill, into an extremely uncomfortable position. Although before it acquires feelings and a sense of job safety, I guess chatGPT can be better at that part.
- kqr 4y agoIt's so refreshing to read this discussion. I've had these thoughts and feelings a lot but this is the first time I see them reflected in other people!
- 314 4y agoSLPT: on the Friday night you can quieten the little voice by drinking beer, and then you will promoted faster. If you really want to play for keeps then on Monday you can explain that you had a fantastic idea over the weekend for how to improve the results and make them more accurate.