You know what else is a cognitive burden? Picking up a new magazine and reading the table of contents. Yes, Windows 8 is a cognitive burden, but it ain't quantum physics. It is different though.
Also, my car has an "alarm system" factory installed. I'm pretty sure the only thing it does is has a flashing LED. I've never heard it go off. I don't know what it sounds like if it did. So far, no break ins, though.
Where I grew up, I found that simply having alarm company stickers on your door was good enough to stop burglars. There are plenty enough houses there without any sort of security system. Even tweakers understand the idea of going after the low-hanging fruit.
Reading that article you cited, I don't see any cozy relations between the nazis and the Catholic Church at all. I see a lof of mistrust and a lot of deception on the part of the Nazis and a falling out even before the the second world war began.
Exactly, which is why it's best to work with the customer to understand their process then come up with a solution. I have had projects where the customer came to me knowing exactly what they needed (usually a very small project) and there were no objections from me to building it exactly as they had spec'ed it. Most of the time, the customers come to me with a vague notion of what they want and if they're flexible we can come to some middle ground that will make them much more happy in the end. If they come to me with a vague notion and aren't willing to budge, then I build it; they see the errors of their way and revise the project, and I build it; they find more problems, and I build it; and on and on and on. It's profitable for me, but I don't like working on those projects. Usually around the 3rd or 4th iteration, they start asking me for input, and the thing gets wrapped up, but now instead of starting a fresh code base, I have a half-assed legacy application that I have to adapt to the new design.
The problem isn't that the customer doesn't know what they want, it's that they don't know what we can do for them. I have no doubt that they understand their processes way better than I will.
I just wish there were salespeople who would take a moment to ask me what I'm looking for in a product with the knowledge, experience, and honesty to make a decent recommendation:)
I just don't think his stuff is funny. I don't mind cynicism, if it's funny. The Oatmeal seems to me like the latest in a series of unfunny webcomics that get popular simply because they make jokes about certain subjects (science, video games, etc) without actually being humorous. It's like the web equivalent of "The Big Bang Theory".
She needs to send them out to find her a switch. And if it ain't big enough, she's going to find herself a switch, in which case they're both gonna get they're hides tanned!
Apple NEVER had a huge share of the market in desktop computers. The most they ever commanded was about 15.8% reported in 1980, in the nascent desktop market.
The difference is that I have 20+ years of experience with a variety of technologies and projects and he has 3 months experience shovelling whatever the higher ups tell him is the best product, what he reads on the internet, and what he hears from his friends.
When I walk into Fry's looking for a cheap HDMI cable, I don't need some dope pushing Monster cables at me. (Which has happened. I asked him again, nicely, where the $1.77 6' Shaxon HDMI cables were, and to his credit he relented and pointed them out to me, but not without expressing his disappointment with my choice of a lower quality AV experience.)
For example, a person might go into a store and ask a clerk for an iPad. A good clerk would politely ask why they want an iPad. If the customer was looking for a highly mobile device for reasons.... then a 7" Android tablet might be better. In this example the customer lacks expert knowledge regarding tablet devices and their proposed solution was less then optimal. By understanding the underlying problem, the clerk is able to recommend the most appropriate device. It is the same for developers - take the time to understand the problem if you want the customer to be happy.
The last thing I want when going into a store to make a purchase is some dillwad sales clerk second guessing my researched decision.
I agree that you need to find out why people are asking for what they're asking. I just hate dillwad sales clerks.
As a developer, I've learned that it's a large part of my job to educate project stakeholders on what is possible and practical, as well as to do what they ask. The most successful projects are ones where the stakeholders explain the entire process to me and we work together to come up with a good solution. The worst ones are when a stakeholder comes to me with an inflexible pre-conceived notion of what needs to be done. Most of the time, these projects take too long and they never work as well as the principles envisioned.
Yep. It's worth whatever Honey Boo Boo Child's family is getting. Apple is the new Honey Boo Boo Child!
the Lisp fanatics believe that every language since was a wrong turn
You're aware that javascript is lisp with an alternative syntax?
And its still a wrong turn!
You know what else is a cognitive burden? Picking up a new magazine and reading the table of contents. Yes, Windows 8 is a cognitive burden, but it ain't quantum physics. It is different though.
Also, my car has an "alarm system" factory installed. I'm pretty sure the only thing it does is has a flashing LED. I've never heard it go off. I don't know what it sounds like if it did. So far, no break ins, though.
Where I grew up, I found that simply having alarm company stickers on your door was good enough to stop burglars. There are plenty enough houses there without any sort of security system. Even tweakers understand the idea of going after the low-hanging fruit.
Hmm, looks like another single source wonder. Well, if Aarons and Loftus said it was true, it must be.
It's no excuse, but it's a hell of a rationalization.
Ad hominem and non sequitur.
But surprisingly accurate.
Did you seriously TL:DR everything after the ellipsis? Perjury is illegal, even if you're a journalist.
They're already on the shitlist, why should they kowtow?
More FUD.
It's that kind of thinking that doomed the quants to a footnote in the (stupid) economic history of the late 20th century.
Reading that article you cited, I don't see any cozy relations between the nazis and the Catholic Church at all. I see a lof of mistrust and a lot of deception on the part of the Nazis and a falling out even before the the second world war began.
They're all doing it wrong. If the leftist academics had a shot of running the show, I'm sure it'd work just fine.
Would someone explain to me this fruits stuff? I don't understand the metaphor? Someone doesn't like Apples? Yeesh!
Newsflash: They didn't create the market, fanboy.
Exactly, which is why it's best to work with the customer to understand their process then come up with a solution. I have had projects where the customer came to me knowing exactly what they needed (usually a very small project) and there were no objections from me to building it exactly as they had spec'ed it. Most of the time, the customers come to me with a vague notion of what they want and if they're flexible we can come to some middle ground that will make them much more happy in the end. If they come to me with a vague notion and aren't willing to budge, then I build it; they see the errors of their way and revise the project, and I build it; they find more problems, and I build it; and on and on and on. It's profitable for me, but I don't like working on those projects. Usually around the 3rd or 4th iteration, they start asking me for input, and the thing gets wrapped up, but now instead of starting a fresh code base, I have a half-assed legacy application that I have to adapt to the new design.
The problem isn't that the customer doesn't know what they want, it's that they don't know what we can do for them. I have no doubt that they understand their processes way better than I will.
I just wish there were salespeople who would take a moment to ask me what I'm looking for in a product with the knowledge, experience, and honesty to make a decent recommendation :)
I just don't think his stuff is funny. I don't mind cynicism, if it's funny. The Oatmeal seems to me like the latest in a series of unfunny webcomics that get popular simply because they make jokes about certain subjects (science, video games, etc) without actually being humorous. It's like the web equivalent of "The Big Bang Theory".
She needs to send them out to find her a switch. And if it ain't big enough, she's going to find herself a switch, in which case they're both gonna get they're hides tanned!
Wait, is that their crack pipe design you're describing? I can't tell from those phrases.
Apple NEVER had a huge share of the market in desktop computers. The most they ever commanded was about 15.8% reported in 1980, in the nascent desktop market.
A terribly unfunny web comic.
Fry's has pre-paid phones on Verizon for sale for $15.
The difference is that I have 20+ years of experience with a variety of technologies and projects and he has 3 months experience shovelling whatever the higher ups tell him is the best product, what he reads on the internet, and what he hears from his friends.
When I walk into Fry's looking for a cheap HDMI cable, I don't need some dope pushing Monster cables at me. (Which has happened. I asked him again, nicely, where the $1.77 6' Shaxon HDMI cables were, and to his credit he relented and pointed them out to me, but not without expressing his disappointment with my choice of a lower quality AV experience.)
For example, a person might go into a store and ask a clerk for an iPad. A good clerk would politely ask why they want an iPad. If the customer was looking for a highly mobile device for reasons .... then a 7" Android tablet might be better. In this example the customer lacks expert knowledge regarding tablet devices and their proposed solution was less then optimal. By understanding the underlying problem, the clerk is able to recommend the most appropriate device. It is the same for developers - take the time to understand the problem if you want the customer to be happy.
The last thing I want when going into a store to make a purchase is some dillwad sales clerk second guessing my researched decision.
I agree that you need to find out why people are asking for what they're asking. I just hate dillwad sales clerks.
As a developer, I've learned that it's a large part of my job to educate project stakeholders on what is possible and practical, as well as to do what they ask. The most successful projects are ones where the stakeholders explain the entire process to me and we work together to come up with a good solution. The worst ones are when a stakeholder comes to me with an inflexible pre-conceived notion of what needs to be done. Most of the time, these projects take too long and they never work as well as the principles envisioned.