Reactive Wire Parameters and Refreshing Data

@api recordId;

@wire(getRecord, { recordId: '$recordId', fields: [NAME_FIELD] })
account;

The $ prefix on '$recordId' marks it as a reactive parameter — whenever this.recordId changes (for instance, because a parent passed down a newly-selected record's ID), the wire automatically re-fetches with the new value. No manual refresh call needed for this case.

import { refreshApex } from '@salesforce/apex';

async handleSave() {
    await updateRecord({ fields });
    await refreshApex(this.wiredAccountResult);
}

Some changes — like an update made through a different path than the wire itself watches — won't automatically trigger a re-fetch. refreshApex, given a reference to the wired result, forces a manual re-fetch so the UI reflects the latest data.

@wire(getRecord, { recordId: '$recordId', fields: [NAME_FIELD] })
wiredAccount(result) {
    this.wiredAccountResult = result; // keep a reference for refreshApex later
    this.account = result.data;
}

Using the function form of @wire (rather than a plain property) gives access to the full result object, which is what refreshApex needs a reference to.

"I updated the record, but the UI still shows the old value" is a very common real bug — it almost always means either a reactive parameter wasn't actually reassigned, or refreshApex was needed but never called after a write.