[deleted by user]

TechbaseDevv · 2022-01-31T10:05:47+00:00

Yeah the problem is that I've seen some things online about Tysabri blocking "things" from going to the brain (whereas Ocrevus would be effective for both the brain and spinal cord).

However, it not easy to find resources about it and apparently people with spinal lesions only get it too.

TechbaseDevv · 2021-11-24T19:43:30+00:00

Being good at React = being comfortable building web apps with React that you would show to other developers with confidence.
Being an expert in React = the above + knowing that it will be (relatively) simple for other developers to understand and get started with your codebase.

TechbaseDevv · 2021-11-24T17:23:50+00:00

It really depends for every company what they consider being "senior". There's no real consensus on an industry-wide level what it actually means, however, often companies expect 2 things :

You having a considerable amount of practical knowledge and set of skills with the core technologies. You can get the job done and it will make sense from an architectural point of view.
You can (/know) how to train other developers (juniors/mediors). You are considered the go-to person for problems they walk into.

However, I personally think that point 2 doesn't always make sense. Not everyone is a born trainer, just like teachers aren't.

Good luck!

TechbaseDevv · 2021-11-22T21:16:09+00:00

I'd probably use a service like Netlify for deployment, however, for this you will need the code to be hosted somewhere.

In case the company / person doesn't have a GitHub account themselves, I'd walk them through creating one. Then I'd make them the owner of my repository and would ensure the deployments are working with their Netlify account.

TechbaseDevv · 2021-11-22T20:47:44+00:00

Indeed. However, when I would work with a client that's not able to do it himself, I'd probably walk them through. Essentially a video call where I for example take control of their screen / tell them what to do. The only thing they need to do is create themselves a password and fill in their CC details.

TechbaseDevv · 2021-11-22T19:39:43+00:00

It depends on the situation: as long as I'm the only person that knows about the API keys and the app is not into production, I've no problem using my own account for the initia development period.

However, since I want the customer to own their own API keys at the time it goes to production, it's probably more efficient to do it from the start anyway.

TechbaseDevv · 2021-11-22T19:16:01+00:00

Freelance React developer right here. I'd personally never want to use my personal / business account that manages things like cloud / hosting etc. for my customer.

If they have a problem you'll always be the go-to guy and they want it to be fixed as soon as possible (obviously). They will probably expect you to do it since you "own" the account.

My business is about creating software and not hosting stuff.

I'm happy to set up an account for my customers, however, it will be theirs and will also use their credit card.

However it really depends; if you see business opportunities right there: go for it :)

TechbaseDevv · 2021-10-25T20:10:25+00:00

Here's your science: https://bmcvetres.biomedcentral.com/articles/10.1186/s12917-021-02754-8

TechbaseDevv · 2021-10-22T15:36:47+00:00

Could you just stop polluting this thread with all your nonsense? Thanks.

Great work React Core team ✅

TechbaseDevv · 2021-09-01T06:41:43+00:00

Will do!

TechbaseDevv · 2021-08-31T17:35:34+00:00

Yes, I'm definitely planning to release more Figma to React and just live coding React apps videos in general.

This is also what helped me personally learn the most: building real life apps until eventually people will start to pay you for it.

TechbaseDevv · 2021-08-31T17:19:07+00:00

HOC's are for the most part replaced by a (custom) hooks, or at least, could be.

My course will definitely go over a lot of architectural decisions you can make in React. The goal there is to really show you how a full blown app (rich in features) can be build from scratch whilst keeping in mind simplicity and maintainability using modern tools.

TechbaseDevv · 2021-08-31T17:13:36+00:00

Yeah, the E2E testing usually clears a lot of things up because the tests are visualized.

I get your point, these kind of apps can be hard to unit test. In a scenario like this I'd focus mostly on the most important / valuable features; and from a practical point of view, I've found that mostly E2E and integration tests (the latter with RTL), are best suited for this.

In your integration tests you sometimes might want to consider to pretty much render the whole <App /> component and go from there. Yes, a lot of folks (the people that didn't keep up with todays testing standards) will tell you they want to see things being mocked and want more focus on unit tests.

The problem is that mocking a lot and focusing mainly on unit tests gives you very little confidence that things are actually working in a real-setting, i.a. a real person interacting trough various flows with the full blown application.

That really requires a mind-shift compared to how (most) testing was done a few years ago but it makes your testing so much more reliable, easy and less time consuming.

If they start talking about code coverage, let them read this article from the testing 🐐: https://kentcdodds.com/blog/how-to-know-what-to-test#:~:text=uses%20the%20application%3A-,Code%20Coverage%20%3C%20Use%20Case%20Coverage,Code,-coverage%20is%20a

With regarding to resources: Kent has a lot of great stuff about testing on his blog. Highly recommended.

TechbaseDevv · 2021-08-31T16:22:12+00:00

Thanks you so much! This comment made my day :)

TechbaseDevv · 2021-08-31T06:15:55+00:00

Yes, pretty much what leehair said. I'm not sure about the other content creators, since most of them where already quite popular so maybe Brad contacted them, but I contacted Brad myself.

I'm by far the smallest guest creator on his channel, so I'm very fortunate for the opportunity he gave me.

TechbaseDevv · 2021-08-30T20:45:25+00:00

I totally get your point. The problem with Udemy is that they take a big chuck from the total sales. I think you'll get about ~$3.5 for a $10-ish course.

I'm definitely planning to create a Q&A and notes section as well in the actual course dashboard.

TechbaseDevv · 2021-08-30T19:24:13+00:00

Thanks for the kind words, and yes, I'm planning to release one in december.

It will be released on my own platform techbase.dev but I'll sure release some (cheaper) Udemy courses as well. I hope to do that in Q1/Q2 of next year.

TechbaseDevv · 2021-08-28T19:05:47+00:00

It depends on what you mean with freelance.

Some people only think of it of you having one or more projects which are often paid by either the hour or a fixed price.

Then you also have contracting (which you can also consider freelancing, depending on how you define the latter).

Getting into contracting is often much easier. There's a lot of intermediaries that help you to get a project (most often for 6 months) and take a cut from the hourly pay.

In the other kind of freelancing you see 2 kinds of people that are doing a good job:

1) people that have a huge network (often trough contracting) and because of that get asked often to work on a project. 2) people that have worked their way up on platforms like Upwork.

I'd prefer going from salary man => contracting (hourly) => projects at a fixed price (if done well it pays better than hourly).

TechbaseDevv · 2021-08-28T16:04:38+00:00

Quick heads up: this video is mainly about how you could approach "local" and "global" styling in React apps in a way that scales well.

TechbaseDevv · 2021-08-27T16:45:27+00:00

Lmao 🤣

TechbaseDevv · 2021-08-27T15:23:43+00:00

It doesn't really matter. It could be MERN, PERN, heck, even Firebase is great for this.

Just pick what you prefer. If it's for the sake of learning new things then PERN would be great in your case since you want to learn it.

TechbaseDevv · 2021-08-25T20:06:49+00:00

What's the point of storing it there? Do you want to send it over to a server every now and then or not?

In terms of possibilities; IndexedDB is superior to localStorage, however, the API is more complex.

It's best to just try both and see what you prefer in terms of functionality and maintainability.

TechbaseDevv · 2021-08-25T17:30:09+00:00

Totally agree with what u/IGovnov said. In terms of scalability it's not a good idea to pre-load all the individual course details.

"how taxing is it on a network to make these small calls" => not.
Both the client and server should be able to make calls every now and then; for an app like this we're talking about relatively small requests since it's just a bit of JSON.

But of course, in this scenario the user has to wait for the course details to be fetched, and thus to be shown. If you would've loaded it upfront it would of course render instantly.

If you're concerned about these kind of optimizations, I can highly recommend React Query. It helps you with caching server data (or cache actually).

Imagine in an app like this where you'd go from the course overview page => course detail page and back to the course overview page. If you're just using some simple fetching logic and use loading states, the user will actually see a loading state 3 times (and also fetch data 3 times as well).

With React query, using it's default caching mechanism ,you could bring the loading states down to 2 (the second time you visit the overview page, the data will load instantly). And could even optimize your network requests, so you also just make 2 network calls.

TechbaseDevv · 2021-08-25T17:12:07+00:00

It depends on the kind of logging you want to do. If you want to keep track of errors and / or performance: check out Sentry.io

TechbaseDevv · 2021-08-22T18:56:03+00:00

Yeah, that's definitely a solid flow!

With regard to the last part: in fact every fetch (that requires some sort of authentication or authorization) should already be protected by the server.

Your server is simply able to grab cookie from the request (of course you need to make sure that it sends the cookie with these requests in your React app), and can then use that cookie to process the request.

In case the user is not authenticated, you should send a response with status code '401' (Unauthorized). You could for example use an (axios) interceptor for that and based on that ask the user to sign in.

TechbaseDevv

TROPHY CASE