jmcdonald-ut

Great work on this, had a blast!

The article links out to OpenAI's advice on prompting, but it also claims:

    OpenAI does publish advice on prompting o1, 
    but we find it incomplete, and in a sense you can
    view this article as a “Missing Manual” to lived
    experience using o1 and o1 pro in practice.

To that end, the article does seem to contradict some of the advice OpenAI gives. E.g., the article recommends stuffing the model with as much context as possible... while OpenAI's docs note to include only the most relevant information to prevent the model from overcomplicating its response.

I haven't used o1 enough to have my own opinion.

I'm not sure what this comment is trying to insinuate? I mean sure they might have a financial interest, but they're also writing about stuff they know well since they use it.

I'll add my two cents on top of the author's. I have both the Amazon Echo and the Amazon Tap. This article was spot on. I'm perhaps less forgiving than the author. If Alexa can't answer a question on the first try I'll just give up. When Alexa does answer a question or a request she usually does a phenomenal job and it's just really cool. It really feels futuristic.

Echo is cool, it can be pretty useful, but it hasn't realized its full potential yet.

I bought the Tap as a portable speaker to take with me on bike rides with friends. Well I took it out the other day and the minute it lost WiFi connection it just wouldn't work. I'm sure this was a problem on my end, but I had already paired the devices and I wasn't going to spend time fiddling with it while I was out with friends.

EDIT: Also it doesn't happen too often but Alexa has definitely accidentally triggered. It even woke me up at 2 AM after the power went out temporarily to tell me that it had no WiFi.

I got to take Matt's compilers course. He was a really exceptional professor who had a way of presenting pretty mundane and rigorous material in an interesting way. His lectures were always engaging. If your interested in understanding programming languages at a lower level I can't recommend enough perusing his blog.

He addresses this in his post.

  if x.in? my_set   # very ugly

With that said, I personally don't agree with the post.

I'm a current CS student, finishing this year. I work with both people who are self taught and people who have degrees. I think pretty highly of those I work with who are self taught. All in all the differences are minimal when getting the job done.

CS emphasizes theory and mathematics. Programming and coding is usually discussed in the introductory courses, but from there students are expected to teach themselves to keep up.

Heh, not so complicated. It's just used to generate boiler plate code. Kind of like data object files in C#, Java, PHP, etc. That would be really cool though :).

This was a really cool read :). I'm working on my own DSL for generating code. I'll make a Show HN soon, but it was really cool to see someone else doing something so similar.

I'm taking the class this upcoming semester from Matt. I'm excited to understand what tools like gcc, clang, and so on are doing under the hood.