Had a good conversation about how we should incorporate product thinking into software analysis/programming language design. When people think about user research here, it's often about after-the-fact user studies. Understanding user needs beforehand could be much more impactful.
-
Show this thread
-
When I was starting Akita, I spent a lot of time learning how to conduct user research to understand not just what people say their problems are, but why they are problems. I learned that there can be a scientific process behind the assumptions people make in technical work.
1 reply 1 retweet 6 likesShow this thread -
Even though the technologists who have the most impact are often excellent product thinkers, product thinking tends to get left out of our training. (We believe in proof frameworks, so why are we so sloppy about the frameworks for reasoning about whose needs we're serving how?)
2 replies 3 retweets 8 likesShow this thread
"It is curious to observe how the authors, who in the formal aspects of their work require painstaking demonstration and proof, in the informal aspects are satisfied with subjective claims that have not the slightest support." - Peter Naur, 1989
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.
cognitive psychology. PhD