zippy786

> I'd like to believe that's true, but I've spent quite a lot of time trying to explain pointers and recursion to people and either they get it right away or practically never.

Have you thought about may be you don't understand pointers and just think you do ? May be you should not start teaching and explaining about pointers before you understand it well. If you can't pin-point why your students don't understand and just say they won't understand at all (may be weak math background or something else), then I'm sorry you lack the knowledge to teach or use pointers.

Your reference to Joel and how you rely so much on your intuition tells me that you tend to have "I'm better than other" type of feeling just because you understand DP. This is the exact toxic I would want to avoid in the workplace. Same with Joel's reference, I'm shocked that he thinks understanding pointers is not a skill (may be I should interview him on pointer arithmetic and see just how good he is). My experience has been that these interviewers who say they are so good in DP, pointers, recursion and throw this aura of 'false negative' and know it all show true colors after the interview. They make wrong decisions on when to optimize, are clueless about scale and distributed systems, can't write complex sql, just don't know how to turn on little knobs to solve the problem so write huge unnecessary code. All this is probably because they never thought more than DP/recursion (which I would avoid at any cost in my code base).

Q. Can the users completely delete their data ?

Zuckerberg: Yes, there are two options. First to deactivate because students and want to suspend and come back because they want to study for exam. Second option is users can totally delete all their data.

Where is the second option anyone from Facebook ? There is only an option to delete the account after you DIE, not an option to delete it when you are alive.

So many lies.

Whiteboards are bad for writing programs. Think about how often you write programs on whiteboard, it's mostly for diagrams and system flow not to write for and while loops for hard problems. My thinking pattern is different when I write program I tend to write the skeleton first and then fill it out. Writing on whiteboard although I know the solution I'm just spending time writing which sucks (may be because the only thing I write is a cheque once a month and I'm not used to writing for years). Now if it were typing, within the same span of time I can write two or three programs find mistakes and solve everything. Hence I find coding on computer much better than whiteboard and these days I refuse interviewing on whiteboards and say so to anyone who wants to hire me.

Edit: It's ironic how the so called cutting-edge tech companies can't afford a keyboard, mouse, laptop and a projector which would make things way better. I even had a case where the interviewer changed the question with 5 min. to spare , I explained the solution he said it would work and then told me to write it. I was just erasing and pointing arrows because I did not have space etc. So easy to forget that while typing you just hit enter and get a new line. Draw on white board, write on computer; that's how it should be.

I think you will be wasting your money and setting up a bad culture. How many rounds of review are you going to ? After the first round will you hire another one to do more rounds ? Although the product works, it seems you seem to want 100% bullet proof product which will not be possible. Just make sure your product works and when you start making money hire a team and not freelancers to do your code review and manage the product.

Early 30s. Was 8 when I was writing ruby, 7 when using Rails, now Node.js it is 1.