Internet Explorer does that. Use Ctrl + Shift + P for opening an InPrivate windows. Every window runs in its own process.
60 karma · joined November 29, 2011
1. I identify the customer value derived from my product/idea.
2. Understand and identify market type: a) Existing market: People know about the product, the problem it is solving. b) New market: Even if there are other players out there, it's still not commonly understood by customer why it matters
3. How to position yourself. a) Existing market, you need a something different... this is what I ask myself: * Can I provide the same value for cheaper? * Can I provide more value for similar price? * Can I focus on a a subset of the market (e.g. niche), and adapt better to it?
b) New market: The challenge for new markets is not so much how 'good' the product is, but rather how good you are are explaning to customers why you matter. So I ask myself: * Can I make it simpler/more understandable? * Can I get better market adoption through my own techniques?
If I don't answer "yes" to any of those questions, I either rethink to idea so it fits one of those cases, or move on. Hope this helps :)
> A cv is useless for conveying who you are and what value you bring relative to all the other thousands of people out there. A paper is a paper is a paper.
True. Therefore if you're looking at integrating a Startup, it is great because educated developers might have the time to meticulously review every application. But when you're looking for a job, any job, especially in a more established company it doesn't work the same way.
Of course, if your github projects are "famous", say you created Redis (the 1% case), then it can act as a CV replacement. A replacement NOT because someone will dig into the actual code, but rather because they'll know you created this known thing called Redis (or they'll read about it on Wikipedia and realize it's a big deal)... so it's in a way your CV. But if your github only has random projects (which is the 99% case), it's actually quite hard and time consuming to jump into the code to evaluate an applicant's skill.
To better explain my point that a resume/CV actually makes the difference, let's look at it the other way around. Imagine you are a recruiter, you have 100 applicants, and you need to filter the list because you can't interview all 100 of them. Are you going to look into at everyone's repo?! No. Instead you will give a quick look at the CV to identify 'potentially' good candidates. Having a link to your github on the CV is a big plus at this point (independently of what it has), because it's different from most of the other ones (aka: you're special, more passionate about technology). Once the filtering is done, only then will you usually have the occasion to be heard through an interview. And it's at this point that you actually need to show you're real value.
Now I do agree that this system is flawed, but it's the game. If you want to maximize your chances, which you most likely do considering you have no options, you should play the game and get a solid cv/resume. Having said that, if you lack experience or content for your CV, personal projects (on github) are a good filler ;)
1) I think the idea sucks:
Stay honest, but polite. I try to explain why I believe the idea is not, in its current form, good enough. I stay as scientific as possible in this explanation, by giving concrete examples, scenarios and cases where it wouldn't work. At the same time, I provide some advice in terms of what I think there are opportunities for the idea (if any) and almost always finish with a motivational message about not giving up. After all, it's not because I think it's not a good idea that it is not... and who am I to crush people's dreams.
2) You're not interested in the idea:
A lot of us have busy lives, and that's a fact. There are many things you would like to do, try, and experience but at some point there are choices to be made and priorities to establish. When I'm not interested I explain that there's a lot on my plate already, and that I wouldn't be able to keep up with it. So instead of saying yes, out of excitement, and disappointing later, I'd rather politely decline upfront for everyone's best interest :)
--
Bottom line, there is no need to lie or invent excuses, but 'explain' it in a way people understand, and they shouldn't get hurt.
Also, consultants have the benefit of having been 'dropped' in many different businesses, and learn about their problems/structures. His potential knowledge of those markets would also prove to be valuable.