gashmol

7 ms·

61.
by gashmol 5y ago
I think there's should be a difference between customer feedback and user feedback. UI prototype is effective only in finding what users want. To get customer feedback you probably need a full fledged MVP and ask for money or other kin
62.
by gashmol 5y ago
IMHO its better to start with a UI prototype. It's much faster and cheaper while still being effective.
63.
by gashmol 5y ago
If you substitute writing with developing software (or prototyping) and ideas with requirements then you get great advice for making something users want. It even suggest the practice of checking requirements to be precise and complete. Int
64.
by gashmol 5y ago
How about the time when Israel rescued some 14,000 people of this community in 36 hours from Addis Ababa just before rebel forces arrived at the city? Israel made some great things for this community and it made some awful things as well. M
65.
by gashmol 5y ago
You can always cherry pick news items to depict Israel as bad or as good as you want to. But remember, reality is more complex than what's on the news. While there are some terrible mistakes, Israel's treatment of Ethiopian Jews i
66.
by gashmol 5y ago
Generally speaking, you can reduce the combinatorics in tests by using techniques like cause effect graphing (from The Art of Software Testing). It also contains notation for cases that "can't happen". It's very technica
67.
by gashmol 5y ago
I think there is another big issue related to Clean Code (and friends) that is rarely discussed. There are two types of design methods: those that help you to generate a solution to the problem and those that only help you to optimize a sol
68.
Prototype the UI before building an MVP(gashamola.com)
2 points by gashmol 5y ago|0 comments
69.
by gashmol 5y ago
Are you sweeping something under the rug? Loss of interest or pleasure is a symptom of depression. When you get rid of your depression, you'll enjoy programming again. If you don't think you have depression or other issues then tr