hazza1

Looking forward to trying this now, Java is too engrained in the enterprise backend for me to use at work.

He's about the launch his TypeScript training course...

The rules state they don't apply on initial submission?

Potty training at 6 months sounds like the masochists approach. Why would you train before they can physically get on a potty? Yes, they pee all the time at 4 months, do they really gain much being held on a potty?

I don't want to plop a baby in front of TV but likewise I wouldn't want their early months to be all about the potty.

When they're ready, if they've had a rounded start to life it's a just another simple transition.

especially as the author works from home so I assume could choose to live anywhere?

Agreed, I just turned down an online coding interview as it required 3 hours dedicated time, especially for those of us with families 3 hours at home is precious and not usual uninterruptible. Companies who set tasks like this probably aren't the sort of company you want to work for.

Prior to having a family, I'd spend 12 hours on a test but claim it was only 6, now I'd be pushed to spend 3.

you don't really want the overhead of checking types on every call, you know where your applications entry points are - if you need checks add them.

Pretending you're based in Switzerland or some other tax haven to avoid local sales tax gives you a massive advantage over national companies.

You don't need to choose the library but there's still the same amount of documentation to wade through, the amount of learning is the same.

although, code separation is native in React now and if you think http clients is still a thing you're too far into the Angular ecosystem to be helped.

Only if you know typescript and rxjs already is Angular easier to get up and running, react especially with create-react-app is trivial to get going.

Especially as they'll make the code public if you don't pay, so even if you don't have it locally there seems a free way to get it back?

I think it was the fact that v3 to 4 was "basically a new project" with a new paradigm that earnt the reputation for breaking changes but then React Router is such a marketable name I can see why you'd be reluctant to spin off a new project.

Custom hooks encapsulate logic so you can no longer use it in all of your app

Hooks solve some problems nicely, the main killer for me is that they don't work with classes, so you end up with 2 wildly different paradigms in your codebase.

Feels like hooks should have been a clean start in a new framework rather than retrofitted into React.