2/ I get that publishers can't produce "Z for [A-Y] programmers" for each pairing. But, how much quicker could you introduce people if you met them at the intersection of their (really common) experience and needs, rather than pretending it's all new terrain?
-
-
Show this thread
-
3/ "But you shouldn't program Z as if it were Y." (Concrete example: Don't program an in an OO language like you would a functional one.) Okay, that's true. But, ignoring the users habits doesn't make them less accessible. Contrast them, explicitly. Make them obviously different.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.