4 ms·

The space is moving so fast that, if I wrote down my workflows and workarounds just two months ago, so much of it would be stale today. I think all these recomm

The space is moving so fast that, if I wrote down my workflows and workarounds just two months ago, so much of it would be stale today. I think all these recommendations need to list the models and harnesses being described front and center.

Aeolun 1y ago
Yeah. I have Claude 4 correcting code that Claude 3.5 wrote a few months ago.
- bdangubic 1y ago
  hehehe - same :)
- pmbanugo 1y ago
  I haven’t tried Claude 4. Maybe I’d give it a spin to see if it can improve my design document
- motorest 1y ago
  > Yeah. I have Claude 4 correcting code that Claude 3.5 wrote a few months ago. You don't even need to switch models. Write a prompt to generate some code and immediately after prompt the same model to review the code it just generated. Sometimes it takes 3 or 4 prompts to get the result to converge. But converge to where?
brumar 1y ago
Very important comment. My workflow changed dramatically with the increased capabilities of these tools.
motorest 1y ago
> The space is moving so fast that, if I wrote down my workflows and workarounds just two months ago, so much of it would be stale today. There is also the problem that none of these workflows were validated or verified. Everyone is free to go on social media or personal blogs and advertise their snake oil. Thus in a scenario where these workflows are found to be lacking, the perceived staleness might actually be ineffectiveness beyond self promotion.
- aerhardt 1y ago
  I'm seeing a lot of this too. I can tell with my own eyes that the technology is extremely useful, but also that it has limits. On the internet however you'll see a decent amount of randos claiming that they're one-shotting hyperscale complex systems with the latest trendiest tool. My approach is to keep using LLMs where they reasonably make sense and experimenting here and there with new workflows and tools, but I'm past changing the way I work every two weeks.

Aeolun 1y ago

Yeah. I have Claude 4 correcting code that Claude 3.5 wrote a few months ago.

bdangubic 1y ago
hehehe - same :)
pmbanugo 1y ago
I haven’t tried Claude 4. Maybe I’d give it a spin to see if it can improve my design document
motorest 1y ago
> Yeah. I have Claude 4 correcting code that Claude 3.5 wrote a few months ago. You don't even need to switch models. Write a prompt to generate some code and immediately after prompt the same model to review the code it just generated. Sometimes it takes 3 or 4 prompts to get the result to converge. But converge to where?

brumar 1y ago

Very important comment. My workflow changed dramatically with the increased capabilities of these tools.

motorest 1y ago

> The space is moving so fast that, if I wrote down my workflows and workarounds just two months ago, so much of it would be stale today. There is also the problem that none of these workflows were validated or verified. Everyone is free to go on social media or personal blogs and advertise their snake oil. Thus in a scenario where these workflows are found to be lacking, the perceived staleness might actually be ineffectiveness beyond self promotion.

aerhardt 1y ago
I'm seeing a lot of this too. I can tell with my own eyes that the technology is extremely useful, but also that it has limits. On the internet however you'll see a decent amount of randos claiming that they're one-shotting hyperscale complex systems with the latest trendiest tool. My approach is to keep using LLMs where they reasonably make sense and experimenting here and there with new workflows and tools, but I'm past changing the way I work every two weeks.