This is also bugging my mind since using enum means you don't need to remember the exact literal string like "PENDING_VERIFICATION". You just define

enum AccountStatus {
  PendingVerification = 'PENDING_VERIFICATION';
  Active = 'ACTIVE',
  Locked = 'LOCKED'
}

and use VSCode autocomplete feature. E.g. AccountStatus.Pend- => AccountStatus.PendingVerification

VH VSCode will still autocomplete a union of string literals for you, e.g.

type Foobar = 'FOO' | 'BAR';

const doFoobar = (prop: Foobar) => prop;

When you use doFoobar VSCode will suggest/autocomplete once you have typed doFoobar(

Anthony Manning-Franklin Yep it sure supported autocomplete, my bad @@ and I also found out about how enum wasn't that good in TypeScript so I have fully switched to Union Type now.

Ah yes thank you for these awesome blog plots. I have implemented some in my project. I also ask questions in some of your article's comment section. Can you please check them :")

Thanks for the question!

I think I wrote this entire article in a couple of hours, plus some proof reading from my partner, writing the code maybe took up 25% of that time?

These functions are basically muscle memory for me now. By repeating the pattern over and over, I don't need to burn brain cycles remembering the pattern, I only need to think about the particular requirements of the business case being implemented.

This is the value of the practice of Kaizen. Have some exercises you repeat regularly, so you can internalise common patterns. Each time you do it, you will also make little improvements.

Then when it comes time to do it for real, you're not practicing in production on company time.