Great point, thanks for the clarification.
18 karma · joined October 31, 2011
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.
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.
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 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.
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.
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.
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.
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. :/
THISSSSSSS
My advice is bias.
You probably aren't in the last 2 and a half years of the program yet where you do coding projects. I find that I don't have to be at every class ( although I go anyway ) to do well in those because a lot of it is coding and completing projects. (Binary Tree, Hash Tables, Disjoint Sets, Linux File Systems, Building an Operating System).
Whats my advice?
Suck it up. You will convince yourself you love to learn from people you have paid to listen to that you don't fully respect (you didn't fully respect your teachers in high school from the sound of it), you love to learn computer science because you love how close it is to pure creation (in my opinion). You love the fact that with the foundation that you pick up you will be able to build wonderful applications for millions of people to use.
There is no secret, listen to what your lecturers have to say, take notes, and just do it.
High school is easy, college is easy, computer science is not. You can't allow yourself to get use to that 'selective' hearing bullshit. But I have faith in you, life is all about effort and if you actually put the effort in you won't struggle in the long run.
Or maybe the major isn't for you. My 2 cents.
Oh.