No question. Just no easy instructions on how to get the window to appear.
People can write code...but can't think?
/et also works.....
No question. Just no easy instructions on how to get the window to appear.
People can write code...but can't think?
/et also works.....
after years of being friends with a variety of coders and just generally really brilliant people, I'd say it's not an issue of people not being able to think...it's an issue of being able to communicate well, across multiple perspectives and approaches and backgrounds, which is something many of my engineering-minded friends have...issues, with
of course, it's not *just* engineering minded people, but it seems to be a common problem for many of them. There's something about being the one doing the coding that...blinds you, I suppose...to the huge range of different perspectives users might have actually using the code. It just doesn't occur to the coder that certain questions might be asked, or that basic instructions that every coder knows have to exist in order to be able to code might never occur to a particular user that is walking into this program expecting it to work like the candy crush app on their phone
I'm experiencing this at work a lot lately, and not just with engineers...just people that seem to have trouble anticipating alternate perspectives and alternative senses of "common sense" when trying to create instructions for how to do something
anyway, I guess my point is, if you ever find yourself being frustrated by the arcane and nonsensical design of a particular program, it's not always, or really even often, a coder who doesn't know how to think - it just never really occurred to the coder that you'd try to do it *that way*, or that you didn't know "like you *obviously* should have known" that you have to do such-and-such before you can do that other thing...and so on