On Tue, Mar 9, 2010 at 18:49, Wayne Fay <[email protected]> wrote: > You're going about this the wrong way... YOU should be the customer. > The next time you're doing something and think to yourself, hey I wish > there was an app that would help me do X, you should BUILD IT. And if > you don't have any needs right now, either wait a little bit until > something occurs to you OR ask your significant other/friends if they > have a need, and use that as the base for your work.
Full ACK! - It is also sufficient to watch a few people working to see what could help them. Often during projects when discussing workflows I notice plenty of possible improvements. On Tue, Mar 9, 2010 at 20:51, Rakesh <[email protected]> wrote: > once you involve other people then there expectations too meet and > ultimately stress. Yes, that may be - although if you manage it right, people would know what they can expect and what is plain science fiction. If you do not include expectations and needs of others you will not know if the new technology you are learning is really fit for a real customer project. And it is better to not deliver the desired to your friends than to disappoint customers. -- Martin Wildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
