Some people believe JavaScript/V8 is faster than Java so I would also be glad to see the comparison here...

No, no innovation in vaporware.

High school project?

GraphQL isn`t an alternative for REST. GraphQL is a solution for very specific cases and even in this cases it has his own drawbacks.

I have been using react since 2015, hooks for the most part seems like a miss.

I use sometimes, but for the most part is overused feature.

I think thats a symptom of a problem with the front end community, people get too attached to the new thing and try to make it the standard instead of building something stable and concise.

Im tired to having to rewrite a code because one library that I had to upgrade decided to migrate to the "new thing"

The composability of hooks, which was one of it main selling points, is also my main gripe with them now. I often have to wade through multiple levels of hooks to figure out what's really going on.

And using it professionally for years now, there's still some cases I can't wrap my head around. And the mental model is just a bit "off". Like, the same function is ran multiple times, but with different behavior (like a useState only uses the parameter the first time the function is ran) which is very unclean.

Maybe we can get a United Ireland by 2024 as Star Trek predicted

Technically 4 days would be better because of the commute and extended weekends for the employee. But as an employer 6 hours workdays would be the best, you get basically the same value of your employees, since mostly office workers don't really work the 8 and also would make then free to study.

You could also go crazy and get a second or third job.

Non-essential dependencies are for the weak and every single company that I worked for.

HackerRank is a terrible product. If any company I applied uses it I withdraw immediately.

Same. If they insist on HackerRank, that tells me they hire based on solving logic puzzles and not building software and systems. Not a place I'm interested in

It depends how you use it.

I've used it to pre-screen candidates with very basic code questions. It filters out a lot of people who are either lying or just don't believe they will have to ever write any code.

This allows me to consider a much wider range of candidates outside top tier schools and employers.

That's fair, and not at all the way I've seen it used

I would probably think twice before accepting an offer if I had a peek in the codebase of some companies I worked on. From weird practices to complete useless tests and straight copies of other projects without any planing.

But for first step a Psychotechnical test on the candidate, and to be fair, the team and manager.

For an interview, I took a copy of the product's source code to the interview with me to talk about issues it had.

They couldn't work out how I got hold of it. It wasn't open source and only distributed as a binary.

It got me the job. Risky strategy.