Building Notice Application Form.Doc: Fill & Download for Free

Hey, I'm one of the founders @ rethink. FYI, my opinion on the matter is arguably the most biased you'll ever come across :) With that out of the way, let's get to the nitty-gritty!Alex Popescu is working on detailed technical comparisons -- we'll be posting these in the next few weeks. We're working hard to make these fun and educational, so even if you don't go with rethink, hopefully you'll feel your time is well spent. I can't cover all the technical details in the scope of this answer, so I won't try to duplicate this effort here. Instead I'd like to speak to the spirit of RethinkDB.Here's the rub -- while you have to read technical comparisons to make an informed decision, some products have a very strong visceral component that makes bulleted lists alone insufficient to understand what the product is about. For example, you can spend a long time reading about the differences between Java and Python, but until you fire up a Python shell and start typing commands, you won't have the intuitive experience of the ineffable quality that makes people fall in love with Python. This is very common in software development tools, and I dare say RethinkDB is such a product. Let's try to illustrate this with an example.Suppose, in a dash of whimsy, you decide to play with the U.S. census data and presidential elections polling data to figure out how many voters the democrats would have to turn to win the election in swing states. Here's what this query looks like in RethinkDB (in Python, but it's very similar in Ruby or JS):(r.table('county_stats').eq_join('Stname', r.table('polls'))  .zip()   .pluck('Stname', 'state', 'county', 'ctyname', 'CENSUS2010POP',  'POPESTIMATE2011', 'Dem', 'GOP')  .filter(lambda doc: (doc['Dem'] < doc['GOP']) & (doc['GOP'] - doc['Dem'] < 5))  .grouped_map_reduce(  lambda doc: doc['Stname'],   lambda doc: doc['POPESTIMATE2011'] * (doc["GOP"] - doc["DEM"]) / 100,  0,   lambda acc, val: acc + val)  .order_by('reduction')  .run()) (I won't get into the details of what this query does -- if you'd like to understand it, it comes straight out of the tutorial here: RethinkDB Documentation).Once you get past looking up the commands, you'll start noticing a number of striking things about this query:Everything is very pleasantly integrated into the host language. Doing math is just a matter of typing Python's math operators. Logic is very close to that (we use unary and because Python makes overloading binary and impossible, but once you learn that, it becomes second nature). Accessing documents is just a matter of using Python's native lambdas and bracket operator. There is a lot of machinery on the client side to turn this query into a ReQL syntax tree and send it over the wire to the server, but the user never has to worry about it -- the whole thing is perfectly seamless and natural.Joining two tables is just an eq_join command.You can chain complex commands just like in jQuery, which makes building up complex queries really intuitive.If you wanted to replicate this in Mongo, you'd have to write a rather long program. In big applications that adds up very quickly, and easily specifying complex operations makes an enormous qualitative difference. But there are some things about this query that MongoDB can't do at all!What's really special about all RethinkDB queries is that the program you wrote gets sent to the server, broken up into chunks, sent to relevant shards, executed completely in parallel (to the degree that the query makes possible -- complex queries often have multiple parallelization and recombination stages), but as a user you don't have to care about that at all. You just get the results. With MongoDB you'd have to do a large number of back-and-forth roundtrips between the client and the server, and if you wanted to achieve the same degree of parallelization, you'd have to have very intimate understanding of MongoDB internals. With RethinkDB, all of these details are taken care of for you, and you have to put no effort whatsoever into making this work.Of course the visceral experience you get from using RethinkDB isn't just about the query language, or parallelization, or pleasant client libraries. It's about hundreds upon hundreds of examples like it, some large, some small, that add up to a completely different product. The team is fastidious about every command, every pixel, every algorithm, sometimes even every assembly instruction (rethinkdb), so that people can use the product and at every step say "Wow, I can't believe how easy this was, how do they do that?!!"I'd like to point out that MongoDB also has strong advantages. RethinkDB is a new product -- it has been in development for three years, but has only been in the wild for a week, so we're not yet where we want to be in terms of user experience. For example, rethink isn't yet available on all platforms (rethinkdb), people still run into bugs (rethinkdb), and there are some missing features (rethinkdb). We're working very hard to fix these issues, but it will take some time before everything is sorted out.To give you an idea of where the product is going, our goal is for developers to say "RethinkDB makes distributed databases so painless, how did we ever build software without it?" We're not quite there yet, but based on the amazing early responses we got, I'm cautiously optimistic that we're not far from that goal.

For Google:The usual process would be to apply online through the careers page. The applications for the summer internships open by October and are open till March/April.A (better) alternative to this would be to have a college senior(or any other Google employee) refer you for the internship.Another option would be to reach out to a recruiter through linkedin or mail.Options 2 and 3 would increase the odds of your CV getting noticed.If a recruiter is interested in your application, he/she would set you up for multiple rounds(usually two, sometimes three) of telephonic interviews. The interviews would be telephonic - a Google engineer would call you on your cell phone and you would be expected to write code on a Google Doc shared beforehand with you.The interviews would be standard coding interviews and would test you on your Data Structures and Algorithm skills. The interviewer`s feedback would be forwarded to a hiring committee which would decide upon your candidature.If they approve it, you are selected for the internship. The host matching process (atleast for Google India) happens during March/ April during which you are asked for your preferences about the team you'd like to join.For the other companies, I think the procedure would be similar. And I am quite sure that the odds of your CV getting noticed by a recruiter would be much higher through a referral than otherwise.About how you can utilize your time in college, a few things off the top of my head:1. Do projects outside your regular courses. Build cool stuff. You would not only learn a lot but it will also help you get noticed.2. Contribute to open source. Read about Google Summer of Code (GSoC) and try to get selected in it. Your institute really doesn't matter for this. Having a GSoC in your second year would be a great learning experience of writing clean code besides getting a referral for your third year internship. 3.Competitive programming would help you sharpen your algorithmic skills. However there are other ways too in which you can improve upon your Data Structures and Algorithms - InterviewBit and geeksforgeeks are also useful while preparing specifically for interviews.4. Maintain a decent record in your academics. Remember it is probably the most authentic indicator of your interest and capability in computer science and will be looked at while considering you for your internships.

I didn’t follow any Udemy or course/schooling type websites and pretty much still mastered react. The way I learned react was to just start reading the documentation (it’s quite short if you ask me) and building stuff with it, do some more building, and then some more.The best way to understand it is to use it, fight with it, bump heads with it and get to the point where your so fed up with it that you want to throw that piece of trash in the bin. You should definitely have experience with JavaScript prior to React and that will be very helpful in your journey. But..here’s where it gets interesting, after you build enough small apps - you should have a lightbulb moment and you will begin to understand how to use setState, props, and the component life cycle hooks properly.As you can see from above, the learning curve for mastering Drupal actually throws the developer off the cliff a few times before they really start to understand and love it. Same idea applies here, however, you are fortunate that React is actually much simpler to learn compared to other frameworks such as Angular.Once you have struggled a little, now is the time to build something great - read the docs all over again this time trying to understand it, make notes of the syntax, write everything down, don’t follow more than a couple tutorials or you’ll be stuck in tutorial hell (other great posts about this). Try to let yourself get stuck and get yourself out of the situation without help AND if you cannot solve the issue yourself then of-course google away!Try to create something simple and work your way up. I started with react for the web and then transitioned to react-native as I found the web API far more easy to work with. And ofcourse my own experience was with building websites and not apps thus creating web apps made more sense. But now I am able to use what I learned with React to build awesome apps still using only React methodology - learn once, write anywhere.Here’s a list of things you can start to build right away:Simple weather appShould teach you how to work with external apisChat applicationLearn to work with internal apis (add message, delete message etc…)Todo AppShould teach you how to build components and how to break down things into smaller reusable components, but you should have already had that big EUREKA! moment in the previous apps.Calculater appTic tac toe (slightly challenging)Random quote generatorAirbnb clone or some sort of booking service that involves date & time fields, this can help you understand how dates work in general along with querying data from a database and retrieving data for your front-end. This can be broken down into a few simple components:Dashboard (Show random or chronologically listed items)Add listing pageFull view mode for listing (page/component to see full data for any listing)Start to build things you want to build :) you will realize React in 2018 isn’t all that much different from react in it’s early days. Under the hood it has changed dramatically but it was done so well almost no one noticed it.So to answer your question which I think is how should I learn react? I cannot provide you a list of resources but I can provide you with things you should start to build.