me: "Hi, I'd like to buy a White 13" Macbook with a 500gb HD and 8gb of RAM. Could you please get one for me?"
sales person: "What are you using it for? Do you browse the internet? look at photos? do a lot of word processing?"
me: confused "um, I do web development and use Photoshop sometimes..."
sales person: "Oh well you need a Macbook Pro then."
me: "no, I can't afford that and the regular Macbook is plenty powerful for what I need. Can I just buy one please?"
sales person: "Photoshop won't run well on the regular Macbook. What you really want it the Macbook Pro. You'll need at least 16gb of RAM and if you're editing photos you'll want a bigger harddrive, not to mention the extra power that comes from the Pro's CPU."
me: "um, I have money in my hand right here that I will give you in exchange for a regular Macbook. Can you please go get one and take my money?"
You present identically to the kind of person who is completely non-technical and was mis-advised by a friend of theirs, and who will come back in a week complaining about how Photoshop doesn't run well enough and their hard drive is full.
Apple has decided that they want to ensure that you are happy with your purchase, and part of that process involves the salesperson being convinced that you are buying the right thing.
I just get frustrated being told what I want, being upsold, and being made to feel as if I don't know what I'm talking about when in fact I probably know a lot more than the sales person who has probably never used the device in question the way I've described I will be using it.
I understand that the general case is better serviced this way, but for someone who walks in knowing the part numbers they want, the added friction is a turn off.
I personally avoid going to Apple stores because of how hard it is to actually buy stuff there. Even grabbing a simple USB key off the shelf is incredibly hard to pay for when the cashiers are all hiding in a sea of other people.
Not to a systems software developer, sonny.
/s
(Besides, "I do web development" could easily mean "I know what Dreamweaver is". (It's that song by Gary Wright which helped inspire Freddy Kreuger, right?))
People who fall into the (negative) category "I know what Dreamweaver is" never describe themselves as web developers, but rather as web designers (and the serious web designers, say, as UX designer).
Just say something like "I don't want to get into that - I know this is what I want to buy."
I've never had a problem with this.
Either way, in a Q&A site like StackOverflow, asking for more context for a problem is rarely an issue in of itself. I find that more often than not people that are put off by that are in fact asking bad questions.
I had a few changed files in a working directory. I did `git add -A` to stage them. I then intended to `git stash` those changes, but I accidentally did `git stash pop`. I now have two sets of unrelated changes checked out: one staged and one not. I'd like to just stash the staged changes for now, but I don't know how to do that off the top of my head.
Google brings up this answer: http://stackoverflow.com/questions/14759748/stashing-only-st...
The original poster asks pretty much what I'd like to know: "How can I stash only staged changes?" However, he also provides some background. It sounds like he legitimately has an XY problem here, and the top answer is a long discussion of alternate workflows. However, when I search for something like "git stash only staged", I get a very unhelpful answer.
"Am I going about this the wrong way? Am I misunderstanding how git can work in other ways to simplify my process?"
Which is answered correctly. It could have been a typical XY problem but he adds enough background information that he's able to get a better answer. Great question AND great answer.
I'll give you that Google didn't index that question particularly well, but that's not really StackOverflow's fault.