garrettdimon

It still creates non-trivial day-to-day overhead for customers where they now have to think about who to invite and what permissions to grant them in conjunction with costs.

We'd much rather that 90% of the cases, customers can just invite anyone on their team without fearing ballooning costs. Then they can think about permissions purely from a permissions/access perspective and not have to factor cost into that decision.

There has to be some sort of limit because "unlimited" can easily lead to customers using far more resources than they're paying for.

However, by moving away from per-seat pricing, customers who have switched to the new pricing have now added many more users who can benefit from having access to the Flipper Cloud UI but were not worth paying for individual seats before.

So based on customer behavior and reception to the new plans, it has made things much more flexible for them in practice.

I don't have a singular, one-size-fits-all better option, but I explicitly included several options that I've seen work well either as the applicant or from the hiring side. I just wasn't going to presume that there's one perfect replacement that will work for every team or role.

I added that after-the-fact in response to this comment. So that's on me for not including it originally. It's a great idea and one I wholeheartedly endorse because it forces the company to put some skin in the game and helps limit the number of applicants that they would request perform the take home test while also recognizing that applicants' time is in limited supply.

That’s not always accurate that the company doing the hiring contributes nothing. (Also good companies could offer to pay for that take-home test time.)

Having done take home before from the hiring side, it was incredibly time-consuming for us. We had someone anonymize the three finalist submissions, and then we had three people each individually review and comment on each one, and then we got together to discuss and choose the final candidate. Once we agreed on one, only then was it de-anonymized.

All-in, it took way more time than a single developer doing three live coding interviews. But my guess would be that most companies wouldn’t be willing to be that deliberate with take home.

I don’t have any trouble with the three bottom thumb keys in the cluster, but the top three aren’t very useful. I’ve remapped them to media or macro shortcuts that I don’t use while typing.

We have three TCL Roku TV’s, and while they’re all blocked now, they were responsible for about 98% of the requests on our network according to Pi Hole. Now they’re blocked at the router level as well because it’s hard to trust them at all. Pi Hole doesn’t block them by default, but the endless requests to Roku domains are easy to blacklist.