olivolive

This is a great idea, and looks very nice! Several of my friends are pregnant right now, and they are all registered at multiple places. This would be very convenient.

If I'm buying a gift for a friend, do I need to know their mailing address in order to have it shipped to them? It would be amazing if this took care of that for me.

This is an interesting idea, and I like your site design.

You have two types of users, the business owner who offers appointments, and their customer. You've done a nice job showing what the end customer will do to make an appointment, but you haven't explained what the business owner will have to do to get set up. The business owner is the one making the decision to use your service. I would change the How It Works section on the main page to be from their perspective, and keep the current How It Works to show what their customers will see.

Some co-workers of mine have been doing 365 projects for 2010. On their server, each photo has a comments section where they give each other feedback and suggestions. That community aspect has really encouraged them to keep going. They talk about how hard it is to find something that makes for an interesting photo every day, but it's made them pay attention to their surroundings, and the feedback is making them better photographers.

One guy was pretty intimidated by the project at first. He started by trying it for a week, and now he's done 320 days or so.

They had their own server, but it recently died. The photo are copied elsewhere, but the comments are possibly gone forever. I'm certain that any of them would pay $20 for someone else to take care of the servers.

The essays at the beginning of Holub on Patterns completely changed my understanding of OOP.

Implementation inheritance violates encapsulation. So do getters and setters. They let code outside your object rely on your implementation and make your system brittle.

WikiLeaks has said that their next leak is from a major US bank, and they'll be releasing it early next year.

There's some guessing that it's BofA, because a year ago he said:

"At the moment, for example, we are sitting on 5GB from Bank of America, one of the executive’s hard drives"

A reason I've heard is that they want people who really want to work at The Company, not people who are motivated by the pay bump.

If you find out the name of someone who will be interviewing you, and they have a LinkedIn profile, you'll find out their job title, and possibly their whole resume. That should help you prepare for the interview.

Unless you're actively looking for a job (or are trying to hire someone) it's probably not a site you go to every day.

LinkedIn has done a good job of creating a social network for the professional aspect of your life. You can have co-workers who you enjoy working with, respect, like, but they still might not really be your friends.

But I think LinkedIn's success is partly because Facebook hasn't solved the social context issue. Work vs. friends is very important, but there are also differences in how we act with close friends vs acquaintances, friends vs. family, or even close friends that we met at different points in our lives. That would be a very difficult problem to solve cleanly, are there any social networks that are trying?

I also get e-mails every 6 months from Google.

A few years ago Google required a 3.75 or higher college GPA. That is an amazing GPA for the college I went to, so I've never applied. I wonder if they have relaxed that criteria.

That would have been a great follow-up question.

The application must have had a description of an idea that was good enough to get the interview. Probably the interview starts by asking the team to explain their plans in more detail. If after 5 minutes pg & friends don't have a clearer picture than what they got from the application, then is the team going to be able to explain the idea to customers (who are not going to give them 5 whole minutes)? Or be ready to pitch VCs in a few months (which is even more stressful)?

The worst YC interviews being the ones where people cannot explain what their start-up is going to do is interesting. The same thing happens when talking about past projects in technical interviews. The worst candidates cannot clearly explain what the project was, or give specific details about their work. I'm never sure if they are actually confused about it or just aren't good at explaining, but either way it is not a good sign for how it would be to work with them.