Consolidated Search Engine Results

Create A Portal With a search box and provide functionality of search.
The results Page Displays Top 10 Results each from Google , Bing and Yahoo.com
and user gets to choose from different search engine results.
The page is divided into 3 columns for results from each of the search engines.and a close button to hide the unwanted results.

Advertisements

What can I learn right now in just 10 minutes that could be useful for the rest of my life?

Answer by Shibu Lijack:

Find Direct Download Links using Google.

Tired of torrents running out of seeders? No worries. You can search for direct download links using Google!

To download movies, perform a Google search as below:

YOUR SEARCH TERM HERE” -inurl:(htm|html|php|pls|txt) intitle:index.of “last modified” (mkv|mp4|avi)

Example:
Titanic -inurl:(htm|html|php|pls|txt) intitle:index.of “last modified” (mkv|mp4|avi)

You can use this search trick to download not just movies, but almost any file.

For instance, to download music,

YOUR SEARCH TERM HERE” -inurl:(htm|html|php|pls|txt) intitle:index.of “last modified” (mp3|wma|aac|flac)

Just change the file format [(mp3|wma|aac|flac) part] to your required format and you will get a search result of sites containing direct download links to your search query. Enjoy!

What can I learn right now in just 10 minutes that could be useful for the rest of my life?

How much time did you spend preparing for Google’s interviews?

Answer by Andrew Latham:

Four weeks.

Context:  I was interviewing for a full-time position after graduation.  I passed the phone interview in mid-July and had maybe 3-4 weeks to prepare for the on-site.  Google was my first interview in two years and my first interview for a full-time position in any company.  In the end, I got an offer, which I accepted.  Here is what I did.


There were two different parts to this, knowledge-based preparation and comfort-based preparation.  The purpose of the knowledge-based part is to refresh the basic-to-intermediate computer science stuff that you've forgotten but that you need as a foundation for your intuition and understanding.  The purpose of the comfort-based part is to get to the point where you can be comfortable, confident, and relaxed fielding questions from Google.

Like Gayle said, the questions Google asks are really not that hard or different from the questions other top tech companies ask.  You don't need to memorize how to do X complicated algorithm or spend 10,000 hours becoming such an expert in interview questions that someone could ask you a research question for an algorithms grad student and you could solve it in 30 seconds.  Realizing that the space of questions you'll get is not actually all that enormous is key to focusing on the right knowledge and becoming comfortable going in with what you know.


First, the knowledge-based preparation.  Basically there was a bunch of stuff I had learned and then didn't really remember.  So I had to go make sure I remembered it all again.

Review data structures and algorithms
I already had a pretty good grip on these because I had done enough interviews before that the basics were pretty internalized.  Instead of looking at the more complex algorithms in the back of the Algorithm Design Manual I just focused on hashtables, heaps, linked lists, etc. basically the algorithms and data structures covered in a standard intro course.  Went up to AVL trees and Dijkstra's algorithm.  I also made sure to review tries, because I was expecting a lot of questions involving text data.

Fall in love with algorithms, again
I had some notes from the second half of Algorithm Design Manual and went through them one night just to rekindle my old love of algorithms by re-acclimating myself with all the awesome possibilities for algorithms there were.   I wasn't asked to implement anything complex like these but it was always fun to have a conversation after solving a problem that started with "you know, there's actually a crazy algorithm out there, I forgot what its name is but basically it does this… and you might actually be able to solve this problem way faster with it."  Then the interviewer and I could have fun just talking about a cool algorithm I vaguely remembered and how it could apply to the problem, which was great.

Review operating systems, networking, computer architecture, system design and scalability
I only spent a weekend on this, just re-reading my notes from when I took the respective classes to remember how computers and systems worked.  I never took classes just on scalability or system design, but had a pretty good intuition from projects and internships, so I just Googled some stuff to get a good idea of what the standard tricks were to make things work on a large scale so I could know I wasn't missing anything basic.

Get really comfortable with language of choice
I chose Python, so I started from the basics by re-doing "Python the Hard Way" up to the big Django program, and then crawled around through the Python API, Python Quora/StackOverflow, "Pro Python", Google's Python Style Guide, and some Python blogs (including Guido's blog about the history of Python) just to really get myself in the Python environment and mindset after having programmed in Java for Amazon for the last three months.  Whenever I ran into something that I didn't know, or something that I knew I forgot all the time (i.e. conditional list comprehension is for…in….if, not for…in…where like I always want to use) I wrote it down in a Notepad doc.  I could have just used Java, but I found Python much easier to whiteboard and think clearly with.  Also critical was figuring out what the APIs and standard implementations for the different data structures were in Python (There's a Heap API, most of the rest you have to do yourself) so I could just whip them out in the interview.

Learn Google stuff
I did this before the phone interview, but basically I just skimmed the papers about Google File System, MapReduce, and BigTable so I had an idea of what they did, and then read a little about the history of Google and what its current goals and major products were.

Basically, the knowledge-based preparation was a couple evenings spent reviewing data structures and algorithms, then one weekend that was "Computer Science review weekend" and a second that was "Python review weekend."


On to the comfort-based preparation, by which I mean being comfortable solving problems during the interview.

Problem solving
Most of the rest of my preparation was just going through Elements of Programming Interviews (Elements of Programming Interviews: The Insiders' Guide: Adnan Aziz, Tsung-Hsien Lee, Amit Prakash: 9781479274833: Amazon.com: Books), which is great because it just has tons of problems up to a really high level of difficulty (if you've ever studied chess, it's analogous to the famous Imagination in Chess).  I'd randomly pick problems, solve them in pseudocode on paper, and then write solutions in Python and test them on some basic cases to make sure I was doing the right thing.  Usually only 1, maybe 2, problems a day on those days I did work on it — the quantity of problems wasn't what was important so much as just figuring out what the typical mistakes I was making in Python were and sorting them out.  It didn't take long to figure out which sorts of design patterns in Python I was most comfortable with, and after that things started going much faster.  I used PyLint to make sure my code wasn't sloppy.

Sometimes I looked at the answer if I wanted to feel good about myself after solving a problem, but usually I'd skip it if I knew I was right; if I didn't know how to solve it I'd never peek, instead I just let it sit in my head for a day or two until the answer hit me.  Some days before walking to work I'd look at one of the "very hard" problems over breakfast and think about it on the walk; I usually couldn't solve these but just thinking about them helped me build creativity and get comfortable using my knowledge to throw different solutions at a problem.  I also did some practice with friends to work on my ability to explain my answers and not feel as nervous during the interview.

The main thing, though, was that while I was doing this I noticed that there were a lot of thinking patterns, and that for certain problems once I figured out what kind of problem it was there were easy patterns I could jump into that would go right to the solution  i.e. "stream of data where we want to find some sort of representative?  Sounds like a heap problem."  I never really wrote them down (kept meaning to but forgot) but they were pretty well internalized after 30-40 problems.  EPI is a really good book for this because a lot of the "easy" problems are pretty simple but strike at the core of the concepts for those types of algorithms — a lot of other books give questions that have a lot of edge cases or complexity, and those aren't as good for building intuition.

Keeping it real
An important point is that I didn't overdo it here.  I only spent maybe a couple hours every few days working on the above.  The rest of the time I spent relaxing, spending time with friends, going to concerts, etc.  Keeping grounded in reality and maintaining your personality, I think, is an important part of preparing for the interview, because it's easy to get so lost in your preparation that you forget who you are, you define yourself by how ready you are for the interview, and I think that makes you really fragile and cold.  The end result of doing things this way was that instead of being anxious and afraid of my interviewers, I was able to talk to them, have a laugh about the whiteboard quality, connect with them; then when the questions came, instead of feeling like they were coming from some sort of Google God who was judging my destiny, they just had the same vibe as a buddy asking me a question after work.  If I had spent four weeks as a shut-in doing nothing but solving programming problems, I wouldn't have been able to be as friendly or happy — instead, I would have been constantly thinking "OK, come on, let's get to the questions, I have to do this perfectly, I spent four weeks on it."

Don't let it be a once-in-a-lifetime chance
Finally, have some other options.  Don't let it be your one big chance to get into Google.  Realize that you can always apply again next year, and apply to other companies at the same time, just to keep your wits about you and not get nervous and stressed out by putting too much significance on every minute of the interview.  Besides, this is probably one of the few, if not the only, times in your life when you'll be so ready for a tech interview; why waste the moment just interviewing with Google?

Anyway.  That is what I did and it worked for me.  If you have a CS degree, you probably already have the knowledge you need, you just have to go build the ability to access the parts of it that are relevant for the interview in an organized and quick fashion.  The key is just to get to the point where you're comfortable and relaxed during the interview so you can think clearly and have fun.

One final thought.  A lot of the suggestions on here are like "look at all these links, these are mandatory" or "you need to know all these things" which I think creates the impression that you need to know **everything** and that if you miss one thing you're doomed.  That's not a good mindset to have because you'll be focused on the wrong stuff — you'll be focused on thoroughly understanding every corner of CS rather than actually having the confidence to solve problems.  Knowing stuff is important, but you have to draw the line somewhere.  Becoming extremely comfortable with the core of what you know is more important.

Also, it's really tempting to want to be as thoroughly overprepared as possible and understand the theoretical justification for A* or memorize all the string methods in Java or what have you, especially if you have a long time to prepare, but trust me, you won't need to know that stuff, and if you fill your mind with it it's just going to be like fat on a muscle, and the amount of time you waste learning it will hurt you a lot.

How much time did you spend preparing for Google's interviews?

I am looking for a new book which is worth reading. It may be fictional/non-fictional/motivational. Any good book that you have read and …

Answer by James Altucher:

I highly recommend all the books written by the guests of my podcast:

"The James Altucher Show"

(format is: name, blog (if they have one), and then their books. I hope this is useful to people.)

TIM FERRISS
The 4-Hour Workweek and Timothy Ferriss

JIM NORTON

CONGRESSMAN TIM RYAN

PETER THIEL (coming later this month)

TUCKER MAX
TuckerMax.com

MATTHEW BERRY
The Ultimate Fantasy Football Resource

PAUL OYER

ROBERT GREENE
Power, Seduction and War | The Blog of Robert Greene

RYAN HOLIDAY
Meditations on strategy and life

SETH GODIN
Seth Godin

STEPHEN DUBNER
>

STEVE SCOTT
Kindle Publishing Tips and Authority Internet Businesses

STEVEN KOTLER
The Rise of Superman

TOM SHADYAC
Page on lifesoperatingmanual.com

GARY VAYNERCHUCK
Gary Vaynerchuk

GREG ZUCKERMAN
Gregory Zuckerman

HUGH HOWEY
Best selling author of WOOL and the Molly Fyde series

KAMAL RAVIKANT
Page on foudnerzen.com

LEWIS HOWES
Lewis Howes

MARC ECKO
Marc Eckō Cut & Sew

MARK CUBAN
the mark cuban weblog

ADAM BRAUN
Home – Adam Braun

ADAM CAROLLA
The Adam Carolla Show – A Free Daily Comedy Podcast from Adam Carolla

AJ JACOBS
AJ Jacobs – Official Website

ARIANNA HUFFINGTON
Breaking News and Opinion on The Huffington Post

AUSTIN KLEON
AUSTIN KLEON is a writer who draws.

CHARLIE HOEHN
CharlieHoehn.com

CLAUDIA AZULA ALTUCHER

CHRIS BROGAN
chrisbrogan.com

DAN HARRIS

GABRIELLE BERNSTEIN
Gabrielle Bernstein, Inc.

DR. WAYNE DYER
Dr. Wayne Dyer – Internationally renowned author and speaker – Official Site

I am looking for a new book which is worth reading. It may be fictional/non-fictional/motivational. Any good book that you have read and …

What is something every person should experience at least once in a lifetime?

Answer by Shikhar Agarwal:

Failure

Before you think negatively about this, please read on!!!

In one single moment, you would realize the value of life if you have taken it for granted. You would realize what it feels to be someone whom you conveniently mocked and laughed at. You would understand how it feels to be someone who is blamed to be incapable even though he is more than capable for a job. It is enough to bring you to the ground, make you humble and caring.

In search of happiness and motivation to spring back, maybe you would realize that there are millions of people out there who are in worse conditions – with no money, food or shelter, and thus, might lead you to inculcate compassion and a feeling of social responsibility.

It will help you to know yourself – what motivates you, what you did wrong, what makes you happy and so on, ie you would know thyself. It will help you develop better ideas, new approaches and would make you a better human being.

And yes, it will make your success that follows much, much sweeter.


Follow on:
Life: What is not important in life?

What is something every person should experience at least once in a lifetime?

What are some practical ways to become a nicer person?

Answer by Shikhar Agarwal:

Here are 10 ways that I have found very useful till now:

  1. Listen. And keep that smartphone away: I come to you, excited and all, to tell you about my party last night when in the middle, your neck start to "oscillate" between looking at me and at your phone. You see, I know you are smart enough to listen and type at the same time, but I don't give a damn. This  is not only rude, but gives me a feeling that I am not worth your time, which is not nice. So make sure you listen without breaking the conversation and give your 100% attention.
  2. Make people feel important and good: Show interest in them. If some one comes and tells you about their recent trip, listen to it, maybe ask a question or "like" their Facebook photos even though you might not be even remotely interested in this. Make a person feel important for the work he is doing. The next time you see your office cleaner, tell him, "Wow, the floor looks so clean, I can even see my face's reflection!" and see him smiling and probably blushing. I see you smiling 🙂
  3. No Bitching please: You to A, "Hey that's a lovely dress!", and then moments later to B, "This is the 3rd time she is wearing that dress this week…and you know yesterday A went to…and did that…". You might come in good books of B, but sooner or later, people would realize this nature. Don't ever be a two-faced person.
  4. Earn trust, maintain it: I know it's very hard to digest that secret – it's so tempting to tell atleast 1 person! If you tell A's secret to B, then B also gets an indication that you might tell B's to C, so you lose everywhere. Either don't listen to some personal stuff, or learn to digest it.
  5. Smile and greet: A small smile with the words "Good morning" or "Nice shirt" can do wonders. Ask these little questions "How was the weekend?" or "What's your plan for the vacations", or simply "How are you?". These don't take any time, but are very pleasant and sweet.
  6. Be polite and avoid sarcasm: Remember that more the fruits, more the tree bends, and empty vessels make more noise. Be humble and polite when you talk to others. And use sarcasm only when you are talking to your friends who don't mind. A polite "no" is much better than "yeah, right." The other person automatically feels respectful.
  7. Be sincere and reliable: How would you feel if I had promised to wake you up at 8 am for your interview, and then forgot because I had partied all last night? However important the thing is either don't commit, or fulfill it. Obviously certain times you won't be able to, but this should be an exception, not a norm. And pay attention – I said be sincere, not serious…always be fun!
  8. Act, don't react: Suppose you write a thoughtful Quora answer, and someone puts a mocking comment there. Don't you feel like reaching down his throat, pulling his intestines and tying it around his throat? But best is to drink your anger and ignore it, or put a witty reply. This is what is Quora's Be Nice Be Respectful (BNBR) policy.
  9. Be genuine: Unless you are from the league of Christian Bale, Tom Cruise, etc, chances are people would know when you are faking it. Whatever you do, do it with your heart and mind in it.
  10. Know thy self: Be aware of yourself, your nature, your mood swings, what makes you angry, what makes you lose your temper and so on. This would help you to understand why you behave in a certain way in a situation, and you would be able to control and improve yourself. How can you be nice to someone else when you are not nice to yourself first?

All of these are pretty easy to implement without putting any significant efforts. Practice these consciously and soon they will become your habit.

What are some practical ways to become a nicer person?

Why do we all love children?

Answer by Miraz Zaidi:

We love children , because:

  • They are innocent.
  • They laugh loud when happy

  • and cry hard when sad.

  • They are honest.

  • They don't care what others think of them, even if they roam around naked.

  • They believe in God but don't have religion.

  • They love people for how they are, and not who they are.

  • They believe everything is possible. (Yes, flying too.)

  • They believe cartoons are real.

  • And they don't always need a bed to sleep in.

  • They are everything we wish to be, again.

So, what's not to love? 🙂

Why do we all love children?