Why Tony Stark is better than you
julio-ody.tumblr.com
julio-ody.tumblr.com
The article writers contention that programmers should also have solid HCI knowledge is not necessarily unreasonable, but the comparison to "2 meetings a week, and in a year..." is just ridiculous. Perhaps it was intended to be over the top, but division of labor exists for a good reason. What we really need are amazing back-end and interface engineers who can work with eachother effectively. That, and, as we are seeing with the iPhone becoming mainstream, a cultural willingness to put in extra work on the UI because it matters.
I've also spent more time and energy configuring Apache and various *nix apps than most sysadmins. But I don't feel comfortable blogging about "Top 5 Unix commands you must know" because I always feel there are 100 others who know more than me so I'll let them blog on these topics. I'll blog about what I'm good at or my own experiences. Which brings me back to the do-it-all topic - if it needs to be done, I want to learn how to do it and do it well. I delegate and outsource when I have resources available but if not, I just do whatever needs to be done. Heinlein's quote seems pretty appropriate here:
"A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects."
Knowing how the tools and palettes work in Photoshop makes you a good designer like knowing Java's syntax makes you a good programmer.
Knowing the Photoshop interface is clearly not what makes you a good designer, but in general it is a necessary-but-not-sufficient prerequisite to being really good.
The most productive I've ever been has been while working in tandem with a good designer, because it frees me up to do what I do best, and that's write code.
Now, I will say that it's important for any web developer to understand principles of design, because understanding what your users actually want is crucial for both backend and frontend work, thinking about user interaction, your data model, etc.
When your designer knows the basics of how programming works, and when your programmer has a grasp of the tenets of design, neither person has to operate as if the other is some sort of stupid magician. It's so refreshing.
To me, the design and the implementation are two very different things, and advanced CSS seems to be more in the programming realm (despite its goals to be accessible to the average designer).
Looks very nice at a glance, but fails its usability tests. ;)
That infact there are many, many, many developers who work on projects that are enormous that never see "end users" in the, guy who owns an iMac, sense of the word.
The implication that anyone who writes great software, but lacks "design" skills (in the graphical sense of the word) is so crazy... I wonder if this guy has ever thought about the guy who wrote the embedded realtime system in his car that runs his anti-lock breaks, no WOW factor there.
EDIT: never have I ever wished I had enough karma to vote something down before.
I pity 'da fool.
Actually come to think of it, you were right in the first place.
People should stop being so serious. People should take a look at things from a different perspective, and gain positive values from it.
I think he meant "left side of the brain". Does he ?
Edit: let me clarify. This blog post is written by an infantile, narcissistic know-it-all and exudes the odor of vomit and feces. The fact that it appears here lowers my esteem of HN and further confirms my suspicion that the community is full of daft fight club-wannabe group-thinkers. Fuck you very much.