One example I have that made me excited for this feature is the free recipe manager website I run.
Many of the paid-for competitors give users the ability to import unstructured recipe data these days from sites like instagram or at least text-only websites.
I can't afford to offer this as a feature since my website has no advertising and I just pay for it out of pocket, but it's an incredibly easy feature to add if you have the money to pay for tokens.
If I could use a local llm to do it though that runs in the person's own browser then I think it would definitely be valuable.
That said, I'm not sure the state of local llms provides a good enough experience yet (small models and slow) but that doesn't mean that in the future it might not be useful.
The propsosed apis do work for this purpose, albeit more slowly and lower quality
Why do you think this is madness?
FB doesn't use git for these monorepos, so that's not really relevant, but I don't understand why you think that it's better to break a repo up because the SCM can't handle the size vs fixing the SCM so it can handle the size.
I work for meta (nothing to do with the teams working on this though) and I can assure you people have considered the tradeoffs of breaking repos up just to accommodate existing SCMs vs improving the SCMs.. I think if you believe improving the SCM instead of breaking up the code is madness you should probably provide a bit more of a justification
The questions are designed to allow an interviewer to get as much signal in the 45 minutes spent in the interview.. that's why they're contrived rather than your typical piece of work.
They're not designed to test you on something you would never encounter though.
If a company is asking these kinds of questions and the job only ever requires dealing with npm packages that shields the engineer from this complexity then they shouldn't be doing that in my opinion.
But most of the companies asking these questions are in the business of building software that requires this lower-level knowledge
I conduct interviews for Facebook and we do not discriminate on age. I assume the recruiter just got the impression you really didn’t want to interview with us.
I only do the coding interviews but every piece of interview feedback I write is focused on the same criteria and that definitely does not consider age. We don’t even refer to the gender of an applicant in the feedback, and comments on an applicants age would be a quick way for me to get dropped from the interviewer pool.
This is the correct explanation (thank you)
There’s no intention to hide the fact that certain links are blocked. The bug is that the status of failed message sends (not limited to blocked links) only shows an exclamation mark against the last message on web.
At the company I work for UI accessibility issues are automatic high priority bugs. You'll be an asset (as a frontend developer) to any company that values accessibility (and I'm certain that many do).
Contrary to your concerns, I think that being visually impaired and being a frontend developer will most likely open up opportunities rather than close them down.
In firefox it skips one letter at a time and maybe that is the intended behaviour, but it doesn't seem consistent with what I'd expect from a WYSIWYG editor.
I'd expect there to be 2 positions between the "e" and the "t" that the cursor would stop at so I can either insert text with the formatting of "one" or "two"
Many of the paid-for competitors give users the ability to import unstructured recipe data these days from sites like instagram or at least text-only websites.
I can't afford to offer this as a feature since my website has no advertising and I just pay for it out of pocket, but it's an incredibly easy feature to add if you have the money to pay for tokens.
If I could use a local llm to do it though that runs in the person's own browser then I think it would definitely be valuable.
That said, I'm not sure the state of local llms provides a good enough experience yet (small models and slow) but that doesn't mean that in the future it might not be useful.
The propsosed apis do work for this purpose, albeit more slowly and lower quality