3 ms·

There are some typical things that apply to just about any software project that you can try. Avoid feature creep by writing down the exact list of things you

There are some typical things that apply to just about any software project that you can try. Avoid feature creep by writing down the exact list of things you need to do, and if you come up with more ideas, put them on a separate list. Try to build a Minimum Viable Product, which is a vertical slice of the most minimal version of your product that works.[1] If that doesn't work out, build some feature-complete tech demos and refactor them into an MVP. Find a friend to help you with it. A fresh pair of eyes can help you validate your project and see what you could be doing better! Experiencing friction means you're learning. Too much friction, however, can burn you. Don't burn out. Take a break. If you find yourself feeling unable to finish a task today, either try a different task on the todo list, or do something that relaxes you instead. Worrying about when you'll finish won't get you any further, nor will pushing yourself past your limit. Best of luck in your endeavor! 1: http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-o... (has a really nice infographic that might help you understand!) P.S. It's okay to fail. Fail forward.

hoodoof 11y ago
Thanks for the helpful support. Good link. A friend of mine thinks of an MVP as throwing anything out the door as soon as he possibly can. "Hello World up and running? There you go, that's an MVP, let's ship it!" Well not quite, but he's certainly more minimal than viable. I think of an MVP as Minimum Valuable Product - i.e the minimum that allows execution of the core concept. Part of the problem for me is that alot of stuff needs to be in place for the concept to hold together. It's quite a technical product - the sort of thing where you couldn't deliver a plane without a rear tail. First customer: "Hey nice plane! I like your innovative tail-less design, lets take her up for a flight!" Me: "Errr, how about you go on your own and I'll keep working on the tail."
- CyberFonic 11y ago
  ROFL Yeah! let others fly the tail-less plane. Isn't that a different way of describing v1 (aka beta test) of many products?

hoodoof 11y ago

Thanks for the helpful support. Good link. A friend of mine thinks of an MVP as throwing anything out the door as soon as he possibly can. "Hello World up and running? There you go, that's an MVP, let's ship it!" Well not quite, but he's certainly more minimal than viable. I think of an MVP as Minimum Valuable Product - i.e the minimum that allows execution of the core concept. Part of the problem for me is that alot of stuff needs to be in place for the concept to hold together. It's quite a technical product - the sort of thing where you couldn't deliver a plane without a rear tail. First customer: "Hey nice plane! I like your innovative tail-less design, lets take her up for a flight!" Me: "Errr, how about you go on your own and I'll keep working on the tail."

CyberFonic 11y ago
ROFL Yeah! let others fly the tail-less plane. Isn't that a different way of describing v1 (aka beta test) of many products?