3 ms·
Oh, thank you! I felt stupid for about the same amount of time until I read your comment.
by jarrethardie 16y ago
Oh, thank you! I felt stupid for about the same amount of time until I read your comment.
- Stormbringer 16y agoYay mystery meat! This perfectly illustrates something I said earlier about the difference between an OS with well defined UI standards, and one where the developers just do whatever the hell they want. I boldly asserted that in such an environment, the developers will implement the one method of control that makes sense to them, and ignore all the other options, which means the user has to try everything they can think of until they hit on the right combo, which can take a while, leading to frustration. === Developer Driven Development. Interesting concept... "dumb ideas are not worked on" wonderful. Nirvana? What I think is that development works best when the developers understand the problem. No methodology is a substitute for an actual understanding of what you're trying to achieve and why you're trying to achieve it. Of course, developers understand the issues that effect developers. So of course they will be happiest (most effective?) fixing the problems they are themselves the client for. Also, this removes a layer or two of communication, since you don't need to have the customer talk to the developer, or have a Business Analyst interrogate the customer and then translate it into programmer-ese. If you understand the problem, you can tell which are the dumb ideas (sometimes you figure this out retroactively). If you don't understand the problem, you're simply not qualified to judge which are the dumb ideas.