New idea in Usable Software Design: Mistake Proofing Design
Hi fellow craftsmen,
I'm continuing the series on Usable Software Design with a new topic. None of us likes to make mistakes when writing code, yet mistakes still happen. This is a problem from an economic point of view - fixing mistakes can prove costly- but I'm more interested in the user-centric view. In this case the developer-is-the-user-of-the-design-centric-view.
I tried in this blog post to detail 5 steps to mistake proof software design so that it becomes more usable for developers. Here's the link: http://mozaicworks.com/blog/5-steps-to-mistake-proof-software-design/.
As always, I appreciate any feedback, comment or idea. Is this topic interesting for you? Why not? What would you like to learn about it?
Thank you, and happy crafting,
You received this message because you are subscribed to the Google Groups "software_craftsmanship" group.
To unsubscribe from this group and stop receiving emails from it, send an email to software_craftsmanship+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To post to this group, send email to software_craftsmanship-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Visit this group at http://groups.google.com/group/software_craftsmanship
For more options, visit https://groups.google.com/d/optout