Depends on the usecase. Unit tests are nice, but having had to upgrade a lot of front-ends recently, I wish all these tests were actually going through the browser route, even if it's slow. We only use tests manually so it's not slowing down deployments or commits.

Indeed. It's not even about tech people I don't think. It's non-tech people who make decisions. And at the moment they seemed to rather make sure they are seen as super impressive and on board than calculated and pragmatic.

The easy explanation is it's quite natural to feel strongly negative about something sold as "yeah, bitch, your livelihood will go away, suck it!"

Once I get there in 4-6 months, will need to figure it out, I suppose 😅 but yes, hopefully it'll go better, cheers 🤞

Hah, I'd say (unironically) marketing will always be the issue (to improve on).

However, at this time I'm not actually trying to MMR anything (yet... Not publicly anyway 😅)

Good article. I liked the "importance of the single flow" approach too, maybe even more than the JS stuff.

My approach was to quickly get something out for a browser plugin and I didn't want to massively complicate it, but didn't want to have to duplicate biz-logic to check the same state.

Nice, will have a read tonight. Thank you for sharing.

Link? I would like to see how other devs have approached this.

Oh where it signs multiple values to instance on construct, and you don't have to do match in method.

Gotcha!

Yeah that would be neat and a bit cleaner, especially if you have loads of labels you want to print out or same value from method is used multiple times.

Good shout!