It’s been a while since I’ve worked with AOSP, but I had always understood it to be some weird shit with Google’s internal processes. The “do not merge” commits are all over the AOSP, or at least they used to be.
Don’t use OpenAI’s outdated tools. Also, don’t rely on prompt engineering to force the output to conform. Instead, use a local LLM and something like jsonformer or parserllm which can provably output well-formed/parseable text.
I’ll be informal to boost your intuition. You know how a parser can reject invalid inputs? Parsers can be generated from grammars, so we can think of the grammars themselves as rejecting invalid inputs too. When we use a grammar for generation, every generated output will be a valid input when parsed, because the grammar can’t build any invalid sentences (by definition!)
For example, suppose we want to generate a JSON object. The grammar for JSON objects starts with an opening curly brace “{”. This means that every parser which accepts JSON objects (and rejects everything else) must start by accepting “{”. So, our generator must start by emitting a “{” as well. Since our language-modeling generators work over probability distributions, this can be accomplished by setting the probability of every token which doesn’t start with “{” to zero.
They are all named some variant of “tutorial_Ch01” or “testprogram” probably. And one repository named “My Unnamed MMO” (or some other overly complex but trendy genre) that has like 12 lines of code so far and a crappy drawn pixelart png.
This isn’t my experience. I’m way more focused in the morning and then it’s all downhill after lunch. By the time it’s the evening I have zero motivation to do any code.
I was getting emails about pull requests and issues all night. It’s like some people just took advantage of everybody being outside of the house to code 😅
No one died this kind of stuff because someone asked then to do it. This is the kind of useless insane stuff you do for the lulz, or because someone dared you.
Yes, it’s been established that you can still use JavaScript, and it will only backfire sometimes, even though it’s a bad language. And yet, people try to use it where it’s not even required.
It never ceases to amaze me how far idiots will go to avoid learning the most simple things. SQL isn’t hard, people’s difficulty with it says a lot more about them than it does SQL.
People think in different ways. What might seem logical to you might look alien to another. I know SQL well enough to optimize queries, but I find it a lot easier to think about and write queries as LINQ methods. A lot more cleaner and logical to my brain.
Just release unfinished DLC for $35, release a "definitive version" even though that was only the first half of the DLC, release the even more unfinished second half of the DLC and still leave a bunch of shit from the base game unexplained. Yeah I'm still salty about something, how'd you know?
Only C and Lisp actually completed the initial task of getting the princess free, and Author clearly favors C over the drooling and homeless lisp hacker. Also, turns out, C greatest weakness helped to save not only the princess but everything she ever possessed! How convenient!
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.