joemoon

Spidey senses going off here. The first two comments read like an LLM.

Thank you, this was a very interesting interview.

While the post didn't particularly speak to me, I think you are being overly reductionist. You can dismissively summarize anything into a few "key points."

Just in the first couple of paragraphs alone:

- The author discusses the "why" by pointing to research on how new information triggers dopamine pathways. Maybe this is obvious to you but it's not necessarily obvious to everyone.

- The author points out that this would have historically been an evolutionary advantage (at least that's my interpretation), but access to modern high-volume, low-nutrient information has made this an addictive unhealthy habit.

- For those already familiar with how modern access to high-calorie, low-nutrient food (that triggers the dopamine response), the author is showing that the same mechanisms are at play with information.

I think it's actually your comment that contains the tweet-able one liners (as "key points") that are likely to result in head nods and smug self assurances but aren't doing anything to encourage deeper thought.

It's definitely a very similar method but fundamentally different in that the 'Distilling step-by-step' approach is a multi-task model.

As I understand it, rather that training the smaller model to produce the CoT/rationale as a part of the (decoded) response, it actually has two output layers. One output is for the label and the other is for the rationale. The other layers are shared, which is how/why the model is able to have an improved "understanding" of which nuances matter in the labeling task.

While sleeping? This is one of the signs of sleep apnea.

Thank you for the anecdote. It was well written and I think it’s very applicable to the current topic.

I suggest integrating this with every single help desk software you can. They all provide integrations. We were looking for something like this earlier in the year as it pertains to customer support and using SMS as a channel.

If help desk isn't the answer, then maybe another type of platform. Generally, I think you need to ride the coat tails of larger platforms.

(Note: I do realize this is developer focused today, but it didn't necessarily need to be.)

I strongly disagree with the sibling comment. Your website _does_ matter. At least in so far as it represents how you are positioning yourself to your clients.

Your website is all about what kind of software you can build. Your clients don't care about that. They want to know what kind of business value you can deliver. What kind of results can you achieve?

As a business owner, I don't want to see example websites, I want to see a case study about how you increased revenue by 20% with a new user onboarding process. I want to see how you saved 100 hrs per month in staff time (i.e. expenses) with the new set of automation features you developed.

If you don't have this data from past projects, then start collecting it. Start framing all of your conversations this way from now on. If a client is working toward a business objective, help them achieve it and make sure you put mechanisms in place to measure success and assign a real dollar value to what you helped them achieve.

Adding keywords: ruby, rails, devops