Hacker Newsnew | past | comments | ask | show | jobs | submit | oxidant's commentslogin

I saw someone handing out samples of creatine at Costco the other day, spouting all sorts of stuff like it's a wonder drug.

It's definitely becoming mainstream.

I've taken it off and on for the past 15 years, the most noticeable effect is about 5lbs of weight gain. I do think it helps gym performance and the increased water retention mames for better muscle definition.


Can we really call it a drug when it's something the body synthesizes for regular function?


What would you call insulin?


Ask for output to the user in "simple technical English", let it think how it wants. It is hard to believe all the flowery prose is actually helpful to the model.


Experienced this using the API. Got told it's a "wontfix"


I like capslock bound to esc.


There's nothing wrong with that. Everyone has their own vimrc, you do you.

But most people don't know about <C-[>, which works across your terminal, It isn't just a vim thing.


Stopped after

> Headline. The crash is real and reproducible.


I really hated that kind of language, feels like speaking to a motivator

anyway it's slop, can sense it even before i started reading


The worst thing is that I know there's something interesting in there but I'm too arsed to take the time and decode what data the author must have used to generate that text.


Exactly, it would be so much better if they shared the prompts instead of the output, at least then we'd be able to make some sense of what they were thinking about.


Unfortunately the prompt may have been something like "investigate this bug and file an issue when you think you understand what's going on". The "better just to share the prompt" heuristic falls down when the actual underlying intellectual work was also done by the machine.

(Feel free to pretend that I used some phrase other than "intellectual work" if you dislike seeing it used to describe something done by AI.)


Yeah in that case just closing it and moving on would be better IMO. A sufficiently large fraction of the time the issues with vibeslopped code and/or analysis are bad enough once you start digging into it that it's not worth spending time on. My heuristic would be to simply ignore contributions derived from lazy prompts. I don't think there are very many healthy babies in that bath water.

So having the prompt available would be useful even in the degenerate case.


How so? We can give the same starting point to the same AI and ask it to investigate too.


Get your own AI to give you the tldr :/


How does that help anything?


Makes the stock market go up


Old reddit still works, images and videos are usually forced to go to new reddit. You can sometimes get around it by clicking on the comments link.

I started getting a blocking overlay telling me to download the app on new reddit and I just leave.


I encountered that blocker today, so I decided to try Safari's Hide Distracting Items (1) feature, which blocked it once and for all, which I was pretty impressed by.

(1): https://support.apple.com/en-us/120682


> Old reddit still works, images and videos are usually forced to go to new reddit.

By default it sends you to new ("www"), but I've found (at least on non-mobile) I can edit the URL to use "old" and works (at least for now).


10DLC in North America


Interesting question. From the Wikipedia article,

> ISO 8601 allows Gregorian dates from the introduction of the calendar on 15 October 1582.

https://en.wikipedia.org/wiki/ISO_8601#Dates


This works well for jobs that are long-ish. You need another process to sweep for orphaned jobs and requeue or fail them. Add a timestamp of when it got picked up to keep track


Exactly the point I was going to make. Shipping something requires knowing how to ship it, monitor it, and fix it.

Writing code is the "easy" part and kind of always has been. No one triggers incidents from a PR that's been in review for too long.


LLM's can help with all of the above. Deployed an app with a backend, frontend, docker database and more with gitea on my NAS just yesterday. Have little knowledge about how it did it. Now I have a git remote to which I push and the app updates itself.


I guess it works well until you hit a stateful failure. My concern would be Day 2 operations—debugging a database issue or networking partition without a mental model of the underlying architecture seems pretty painful.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: