meanJim

Great point, thanks for the clarification.

1. Thanks for the feedback! I think that's a really great point. We believe it is also important to optimize for the developer that wonders if a library will work on everything if they use it.

When we help people, people tend to be confused when a library fails to work on Android and not iOS, and vice versa. We should do a better job about communicating this is a smart way.

2. Our intention was to help the React Native community. In the hypothetical: native.directory could be filled with libraries that aren't compatible with Expo and it would be fine with us. Expo happens to care a lot about React Native and is also a part of this community. There is no disingenuous motive behind our intent.

It is a manual process right now

We ask people to add libraries, and when they submit a PR they need to specify whether or not it works on Web, Android, iOS, and Expo.

We launched this website to help anyone find React Native libraries. We think its helpful because its not always clear what you can use.

If you want to see the code, feel free to do what you want with it here: https://github.com/expo/react-native-libraries

Let us know how we can help you!

I got really excited until I realized I couldn't use JavaScript. Over the last year I got super passionate about making the smallest JavaScript bundle size possible with RiotJS or Preact.

I guess they really mean the old school 'website' (like the html 1.0 strict days), so maybe a html document with everything inline and no special fonts.

I usually supplement the interview with a take home project, because front end web dev (emphasis on web) is about building interfaces and managing state really well and that is hard to test in an hour!

Some of the more domain specific stuff is about building a scalable components library that your team can use, testing your code, building assets in the most elegant way possible (gulp, webpack, grunt). So make sure you're very honest with your resume!! (dishonesty is bad).

For the case of front end web, here is what I would ask from the top of my head (thinking aloud):

- A good interview will have some pair programming. I usually like to give a very simple mock. These mocks will have a simple task where I will ask you to implement me a two column layout, or a popup window. Therefore I'd like to see that you have strong fundamentals of CSS, HTML, and Basic DOM manipulation using JavaScript. Nice interviewers will allow the use of google!

- You should understand how a network request and response works. I'll probably ask you to teach me what an AJAX request is to start. I hope to have a good conversation because I forget things often and like to learn from others.

- I will probably ask you what are some ways to implement components that won't produce side effects in a large codebase.

- I will probably ask you questions about how you plan to work with Design and other product stakeholders to ensure that you're able to iterate quickly on the front end. This is because requirements and design changes frequently (more common with companies that are focused on product versus growth/retention).

- I will ask you how you approach testing, and how do you ensure your interface will work cross browser, cross device.

- If you're really a generalist and you have no front end experience but a lot of other programming experience, I'll probably ask you to serialize a network response with JSON, where you'll create a map of ids and their resources (for fast access!) and walk through an object tree to do this. We can probably pseudo code this if you've never touched JavaScript and know nothing about its data structures (this jon snow case is rare, like jon snow).

- If you're really junior I'll ask you a generic algorithm question because I'm probably going to train you on the job anyways. No one should be punishing junior people for being junior with stupidly difficult domain specific questions. Don't work somewhere where they punish you for being junior because they won't realize how much potential you have (you have a lot).

Last note: Good luck and have fun, remember to be yourself and try your best.

There is room for both the passionate and non-passionate developer.

Because passion doesn't necessarily equate to skill. Passion looks like an eagerness to be immersed in a topic and invest time in that topic. Some people work out of necessity and not necessarily passion (maybe just passion to make a living, pay the bills, and support their families).

What actually matters is that you:

- follow through with your promises and claims to your team or manager/boss/founder/yourself

- you leave things better than you found them

- you're reliable

If you adequately do those things, there is plenty of room for you, passion or no passion.

This looks so useful, I feel like people make requests for this kind of data all the time. Automating this just feels smarter.

Wow I love this so much. The attention to detail is incredible. Unfortunately using hydra.exe forces me to have to refresh but I bet that's probably intended!

I'm really happy this developer stuck through and made this game. It's really inspiring and it shows that not all projects have to be motivated by external motives. Sometimes you just want to make something because it matters to you.

"Invest in reusable training materials to onboard new engineers."

So important! Doing this really helps keep people on page and limits the amount of time spent arguing about semantics or why we came to a certain decision.

How does Uniloc honestly sustain itself as a business?

Lol I've gotten so many down votes. I disagree, and I wish people would leave room for discussion instead of being so quick to plaster me with down-vote bullets for what I think.

Piracy in my opinion is rampant. For example: You can go on the pirate bay and pirate the adobe cs suite, microsoft office, your favorite albums, your favorite movies, with ease. You are (if you forgot) supposed to pay for these things.

And this level of access is available to everyone with an internet connection.

I'm not talking about "profits", we all know big media makes enough money to stay afloat & some. But you can't make the assumption that everything is a lie.

I hate it when people go to extremes, and I admit that my claim may be assumption you don't agree with. :/

I think I was a little misinterpreted

This is a good thing, piracy is illegal. If there wasn't rampant piracy we wouldn't have to worry about idiots drafting up bills like Protect-IP and SOPA.

Merry Christmas! Thanks for all the great articles

Do make sure the company you switch to isn't supporting SOPA either, cause that would be embarrassing.

I would really rather Anonymous just stay out of this. Kind of taints the purity of the Anti-SOPA campaign and its never good to be associated with criminals, especially the ones who expose active duty undercover cops who have dedicated their lives to protect us. Just saying.

I could've sworn I read a post from them yesterday saying they didn't care and it wasn't affecting business.

"This used to be funny, but now it’s really just terrifying. We’re dealing with legislation that will completely change the face of the internet and free speech for years to come. Yet here we are, still at the mercy of underachieving Congressional know-nothings that have more in common with the slacker students sitting in the back of math class than elected representatives. The fact that some of the people charged with representing us must be dragged kicking and screaming out of their complacency on such matters is no longer endearing — it’s just pathetic and sad."

THISSSSSSS

Thank you so much for clearing that up with me. I do agree with corporations having the copyright act and the DMCA to protect their intellectual property rights.

I'm no expert, but this really sucks that we've reached this point. Can we just come up with a better bill? Why does it have to be this one that every media corp wants to go through.

Jack Dorsey made a pretty good statement during his interview on APD. it went the along the context of "trying to take a really complicated idea/process, and making it simple". And that is very hard.

agreed.

I applaud you for all the things you've achieved, it's pretty commendable ( always like to hear stories about people working hard and getting stuff done ). But the truth is, it wouldn't hurt to go and take the time to re-visit the topics he mentioned and tie up loose ends. It would help your career regardless of what was said here. 2 cents.

He has accomplished a lot, and we all try to stand on the shoulders of giants.