Reputation
723
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
7 19
Newest
 Nice Answer
Impact
~22k people reached

May
14
awarded  Nice Answer
Jan
26
awarded  Altruist
Jan
23
awarded  Constituent
Jan
23
comment How to avoid that “Path to Completion” results in “Previous” becoming the next logical action?
@AndréDaniel It would certainly be an option, not sure if I'd prefer it though: users will probably not find "Previous" easily enough when they need it.
Jan
23
accepted How to avoid that “Path to Completion” results in “Previous” becoming the next logical action?
Jan
23
revised How to avoid that “Path to Completion” results in “Previous” becoming the next logical action?
Clarification that my question is about the buttons, not about the flow of labels/inputs
Jan
23
comment Best way to display code to non-programmers
@KromStern Sorry you feel this answer is bad advice. IMHO writing a test harnass is reverse-engineering. Further, visualizations were not deemed necessary by OP as indicated by his comment to the question. Also, OP's comment to my answer here suggests (to me at least) that it does answer the question, even though due to circumstances it's not an option.
Jan
23
comment How to avoid that “Path to Completion” results in “Previous” becoming the next logical action?
Thank you for taking the time to answer. I do realize there's also the issue of top aligned labels, but I see that as a seperate choice / issue (I may later update my question to better reflect that if I have time). My question was mainly about the placement of the Prev/Next buttons. On that point you seem to agree with @locationunknown's earlier answer though, and I'm now indeed inclined to take that advice. Tyvm!
Jan
22
revised Relation between a Wizard's Previous button and history's Back button
Landed on this question, took me a while to see the *actual* topic. It's a good question, tried to format the body to more easily spot the actual question, and edited the title to better reflect the content.
Jan
22
asked How to avoid that “Path to Completion” results in “Previous” becoming the next logical action?
Jan
22
awarded  Excavator
Jan
22
revised Placement of buttons for Previous, Next, and Save Draft actions
Highly viewed/rated question, tried to optimize text-flow/readability. Also removed disclaimer, clearly this question came out on top so it's not needed (anymore).
Jan
22
suggested approved edit on Relation between a Wizard's Previous button and history's Back button
Jan
22
suggested approved edit on Placement of buttons for Previous, Next, and Save Draft actions
Jan
21
awarded  Good Question
Jan
19
awarded  Investor
Jan
19
comment Best way to display code to non-programmers
Note by the way that I didn't want to imply "just a few test cases". You can get quite good coverage with automated tests. In fact, with tests there's even a metric (though debatable how useful it is); with a flow chart or list of business rules measureing is a lot harder. If I have time tonight I may update my answer a bit on that.
Jan
19
comment Best way to display code to non-programmers
Thanks for your kind comment. I understand my solution may not be for you, nonetheless I'll leave it up there for others that may have use for it.
Jan
16
answered Best way to display code to non-programmers
Jan
16
comment Best way to display code to non-programmers
Does it need to be a visualization? Unit- and/or integration tests could help too, and they'd remain useful if business will follow up by asking for changes. They'd also allow you to be reasonably certain you're correct. The business could be presented with just the descriptions/titles first, diving into details when asked...