Posted by yusyd 5 hours ago
All it can do is randomly shuffle around the steps and ask if the customer likes it. If they don't, shuffle them around again and hope it's better this time.
And yes, super easy to make with almost no skill.
[0] https://m.youtube.com/watch?v=uJcO1W_TD74&pp=ygURVGVjaG5pcXV...
But Lam Lam's cold sear video doesn't seem to make that much smoke on a non-stick, so I'll give this a shot again.
(Personally the reverse sear has been my idiotproof go-to.)
Thanks!
But the thing is that most of this can be encoded in a markdown file for agents to read if it doesn't already come out of the box in the next round of sota models. And funnily enough as agents get smarter, you risk being overprescriptive where you hamstring the agent from making a pivot that would have led to better engineering.
The future is pretty clear to me at this point that we won't need software engineers looking over the shoulder and instead it's just a "user with taste" asking for revisions.
Have you ever been really deep in a thread with an agent on a technical deep dive? The trade-offs conversations would not make sense to someone that is not able to decode the real decisions they’re making.
You can dumb down the agent, but the reason domain language matters is because of the precision of the word sometimes - not to be a gatekeeper.
Anyway - user with taste that understands all the elements of their decisions would be my modifier :)
Over the last year, I've noticed that the recommended option for technical questions has become one that is always sufficient to the point that I'm once again in a tastemaker position, not in the "here's a better idea btw" position.
And if that's true, then my participation in the intermediate steps isn't strictly necessary to get a well reasoned position that's only directionally wrong.
The Codex app only does it in Plan mode, I believe. I did not touch the Plan mode for a while.
Now I only eat steaks grilled from frozen. Get the grill nice and hot (450F at least) and throw the frozen steak on the grill. 5-10 minutes each side usually gets it nice and crispy on the outside while rare and tender in the middle.
Seriously, try it.
But so much of the AI capability discussion can be avoided once everyone understands that a) There is some multivariate supply and demand market for software and b) AI is shifting the supply curve of software.
The shift is uneven, not perfectly monotonic, and might actually result in shifts in the demand curve (as e.g. 10x seniors get more valuable).
This insight makes it easier to see the forest despite the trees.
Hiring AI cooks is not a problem imo, as long as the human glances over everything that they serve.
God I, totally unironically, love HN.
But I actually got something out of this -- which is that maybe before now, humans had to soak up the complexity of where value was made in software. And you saw this in the highest and best paid engineers in science and platform teams and basically that you had to invest in brains where you thought the value in your product was.
Without humans managing complexity, you have no idea where you should be investing once the product grows out of the concept stage
- Cut steak in preheated oven at 250 degrees. - Pull at 125-130 degrees internal temp - Cook one minute per side in a skillet on medium heat