<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[User Experience and being human — interaction reimagined - Medium]]></title>
        <description><![CDATA[How do we create positive experiences that encourage learning and creativity? Also: Regex You Can Read (Regex UCR) and related efforts live here. It’s a new visual syntax and UI for regex. It allows humans to concentrate on the actual matching. - Medium]]></description>
        <link>https://medium.com/interaction-reimagined?source=rss----778b8ec183e9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>User Experience and being human — interaction reimagined - Medium</title>
            <link>https://medium.com/interaction-reimagined?source=rss----778b8ec183e9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:33:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/interaction-reimagined" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[By relieving the brain of all unnecessary work, a good notation sets it free to concentrate on more…]]></title>
            <link>https://medium.com/interaction-reimagined/by-relieving-the-brain-of-all-unnecessary-work-a-good-notation-sets-it-free-to-concentrate-on-more-d2d91e177d4b?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/d2d91e177d4b</guid>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Mon, 30 Nov 2020 11:22:27 GMT</pubDate>
            <atom:updated>2020-11-30T11:22:27.486Z</atom:updated>
            <content:encoded><![CDATA[<p>By relieving the brain of all unnecessary work, a good notation sets it free to concentrate on more advanced problems, and in effect increases the mental power of the race.</p><p>A.N. Whitehead</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2d91e177d4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/by-relieving-the-brain-of-all-unnecessary-work-a-good-notation-sets-it-free-to-concentrate-on-more-d2d91e177d4b">By relieving the brain of all unnecessary work, a good notation sets it free to concentrate on more…</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dangers of Modal User Interfaces]]></title>
            <link>https://medium.com/interaction-reimagined/dangers-of-modal-user-interfaces-316828de8161?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/316828de8161</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Fri, 15 Sep 2017 16:49:43 GMT</pubDate>
            <atom:updated>2018-04-23T16:58:18.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*vae0BJUSFI13zXY1LiUbcQ.png" /></figure><p>Modes can be dangerous in a user interface, especially if the UI does not make the modes and their states clearly visible. This is often heard advice about UI design. I collected snippets of this advice/heuristics here.</p><p>If you have a different point of view or know scientific articles or textbooks that further discuss this, I would love to hear about it!</p><p>See also: <a href="http://www.azarask.in/blog/post/is_visual_feedback_enough_why_modes_kill/">Visual Feedback and How Modes Kill</a> <br>(via <a href="https://twitter.com/sashika">Sasha Maximova</a>)</p><h3>Collected quotations</h3><p><a href="http://www.usabilityfirst.com/glossary/modal/">Usability First Glossary</a>:</p><blockquote><em>modal</em></blockquote><blockquote><em>a type of interface where the user moves between different states, or modes. In each mode, input from the user is interpreted in a different way. When a user is in a given mode, it’s a good idea to provide an extremely salient indicator of which mode is currently active, e.g. by providing a large icon or shifting the color of the screen.</em></blockquote><blockquote><em>Modes are usually good to avoid because users are restricted in their available actions and they may be confused that the meaning of their actions changes as they change contexts. However, modes can sometimes be helpful to control and guide input (providing security and preventing accidental errors), and modes may be appropriate when they are short and actively maintained by a user (e.g. the fact that keys refer to capital letters only when the Shift key is held down) and when they follow well-understood conventions, such as painting tools.</em></blockquote><blockquote><em>Examples of modes include:</em></blockquote><blockquote>- Choosing a painting tool in a paint program. When the Line tool is selected, for instance, all mouse clicks create lines. When a brush tool is selected, the user is in a different mode because all mouse clicks are then interpreted as painting.</blockquote><blockquote>- Old text processors, such as ‘vi’ in UNIX, often used a command mode and an edit mode. In a command mode, keystrokes issued commands. In an edit mode, keystrokes were entered into a text document.</blockquote><blockquote>- Moving between pages on a website. Each page is a mode which limits the kinds of actions a user can take (where they can go).</blockquote><blockquote>- Modal dialog boxes are ones that force a user to respond to them before the user can go back to using other aspects of the application.</blockquote><p>The Art of Unix Usability, <a href="http://catb.org/%7Eesr/writings/taouu/html/ch01s03.html">Chapter 1, Section 3</a>:</p><blockquote><strong><em>Rule of Modelessness: The interface’s response to user actions should be consistent and never depend on hidden state.</em></strong></blockquote><blockquote><em>This rule could be taken as a consequence of the Rule of Transparency, but violations are so common and such an important cause of interface problems that we have chosen to foreground it by making it a separate rule.</em></blockquote><blockquote><em>An interface with “modes” responds to the same input gesture in different ways depending either on hidden state not visible to the user, or on where you are within the interface. Since the early days of the Macintosh, which eliminated mode dependencies almost completely, it has been widely understood that modes are a bad idea.</em></blockquote><blockquote><em>The classic bad example in Unix-land is vi(1), a commonly-used editor in which typed characters are either inserted before the cursor or interpreted as editor commands, depending on whether or not you are in insert mode. This is a well-known cause of confusion to novices, and even experts at this editor occasionally trash portions of their documents through having lost track of what mode they are in or inadvertently switched modes. Modern versions of vi(1), partly mitigate this design flaw by providing a visible mode indicator. We know this is not a complete solution, because even expert users can overlook the state of the mode indicator and find themselves in trouble.</em></blockquote><blockquote><em>We’ll see in </em><a href="http://catb.org/%7Eesr/writings/taouu/html/wetware.html"><em>the Wetware chapter</em></a><em> that modes interfere with the process of habituation by which users become expert with interfaces; indeed, they turn habituation into a trap. A computing system ideally designed for human use would have one single set of gestures and commands that are unformly applicable and have consistent meanings across its entire scope.</em></blockquote><p>The Art of Unix Usability, <a href="http://catb.org/~esr/writings/taouu/html/ch04s04.html">Chapter 4, Section 4</a>:</p><blockquote><a href="http://www.catb.org/%7Eesr/writings/taouu/html/ch04s01.html"><em>Raskin</em></a><em> makes the empirical point that human beings cannot be prevented from forming habits about routine tasks, and elegantly defines good interfaces as those which encourage benevolent habituation. We can go a bit further and observe that “benevolent habituation” — the ability to do the right thing by unconscious or half-conscious reflex — is precisely what we normally mean by </em>expertise<em>.</em></blockquote><blockquote><em>Thus, our Rule of Modelessness. Users will form gestural habits, and it is a bad thing when gestural habits they form in one part of the system become inappropriate or even destructive in another part. When this leads to problems, the fault lies not with the user’s habits but with system designers’ failure to maintain consistency.</em></blockquote><p>Also some of <a href="http://www.useit.com/papers/heuristic/heuristic_list.html">Nielsen’s heuristics </a>seem relevant:</p><blockquote><strong><em>Visibility of system status</em></strong></blockquote><blockquote><em>The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.</em></blockquote><blockquote><strong><em>Error prevention</em></strong></blockquote><blockquote><em>Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.</em></blockquote><blockquote><strong><em>Consistency and standards</em></strong></blockquote><blockquote><em>Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.</em></blockquote><p><a href="http://www.oxfordreference.com/views/ENTRY.html?subview=Main&amp;entry=t11.e6022"><strong>A Dictionary of Computing</strong></a><strong>:</strong></p><blockquote><strong><em>dialog management</em></strong><em> The methods and procedures governing the way that information is exchanged between the user and the computer system. It involves the consistent formatting of prompts, check boxes, lists of options, sliders, messages, and other constructs. There are modal dialogs, where the user can do nothing else until the action required to satisfy the dialog has been taken; this can be as simple as acknowledging a message. Conversely, a modeless dialog is one that may be returned to after attending to other matters. See also dialog box. (Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. Oxford University Press. Tampere University. Looked up on 14 November 2011)</em></blockquote><p><a href="https://savolai.net/software/moodle/2011/08/27/dangers-of-moded-user-interfaces/">Originally published in my Moodle usability blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=316828de8161" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/dangers-of-modal-user-interfaces-316828de8161">Dangers of Modal User Interfaces</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product and framework thinkers: When developers and UXers don’t get each other]]></title>
            <link>https://medium.com/interaction-reimagined/why-dont-developers-and-uxers-get-each-other-5702df8daed6?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/5702df8daed6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 21:11:03 GMT</pubDate>
            <atom:updated>2016-11-08T12:35:33.117Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElbBGGtnT8z7n4X4h1f6qw.png" /></figure><p>Developers and UX professionals often seem like beings from different planets. I’ve found that shared understanding about software project goals can sometimes be hard to achieve.</p><p><strong><em>Product and framework thinkers </em></strong>is a helpful way to reason about this (Reichelt, 2009).</p><ul><li><strong><em>Product thinkers’ </em></strong>aim tends to be an integrated experience for users. Product thinking considers the consumer/user experience as a whole. <em>Users need to figure out how pieces of your product fit together? Let’s avoid that.</em></li><li><strong>Technical professionalism often steers towards <em>framework thinking</em>. </strong>It asserts that flexibility and re-use is a key priority. <em>Let’s give our users freedom to combine the tools the way they want them.</em></li></ul><h3>Value means different things</h3><p><strong>Modularity </strong>is a key value for <em>framework thinkers</em>. Unix philosophy comes close, too. Framework thinkers don’t necessarily empathize with what they perceive a consumer attitude. They are often builders themselves. <strong>They want access to what the thing is made of </strong>and they wish their users did, too.</p><p><em>Product thinkers </em>tend to be more oriented towards integration<strong>. </strong>Their criticism towards framework thinkers may be that <strong>framework thinkers tend to overload users with options — </strong>making the user experience worse. Sometimes people just want to get the job done.</p><h3>Finding common ground</h3><p>Product thinkers are focused on the reality of the market of customers out there. They aim to evaluate the abstraction level appropriate for target users. A pile of lego blogs, or a ready-to-use solution? Perhaps something in between — a suitable mix of flexibility, and ease of use? They may want to decrease need for documentation. Instead, they learn about the the user and their goals. Based on this, they prioritize what to present, and when.</p><p><strong>“Product thinkers take users to be more simple-minded than they are!” </strong><em><br></em>This is something you might hear from a framework thinker. Integrating products too tightly results in users losing freedom —and so, degraded UX. Documentation is the natural price users must pay if they want the power of the software.</p><p>Both product and framework thinkers aim to provide good service to users . Just their approaches to this are different.</p><blockquote>Hope to gain favor among your group of users? Your product will need integration and top-down design. To suit various needs though, your architecture will also need flexibility, and documentation to match.</blockquote><p><strong>Should you emphasize product or framework thinking? Depends on the kind of software product you are building.</strong></p><p>Professionals might use the software <em>even if it has a poor UI</em>, if they are committed to the need it meets. They may be willing to spend the effort and wade through extensive documentation. Applications for non-developer users will nonetheless require more careful thinking of your users’ goals. Bad UX puts you in a vulnerable position in any marketplace.</p><p>What is important here is to <strong>be aware of the differences of thought </strong>when discussing goals. If the makers and builders understand each others’ motivations, they can achieve a common vision. What’s that?</p><blockquote>Get something out the door that is valuable to your users.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5TdJRGBki8TEGcg6WZSQxw.png" /></figure><p><strong>References</strong></p><p>Reichelt, L. (2009, October 12). <a href="http://www.disambiguity.com/designing-for-the-wrong-target-audience/">Designing for the wrong target audience (or why Drupal should be a developer tool and not a consumer product). disambiguity.</a> Retrieved May 27, 2010</p><p>Adapted from my <a href="http://savolai.net/software/moodle/2010/09/30/masters-thesis-about-moodle-and-open-source-usability/">thesis</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5702df8daed6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/why-dont-developers-and-uxers-get-each-other-5702df8daed6">Product and framework thinkers: When developers and UXers don’t get each other</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Experience Design in Open Source: Inviting the Users]]></title>
            <link>https://medium.com/interaction-reimagined/user-experience-design-inviting-the-users-25ccd00711c7?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/25ccd00711c7</guid>
            <category><![CDATA[participatory-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 21:10:40 GMT</pubDate>
            <atom:updated>2018-09-10T14:06:46.785Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*82oN2_rSeN_zWJVmt37IZA.jpeg" /><figcaption>Garry Knight: Chatting with a Shopkeeper, CC-lisenssi</figcaption></figure><p><strong>In any software project, we need to understand the people who will use the product. </strong>There are many different points of view onto what approach we should take.</p><h3>Spool: Vision, feedback, culture</h3><p>Some promote approaches to usability practice alternative to User Centered Design (UCD).</p><p>Spool (2008, 2009) calls the attention of the usability community to the risk of accepting methodologies blindly, of following them as dogma. Instead of measuring the results, he says, usability practitioners tend to focus on convincing people: “We are following the right methodology, so the product must be good”.</p><p>Instead of UCD, which he argues never worked, but leads to people following the process blindly, he encourages what he calls informed design. This is a reward system for any design activity such that the effectiveness of the activity can be measured.</p><p>Spool states having researched successful and unsuccessful interaction design projects. He claims having found three quality attributes successful projects had in common: a long-term user experience vision, a working feedback loop, and a culture of encouraging design failure.</p><blockquote><em>“Vision : Can everyone on the team describe what the experience of using your design will be like five years from now?” (Spool, 2008, 2009)</em></blockquote><p>The point here is that you have a larger goal, and when you take daily baby steps in your design, you can tell whether those steps are towards what you’re aiming, or not. This <strong>seems to also facilitate consistency, as everyone in the team are supposedly aiming for the same, shared goal</strong>.</p><blockquote><em>“Feedback : In the last six weeks, have you spent more than two hours watching someone use yours or a competitor’s design?” (Spool, 2008, 2009)</em></blockquote><p>The usefulness of feedback from actual users is rather obvious. Spool seems to stress the <strong>importance that everyone in the team have the experience of seeing real users use your design</strong> — supposedly, in order to remember just how differently real users perceived your design than you did.</p><p>The reason Spool argues for six weeks as the maximum amount of time one should be allowed to not sympathize with users, is that according to him, after that time memories fade. In an online, distributed development environment, we want to regularly expose developers to perceptions about how users experience their designs.</p><blockquote><em>“Culture : In the last six weeks, have you rewarded a team member for creating a major design failure?” (Spool, 2008, 2009)</em></blockquote><p>Here, Spool argues that <strong>encouraging failure results in a culture of learning from that failure, instead of making contributors ashamed or afraid of mistakes</strong>. This also seems to facilitate creativity and trying also experimental design ideas.</p><p>Regardless of the validity of Spool’s criticism against UCD, his propositions for things to include when designing for our actual users look useful, because they can be adopted seemingly without burdening the team with a heavyweight process.</p><p>Open source, for example, has been considered loosely a form of distributed participatory design (Barcellini et al., 2008; Terry et al., 2010) . Participatory design is concerned about democracy at work and about democracy in design. In its roots then, its approach to design is quite similar to the ideals of open source (Nichols &amp; Twidale, 2003), where transparency of the development process is a key value.</p><h3>Participatory design</h3><p>In UCD, the focus is on researching the users so that designers can make better design decisions. In contrast, participatory design seeks to empower users as decision makers in the design process itself.</p><p>Researcher-designers are thus expected to facilitate user-designer cooperation instead of representing the users (Iivari, 2009) . Ehn (1993) approaches the question of communicating understanding about the intricacies of work, between designers and users, in terms of wittgensteinian language-games:</p><blockquote><em>“If designers and users share the same form of life, it should be possible to overcome the gap between the different language-games [of users and designers]. It should, at least in principle, be possible to develop the practice of design to the point where there is enough family resemblance between a specific language-game of the users and the language-games in which the designers of the computer application are intervening. A mediation should be possible.” (Ehn, 1993, p. 70)</em></blockquote><p>Within the domain of participatory design there are techniques, supposedly helping both users and designers see “other person as partner” instead of “other person as problem”, recognizing the differences in perspective of different stakeholders (Allen et al., 1993). Also in the context of an open source project, users and developers have different language-games. Participatory design explores the conception that making mediation possible between those language-games facilitates design and user participation through enhanced communication.</p><p>Erickson (1996) discusses telling stories, considered perhaps an initial, less formal alternative to scenarios , as a similar “equalizer” of different participants of discussion, since storytelling requires no special skills. This comes very close to the challenge of involving users in development that seems to have a culmination point in open source development.</p><p>An open source community indeed engages users at a level of discussion. Observation of users in their real working environment is difficult — and sharing those observations in a way that engages the community (such as a video narrative illustrating users’ environments) raises privacy issues — and again, is very time-consuming. Thus, the notion of a solution encouraging users to further participate in the design instead of being observed is a very tempting one.</p><p>However, Iivari (2009) states that in the OSS project she studied, users do not have actual decision making power regarding the OSS but are left in a consultative role. This seems to be true of most OSS projects. Ultimate decision making is left to developers only, to whom a very limited amount of understanding about the users of the software is available in the forums of the community (Iivari, 2009).</p><p>In OSS projects, user involvement is thin from the perspectives of both UCD (no usability practitioners to represent users) and participatory design (the few users who do participate have no true power over the eventual software). Warsta &amp; Abrahamsson (2003) have studied the similarities of agile methodologies and open source development. Sy (2007) builds a case for agile as an efficient framework in which to employ user-centered design.</p><p>Further research could reveal whether these approaches might also be applicable to open source development. So central questions, yet ones without clear answers, seem to include:</p><ul><li>Is there a way UCD understanding could enrich the natural way OSS projects learn about their users?</li><li>Could usability practitioners plug in to the community’s existing means of communication, finding fruitful points of contact with the community while using methods favoured by UCD, such as ethnographies, to fuel design?</li><li>Or should we perhaps concentrate on what seems to come naturally to an OSS community, and only refine user research methods to be based on the open source community’s feedback?</li></ul><p>(Adapted from <a href="http://savolai.net/software/moodle/2010/09/30/masters-thesis-about-moodle-and-open-source-usability/">master’s thesis</a>, Chapter 8.1. Originally published in <a href="http://savolai.net/software/moodle/2015/05/30/user-experience-design-inviting-the-users/">Moodle usability blog</a>.)</p><h3>References</h3><p><strong>Allen, C. D., Ballman, D., Begg, V., Miller-Jacobs, H. H., Muller, M., Nielsen, J., &amp; Spool, J. (1993)</strong>. User involvement in the design process: why, when &amp; how? In Proceedings of the INTERACT’93 and CHI’93 Conference on Human Factors in Computing Systems (p. 254). ACM Press.</p><p><strong>Barcellini, F., Détienne, F., &amp; Burkhardt, J. (2008)</strong>. User and developer mediation in an Open Source Software community: Boundary spanning through cross participation in online discussions. International Journal of Human-Computer Studies, 66(7), 558–570.</p><p><strong>Ehn, P. (1993)</strong>. Scandinavian Design: On participation and skill. In D. Schuler &amp; A.Namioka (Eds.), Participatory Design. Routledge.</p><p><strong>Erickson, T. (1996)</strong>. Design as storytelling. interactions, 3(4), 30–35. doi:10.1145/234813.234817</p><p><strong>Iivari, N. (2009)</strong>. User Participation in ‘Configuring the User’ in OSS Development. International Conference on Information Systems (ICIS) 2009 Proceedings, Paper 199. Retrieved March 19, 2009, from <a href="http://aisel.aisnet.org/icis2009/199">http://aisel.aisnet.org/icis2009/199</a></p><p><strong>Nichols, D. M., &amp; Twidale, M. B. (2003).</strong> The Usability of Open Source Software. First Monday, 8(1). Retrieved from <a href="http://firstmonday.org/article/view/1018/939">http://firstmonday.org/article/view/1018/939</a></p><p><strong>Spool, J. (2008, April 12)</strong>. Journey to the center of design (Slideshow with audio). Retrieved from <a href="http://www.slideshare.net/jmspool/journey-to-the-center-of-design">http://www.slideshare.net/jmspool/journey-to-the-center-of-design</a><br>See also: <a href="https://articles.uie.com/the3qs/">Spool’s own in-depth story</a></p><p><strong>Spool, J. (2009, March 19)</strong>. Journey to the center of design. Presented at the SXSWi 2009. Retrieved from <a href="http://www.youtube.com/watch?v=WCLGnMdBeW8">http://www.youtube.com/watch?v=WCLGnMdBeW8</a><br>See also: <a href="https://articles.uie.com/the3qs/">Spool’s own in-depth story</a></p><p><strong>Terry, M., Kay, M., &amp; Lafreniere, B. (2010)</strong>. Perceptions and practices of usability in the free/open source software (FoSS) community. In Proceedings of the 28th International Conference on Human Factors in Computing Systems CHI ’10 (pp. 999–1008). ACM Press. doi:10.1145/1753326.1753476</p><p><strong>Warsta, J., &amp; Abrahamsson, P. (2003)</strong>. Is open source software development essentially an agile method? In Proceedings of the 3rd Workshop on Open Source Software Engineering (pp. 143–147). Presented at the 25th International Conference on Software Engineering.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25ccd00711c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/user-experience-design-inviting-the-users-25ccd00711c7">User Experience Design in Open Source: Inviting the Users</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regex UCR: Generating different Regex dialects]]></title>
            <link>https://medium.com/interaction-reimagined/regex-ucr-generating-different-regex-dialects-d58f48acdf30?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/d58f48acdf30</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[regex]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 10:47:58 GMT</pubDate>
            <atom:updated>2016-09-13T05:31:57.027Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbnx9XV9VtNIJBOVnwVjrA.png" /></figure><p>How to keep Regex UCR’s UI simple, while supporting pretty much all the features Regex itself supports?</p><p>You might want to read <a href="https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1#.99d28f216">Part 1</a> and <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.jzswg3pmk">Part 2</a> before this to understand what this is about.</p><p>Let’s get started with the simplest possible editing view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*_lDq65GYcUKkfJ2p3cYzSQ.png" /></figure><p>Regex UCR has a default dialect called Simplified Regex, which is the <strong>smallest common denominator </strong>of all regex dialects.<br> <br>When there is only stuff that works in all languages, we do not remind the user of the existence of dialects at all, allowing the user to concentrate on task at hand.</p><h4>Editing existing regex</h4><p>Ok, let’s say <strong>you already have a regex you want to edit</strong>. Say, you are identifying a decimal number in Python.<em> </em>Something like <em>-3.53e4</em>, a pretty small number.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*zZLHEW8Ir5MszA0vqGSWoA.png" /><figcaption>Warning when selected dialect doesn’t support all features used</figcaption></figure><p>You paste it into the regex (text) area of Regex UCR. Your expression gets evaluated and translated automatically into the visual regex syntax.</p><p><strong>We can’t handle named groups in the generic Simple Regex</strong>, so the editor</p><ul><li>highlights unrecognized parts, and</li><li>asks you which dialect you would like to use now.</li></ul><p>So you select Python in the dropdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*fLVduHSsK2LMx0Dh0z_IFg.png" /><figcaption>Incompatibility situation resolved</figcaption></figure><p>Ok, now Regex UCR is in Python regex mode. The warning is removed from the UI.</p><p>You can now edit either, and the change gets reflected in the other.</p><h4>Debugging your regex</h4><p>Now you want to verify your regex actually matches everything you think it does, and none that it shouldn’t. How would you go on doing that?</p><p>There is a button on a toolbar that says “Test”. You click on it.</p><p>There is field to enter some sample text. Also, you can see a button that says “generate random text that matches”. So you do.</p><p>The app generates matches for the regex. In many cases you can see already from this that this isn’t quite what you needed, without having to actually think of different samples yourself. Because producing samples is boring.</p><p>Thanks to Byron Houwens and Sam Sullivan for the discussion that led to the design for multiple dialects.</p><p><strong>If you think it’s your thing, to make more detailed mockups of how a great regex debugger will work, or even to implement that or the above, please join us!</strong></p><p><a href="http://savolai.net/personal/contact-olli/">Contact me to join our Slack channel</a> if you want to work together on this. Our github repository is also now open. So far we have a React-based skeleton UI built. We warmly welcome any help bridging the gap from design to code.</p><p><strong>See also: </strong><a href="https://medium.com/interaction-reimagined/8c9c7b5c74cd">Part 4: Plans forward — licensing and architecture first steps</a></p><p>Main stories about regex UCR: <a href="https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1#.gv5b8269l">Part 1</a>, <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.yht57gzfr">Part 2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d58f48acdf30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/regex-ucr-generating-different-regex-dialects-d58f48acdf30">Regex UCR: Generating different Regex dialects</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regex UCR: Plans forward — architecture and licensing first steps]]></title>
            <link>https://medium.com/interaction-reimagined/regex-ucr-plans-forward-architecture-and-licensing-first-steps-8c9c7b5c74cd?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c9c7b5c74cd</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[regex]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 10:03:36 GMT</pubDate>
            <atom:updated>2016-09-12T18:17:10.533Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 4</h4><p><a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.jzswg3pmk"><strong>Regex You Can Read: How It Works</strong></a><strong> </strong>presented the why and what of Regex UCR design. Now it’s time to look at how we are gonna go about creating actual software.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZof6fZnQBS4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZof6fZnQBS4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZof6fZnQBS4%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f932259f851239c4e1f26d990435368/href">https://medium.com/media/9f932259f851239c4e1f26d990435368/href</a></iframe><h4>What we’ll need next</h4><p>(Updated Sept 9, 2016) This is a GPL’d open source project. My wish is to give out plenty of responsibility to people who share enthusiasm for something like what’s presented above. Below, I present specific areas of responsibility that I would love you to take over, but there is still plenty of room for you to carve out the role that works for you exactly.</p><p>Regex UCR will primarily be a web app. In the long term, the goal is to have an IDE plugin as well.</p><p>We already have a simple non-functional React UI by <a href="https://twitter.com/BHouwens/">Byron Houwens</a>. I am dreaming of TypeScript both client and server side, but this decision really depends on the team makeup and what the key players are comfortable with.</p><p>We would like as much of this as possible to run in the browser, to see how much of this can work also in offline mode (and perhaps also be embedded as an IDE plugin, for example). We can likely do the lexing and parsing client side. For debugging, I think we will need a cloud server that can actually run all/most of the various regex engines. That part can parhaps also be a premium/paid service.</p><p>We’ll also need is a data structure — a <strong>dictionary of some kind — </strong>for this reasoning. <strong>It will contain data about the dialects and their corresponding symbols in the visual notation</strong>.</p><p>Also, though not strictly necessary for the MVP (minimum viable product), we will need the contextual data for the menu, possibly in another data structure. When we are inside structure X, prioritize elements S in the menu.</p><p>Of course we also need the actual UI presentation. In current plans, React and d3 will likely help us here, allowing us to sync the regex and the visual UIs, and to render the visual syntax, along with the cursor and the menu.</p><h4>Plans forward: Modular architecture</h4><p>The aim is to have a plugin architecture built in. As I see it now, there will, in time, be several parts of the UI that are suitable to be implemented as Core Plugins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXmC12JZIxpTwn2QcYRjsg.png" /><figcaption>Element description panel mockup by Byron Houwens, one of the first members of the current small team</figcaption></figure><p>These will be described in future posts, and include:</p><ul><li>Element description panel (prototype championed by Byron Houwens)</li><li>Regex testing/debug panel</li><li>Element insertion panel (idea pioneered by Sam Sullivan)</li></ul><p><strong>All the dialects will be pluggable as well</strong>, as new ones come and go. We will eventually need a dialect definition format that allows defining elements and linking them to elements of other dialects. You may also have noticed that switching between different regex dialects is not trivial in some situations. This is covered in Regex You Can Read: Generating different Regex dialects.</p><p>Our current skeleton of a minimal viable product is built using React. Help with breaking down work into manageable tasks is appreciated to be able to estimate the amount of work that the minimal viable product will require.</p><blockquote>working to map out importer/exporter classes for a base dialect, like PCRE.<br> — Then, we could take those classes and build a set of terms that relate to different sets of our dialect’s definitions. This could be searched very quickly on the backend with something like Elasticsearch…I think we could make this have an acceptable latency for a web app. <em>-Sam Sullivan</em>The vision is one of a web app that can work in <strong>offline mode, at least to a limited extent</strong>. When in online mode, I would very much like to leverage technology that enables collaboration for this, i.e. something like Meteor’s syncing capabilities.</blockquote><p>There <strong>will also be mouse and touch compatible UI </strong>with an element palette and right click menus. We have agreed for now though that getting the keyboard interaction is first priority.</p><h4>Licensing</h4><p>We need doers and shakers. Developers, and crowdfunding experts, please join us. I am not in this for the money — I just believe the quiet majority of users needs someone to champion their point of view in the regex community. <strong>I want to work as collaboratively as is humanely possible. Good design rarely happens by committee, but I welcome fair and open discussion and debate at any point.</strong></p><p>I am here to share and discuss, and to find a financial model that makes this viable. <strong>I will be spearheading creating a crowdfunding campaign. </strong>We will create a fair model together on how to share the income and make this happen.</p><p>The service will be paid/freemium with added features. The source of the product will be open and free for users but it seems reasonable to incentivize IDE developers to pay license fees, by using a license such as GPL.</p><p><strong>That said, </strong>our first priority is making it actually publicly available as a reliable online service.</p><p>I’d be hard pressed to think of this as a purely commercial/closed source product, but I will hear your argumentation, and if you think that’s what it takes to get this into people’s hands, I am prepared to reconsider.</p><p>The funding will roughly be used as follows.</p><ol><li>Maintenance cost of the service, i.e. infrastructure costs.</li><li>Fair, contribution based compensation for designers and developers working on the product.</li><li>Buffer fund to make sure we can prepare for future challenges and product development needs.</li></ol><h3>Your thoughts?</h3><p><a href="http://savolai.net/personal/contact-olli/">Contact me to join our Slack channel</a> so we can work together on this. Our github repository is also now open. So far we have a React-based skeleton UI built. We warmly welcome any help bridging the gap from design to code.</p><p><strong>See also: </strong><a href="https://medium.com/@savolai/regex-ucr-generating-different-regex-dialects-d58f48acdf30#.cduzvavzh">Part 3: Generating different Regex dialects</a></p><p>Main stories about regex UCR: <a href="https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1#.gv5b8269l">Part 1</a>, <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.yht57gzfr">Part 2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c9c7b5c74cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/regex-ucr-plans-forward-architecture-and-licensing-first-steps-8c9c7b5c74cd">Regex UCR: Plans forward — architecture and licensing first steps</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regex You Can Read: How It Works (a Syntax and App for Building Regexes)]]></title>
            <link>https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/f1ef1f577cca</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[regex]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 10:02:56 GMT</pubDate>
            <atom:updated>2017-04-30T12:47:55.922Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnxoFDnsFueN94vs5kgT3g.png" /></figure><p><strong>Regex UCR is to be an app</strong> <em>which removes guesswork from regex composing</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8UMCmXFHumTOsRUooKZpw.png" /><figcaption>Simplified <a href="http://www.regular-expressions.info/email.html">email matching</a> in new visual regex syntax (not for production use; <a href="https://hackernoon.com/the-100-correct-way-to-validate-email-addresses-7c4818f24643#.tp91jump8">there’s a sensible way to do this</a>)</figcaption></figure><p><strong>Keep all the good parts of regex, namely the terseness, depth of functionality, and the fact that it’s widely available. </strong><em>It’s the same regex </em>without the syntax issues or the memorization of special case after another.</p><p>The <a href="https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1">first story about this regex editing design</a> got 87K visits, &gt;400 comments on <a href="https://www.reddit.com/r/programming/comments/4jfuq4/regular_expressions_you_can_read_a_new_visual/">reddit</a> and <a href="https://news.ycombinator.com/item?id=11700725">hacker news</a>, and <a href="https://twitter.com/search?q=%22regular%20expressions%20you%20can%20read%22">a few tweets</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3feac1a26db610f52fbbf1647bf1a282/href">https://medium.com/media/3feac1a26db610f52fbbf1647bf1a282/href</a></iframe><p>(<strong>If you just want to use it already</strong>, go <a href="http://eepurl.com/caemmP">here to enter your email</a> and we’ll let you know.)</p><h3>Input and Editing</h3><p><strong>When you want to match a literal, you type it. </strong>Typed content gets added into a blue box if we are in/near one, otherwise a new blue box gets created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*nXWGW0olAW9BjK3hKWwzHg.gif" /><figcaption>Three samples of how cursor size varies depending on its location in the structure</figcaption></figure><p>The UI provides you with any command when you need it, and guides you through on how to use it. You select the dialect you want, compose the logic, and Regex UCR takes care of the rest.</p><p>Consecutive literal characters are concatenated inside a single blue box.</p><h3>Ctrl+Space Menu</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lwl5kDjqi01yCV_5P_1ewg.png" /></figure><p><strong>Whenever you press Ctrl+Space, you get a menu</strong>. This menu is context dependent: It will present the choices on top that make most sense where the cursor currently is.</p><p>In this example we are inside a group so by default it will suggest quantifiers at the top of the list.</p><p>We will also show this menu when typing backslash \ , opening parenthesis or bracket ( [ or closing parenthesis or bracket ) ]. Perhaps others, too (full stop, dash). We will prepopulate the search menu with that character in question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSOjQotvqR0CYjjRhXTPcg.png" /></figure><p>You can just type backslash expressions like you would in traditional regex. You just add an enter key press after finding the command you want in the menu, to confirm the item selected in the menu is indeed what you want. The corresponding literal is also available in the menu, of course.</p><p>The menu will immediately narrow down the menu contents when you start typing. You can search both among traditional regexes (presented in grey below title) or the titles,<strong> so effectively you can just go ctrl+space and wing it.</strong></p><h4>There are two cursors, one in each view.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*oxmNptc0gkFvmtIeV5iZtw.gif" /><figcaption>Decimal number matching: All the blue boxes are matched literally against themselves, everything else is functional regex one way or another.</figcaption></figure><p>When you move your cursor in <strong>visual view </strong>or <strong>traditional (text) view</strong>, you can see the cursor move in the other view, respectively. You can freely edit either view, and immediately see changes in the other.</p><p>Any character typed outside the Ctrl+Space menu is treated as a literal. If you want to match * or . you can just type them in the visual view as such. They will appear in a blue box — either creating a new one, or added to an existing one. (Any char and quantifiers are added via the ctrl+space menu)</p><p>It’s worth noting that <strong>this is not yet another regex generator</strong>. The two way live conversion ensures you can simply use this to edit any regex you want. <em>There is no lock-in</em>: You can go back and forth between syntaxes freely.</p><h3>Give it to me</h3><p><strong><em>To get early access perks in our crowdfunding campaign, and to know when you can try this in action, go </em></strong><a href="http://eepurl.com/caemmP"><strong>here to enter your email</strong></a><strong>.</strong></p><h3>How you can help</h3><p>Let’s do this together. I mean really together. <strong>Listen to what’s in you that wants to become visible. If you think this project needs that, I’d be really happy to hear about it.</strong></p><p>Regex UCR will primarily be a web app. In the long term, the goal is to have an IDE plugin as well.</p><p>What we most urgently need implementation wise, is a generalizable way of parsing different dialects: Tokenizing them so we can reason about individual symbols, their sequences, and hierarchy. <strong>Any suggestions on approaches, libraries and frameworks that might work for this are more than welcome. </strong>A <a href="http://www.palgorithm.co.uk/2009/03/on-parsing-regex-haskell-and-some-other-cool-things/">parser</a> <a href="https://www.google.fi/search?q=js+parser+combinator">combinator</a> maybe, since regex itself can’t handle hierarchy?<strong> See also: </strong><a href="https://medium.com/@savolai/regex-ucr-generating-different-regex-dialects-d58f48acdf30#.cduzvavzh">Generating different Regex dialects</a> and <a href="https://medium.com/interaction-reimagined/regex-ucr-plans-forward-architecture-and-licensing-first-steps-8c9c7b5c74cd#.k3mcopmjv">Regex UCR: Plans forward — licensing and architecture first steps</a></p><h4>Skills in urgent demand</h4><p>We’re still on the lookout for more people to join us. Particularly, at the moment you would likely need to:</p><ul><li><strong>understand parsing regexes</strong>, have ideas on the <strong>implementation of the data structures needed, or on generating regexes </strong>from the syntax.</li><li>you know React and the JS universe well</li><li>have any experience (or willingness to learn!) doing <strong>usability tests</strong>, user research, or can see the remaining gaps in the current design spec — and are itching to fill them in</li><li>are <strong>skillful with regex </strong>itself and can help us gather data about different dialects and how different elements correspond</li><li>have crowdfunding expertise, know video production, or can offer other strategical help</li><li>further down the road, something like community manager and test lead come to mind as well</li></ul><p><a href="http://savolai.net/personal/contact-olli/">Contact me to join our Slack channel</a> if you want to work together on this and get write access to our <a href="https://github.com/savolai/regex-you-can-read">github repository</a> as well. (Pull requests are welcome too — so far we are small enough to grant people direct access as well.) We warmly welcome any help bridging the gap from design to code.</p><p>Read more about technical aspects and responsibilities available at: <a href="https://medium.com/interaction-reimagined/regex-ucr-plans-forward-architecture-and-licensing-first-steps-8c9c7b5c74cd#.k3mcopmjv">Regex UCR: Plans forward — licensing and architecture first steps</a></p><h3>Subtle Bihari ϽΓΣⱤẛ∁ on Twitter</h3><p>I am loving this. For a person like me who writes Regex once or twice a year it is like relearning it every time. This should help. @savolai</p><h3>Cheers!</h3><p>If you liked this, click the 💚 below. <strong>It helps others discover this on Medium. </strong>Feel free to comment below: Any questions, suggestions or comments are welcome, as always.</p><h4>Most importantly though, <a href="http://eepurl.com/caemmP">enter your email</a> to be notified when big things happen :) <a href="http://savolai.net/personal/contact-olli/">And do contact me to join our Slack channel</a> if you’re interested in working and playing with us.</h4><p>Update 2017–04–30: switched the first example editing to the simpler email matching example</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1ef1f577cca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca">Regex You Can Read: How It Works (a Syntax and App for Building Regexes)</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regular expressions you can read: 
A new visual syntax (and UI)]]></title>
            <link>https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/526c3cf45df1</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[regex]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 11:06:59 GMT</pubDate>
            <atom:updated>2018-11-03T17:04:54.168Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2juwjCrHq6IRY3xHh3XeIw.png" /></figure><h4>Part 1</h4><p>Lots has been written about the problems with regular expressions: learning them, debugging them, etc.</p><p>I propose <strong>a more</strong> <strong>visual syntax </strong>and a<strong> keyboard-usable UI</strong> for generating regular expressions.</p><p>The UI/syntax proposed here helps address issues related to <strong>readability, learnability, and memorability</strong>. Those who readily understand regex will find that this visual syntax does not slow them down. It makes existing regexes easier to read for both novices and true regex superheroes.</p><p>(<strong>If you just want to use it already</strong>, go <a href="http://eepurl.com/caemmP">here to enter your email</a> and we’ll let you know.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8UMCmXFHumTOsRUooKZpw.png" /><figcaption>Simplified <a href="http://www.regular-expressions.info/email.html">email matching</a> in new visual regex syntax (not for production use: <a href="https://hackernoon.com/the-100-correct-way-to-validate-email-addresses-7c4818f24643#.tp91jump8">more sensible way</a> &amp; <a href="https://www.sitepoint.com/improving-apps-onboarding-ux/">onboarding UX advice</a>)</figcaption></figure><p><strong>You write regexes just like you always have — with optional ctrl+space popup menu command completion or insertion</strong>. Also, part of the UI concept is to be able to import existing regex expressions for editing, then export them in your chosen dialect.</p><p>This <strong>dialect-agnostic</strong> <strong>visual syntax </strong>seeks a balance between two ends of a continuum:</p><ul><li><strong>Traditional regexes are so terse that it is hard to tell apart elements and their meanings.</strong> Literals, syntax, wildcards, variable placeholders, etc. are all mashed up together: <br>\b[A-Z0–9._%+-]+@[A-Z0–9.-]+\.[A-Z]{2,4}\b</li><li>Some <a href="https://medium.com/@bseddon/for-me-this-is-a-disappointing-article-b5b2181d7a9c#.8oh32emue">editors</a> do already visualize regexes with charts. They are not directly editable, particularly not with a keyboard. <strong>These representations are typically very verbose </strong>and as such, are not particularly quick to scan through.</li></ul><p>An example from regexper.com:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*yLJKVpwg7Xo7diNdR8rv4w.png" /><figcaption>A regexper.com <a href="http://regexper.com/#%28regular%5Cb%29|%28expre%28s%2B%29ions%3F%29">sample output</a> for the above email example.</figcaption></figure><p>The real power of the visual syntax comes to life with the suggested UI. The UI will particularly help those who find the traditional syntax hard to remember.</p><p>You write a regex as you normally would. The UI will visualize the structure on the fly. <strong>When you find that you can’t remember a command, you can press <em>ctrl+space</em> to summon a search menu</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvEa42y0BCaPl0FbrKN7MA.png" /></figure><p>This menu contains all regex commands and descriptions: You can either search by command (to confirm if you remember the command’s meaning right) or by description (to recall what is the command for given task).</p><h3>Supporting user memory</h3><p>Regular expressions have a hard-to-memorize syntax. This is a particularly serious an issue considering that <strong>most of us do not write regexes for a living</strong>.</p><p>For many users, regex is a tool that gets summoned say, a couple of times a year. When we come back to them, previous learning has faded, and <strong>we might need hours just to get up to speed with the syntax</strong>.</p><p>To solve this, we will augment the above visual syntax with an UI that enables learning. This means three things:</p><ul><li>As mentioned above, the new visual language is dialect-agnostic. <strong>Generate any dialect from your expression</strong>, the engine behind the syntax takes care of the actual generating.</li><li><a href="https://www.nngroup.com/articles/progressive-disclosure/"><strong>Progressive disclosure</strong></a><strong> for learning special element meanings.</strong> The general aim is to make elements self explanatory. To remain terse though, not all meanings are readily visible. If you forget the meaning of a symbol, you can just hover or click on elements to get explainers on what each element does.</li><li>In the visual syntax,<strong> a symbol means the same no matter where in the expression it is shown. </strong>The traditional regex language is context modal: Different characters mean different things in different situations, and have different escaping rules. This is particularly true inside and outside character classes [ ]. These inconsistencies are particularly difficult to remember between usages.</li></ul><h3>Implementation</h3><p>This is a concept design. The idea is that the visual syntax will generate traditional regexes. You could see it as a visual <a href="https://en.wikipedia.org/wiki/Domain-specific_language">DSL</a> that generates (only barely human readable) traditional regular expressions. Ideally, IDEs would have support for this visual syntax such that you could switch between traditional syntax and this visual one.</p><p>See also <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.tspvtsgnq">Part 2: Regex You Can Read: How It Works</a> for further details.</p><h3>@TODO</h3><p>Even this syntax can get unwieldy if the expression is complex enough.</p><p>Also, this does not solve <em>all </em>issues with regular expressions. Namely, it does not solve the core issue more intrinsically built into regexes: <strong>How do I make sure that my regex matches exactly those strings I want it to and none of the ones I don’t? </strong>There are debugging tools for regexes that allow you to find what you want by means of trial and error, but that’s a topic for another post.</p><p><strong>To get early access to our crowdfunding campaign, and to know when you can try this in action, go </strong><a href="http://eepurl.com/caemmP"><strong>here to enter your email</strong></a><strong>.</strong></p><p>Although Regex UCR will likely be open source, we will need your financial support to pay for coders doing the work. Hear things before others as they happen, and receive exclusive perks when our crowdfunding thing happens. (Added August 3, 2016)</p><p><a href="http://savolai.net/personal/contact-olli/"><strong>Contact me to join our Slack channel</strong></a><strong> if you want to work together on this and get write access to our </strong><a href="https://github.com/savolai/regex-you-can-read"><strong>github repository</strong></a><strong> as well. We warmly welcome any help bridging the gap from design to code.</strong></p><p>We’re still on the lookout for more people to join us. We <strong>would especially like more folks who</strong></p><ul><li><strong>understand parsing regexes</strong>, or</li><li>have ideas on the <strong>implementation of the data structures needed or</strong></li><li><strong>on generating regexes </strong>from the syntax or</li><li>have any experience doing usability tests</li><li>are all around regex gurus and can help us gather data about different dialects and how different elements correspond</li></ul><p><strong>We already have a bunch of folks who have shown interest and plans are underway, but discussion is still just getting started. Open source and GPL. Now’s the time to step up!</strong></p><p>BTW, thanks to <a href="http://worrydream.com/LearnableProgramming/">Bret Viktor</a>. His work has provided inspiration for much of this.</p><p>Go <a href="http://eepurl.com/caemmP">here to enter your email</a> and we’ll let you know when we have something you can try.</p><p><em>See also </em><a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.tspvtsgnq">Part 2: Regex You Can Read: How It Works</a> <em>with more samples of syntax.</em></p><p>(Image <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca">from part 2</a> featuring search menu added 2018–11–03)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=526c3cf45df1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1">Regular expressions you can read: 
A new visual syntax (and UI)</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regex UCR: Why This is Different and You Are Not Your Users (A Sidestory)]]></title>
            <link>https://medium.com/interaction-reimagined/regex-you-can-read-why-this-matters-1414a4409ae5?source=rss----778b8ec183e9---4</link>
            <guid isPermaLink="false">https://medium.com/p/1414a4409ae5</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[regex]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Olli Savolainen]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 11:06:37 GMT</pubDate>
            <atom:updated>2023-04-21T11:27:21.572Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>There was ample discussion on both Reddit and HN about <a href="https://medium.com/@savolai/regular-expressions-you-can-read-a-new-visual-syntax-526c3cf45df1">Regular Expressions You Can Read</a>. The question I have for the critical dev community is: Are you talking to help people learn, or to keep your tools just the way you like them?</h4><p>At 80K visitors, the original post struck a nerve. I feel it’s important to find more connection with as much as possible of the regex community, and with the wider developer community. <strong>This is so that we can start working together to solve this.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQ9BEHsqKm9-y3l4M-kqnw.png" /><figcaption>Validate a decimal number with group names (python regex; someone posted this <a href="https://pad.riseup.net/p/regexes-you-can-read-samples">on our pad</a>; updated 2016–08–03)</figcaption></figure><p><strong>Below I present the basic background ideas for the work. They are core to making any product that has appeal to a wider public, </strong>i.e. that draw people as users of your software.</p><p>Do you like to think you are in it to serve your users? <em>Do you believe that the kind of help you are giving, is what your users actually want and need?</em></p><p>How is this related to regexes? In every way.</p><p>The Regex You Can Read (or Regex UCR) vision is to make a tool that is truly accessible to all users. The below quotation describes well the issue we are up against, and applies to regexes too:</p><blockquote><strong>Learning to configure Sendmail via M4 macros, or struggling with an Apache virtual host setup is not real knowledge.</strong> If such a system one day is no longer in use, what remains in your hands, or better, in your neurons? Nothing. <strong>This is ad-hoc knowledge. It is like junk food: empty calories without micronutrients. -</strong><a href="http://antirez.com/news/107">antirez</a></blockquote><p>What are the jungle of regex escaping rules, or the context sensitivity of commands? Meanings varying, for example, inside and outside brackets? <strong>Junk food for the mind. </strong>Just… needless.</p><p>A lot of the cognitive burden could be moved off the user’s mind, on to the processor.</p><h4>The Expert and the Novice Points of View</h4><p>There are two ways to look at Regex UCR and its identity vis-a-vis other tools in the space. There are two perceived user groups: <strong>Experts </strong>who have a voice in the regex community, and <strong>novices </strong>who tend to believe the experts and thus remain silent about their actual needs.</p><p><strong>Novices: </strong>It appears very likely, also judging by the nearly 80K visitors of the previous posts, that there are many novice users to whom regex barrier of entry is just too high. <strong>We can overcome that barrier.</strong></p><p>We target those people, whose professional role doesn’t permit an intensive investment in maintaining an active working regex skill set. For them, Regex UCR provides the <strong>only viable user experience for being interested in using regexes in the first place</strong>. It does not require memorizing arcane conventions.</p><p><strong>The main competitor at the moment for Regex UCR is not regex itself in this space — nor any of the existing software tools— it is doing things by hand</strong>, as no usable alternative exists.</p><p>All the current web tools use the traditional regex syntax, which in itself poses a cognitive burden that is too much for many people. Or they are diagram editors, which are too elaborate, and do not facilitate actually working with regexes.</p><p><strong>Regex experts </strong>who seeing a benefit in Regex UCR see it mainly as a pedagogical tool. “It can help novices get started learning independently”, they might think. And that’s true, of course.</p><p><em>Even this viewpoint is created as a result of the ideal that a regex user needs to master regexes deeply. </em>Experts don’t come to think of the masses of users who find the basic functionality sufficient — if it only were usable. They don’t realize that for a huge part of the population, learning may not happen once and instantly go deep as the tool itself.</p><p>For a large percentage of users, usage of regexes is currently built on repetition of the initial learning phase. They may never be interested in going beyond that, as they tend to forget even that initial learning phase between uses. <strong>With Regex UCR, the initial phase has at least the chance of sticking, so users may be interested in learning even more.</strong></p><h4>Ultimately: You Are Not Your Users.</h4><p>The basic core principle behind all usability work, including Regex UCR is: <em>You Are Not Your Users</em>. Misunderstanding this is the reason why the vast majority of comments about this on reddit and hacker news are so deeply misguided. It is also the reason why a tool like this doesn’t exist yet.</p><p>Regex experts have long since forgotten the dynamics of the pain of learning regular expressions. They were likely very motivated to learn regexes deeply in the first place — that’s how they became the experts they are now, after all. See also: <a href="https://en.wikipedia.org/wiki/Curse_of_knowledge">The Curse of Knowledge</a></p><p><strong>So the understanding that a sea of users exists that want to use regex but do not want to invest so much in learning it, is a blind spot to these experts.</strong></p><p>How come is it so difficult for many to understand just how deeply true the principle of <em>You Are Not Your Users </em>is? While this principle has sound theoretical basis, it is hard to really learn it in a way that is useful in practice, without real hands-on experience.</p><p>Have you actually usability tested your UIs? After you do this enough, you start to realize just how little you understand your users’ point of view. I’m still learning myself, time and again.</p><p><strong>The very fact that you are a developer makes you incredibly blind to the vast spectrum of variety there exists in humankind in relation to ANY computer related skill. </strong>To create successful software, overcoming this deep bias is a basic requirement. Doing usability testing of some kind is the path to gaining that insight.</p><h4>Please join and help us!</h4><p>Our project needs your technical help. But to be able to help, you need to get out of your professional developer circles and go outside to understand why this is really needed, and how none of the existing solutions even begin to help.</p><p>The conversion from dialects to a visual syntax is not trivial, for example. We need all the hands we can get. If you still have any doubts, please respond to me to this article. Make your questions as specific as possible, so we can move forward. <strong>If you want to help people learn (not just show how knowledgeable you are), this is your chance. I really am here to make this happen.</strong></p><p>If we can find enough people to join, we can get crowdfunding and make it open source from the get-go. Otherwise, we may need to play it safer and keep it closed until funding is secured such that we can make sure this is sustainable. All I care about is that we actually get there. Any thoughts on this are welcome.</p><p><strong>Contact me (Olli) via this </strong><a href="https://savolai.net/contact/form/"><strong>snappy form</strong></a><strong> or on </strong><a href="https://twitter.com/savolai"><strong>Twitter,</strong></a><strong> so we can get you on our Slack channel and talk. </strong>We have a github repository for this too, waiting to get published once we have something more tangible — if you want access, just ask. I also have another post coming up that details the whole of the app design further<strong>.</strong></p><p>See also <a href="https://medium.com/interaction-reimagined/regex-you-can-read-how-it-works-f1ef1f577cca#.tspvtsgnq">Part 2: Regex You Can Read: How It Works</a></p><p><strong>P.S. Like a simple exercise on human centered design? Consider how this video relates to the above.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed-ssl.ted.com%2Ftalks%2Ftom_hulme_what_walkways_teach_us_about_design.html&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Ftom_hulme_what_walkways_teach_us_about_design&amp;image=http%3A%2F%2Fpe.tedcdn.com%2Fimages%2Fted%2F1a7f62c995a816807b85781431f2355d0cb17d50_240x180.jpg%3Flang%3Den&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="315" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2673fd2dc9472c5bf314b68151b3b38/href">https://medium.com/media/d2673fd2dc9472c5bf314b68151b3b38/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1414a4409ae5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interaction-reimagined/regex-you-can-read-why-this-matters-1414a4409ae5">Regex UCR: Why This is Different and You Are Not Your Users (A Sidestory)</a> was originally published in <a href="https://medium.com/interaction-reimagined">User Experience and being human — interaction reimagined</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>