Prompt engineering

So 100% on, you know, the...

The way to provide more context has moved on from Scrum engineering in a classical way.

But the way to provide more context implicitly and without too much effort is still there on whether it's dot cursor, whether it's dot cloud, cloud.md, or memories in open cloud.

And it's always there.

for you urgency means that it is the highest value opportunities that you know have not been worked not simply the fact that they haven't been touched before for you urgent might mean these are the opportunities that your sales manager has started to ask you about and so it needs to look into slack and see like what the sales manager have said so there's all these sorts of things where if you have the right platform and you're working with the right model They can start to piece out that information from you with a back and forth.

And then the next time when you prompt that you say, hey, I need to work on my most urgent opportunities in Salesforce, then there is no prompt engineering you have to do.

There is no back and forth you have to do.

It just works.

And that's where you start to get less information about prompt engineering, less necessity rather about prompt engineering and more just about, well, the context is already stored somewhere.

It knows exactly what I mean.

The next time I do it, it'll be magical.

And that I think will be a really good setup for my next question about prompt engineering versus context engineering as an adoption bottleneck, which has been, you're not the only person talking about this.

You get significantly better outputs and do way less babysitting.

It is about upgrading your entire prompt engineering workflow.

It is a fundamental shift in how we interact with AI.

We are stepping away from the micromanagement of tiny tasks.