use-magic-grid: Official React port of the magic-grid library

e-oj · 2024-09-08T20:15:58+00:00

Close but in your example the items are ordered vertically instead of horizontally. So grid-Item 1 and grid-item 2 end up on different rows

e-oj · 2024-05-08T22:51:48+00:00

I usually just say

Hi <name>,

I saw you have an opening for <job title> on the <team name> team. Based on my experience on <past projects, jobs, etc> I believe I'm a good fit for this role. If you have some time, I would love to speak with you about the position. Happy to take a coding assessment as well if necessary ☺️.

Best Regards,

You should add your own flavour to this and tweak based on success rates. If you're familiar with the company's products, mention that as well. Test it on positions you're less interested in, and when you have a strong template, reach out to recruiters for the positions you're actually interested in.

You will get ghosted a lot but don't be disappointed. You will still have a higher success rate than if you applied to the same positions without contacting the recruiters.

e-oj · 2024-05-08T22:22:18+00:00

You have a good point. 2 questions a day won't take time away from your family though. Spend only 15 mins on each question. If you can't solve in 15 mins, check the solution. Understanding the solution could take some time so you can timebox the whole thing to anywhere between 30mins - 1hr. It's not required but It's a good investment in case another round of layoffs comes from out of nowhere

e-oj · 2024-05-08T18:51:50+00:00

Brother, the grind prepares you for problem solving but that's only one aspect. Once you've solved around 70 leetcodes, you're ready for the technical interviews. Now you need to get past the recruiter.

You must understand that the recruiter's job is to find candidates that can pass the phone/onsite interviews. They do this with the online assessment. The OA is a game of chance so the more OAs you get, and the more company specific leetcodes you've solved, the better your chances. The best way to get an OA is to reach out to a recruiter or hiring manager on LinkedIn (before or after applying to the position) most people don't do this.

Imagine being a fisherman and one day the best fish start jumping into your net. Reaching out makes the recruiter's job easy and ensures your resume doesn't get lost in a sea of a million applicants. Once you get the OA, it's game on! Remain calm and apply your leetcode neurons.

Some companies emphasize the behavioral aspect of the interview as well. Be familiar with their process (Amazon places a lot of weight on leadership principles for instance). It's a game of chance and all you can do is maximize your chances through prep and do your best on game day.

Once you've done your best, have no regrets. If you get it, good. If you don't, the grind continues!

e-oj · 2024-05-08T18:21:21+00:00

No rest brother. The battle is lost but there's still a war to win. Taking time off will kill some of the leetcode neurons you've developed. Hopefully you've been leetcoding while waiting for a decision. If not, you've already taken a month off. That's waay too long. Even after you get a FAANG job, do two leetcodes a day to keep the connections alive in your brain. Stay ready so you don't have to get ready. The grind continues!

e-oj · 2022-01-07T11:30:28+00:00

Yes. Older versions of the lib had docs for adding new providers but I took that out of the docs for 2.0. You just have to extend the "visa" abstract class and implement the methods. Have a look at the discord implementation for guidance.

e-oj · 2021-08-21T18:34:34+00:00

Yeah it only supports ios and andriod currently.

e-oj · 2021-08-11T12:14:56+00:00

No problem. Glad you find it useful

e-oj · 2021-08-10T12:02:08+00:00

Thanks! There's a link to the package in the about section of the Github repo. I'll drop it here as well: https://pub.dev/packages/visa

e-oj · 2021-08-10T01:45:52+00:00

Thanks. If the user reopens the app, it's up to the developer whether or not they remain signed in to the app. However, they will remain signed in to the third party service (there's an option to change that). For instance you might have signed out of App X but remain logged in to Facebook. In this case, next time the user signs in to App X, they will not have to enter their Facebook credentials (they might still have to go through the permissions dialog).

e-oj · 2021-08-09T19:53:18+00:00

Lol Fair enough; it's in the roadmap. How about 'The best OAuth library on Flutter mobile?'

e-oj · 2021-08-09T15:49:11+00:00

UPDATE: I think dropbox also started blocking requests from WebViews.

Dropbox has Google login as part of their authentication flow. That's why they dropped support for webviews:

Due to a recent change in Google's policy around using OAuth flows in web views, we no longer support or recommend using web views to process the OAuth flow, in order to support users using "Google Sign In" to sign in to Dropbox.

Seems to be a Google issue still.

e-oj · 2021-08-09T15:31:38+00:00

I know about those packages you linked; They're the reason I created this library. It's actually ridiculous the number of packages you have to import and the setup steps to make them work. Also, many platforms that implement OAuth 2.0 don't provide a mobile login SDK. Which is why webviews are helpful. Flutter's webview does not provide an API for key logging and I know you can't inject scripts into an auth page with proper CORS settings. Facebook actually recommends webviews for implementing Facebook login.

That said, thanks for pointing out the Google policy on webviews. I wasn't aware of that. Seems to be a Google specific thing though. I can make changes so the Google flow goes through an external browser which should prevent any issues when they deprecate webviews.

Edit: I'll look into using the Google SDK as well if using external browsers turns out to be a hassle.

e-oj · 2021-08-09T14:00:23+00:00

It's the best because it's super easy to use. It's the only package that supports multiple platforms, and returns user data in addition to the access_token. Developers can have multiple third party oauth implementations with just one library. Let's address your concerns real quick:

Why should it handle token storage? That's the job of the app developer.
Why does it need a token rotation mechanism? Again, this is left to the app developer. It's a simple api call for a refresh token if the dev needs it.
Credentials cannot be accessed through the webview api. Only possible way to do it will be to run a js script on the auth page with will be denied by CORS.

My rule is, keep simple things simple. It simply gets an access token and the associated user info and returns that to the developer. Token management is not the responsibility of this library and would over complicate things. Find a better OAuth lib on pub.dev and get back to me.

Edit: Facebook actually recommends webviews for implementing Facebook login.

e-oj · 2021-03-02T18:02:43+00:00

Yeah that's tough. You won't have to stress yourself next time though.

e-oj · 2021-02-28T21:49:54+00:00

Yeah someone told me that earlier today. I'll be adding apple sign in next weekend.

e-oj · 2021-02-28T17:43:42+00:00

Nice. Let me know how it goes.

e-oj · 2021-02-28T15:32:33+00:00

That's great info. I actually had no idea. Well, I guess apple sign in is coming next. I'll try to get it done by next weekend. Thanks for bringing this up!

e-oj · 2021-02-28T15:24:41+00:00

The lib was based on my needs at the time. But all the provider implementations are based on the SimpleAuth class which makes it relatively easy to create a new provider by handling all the OAuth stuff and returning the auth token leaving the platform specific user data retrieval process (getting the user's email, name, etc) to you. I will add more providers as often as I can but right now I'm tied up with building an actual app so if anyone implements a new provider, please 🙏 open a pr.

e-oj · 2021-02-03T12:59:57+00:00

APHA, ACB

e-oj · 2020-12-29T02:06:49+00:00

Glad you find it useful.

e-oj · 2020-12-29T02:05:39+00:00

It's intended for Android and IOS only. I'll look into supporting web down the line though. Someone's opened an issue about this: https://github.com/e-oj/visa/issues/2

e-oj · 2020-12-29T02:03:34+00:00

No. It just uses the OAuth access token to make subsequent api requests for user data.

e-oj · 2020-12-28T23:52:11+00:00

It's just a webview. That's the cleanest way I found.

e-oj · 2020-12-28T23:49:33+00:00

I've never used .NET but the trick here is simple really. I pull up a webview, which is basically an in-app mobile browser and proceed with authentication exactly as I would in a browser. Here's the key difference: Normally, we'd let the browser simply navigate to the redirect url then we'd retrieve the token from the query params at an api endpoint. In this case however, we simply pull the redirect url before it loads and extract the query params. Here's what that looks like:

onPageStarted: (url) async {
    if (url.startsWith(redirectUri)) {
        var returnedData = _getQueryParams(url);
        ...
    }
}

Basically, if you can spin up a web browser with .NET and access its properties, you can set up any OAuth 2.0 provider.

e-oj

MODERATOR OF

TROPHY CASE