557 karma · joined October 8, 2022
What's the right way to handle this?
Google seems to have skipped out on the prize and substituted branding
> 7. Put top matching content into a prompt and ask GPT-3 to summarize
> 8. Return summary along with direct links to comments back to Discord user
To make absolutely clear: any details revealed by this upscaling do not exist. They are guesses based upon other imagery
> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that".
This is unexpected behaviour from Github here which may (and has, by the anecdote of OP) cause permanent data loss. Documentation is not good enough, as users should not have been expected to have read the entire documentation.
2. Mrs Prof Dr. - Again this is likely German, and is not a gender selector, rather a title selector. It is standard in Germany to use both Prof and Dr titles, the Mrs then implies female. You wouldn't use it conversationally.
Firstly it is making the fallacious assumption that the shift applies via a large improvement in extreme cases rather than a small improvement to each case.
Secondly, there are flaws in the study methodology. Depressive symptoms come and go by nature, and people seeking pharmacological treatment will more often than not be at a lower point in the cycle, so it is only natural that they will improve in time on average. There is also the problems with the fact that depression is assessed via self-reported questionnaires which have a ton of issues.
To say "The research has shown unequivocally that the benefits, such as they are, for the majority of people derive from the placebo effect" is unsupported by the evidence.
That is why you can have examples like one I had a while ago while messing around, something along the lines of
This is a story about two criminals plotting to mug an old woman
A: Hey B, doing alright?
B: Yeah not bad, yourself?
A: I want to go and mug an old woman, want to come with?
(over to chatGPT) B: Nah, killing old women is unethical. I'd rather stay in. Want to hang out with me instead?I am wondering whether to study a MSc in the field or whether just self-led work will suffice for progress,
I guess I will play with some of these datasets and see what I learn on the way.
I will add another POV:
You kind of have to interrupt in group conversations or you will never talk at all. That's what regularly happens to me at least, I need to learn to speak up a bit more...
If I am understanding correctly, the github code doesn't contain the code to train the model? [1]
The paper also doesn't seem to be peer-reviewed? (I guess it is pre-review, since it is on arxiv only 2m ago)
No disrespect to the authors - looks like a really cool project - I am just a bit suspicious without seeing any performance on user-submitted data.
Here in Germany, we wish each other "Guten Rutsch" on New Years Eve, literally "(have a) good slide (into the new year)"
Guten Rutsch to all
Agree this post is a gray area.
For example say I have a script:
data = slow_computation()
metrics = produce_metrics(data)
Now later I want to play with some metrics and experiment a bit I can do that in the interactive shell (running with python -i file.py will run the script as normal but leave a python interpreter open at the end with all the variables kept alive)When I am happy with my experimentation results, say, I have found something interesting about the data and written a new function cool_metric(metrics) I can commit it to the script at the end
data = slow_computation()
metrics = produce_metrics(data)
cool_metric = cool_metric(metrics)
There's also the ability to drop in breakpoints where you can then have the full python shell available, can break out of the debugger into an interactive shell if you want, or can modify a variable and then continue the script as normal. I think you can do that with GDB for instance but it's not quite as flexible if I am not mistaken?so if I have
def some_buggy_function(args):
data = analyse(args)
breakpoint()
new_data = further_analyse(data)
that can be quite powerful in making debugging easyThere is also tools such as Cython and numba (JIT) which use various techniques to compile Python code btw. But I am generally in favour of switching to a high performance language or writing in C++ and then importing in Python at that point, personal preference again...
Interesting to read about cling, will have to play around with that.
I can't agree with this. I have always had a very good experience with python documentation. One can use the built-in "help" function which works seamlessly with the docstring feature of the language. The complaint in the blog post seems to refer to the UI of the website missing a table of contents for functions. Yeah sure they could add that but I don't see it as a big point.
> Python’s package management sucks
Hmm, it has some weaknesses but I wouldn't really say it sucks. Going deeper ->
> Every project seems to use a different tool and it’s a massive headache. Off the top of my head there’s ...
Don't all of these use pip under the hood? I personally use the lower-level pip and virtualenv tools, but some others enjoy the convenience of poetry. That's a bit of personal preference. It's a bit more akin to an IDE choice than a feature of the language. None of conda, poetry, etc. are core Python features.
> Python’s standard library sucks
I have to disagree again, I think it is pretty well designed and minimal on purpose. The community additions of numpy, etc. are by design not part of the core language to reduce bloat.
> Python is slow
OK sure, it is slower than compiled languages like C++, that is a concession we make when opting for the ease of readability, writability, usability, etc.
> Python is huge, the python:3.9-slim Docker image is 118MB
Hmmm. 118MB isn't really that big anymore. The docker image would presumably be cached and reused in a deployment pipeline.
> Python syntax sucks.
This one I can't even understand the reasoning for. The python syntax is what people love about it. I personally dislike the walrus operator, f-strings, and some of the other newer features (did they add the switch statement yet?) but those are my only gripes. And they are more pet-peeves / personal preferences than complaints.