thrashh · HackerTrans

il y a 3 ansdiscuss

No but for a popular job listing in a well known company with hundreds of applicants, there are going to be dozens of people who have similar experience as you, plus have the exact qualification that they are asking for, putting you at an automatic disadvantage.

thrashh

il y a 3 ansdiscuss

Well I mean your experience isn’t any different than applying for a job that uses Python when you’ve only used C++.

Sure, they can train you to learn Python, but they’re specifically looking for a Python developer. They’re not looking for a generic “person that can learn stuff” when there are many Python developers out there that can pick up the job day one.

In your case, you had to put in a lot of work because you essentially were switching specializations.

thrashh

il y a 4 ansdiscuss

I don’t have a repo to show but I’ll try my best to explain

First I want to note that I do use React hooks. If I can some UI code in React, I will. DOM code would go in React

I just won’t put business logic in React ever. No non-UI side effects and no external state are allowed in my hooks

I still want my React components themselves to be a reusable library. My applications are basically a reusable logic library coupled with a reusable UI library. It’s that division that makes this style easy to read - your brain is either in UI mode or business logic mode. You never confuse yourself trying to figure out what it’s doing because you can just read one side and ignore the other

Whether you use a fat root state or not is honestly up to you. It’s really the separation that is key

I’d check out mobx examples

I know that’s not super specific and there are edge cases that you’ll run into, but my public repos are either Java and non-UI JS libraries ):

thrashh

il y a 4 ansdiscuss

What had always worked for me is that I write the web app as regular classes / objects, make it observable with mobx, then add React as essentially a template library — like as if it was mustache.js or something.

The non-React code works on its own and is super easy to understand. You could even extract the business logic and make it a CLI or a reusable library.

Shit, all my apps - Java, C++, whatever - have always been structured like this: domain logic + a decoupled frontend. I pretty much only adopt libraries that match my way. Redux did not match my way

My coworkers from past jobs tell me the way I structure my projects is so clear so I think I’m on the right track

thrashh

il y a 4 ansdiscuss

I always thought that iPhones weren’t more efficient — they just dropped a major feature: running background apps.

I remember being able to run Ubuntu in the background on an unrooted Android phone while browsing the Internet. You can’t do that with iPhone.

That said, I rather have battery predictability over features, but I always thought that if Android dropped background apps, they would have the same battery usage as an iPhone.

comments