182 karma · joined April 22, 2010
Some of this stuff is beyond parody...
Coding is less critical for visual designers though. It's better if the visual designer can render his design in html/css (or whatever), but you probably don't want to turn down an otherwise brilliant visual designer if they can't.
The "should designers code" question seems to come up again and again because interaction and visual design gets rolled into one discipline (and often one person).
Maybe B-player is harsh but in my career I've worked with some very good programmers and some real stars. When I talk to the very good programmers I always feel dumber, but whenever I talk to the real stars I always feel smarter myself (though heaven knows that's not actually true). This seems to fall firmly in the "very good programmer" category.
And Joshua is being "bullied"? Really? Sensitive types, these bloggers.
For anyone interested in a C version, I wrote this a while ago, YMMV: https://github.com/jaimz/core_ds/blob/master/MxStringBuffer....
Well bravo you. The problem with recruitment in our industry is not the candidates with no GitHub account, its the egomaniacal interviewers who waste no opportunity to turn any interview, in this case any application, into a passive-aggressive pissing contest.
Perhaps its acceptable for an interview to be adversarial, but I don't think any other industry matches the tech industry for the utter hostility of the interview process.
If you want a fresh look at systems programming then leaning Ocaml or Haskell would be a much better option because you will learn to solve problems in a new way, not just with slightly different syntax.
Also, someone on this thread doesn't understand how downvoting works. If you disagree with something then make a response, save downvotes for deliberately trollish or off-topic comments.
The disquiet some people feel is that frameworks like bootstrap make it very tempting to drop this design phase in favour of snapping widgets together and assuming the end result must be a good UI because users are "used" to the individual widgets. This would definitely not be step forward in software construction - web or otherwise.
Snapping widgets together like lego bricks and declaring the result to be a "good" interface because it adheres to "standards" is sometimes true, but not nearly as often as you would think, and in my experience leads to interfaces that map closely to the underlying system, but not at all to what the user actually wants to do.
It's good that a non-designer can use bootstrap to create a decent looking site, heaven knows the world is not over-burdened with good-looking websites, but neither we nor the "users" want every web page, or every web app, to look the same.