<?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[Stories by Nathasya Eliora on Medium]]></title>
        <description><![CDATA[Stories by Nathasya Eliora on Medium]]></description>
        <link>https://medium.com/@elioranathasya?source=rss-b25216e0025a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8Be62B5LHBWd-63p.jpg</url>
            <title>Stories by Nathasya Eliora on Medium</title>
            <link>https://medium.com/@elioranathasya?source=rss-b25216e0025a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:54:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elioranathasya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Flutter x Firebase, the Dynamic Duo]]></title>
            <link>https://medium.com/@elioranathasya/flutter-x-firebase-the-dynamic-duo-b278d1dc5714?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b278d1dc5714</guid>
            <category><![CDATA[ppl-fasilkom-ui]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[ppl2020]]></category>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 11 May 2020 18:25:12 GMT</pubDate>
            <atom:updated>2020-05-12T03:03:32.623Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you looking for an option of architecture for your app project? I have an idea, let’s talk about this duo.</p><p>This article will be another story telling about my PPL team mobile and web app project, Advokasimu. A little fun fact, we build Advokasimu from zero. It was started from an idea brought by our client, Mr Junaedi, to make an app that helps people have easier access to justice with technology. Shout out to him btw, it was a really good idea.</p><p>As the development team, we are going to turn that idea to live. From a concept to a real usable product. Just like building a house, we also need a blueprint of our software. Let’s talk about Software Architecture.</p><h3>What’s a Software Architecture?</h3><p>As said in Wikipedia (don’t worry its being citated from a scientific book),</p><p>Software architecture refers to the fundamental structures of a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.</p><p>Software architecture is a foundation, how we gonna build the software. It needs a careful consideration when planning and designing. Because every implementation ahead depends on it. Also it will be costly if the architecture change in the future.</p><h3>Let’s start.</h3><p>There is no specific request about what kind of software architecture we have to use. Our team has the freedom to choose. Actually, we kinda prepare ourselves to do a website project rather than a mobile app project. We’ve already discussed to use Svelte for front-end and Sapper for back-end. But there’s a change of direction that time, so here we are ended up doing both.</p><p>We already got the app requirements in general. There’s nothing that kinda force us to use some specific stacks. So our consideration was choosing the structure that able to support us best on implementing our features. One additional note: we are all new-learners so we want to choose the one that has good documentation and big community. We hope it will make it easier for us to learn along the way.</p><p>We did a self-research and finally we made our final choice. We use Flutter for mobile app and Svelte for the web front-end. Then we choose Firebase both as our back-end and database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*VwkbMGuytK0q5NeXvcsSqQ.png" /><figcaption>our software architecture beautifully visualized by our team-mate, Farihin</figcaption></figure><p>This article will only cover the Flutter and Firebase only. I found it interesting so I decided to talk about it and give it a pair-name, dynamic duo.</p><p>But before continue,</p><h4>What’s Flutter?</h4><p>As written in its web, Flutter is Google’s UI toolkit for building beautiful, natively compiled applications for mobile, web, and desktop from a single codebase. It’s has fast development, beautiful &amp; expressive UI, and native performance. It is pretty new. It was first introduced in 2018 and people’s interest and the users itself are growing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7qlZ9-kwvXVSgFr571Tlw.png" /><figcaption>interest trend by Google Trend 4/9/18–12/5/20</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*irkYVZIwlpTfKt3QOp_DaQ.png" /><figcaption>cross-platform mobile frameworks used by software developers worldwide 2019 (2)</figcaption></figure><h4>Why Flutter?</h4><p>It does have many features that benefits the users. Like the fast development mode, the cross-platform ability, etc. But here are what got our hearts:</p><ul><li><strong>It’s easy to learn. </strong>We see that Flutter offers a useful yet easy to learn and use concept like its widget, state management, etc.</li><li><strong>Good documentation.</strong> Yes, Flutter has a pretty good documentation. Even they have a YouTube videos and post video regularly about getting-to-know-Flutter. As I said earlier, we will have a reliable source of learning.</li><li><strong>Big community. </strong>Flutter is growing and still is. There are a bunch of articles, discussion forums (ex: stackoverflow), group community (ex: Flutter Jakarta) about Flutter. We feel that if we have a problem in the future, there are a lot of channel to get help.</li></ul><h4>What’s Firebase?</h4><p>(Also) as written in Wikipedia, Firebase is a mobile and web application development platform developed by Firebase, Inc. in 2011, then acquired by Google in 2014. It’s also said in Flutter website (yes, Flutter) that Firebase is a Backend-as-a-Service (BaaS) app development platform that provides hosted backend services such as a realtime database, cloud storage, authentication, crash reporting, machine learning, remote configuration, and hosting for your static files. Wow, all that in one package.</p><h4>Why Firebase?</h4><p>Just like Flutter, Firebase has a lot lot good things offered. It is works both as database and back-end service, even it can help you with hosting and many other things. But here are some why that make us choose it.</p><ul><li><strong>The features support our project. </strong>We have the requirements of our product. A few of them are authentication, storing files, and chat. Firebase can help us with that stuffs so it is a good win.</li><li><strong>It’s easy. </strong>It comes with a concept of collection that easy to understand. That collection consists of documents inside it. For example you have a user collection. It will contains documents and every document represent data of one user. Plus, it comes in a user-friendly dashboard that boost up the experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*WSq5SabruqYw91oJ00LB8Q.png" /><figcaption>few of flutter dashboard features</figcaption></figure><h3>The Dynamic Duo</h3><p>As you can see from above, each of the two are so powerful. It offers so many features to help developers with their project. Yet it is easy to learn. They provides the ‘learning materials’ to help.</p><p>As each of them already comes in great package, it will be even more so if we combined them. Plus the fact that it seems like the two are friends and made suitable for each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFldEEZ6yBIP85cH_19Z9w.png" /><figcaption>firebase on flutter docs</figcaption></figure><p>The dynamic duo comes with a Flutter-Firebase pulggin called FlutterFire (cute name i know). We use a few of them like the cloud_firestore for accessing database &amp; storage and firestore_auth for authentication.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d7bf3660a618a701024bdc3cd16d403/href">https://medium.com/media/5d7bf3660a618a701024bdc3cd16d403/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0e1a554e2e1bf39c1987ef09d722e36c/href">https://medium.com/media/0e1a554e2e1bf39c1987ef09d722e36c/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8aba02935f2c1a0a26339f3d33d191d0/href">https://medium.com/media/8aba02935f2c1a0a26339f3d33d191d0/href</a></iframe><p>Week by week, sprint by sprint I am thankful that we use these two. They help us to meet the project requirements efficiently. Here’s how the dynamic duo help us so much on the project:</p><ol><li><strong>The authentication service</strong> provided was helping us a lot on the first sprint. It makes our registration and login flow easier. It even facilitates us with the user verification service.</li><li><strong>The chat.</strong> From the first time, we already see this feature as a challenging one. We think its not going to be an easy ride. But turns out, this duo help us going thru it (maybe) easier than it would without it. (But I’m not saying it was an easy ride! Still challenging but yay we’ve already done that)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*BIVjO1X6OTuuGbkFqegFUA.jpeg" /></figure><ol><li><strong>Storage.</strong> Our project has to deal with files. We need to store picture for user profile picture and also documents for Advocate registration requirement. Once again, we are able to do it by their help.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*saMtB-va-3sNXZUavEwLBw.png" /><figcaption>image stored</figcaption></figure><h3>Conclusion</h3><p>If you want to learn to build an app and want to learn working with database, I think this duo can be one of your candidates. I, my self and the team (except Jin) were all just started learning mobile programming and we are happy with the architecture we use. It’s simple, easy to learn, and powerful enough to help us bring Advokasimu to live. May it help you too.</p><p>All writing above are my own opinion by my own research and experience working on this project. Hope you can get a little something from this. Thankyou for reading! :)</p><h4>References</h4><ul><li>flutter.com</li><li>firebase.com</li><li>trends.google.com</li><li><a href="https://www.statista.com/statistics/869224/worldwide-software-developer-working-hours/">(2) https://www.statista.com/statistics/869224/worldwide-software-developer-working-hours/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b278d1dc5714" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From-Design-to-Implementation Workflow (feat Figma)]]></title>
            <link>https://medium.com/@elioranathasya/project-design-guideline-with-figma-implementation-tips-4e8fdc5f8765?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e8fdc5f8765</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 11 May 2020 06:38:34 GMT</pubDate>
            <atom:updated>2020-06-19T09:30:15.280Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Design to Implementation Workflow (feat Figma)</h3><h3>A brief — the main idea of the workflow</h3><blockquote>All these processes are connected.</blockquote><p>Just like a river flow, all this development process are part of one big river. The water journey keep going from its source until it ends at the sea. It’s all connected, from the design phase till the implementation phase.</p><p>Believing so, we can say that <strong>if the first step is done right, then it will make the second step easier. </strong>Having a good strategies for each step will help our process better. I believe that the strategy is:</p><blockquote>Make it efficient, scalable, and consistent.</blockquote><p>As the Advokasimu project goes on, self-study sessions, and experiencing working on another project, I found out that here’s a way to help you going from design to implementation more efficient, make sure its scalable (both design and the code) and consistent.</p><p>Let’s go through it one by one.</p><h3>1. Concept your branding and define a guideline</h3><p>Every product has different values to deliver. Every product has it own ways to communicate. Every product looks and feel different. Every product has its own identity. Yes, it’s a branding.</p><p>All those abstract concept and ideas has to be translated into concrete things. In this app, we can communicate our branding through visuals and experience (UI/UX).</p><p>On consepting a branding, it usually comes from the core/the root of the product/the company. It can start from the vision and the mission, what the product want to deliver. This usually being discussed by the product owner or the man behind the company.</p><p>Color is one of the major element of branding. Different color can give you a different feel. Here’s an example of color meaning in branding as being said in <a href="https://99designs.com/blog/tips/branding-colors/">99designs</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w--yweePmqAPSpRheEARXw.png" /><figcaption>Colors in branding, citated from <a href="https://99designs.com/blog/tips/branding-colors/">99designs</a></figcaption></figure><p>We decided to go with red for Advokasimu. By choosing red, we are saying that we’re <strong>passionate.</strong> We have a mission: we’re going to bring justice closer to you, make your access to it easier. It’s also align with MaPPI FH UI (our client) branding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDGvzsD2vPR8H0ldhPcy3Q.png" /></figure><p>Another important element is typography. When talking about typography, we usually talk about these two type of font, Serif and Sans Serif. The difference between them is the ‘tail’ or the decorative line. This two kind of fonts communicate messages differently. According to <a href="https://www.canva.com/learn/serif-vs-sans-serif-fonts/">Canva</a>, Serif will give you a feeling of rustworthy, established, and reliable. While Sans Serif will make your brand feel modern and sophisticated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ngJymlUACePmLith.jpg" /><figcaption>. sans serif vs serif, source: <a href="https://www.impactbnd.com/blog/sans-serif-vs-serif-font-which-should-you-use-when">impactbnd.com</a></figcaption></figure><p><strong>Professional yet accessible</strong> is another Advokasimu values. That’s why we choose to use Sans Serif font. We want to keep it friendly, not too formal but still polite. Later on, we’ll try to keep its elements simple so it feels professional.</p><p>This branding idea will help users recognize and identify us, also build trust and loyalty. But, <strong>how to keep it consistent?</strong></p><p><strong>Define a guideline — </strong><em>sets of recommendations towards good practice in design. They are intended to provide clear instructions to designers and developers on how to adopt specific principles, such as intuitiveness, learnability, efficiency, and consistency.</em></p><p>To make it easier to follow, I’ll talk about the guideline along with its Figma implementation on the second step.</p><h3>2. Define the guideline as Figma styles and assets</h3><p><em>The tool covered in this article is Figma. Our team choose it because it’s collaborative and has great features that suit our needs. Oh, plus it’s free. You can use any other tool out there as you like.</em></p><p>So Figma has a global styling and asseting features. We can save ours there and use it as we go on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FloCAuzCEwaNOs6hyHDuWA.png" /></figure><p>As said previously, we have to have a guideline to mantain consistency, to mantain the branding. The design kit of guideline usually consists of two, styles and assets.</p><h4>Styles</h4><ul><li><strong>Color</strong></li></ul><p>Color play a big role on creating a vibe. For example is greeny-Tokopedia and blueish-Traveloka. As said earlier, we choose red as the primary color. But we also has other colors and here are them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dxDPL865Zgntn8vkYEMKHQ.png" /></figure><p>We don’t really use much color because of we strive for professionals look. We have red as our primary color, green for success confirmation, and the rest are neutrals. If you noticed, we have different colors for the web and app but it still rhymes. The reason is the mobile app red color are too bright to be used on the big screen and there’s a use case when the red color cover the most of the screen. So we adjust it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DDOi-x8qbkyW0k5_NkqpcA.gif" /><figcaption>Adding new color styles</figcaption></figure><ul><li><strong>Typography</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zBSyjHjBW9QCRVgPWcj37g.png" /></figure><p>Typography is a reading hierarcy. It tells you which one is the most important, which one to read first. This hierarcy can be differentiate by font size, weight, spacing, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nYA8_Csm_sr9sQ0tqGfccQ.gif" /><figcaption>adding new text styles</figcaption></figure><p>For the website typography, we use material.io as a benchmark. But we adjust it according to our needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eO-h3_LUFY1kxT44" /><figcaption>Typography guideline, source: <a href="http://material.io/">material.io</a></figcaption></figure><ul><li><strong>Effect &amp; Spacing Styles</strong></li></ul><p>Actually you can make effect style &amp; spacing style. Effect style is a style that will be applied to shape/picture/etc. Spacing style is a guideline for spacing and padding in the app. But we don’t define this on the advokasimu project. You can read more about it on figma blogs.</p><h4>Assets</h4><ul><li><strong>Icon</strong></li></ul><p>We use icons to help user understand a thing better and faster. For example we use icons on navigation bar and we hope they’re navigating more easily because they’re already familiar with it.</p><p>We also use Flutter icon for icons on mobile app and Font Awesome Icons on admin website so it will be more familiar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnMV307yozqlqLWlJNESHA.png" /></figure><pre>Icon(Icons.file_upload, color: Colors.grey)     # file upload icon</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*WHN-UQ-3Cy-fca7qgNmlLg.png" /><figcaption>Admin website icons</figcaption></figure><pre>&lt;i class = &quot;fas fa-folder-open&quot; /&gt;      # folder icon</pre><pre>&lt;i class=&quot;fas fa-user-tie&quot; /&gt;           # person with a tie icon</pre><ul><li><strong>Components</strong></li></ul><p>If there is anything that can be reused, reuse. So the idea is designing elements that can be reused in the future.</p><blockquote>As being said in the Nielsen’s heuristic, make it simple and familiar.</blockquote><blockquote>As being said in the programmer’s heart, don’t add up my job please.</blockquote><p>Actually this component concept will save your time, energy, consistency, and entire life (hehe jk). My team not really doin this at first. Then when the app scales up… you can guess it yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sX8WBiJ3J_bGnQqdjrMTHA.gif" /></figure><h3>3. Build the your page using the style and assets you’ve made</h3><p>All your component will be stored in assets tab. You can drag and drop it anywhere anytime. Make sure everything in the page is built by components. So if there’s a change on master component, it will applies to all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oV9JZgbSK38s3i8uc4kaUQ.gif" /><figcaption>building a page process</figcaption></figure><h3>4. Code your global styles and make reusable components</h3><p>We use Flutter for mobile apps and Flutter has a theme feature. So we can define global styles there and use it anywhere. For the Svelte website, we defined it as a css file globally.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a8aee2488a5adf477209824bf5285ff3/href">https://medium.com/media/a8aee2488a5adf477209824bf5285ff3/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/821f297010896df3e5744f8a24baa58b/href">https://medium.com/media/821f297010896df3e5744f8a24baa58b/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ef99586e7019b125f7abd42309a05517/href">https://medium.com/media/ef99586e7019b125f7abd42309a05517/href</a></iframe><h3>5. Code happily ever after</h3><p>Yes after you have your styles and assets ready on the coding deck, you can sail captain. You can put all the components to pages and code the rest.</p><p>This Figma guy also has a CSS code rendered. Even though it’s not perfect, we can still take a look at it to get help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q3WAtOv4-ySOkgv7JhDegg.png" /><figcaption>contoh rendered code dari selected text</figcaption></figure><h3>Ok, what’s the problem before using this workflow?</h3><p>From the very first time me and my team aware that we have to have a design guideline to make our design consistent. At that time, it was minimal.</p><h4>First days</h4><p>We’ve already defined the typography, colors, and component. But actually we forgot about the spacing for elements and styles for objects. Hehe, we don’t know its a thing. But we’ll refactor and add consistent spacing rules in the future.</p><p>The typography style in general was okay. We use Poppins all the times and we know that the app bar and title use bold and the rest are regular weight. But the problems comes more when talking sizes. Sometimes when designing we feel like we need to add more colors or more sizes, or more styles like opacity or shadow. But we don’t directly update the guideline, so when the other team mates need that new style, it will turn out different.</p><p>For colors it’s not really a problem because we only have a few. So it’s kinda obvious what each color are for. But for similar colors, maybe we should name it or give a little description on when to use it.</p><p>For components, we kinda did it.. but not for all. Only made these. So the hi-fi design is consist of independence element we made again and over again. Not reusing components.</p><p>And from these first days, we encountered a few struggles. Here are them.</p><h4>The struggles</h4><ul><li><strong>Hard to mantain consistency</strong></li></ul><blockquote>The UI coding part was like sailing, without a consistent captain.</blockquote><p>Our consistency (that time) was questionable. We already have the Figma design, but sometimes the design and the reality are different. For example, the font size looks good on the Figma but not when we implement it. So we have to improvise and adjust the font size. Sometimes we just add this line in the element we are working on.</p><pre>font_size = # any size that works</pre><p>The possibility of the-size-that-works is not in our guideline is high. If we adjust the element one by one, can you smell the inconsistency that will happen a head?</p><p>The typography rules is not a strict guide. It helps mantain hierarcy and the most important part for me is the ratio of each size. We should define theme (in flutter) or style (in css) so we have global style that we can adjust globally if there’s something gone wrong.</p><ul><li><strong>Cost twice bigger than it should</strong></li></ul><p>Redefine the color hex every time.</p><blockquote>Implementing scrum encourages you to has high adaptability.</blockquote><p>Changes are our best friends. We revise a lot. Like a super lot. Not everything already being thought of, talked out, or defined neatly at the beginning of the project. We have to have this high adaptability of changes. So every new sprint, we usually come to the client office and discussed sprint backlogs items deeper.</p><p>We can see the the struggles from design and implementation side. From design side, if there’s some changes it will need some effort to revise. We don’t really do components in our Figma at first so we have to <strong>revise every element one by one. </strong>Kinda wow rite?</p><p>From the implementation side, not really different. If there’s a change, we have to adjust it line by line. Because at that time we don’t define our style globally. We don’t really use components too, so… one by one it is. But hey its part of learning! The most important thing is now we know the more efficient way to do it.</p><ul><li><strong>There’s new update.. Sorry!</strong></li></ul><p>It’s ok to grow the guideline as the requirements scales up. As long the branding is being mantained.</p><p>The rules is</p><blockquote>For every new rules you make, put it on the guideline. Immediately.</blockquote><p>Another tip, you can make separate pages in Figma to help you organized. Add a label maybe FIX or READY when it is final, WIP (Work in Progress), Components, or Guideline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*3ISn3lJOlTiKQP0UO4yisQ.png" /><figcaption>our pages</figcaption></figure><h4>The After</h4><p>Of all five sprint we have, the third sprint was a web sprint. That was the one and only time we work on website, the rest are mobile app. It’s like a new beginning. Learning from the last two sprint, I decided to revise the Figma before the sprint starts. There’s a few changes in wording and content so I revise that, made the guideline more clearly and implementing all the tips above.</p><p>Yes, I can say all of the guideline, Figma, and implementation tips above are not a myth. The User Interface development phase went more smoothly and structured rather than our first days with mobile app. It also helped us in managing our tasks better. We list the sprint tasks by components and pages designed in figma. We also define our style globally at first in style.dart. Our design for admin website is a self-hand-craft by us so this guideline and layer infos are really helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nCNrexmOi7UB-usF0Eycig.png" /></figure><h3>Summary</h3><p>Okay after a long way, here’s the summary of our conversation.</p><ol><li>Concept your brand guideline</li><li>Save it as styles in Figma and make the assets</li><li>Build the Hi-fi mockup with the style and assets you’ve already made</li><li>Code your global styles and make the reusable components</li><li>Code happily ever after</li></ol><p>After all that, there’s a pattern along the workflow.</p><blockquote>Define. Reuse.</blockquote><h3>Conclusion</h3><p>I really wish I knew all these things before PPL started. It would really make everything easier and save a lot of time &amp; effort. But that’s okay anyway! It’s called learning. I hope this article can help you on your upcoming PPL or any of your project. It still may not the very best way to do it, but I hope you can get something from our experiences! Good luck on your journey and don’t forget to have fun!</p><h4>References</h4><ul><li>figma.com</li><li><a href="https://uxdesign.cc/ui-ux-design-feat-brand-values-88fff12d90b8">https://uxdesign.cc/ui-ux-design-feat-brand-values-88fff12d90b8</a></li><li><a href="https://www.interaction-design.org/literature/topics/design-guidelines">https://www.interaction-design.org/literature/topics/design-guidelines</a></li><li><a href="https://material.io/design/typography/the-type-system.html#type-scale">https://material.io/design/typography/the-type-system.html#type-scale</a></li><li><a href="https://blog.tubikstudio.com/color-in-design-influence-on-users-actions/">https://blog.tubikstudio.com/color-in-design-influence-on-users-actions/</a></li><li><a href="https://99designs.com/blog/tips/branding-colors/">https://99designs.com/blog/tips/branding-colors/</a></li><li><a href="https://www.canva.com/learn/serif-vs-sans-serif-fonts/">https://www.canva.com/learn/serif-vs-sans-serif-fonts/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e8fdc5f8765" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make The Best Out Of Your Team]]></title>
            <link>https://medium.com/@elioranathasya/make-the-best-out-of-your-team-6221be4f10c6?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6221be4f10c6</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 02:04:40 GMT</pubDate>
            <atom:updated>2020-04-28T07:23:54.899Z</atom:updated>
            <content:encoded><![CDATA[<p>Wow what a title. First thing first, please read the disclaimer. It may be the most most important part of the story.</p><h4>Disclaimer</h4><p>This article is not self-claiming that our team is the best or we’ve already reached our best. This is a perspective on how we value people and relationships in our team. This is written also as a form of sharing on our journey to be better every day. Hope you enjoy reading this article just like we enjoy PPL! Hehe, just kidding.</p><p>Let’s start!</p><h3>People, Team, and Their Best</h3><p>The main key points are these three: the people, the team, and their best.</p><h4>Why Bother About The People?</h4><p>Someone once said, people are the most valuable thing in the company. In this case, people are the most valuable thing in the team when working on a project. It’s the core of the project, the one that gives it life and makes it real. People are the actuators. Without people, a project is just a myth.</p><h4><strong>What’s the Best Out of the Team &amp; Why Bother?</strong></h4><p>Every person and every team has its potential, has its maximum capacity to do things. Trying to make the best out of it means tying to unlock those unseen things we could become. The key points here are not only to achieve the maximum potential as a student, but also as a person and a team.</p><p>Being able to make the best out of your team will benefit you in many ways. It makes the development process goes well, plus making it fun! Building a good friendship is as valuable as the learning process along the journey, right?</p><h3>About Le Pepe The Team</h3><p>Let me introduce you to my PPL team, Le Pepe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6DMo-YwDw6nWLcOjNDZYAQ.png" /><figcaption>Our first workshop!</figcaption></figure><p>The developer team consists of five-person. From left to right, there’s Farihin, Falya, Jin, Cici (me!), and Igna. We are friends but never worked together as a dev team before. So we start everything from zero.</p><h3>Our Journey on Trying to Make The Best Out Of Us</h3><h4>Get to know each member personally</h4><p>After showing you the team, let me introduce you to each member. There is Falya, the front-end girl that ALWAYS has her job done very quickly compared to the rest. Don’t know how she does that tbh. Then there’s Jin the mob-app guy since the very first day. He was the only one that has experience on mobile app and now he’s being a Flutter and Firebase master. Next is Igna, the real coding guy in the group. His flight hours in this field doesn&#39;t need to be questioned. He is full of fun facts on how to be a tech guy HAHA, from simple vs code hacks to serious Svelte coding. Then there’s Farihin. The one whose house was a basecamp (before quarantine). We always made a sleepover appointment but sadly haven&#39;t got a chance to do that. :( Every sprint planning, Farihin is up on the gitlab board thingy and PBI sheets. Lastly there’s me, Cici, the newbie. Hehe.</p><p>Here’s a picture of us on our early days. Ps: it’s also a documentation of the time when Farihin already wearing a super neat outfit but ends up being a notul guy :( It’s ok Ihin! It was helpful.</p><iframe src="https://www.instagram.com/p/B8bt4TYHQM3/embed/?cr=1&amp;amp;rd=https%3A%2F%2Fwww.instagram.com" width="658" height="882" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1c70b2d74c33ea98def3ec73bda91ed/href">https://medium.com/media/b1c70b2d74c33ea98def3ec73bda91ed/href</a></iframe><p>At the first phase of team forming, try to know as many as we can about each team member. How do they work? How do they build a relationship? What&#39;s their strength? What&#39;s their weakness? What&#39;s the risk that may happen with all the differences of personality? Knowing all the team member well will make it easier to understand each other.</p><h4>Get to know the team</h4><p>Knowing each person on the team isn’t enough. When you team up, the team is born as a new entity. The team is seen as one, not as individuals anymore.</p><ul><li><strong>The Vision</strong></li></ul><p>I KNOW it may sound too serious. What does vision have to do with a small PPL team?? Ok, let me give an example. Le Pepe team took 4 PBI on the first sprint, 5 on the second sprint, 6 on the third sprint. It increments every sprint and that was crazy. I sometimes can’t believe that we decided to choose that many. It is true that our PBI comes in large numbers, 24 (and still counting?). We know that we are not required to finish them all, but we give it a try anyway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aadRYmMLcPq-k9qv" /><figcaption>Our PBI and the progress</figcaption></figure><p>We believe we can and everybody agreed on the decision of taking those (many) PBIs in one sprint. Our team is kind of an optimist. Agree on same vision, getting together as one head, and finding how the team wants to sail is an important thing to figure out.</p><ul><li><strong>Strength and Weakness</strong></li></ul><p>This is really important! Knowing what’s your team do best and what’s that still need improvements is a big win. With the information, we can build a suitable strategy to be better. For us, it’s the can-do attitude that brings out positive energy. But we have to work on our deadliner-workflow. Thank you sprint retrospective, we are able to acknowledge it.</p><ul><li><strong>Work pace and Workflow</strong></li></ul><p>Every team has its own work pace and workflow. So far, we still can keep up the PBI we took and nobody was left behind. We already found our pace. Now let’s talk about the workflow. If you can find the right one, it’ll make everything easier. For us, it was working together as a team on person. We usually go somewhere (Jin’s grandma house, plaza gedung baru) and code together. When doing so, it’ll make it easier if we’re having a trouble or confused about something. We can ask and get help directly.</p><p>Since it is quarantine session, we are not able to do that. At first days, the communication was a total disasters. We don’t really catch up with each other progress and every scheduled call session was end up as a myth. But after retrospective, we talked about this and try to find a new way: Discord.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*L54AXjRhBviGr3uNU0Fzrg.png" /><figcaption>Our Discord</figcaption></figure><p>If anyone doing PPL related things, we get into the Ngoding Kuy voice channels. So if there’s other team members doing the same, it’ll feel like you are not alone. Other than that, we usually do a code together session here. Will talk about it later in the other section.</p><h4>Grow together</h4><p>One may have a specialty on one or few things. A good developer team helps each other grow as a programmer and also as a person. We share knowledge to each other and help each other with what we can do. Here are some ways of us to grow together.</p><ul><li><strong>Sharing is caring</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*90A_dy9G9tHOMka-8q-rqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*5SMc3HZ99FqA264-J2tRuw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*q347vJ586Yda1FXKG3LTcQ.jpeg" /><figcaption>sharing helpful informations</figcaption></figure><p>Yes, sharing information is one form of caring. We always share information related to PPL to the telegram group. Those photos above are some of examples. Usually, we share YouTube videos, YouTube channels, articles, courses, and so on.</p><ul><li><strong>Study time session</strong></li></ul><p>When it comes to the admin web part, the stack used is Svelte. We never used it before, except Igna. So we scheduled a study time session to learn about Svelte before we code our tasks. It’s like watching YouTube tutorials with the ability to interact with the streamer and the other watchers haha.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*iOKOKtxWDLrZHcjzd0Ob2Q.png" /><figcaption>Le Pepe study time + my face hehe</figcaption></figure><ul><li><strong>Flutter Meet Up</strong></li></ul><p>That one time we attend a Flutter Meet Up by Flutter Jakarta community at Google office. We learned more and have a chit chat with a Flutter engineer and the other member of the community. We are also featured on the Flutter Jakarta tweet! Haha.</p><h3>Flutter Jakarta on Twitter</h3><p>It&#39;s a wrap. Terima kasih buat partisipan yang sudah datang hari ini. See you next month 🙌🙌</p><h4>Be more than a partner, be friends</h4><p>Where is the fun when all of this was being done as a formality only?</p><ul><li><strong>Do other things outside the work!</strong></li></ul><p>We talk a lot about anything we want to talk about, from sop buah to candi. We also has a ritual, which is a birthday celebration. Birthday celebration is always fun! Also an excuse to buy some foods. We usually do a not-really-a-surprise surprise every time its someone&#39;s birthday.</p><p>Ping pong was Le Pepe boys favorite. They play like all the time. Even when it close to deadlines. Back before quarantine, if they haven’t show up on daily standup: look for them at ping pong table.</p><ul><li><strong>As one: no one left behind</strong></li></ul><p>Everyone has theirown tasks to get done. But that doesn’t mean when our part is done, then we are done. No. As a team, team progress is everyone’s progress. On the last minute (and I mean day minus one) we usually have a group call. Making sure every task is already completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*Zkdg8Mo5lBDUcBlFrI0XaA.png" /><figcaption>us working together on our unfinished sprint 3</figcaption></figure><p>When there’s a problem or something that hasn’t been done yet, we try to work on it together. The picture above is us discussing a problem on our sprint 3 journey. It really warms your heart when you know you are not alone. There are these people that will be there until we all real-real finish.</p><p>No one left behind counts every time. We always call each other. It is mostly because we are not a morning person. So we have to make sure everybody awakes when there’s an event, whether it is daily standup or else. For example on the last sprint review, the three of us still sleeping at 12 pm when the SR will start in no time. :) sorry guys</p><ul><li><strong>Take some time to reflect</strong></li></ul><p>Thanks to the Scrum guide, there’s a thing called Sprint Retrospective. As I already said on the Agile article, this event facilitates us to take a time to reflects on our last two weeks. Where did we go well and not yet. We list down our good, bad, start and stop on the retro board. Then we discussed about it. In the end, we list down real action we want to take in the future. It helps us improve and tighten the bond at the same time.</p><h4>Have fun</h4><p>I think having fun is one of the most important. By enjoying what we do, everything is easier. By doing things happily, it will turn out better, right?</p><h3>Conclusion</h3><p>That’s all about how we try to make the best out of us. How we try to do and be better every day. This is more like a journey journal. We are still learnin but I hope you can get something from this writing. Working in team always harder, but it always enlightens. Goodluck on your team!</p><p>Bytheway, we are documenting our journey on instagram. You can follow us on @lepepedepepeel. See you later!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6221be4f10c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Love-Hate Relationship with TDD]]></title>
            <link>https://medium.com/@elioranathasya/love-hate-relationship-with-tdd-7f7aba234d32?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f7aba234d32</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 27 Apr 2020 14:53:43 GMT</pubDate>
            <atom:updated>2020-04-28T04:07:56.851Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Confession</h3><p>If I were being asked about the hardest part on PPL, I’ll answer loud and clear,</p><blockquote>Test-Driven Development implementation.</blockquote><p>Yes, I am being 100% serious. Even until the third sprint ended, still, my love story with TDD not going as easy as river flow.</p><h3>What’s this TDD?</h3><p>Before going further, let’s get to know TDD first. TDD stands for Test-Driven Development. It’s a software development approach that turns the requirements into test cases, then the code is written after that to pass the test.</p><p>As Kent Beck said on <em>TDD by Examples </em>book, TDD has a special (yet catchy) mantra. It’s called:</p><blockquote>Red/Green/Refactor</blockquote><p>It’s easier to understand if it&#39;s shown as a diagram, so I’ll drop the pic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/0*AtFa9iXwsCwxMa-L.png" /><figcaption>Image courtesy of <a href="http://www.agilenutshell.com/test_driven_development">http://www.agilenutshell.com/test_driven_development</a></figcaption></figure><p>It has three famous rule, which are:</p><ol><li><strong>Red</strong> — You can’t write any production code until you have first written a failing unit test. Write a little test that doesn’t work, perhaps doesn’t even compile at first</li><li><strong>Green</strong> — You can’t write more of a unit test than is sufficient to fail, and not compiling is failing. Make the test work quickly, committing whatever sins necessary in the process</li><li><strong>Refactor</strong> — You can’t write more production code than is sufficient to pass the currently failing unit test. Eliminate all the duplication created in just getting the test to work.</li></ol><p>The color-naming is so catchy because it’s just like the color of the Git pipeline. We use tagging [Red], [Green], and [Refactor] to label our commits. So that we can see everything a little bit clearer. The red and green phase is better to be done concurrently, it’s usually in a difference of seconds. Before implement, write failing test it first, then code the real construction.</p><p>It goes like this. When you want to code a feature, think about how it will work. After using that user story, break it into steps and write the test to make sure it works. The test should better test the behavior, not the implementation. Commit it with Red tag. Implement the code, commit it with Green tag. Then refactor to make the code neater. Yes, it may sound simpler than it is.</p><h3>About TDD in PPL</h3><p>Fasilkom, where I study now, really encourages the students to do TDD as it was our nature. It’s been introduced early to us since the first website-related course on the third term. Then we go deeper about it on the fourth term on Advanced Programming course. Now it’s also getting a spotlight on the PPL (Software Development) course.</p><p>On PPL, we are expected to write codes with 90% code coverage. We have this Individual Review day when the class assistant will grade our test and code. Yes, we are being watched on our TDD journey on doing the project every two weeks. It sounds like we have already become best friends with TDD, isn’t it?</p><p>Not really.</p><h3>My (&amp; Team’s) TDD Journey</h3><p>I don’t know with the other student, but I don’t really try to follow the TDD concept at first. Back on the third term, I saw it more like an option (which it is) on developing my works. I did it on minimum efforts, not my best. Just to pass the grading criteria when I required to. On my lazy days, I didn’t even do it at all.</p><p>It was never really a problem, until now. Like it or not, PPL made us do it. Turns out I find myself (really) struggling along the way. Not only me, I see my Le Pepe team also find it a little bit challenging when talking about test-first. On our daily standup, <strong>TDD as a blocker</strong> often sits as one of the top ranks.</p><p>People said beauty is pain, but today I’ll talk about how TDD is pain for me.</p><h3>The Pains</h3><p>As I said earlier, for me it feels more like a blocker rather than a helper. It needs big effort and sacrifices.</p><h4>It needs MORE time</h4><ul><li><em>Double the time to think. </em>I have to think about how to achieve the goal. First I have to figure out the way to make sure the behavior right, think about the main idea on how to test, then the main idea on how to implement.</li><li><em>Double the time to learn. </em>I am just an ordinary student with no hardcore coding background. Before doing things, I need to learn everything first. By doing TDD, I need to learn way to do the test and learn how to build the thing literally on the green phase.</li><li><em>Double the time to code. </em>We need to write two kinds of code, so the time needed is also doubled.</li><li><em>Double the time to check if it works. </em>Sometimes I write the test, then implement it. Then the implementation code works. BUT MY TEST FAILS. For example, I am expecting to see the title on the screen. THE TITLE IS THERE, but it failed. Oh my, I have to work on the test one more time to make it pass when my implementation code already works. Sometimes (or more like most of the time) finding where I did wrong is not as easy as flipping hand.</li></ul><h4>It’s harder to learn</h4><p>It’s WAY MUCH easier to look for <em>how to code asynchronously in flutter </em>than looking for <em>how to test asynchronous code in flutter </em>(still struggling with this async test btw)<em>. </em>There are a bunch of articles talking about how to implement, but not about how to test. Also bad news when the how-to-implement already hard to look for, because the how-to-test is definitely way more harder to find. This makes test is harder to learn then implementation.</p><h4>It slows down the pace</h4><p>As you can see from the previous points, it needs time. When we need more time to do the job, it means the job will take longer to finish. The work pace can drop from 2 features a week to 1 feature a week, for example, because we have to put buffer time to prepare. Not forget to mention that in TDD, tests should be the first thing to do. So if we haven’t written it yet, we can’t move on to the next one. So when you have little time, it can cause a problem. As I said earlier, on the standup meeting the conversation of ‘sorry I haven’t done it, I have a struggle on the test thing’ are often heard. The dependent feature has to wait ‘till it&#39;s done.</p><h4>The code coverage metric doesn’t really equal good quality</h4><p>We are being told to keep our coverage high enough. Code coverage is a metric that counts how many <strong>lines </strong>of your code already covered by the test.I understand this is due to the first rule, only write code you need and make a test for every code. So when we apply the method right, the high coverage will come as the code goes.</p><p>In my opinion, it can be <em>one </em>of the metrics but not fully blindly take it for the only consideration of good codes. I think the main idea is to check if the code behavior successfully<strong> works as expected.</strong> I know that this metric will encourage us to work cleaner, because it means that every line written is needed. But try to achieve perfect score on it is not needed. It can be translated wrong that makes people writing <em>not really</em> useful test code just to maintain the line coverage.</p><p>The coin has two sides, so does this TDD. I have to be honest that the pains come with some beneficial deals. Here are them.</p><h3>The Bright Side We Paid For</h3><p>After explaining how it was literal pain, we can’t say it was useless after all. We have to be fair that it also brings some good.</p><h4>Plan better</h4><p>Telling you have to write test code, make you sit and take time to think. What am I exactly want to build? How can my code can be called ‘succeed’? This help us to list the details of minimum criteria that should be in our codes. It makes us see clearer about specification and goal of features, so we know exactly what to build.</p><h4>Less code, yet efficient</h4><p>When you know exactly what to build, you’ll write less code. You will only code what you needed. That’s efficient. That’s also saving you effort and time.</p><h4>Boost the confidence with ‘it works’ guarantee</h4><p>When you already write the minimum criteria your code has to have, when it passed we can say that the code works as expected. It’ll give much confidence when the code is live, cause we know it is works properly. Worry less.</p><h4>Neat library</h4><p>Implementing TDD will make you have a neat repository. You label every progress, every milestone. It’s like having a structured files and folders in your cabinet. It has clear index, you know when you add this functionality you know when you change the code and so on. If you need to get back to some checkpoints or want to debug anything, you’ll easily find it.</p><h4>Save you time (in the future)</h4><p>Even though it needs more time on the first development phase, it’ll save your time in the future. How come? Your code is working. The probability of there’s some bugs is minimize. Other than that, you’ll find it easier to debug because your repository is neat and each functionality already tested so it’ll help you repair.</p><h3>The Love-Hate Relationship</h3><p>With all the pain and bright sides, you can see the good and bad TDD offers (or at least I experienced). It makes the relationship more complex and confusing. I know it offers good, but man, it costs much. It is feel like love-hate relationship between us.</p><p>It costs me MUCH time, but will save time in the future. It needs a big effort to learn how to do write test, but it will save your effort because it minimizes the probability of you-looking-for-a-bug because it’s already passed the test. It slows down the pace but ensures the quality of your code performance. See how this relationship is complicated?</p><h3>The Tweaks</h3><p>Another confession (wow this writing is more like confessions of sin rather than an Individual Review article), I am not a good TDD coder and I am aware of it. So I try to keep implementing the main idea. I list all my user stories, whats the expectation. Here’s example of the sequence of use and expectations of detail kasus page. We can edit and update the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*0xChXxknBLNE_t_yoX_0Ng.png" /><figcaption>notes on expectations</figcaption></figure><p>I’ll try to make test according to the notes as I can, do the implementation, then check it manually if the implementation passed according the notes.But when the test fails like my story on the pains section, I let it be. If I am not capable to make the test that covers all that, I let it be. If the code already covers my list notes, I’ll go with it. If there are still time, I’ll refactor the test code (because my problem usually on how the test written than the implementation not meeting the expectation).</p><h3>Conclusion</h3><p>TDD is a skill. It&#39;s not some rule we read somewhere and then instantly be able to implement it fluently. Its a habit and a habit is being built over time. Also, it needs knowledge &amp; mastery of the stack used to be able to do it concurrently.</p><p>I think I am (and a few friends) struggling right now is because we’re still on the learning phase, not yet the mastery. I am new to the stack used, new to the software development environment, new to the TDD implementation. So trying to achieve those all in the given time is hard work. When the time is not much, doing TDD needs more consideration.</p><p>Despite all, I see the good of the paradigm. I understand why Fasilkom encourages us to implement this paradigm on projects-related. But choosing the paradigm to use is not a take-all-the-best-practices into one bowl. The consideration of needs, situation, time and everything else has to be involved. The TDD <em>may or may not</em> be suitable for me, you, everyone and every project.</p><p>It’s a nice thing to have the skill. It benefits us as a programmer in many ways. It helps us plan &amp; write only-needed codes and ensures our code works properly as expected. It’s a <strong>brilliant idea </strong>that betters software development world. But still, it’s an <strong>option</strong>. If you want to use it then good, but if you don’t then ok. You already got the big idea (that’s the most important part!), you can take it and do some tweaks that meet your needs and situation.</p><p>Just like music, TDD is a rhythm. When you’ve already found the right beat, you’ll find joy playing the rest of the song. Cheers!</p><h4>References</h4><p>Read deeper about TDD &amp; find other perspectives in these sources.</p><p>Beck, K. (2014). <em>Test-driven development by example</em>. Boston: Addison-Wesley.</p><p><a href="https://medium.com/@ayltai/why-dont-developers-use-tdd-in-practice-b1e2362d4676">Why don’t developers use TDD in practice</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f7aba234d32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nielsen Guide to UI Design]]></title>
            <link>https://medium.com/@elioranathasya/nielsen-guide-to-ui-design-48aa1e457fc?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/48aa1e457fc</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 21:19:59 GMT</pubDate>
            <atom:updated>2020-06-19T06:17:04.789Z</atom:updated>
            <content:encoded><![CDATA[<h3>Advokasimu x Nielsen’s 10 Usability Heuristic</h3><p>Pertama kali mendengar Nielsen’s 10 Usability Heuristic adalah saat baca <em>feedback</em> dari asisten dosen setelah mengumpulkan desain <em>prototype</em> Advokasimu. Waktu itu asal lewat aja, cuma dibaca untuk melakukan revisi. Ternyata feedback tsb ditulis dengan prinsip-prinsip <em>interaction design</em> secara umum menurut Jakob Nielsen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*OvSF3el1HhyqSCClXfpCYg.png" /><figcaption>feedback terkait nielsen’s heuristics</figcaption></figure><p>Secara tidak sadar, kelompok kami sudah melaksanakan sebagian dari prinsip tersebut. Setelah mendapat masukan diatas, kami pun melakukan beberapa perubahan pada desain kami. Mari kita bahas advokasimu x nielsen’s heuristic.</p><h3>1. Visibilitas Status Sistem</h3><p>Sistem yang baik harus bisa memberikan pengguna informasi tentang <strong>apa yang sedang terjadi.</strong> Jangan biarkan pengguna bertanya-tanya. Misalnya pengguna ingin tahu dimanakah ia berada sekarang di sistem, maka kami memberikan penanda tab aktif berupa warna di navigation bar. Contoh lainnya pengguna ingin tahu apakah form yang dia isi berhasil terkirim atau tidak, maka kami menambahkan sebuah pop up pemberitahuan. Menampilkan <em>circular progress bar</em>/<em>skeleton layout</em> saat halaman sedang dimuat dan <em>toast </em>juga termasuk lho.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OpQAmXGZgagktW5BoR_Mg.png" /></figure><p>Intinya, komunikasikan pada pengguna apa yang sedang terjadi. Jangan biarkan mereka kebingungan atau bertanya-tanya karena tidak terinformasi tentang apa yang sedang terjadi.</p><h3>2. Keselarasan sistem dengan dunia nyata</h3><p>Supaya pengguna mudah beradaptasi dengan sistem, kita harus menggunakan elemen-elemen yang familiar. Elemen yang dimaksud bisa bermacam-macam, contohnya pemilihan kata, icon, bentuk component, format tanggal, dan lain-lain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iYi7bzDDqoVQL3kwNWAokA.png" /></figure><p>Di Advokasimu, kami menggunakan icon-icon yang representatif dan sering ditemui di kehidupan sehari-hari. Misalnya untuk menggambarkan tab home/beranda kami menggunakan rumah. Untuk form input kami juga menggunakan kotak seperti isian form kertas pada umumnya. Kami juga menuliskan format tanggal dengan DD/MM/YYYY seperti penulisan tanggal sehari-hari.</p><h3>3. Kontrol dan Kebebasan Pengguna</h3><p>Kadang kita tidak sengaja salah klik atau berubah pikiran dan ingin kembali ke halaman sebelumnya. Kita perlu memberikan kebebasan pengguna untuk berpindah-pindah dan memberikannya kontrol untuk melakukan navigasi.</p><p>Dengan memberikan kontrol dan kebebasan, pengguna merasa aman untuk berinteraksi dengan sistem. Pengguna selalu tahu bahwa ia selalu dapat kembali ke state sebelumnya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYK7iPK8B9otAGrQLiKC8A.png" /></figure><p>Seperti gambar-gambar di atas, Advokasimu selalu memberikan emergency exit kepada pengguna. Mobile app dan website kami mengimplementasikan hal tersebut.</p><h3>4. Konsistensi dan Standar</h3><p>Menjaga konsistensi dalam suatu sistem adalah hal yang penting. Misalnya menggunakan wording yang sama untuk setiap hal yang bermaksud sama, menggunakan styling yang sama di setiap halaman, dsb. Hal ini akan membuat sistem kita <em>predictable</em> and <em>learnable.</em></p><p>Ada dua macam konsistensi, internal dan eksternal. Konsistensi internal mencakup konsistensi dalam aplikasimu. Contohnya, di Advokasimu kita memakai nuansa putih merah dan font Poppins di setiap halaman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tsk8FnPE1qaxrCvgUcgmZA.png" /><figcaption>Konsistensi internal</figcaption></figure><p>Sedangkan konsistensi eksternal adalah hal yang biasa diterapkan di sistem lainnya. Sebaiknya kita pun mengikutinya juga, supaya saat memakai sistem kita pengguna sudah terbiasa. Misalnya biasanya tab account berada di paling kanan navbar, maka kami melakukan hal serupa di Advokasimu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kunbKtgpxk5ruzwRxCEtiA.png" /><figcaption>Konsistensi eksternal</figcaption></figure><h3>5. Pencegahan Kesalahan (Error)</h3><p>Terkadang pengguna bisa salah melakukan sesuatu saat berinteraksi dengan sistem. Bisa saja dia tidak sengaja menekan tombol keluar padahal tidak bermaksud demikian. Untuk mencegah action-action seperti itu, diperlukan pencegahan kesalahan (error prevention). Desain punya peran signifikan untuk mencegah hal-hal tidak diinginkan di atas.</p><p>Error prevention yang kami implementasikan adalah sebuah pop up konfirmasi jika ada pengguna yang ingin keluar. Buat saya pribadi, login ulang sangat menyebalkan karena harus mengisi form login. Jadi memiliki confirmation pop up seperti ini akan sangat membantu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kc0CHF0isVUXqlClJ0dyXQ.png" /></figure><h3>6. Recognition rather than recall</h3><p>Akan lebih baik <em>u</em>ser mengenali daripada mengingat-ingat. Menurut rule <em>recognition rather than recall</em>, memberikan elemen, <em>action,</em> dan opsi yang jelas dan <em>to the point </em>akan memberikan pengalaman yang lebih nyaman bagi pengguna. Pengguna tidak perlu repot-repot mengingat langkah dari suatu <em>state</em> ke state lainnya atau susah-susah mengingat informasi mengenai aplikasi. Informasi yang diperlukan harus terlihat atau mudah diakses kapan pun diperlukan.</p><p>Ada banyak contoh penerapan poin ini, misalnya <em>last seen </em>seseorang di chat atau rekomendasi <em>next word </em>yang akan diketik. Di Advokasimu sendiri salah satu contohnya adalah <em>card summary</em> yang berada di beranda. <em>Card summary</em> ini berisi ringkasan konsultasi kasus yang ditugaskan kepada Advokat tsb. Dengan sekali lihat ia mendapatkan gambaran berapa banyak kasus yang sedang ia tangani dan berapa kasus baru yang harus ia mulai tangani.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D07sYv6WY_0uyiuUbvjkZg.png" /></figure><h3>7. Fleksibilitas dan Efisiensi Penggunaan</h3><p>Apakah kamu pernah baru meng-<em>install</em> suatu aplikasi, lalu diberikan pilihan untuk <em>custom install?</em> Itu merupakan salah satu contoh penerapan poin ini. Pengguna dapat langsung memilih <em>recommended installation</em>, namun jika pengguna memiliki keinginan tertentu dapat memilih <em>custom installation </em>agar dapat disesuaikan dengan keinginannya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*chgemLyB99NP5gHcuUAduw.png" /><figcaption>WinSCP installation, source: <a href="https://winscp.net/eng/docs/ui_installer_setuptype">WinSCP documentation</a></figcaption></figure><p>Contoh lainnya bisa juga saat meng-<em>install</em> aplikasi baru, biasanya akan ada <em>onboarding screen. Onboarding screen </em>ini biasanya berisi penjelasan produk atau sedikit tutorial. Biasanya akan disediakan tombol <em>skip </em>sehingga pengguna memiliki kebebasan untuk melewati atau melihat keseluruhan <em>onboarding screen.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*KywSCzxdXhngCCoI.png" /><figcaption>Contoh Slack onboarding screen, source: <a href="https://clevertap.com/blog/user-onboarding-best-practices/">CleverTap</a></figcaption></figure><p>Poin ini juga sering dikaitkan dengan <em>critical path</em>. <em>Critical path</em> adalah langkah paling efisien untuk melakukan suatu action. Untuk pengguna lama, namun tetap ada tanpa harus membuat pengguna baru bingung karena terlalu banyak yang harus dipelajari. Contoh familiarnya adalah fitur like instagram. Untuk pengguna yang baru menggunakan instagram, mereka belajar untuk menggunakan fitur tsb dengan mengklik tombol hati di kiri bawah. Namun untuk pengguna lama kebanyakan memakai <em>critical path/shortcut</em>nya yaitu <em>double click</em> pada foto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*_k4CGoCePQpbGDQAOAYXug.gif" /><figcaption>click on the icon vs double click to like</figcaption></figure><p>Kedepannya kami ingin menambahkan <em>onboarding screen </em>serupa di aplikasi Advokasimu. Kami juga ingin menambahkan <em>critical path </em>di tabel daftar kasus. Untuk melakukan <em>action </em>admin tidak perlu masuk ke halaman detail terlebih dahulu. Semua bisa dilakukan dari beranda dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tLvGquMq6q15JwS530UHTQ.png" /></figure><h3>8. Desain yang minimalis dan estetis</h3><p>Desain minimalis yang dimaksud disini bukanlah harus menggunakan flat design atau pun warna-warna monokrom. Minimalis disini adalah bagaimana caranya mengkomunikasikan informasi seperlunya saja ke UI kita. Hilangkan informasi yang tidak relevan atau tidak perlu. <em>Communicate, don’t decorate</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cZAxQZ56tm6Un0fo_wdsQ.png" /></figure><h3>9. Bantu Pengguna Mengenali, Mendiagnosis, dan Pulih dari Error</h3><p>Jika terjadi sebuah error, pengguna ingin tahu kenapa. Maka dari itu kita perlu menampilkan error message yang jelas, supaya pengguna tahu dimana kesalahannya. Lebih baik lagi jika kita memberikan sugestion berupa solusi. Dengan demikian user dapat mendapat pencerahan bagaimana keluar dari state error tsb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*66eClgUHZxeJQXGJ0qhtwQ.jpeg" /><figcaption>error message</figcaption></figure><p>Contohnya jika field password masih kosong dan pengguna menekan tombol login, akan ada error message seperti di atas. Selain memberi tahu dimana letak kesalahannya, pesan tersebut juga memberi tahu user apa yang harus ia lakukan supaya field-nya tidak error lagi.</p><h3>10. Bantuan dan Dokumentasi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EnCKvxElJ7Cv5k8GF_-mFg.png" /><figcaption>Fitur Bantuan</figcaption></figure><p>Dalam mendesain sebuah aplikasi, kita ingin membuatnya semudah mungkin agar dapat digunakan walaupun tanpa panduan. Namun tetap menyediakan bantuan dan dokumentasi cara pemakaian aplikasi adalah ide yang baik. Kami memiliki fitur user manual dengan pertimbangan jika ada pengguna yang kesulitan menggunakan aplikasi. Dengan fitur ini, kesulitan akan teratasi. <em>Better safe than sorry.</em></p><h3>Kesimpulannya,</h3><p>prinsip-prinsip ini bukanlah suatu panduan khusus yang mengikat. Seperti poin nomor 10, prinsip ini akan membantu kita memberikan pengalaman interaksi yang baik dan <em>helpful </em>bagi pengguna. Saya sangat merekomendasikan menjadikan heuristik ini sebagai acuan saat mendesain sebuah sistem.</p><p><em>Referensi</em></p><ul><li><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48aa1e457fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing — Quarantine Edition]]></title>
            <link>https://medium.com/@elioranathasya/usability-testing-quarantine-edition-999523a910e1?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/999523a910e1</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ppl2020]]></category>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 20:42:31 GMT</pubDate>
            <atom:updated>2020-04-18T12:42:50.250Z</atom:updated>
            <content:encoded><![CDATA[<h3>Usability Testing — Quarantine Edition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWvpId8WWjOJm9hdpt05WQ.png" /></figure><h3>Story time!</h3><p>Balik lagi ke cerita Advokasimu. Produk Advokasimu terdiri dari aplikasi android untuk masyarakat &amp; advokat dan desktop website untuk admin. Sekarang kami sedang di sprint 3 yang agendanya adalah ngurusin website, sebelumnya selalu mobile. Rasanya kayak pindah rumah karena kita pindah repo, pindah environment, pindah bahasa, pindah framework (belajar lagi kak.. 😊), dan juga pindah desain. Lembaran baru istilahnya.</p><p>Merefleksi dua sprint ke belakang, ada pertanyaan-pertanyaan yang sering muncul. Pertanyaan kecil dan cenderung sepele, tapi lumayan bikin mikir karena kami juga gatau jawaban pastinya.</p><blockquote>Hm, orang ngerti gak ya kalau wordingnya kayak gini?</blockquote><blockquote>Ini buttonnya nyaman dipencet gak sih kalo ukurannya segini?</blockquote><blockquote>Warnanya keterangan gak ya?</blockquote><blockquote>Tulisannya kekecilan gak ya?</blockquote><blockquote>Orang kesel gak ya kalo disuruh isi form sebanyak ini?</blockquote><p>Biasanya selalu berakhir dengan dijawab sendiri alias kira-kira. Ternyata, ada satu step yang tidak kami lakukan di sprint sebelumnya: <strong>Usability Testing.</strong></p><h3>Apa itu Usability Testing?</h3><p>Buat anak developer yang ngedesain juga, pasti udah akrab banget sama Usability Testing alias UT. Setelah sebuah desain prototype selesai dibuat, perlu divalidasi ke orang-orang yang bakal menggunakan aplikasi tsb. Yap ini salah satu contoh persona in action. Kalo kamu ketinggalan, bisa baca tentang persona <a href="http://medium.com/@nathasyae">disini</a> ya.</p><p>Selama ini kami mendiskusikan user experience, flow, &amp; desain hanya dengan tim dan klien. Kami belum pernah validasi ke calon user benerannya. Selama ini perspektif yang kami jadikan acuan decision adalah perspektif tim, belum pernah dapat input dari luar. Ini kurang <em>fair </em>karena kami adalah orang-orang yang merumuskan sendiri aplikasinya, orang-orang yang sudah 1000x membahas flow sampai bosen. Maka dari itu kami ngga pernah ada kesulitan saat mencoba aplikasi kami sendiri. Kami udah ngerti banget semua konsep dan cara kerjanya, tapi <strong>orang lain belum tentu.</strong></p><p>Oke karena sekarang lembaran baru, mari belajar jadi lebih baik. Berhubung sempat ada perubahan-perubahan <em>requirements</em> dan <em>wording</em> (agile banget nih), mockup websitenya kita permak lagi. Setelah selesai revisi, kami mau coba menjalankan UT.</p><p>Tunggu dulu. Pepatah bilang, kalau ga ada tantangan ga seru. Kebetulan sekarang ini sedang masa sulit corona. Kota-kota sedang PSBB dan kita semua lagi karantina mandiri di rumah. Jadi sprint 3 fully remote. Ini tantangan baru buat tim kami, karena mode efektif kami adalah ketemu ngerjain bareng. Plus tantangan juga untuk rencana UT kami. Waduh, terus gimana?</p><h3>Sebentar, emang biasanya UT itu gimana sih?</h3><p>UT adalah metode yang sering digunakan untuk melakukan validasi desain interaksi. Kita bakal meminta pengguna untuk melakukan task-task tertentu sebagai simulasi penggunaan aplikasi. Nanti <em>behaviour</em> pengguna akan kita amati dan analisis. Kita sebagai pihak yang mengadakan test (bisa dibilang UX Researcher) hanya berperan sebagai fasilitator, tidak boleh memberikan contekan.</p><h4>Secara umum, langkah-langkahnya seperti ini.</h4><ol><li>Tentukan task apa saja yang mau ditest. Susun skenario, success criteria, dan metricsnya.</li><li>Tentukan partisipan sesuai dengan persona.</li><li>Menyiapkan kebutuhan testing seperti device dan prototypenya. Bisa pakai banyak cara, misalnya play prototype figma di hp. Berikan brief juga tentang penelitian dan UT ini terlebih dahulu.</li><li>Selanjutnya UX Researcher mejelaskan task yang harus disimulasikan pengguna tanpa memberitahukan caranya. Ketika pengguna mencoba, perhatikan bagimana dia berinteraksi dengan aplikasi kita.</li><li>Analisis hasilnya &amp; susun perbaikan yang harus diaplikasikan ke desain kita.</li></ol><h3>UT dengan Maze Design</h3><p>Beberapa waktu lalu teman saya minta tolong untuk UT proyek dia pake <a href="http://maze.design/">Maze Design.</a> Dari situ saya baru tau kalau teknologi udah secanggih ini. Sekarang udah ada fasilitas untuk UT Simulation &amp; Report dan plusnya bisa gratis untuk 1 project! 😜 (gapapa)</p><p>Akhirnya Le Pepe mau ikutan pake maze design ini buat UT website admin. Kita coba sesuaikan langkah-langkah di section sebelumnya dengan penggunaan maze design.</p><h4>0. Set Up</h4><p>Bikin akun dan copy link prototype kamu ke webnya. <em>Voila,</em> project kamu akan terbuat secara otomatis. Kalo kamu pakai figma bisa play prototype &gt; share prototype &gt; copy link (anyone can view) buat dapetin link prototoypenya.</p><h4>1. Menyusun task, skenario, dan success criteria</h4><p>Kayak UT offline, UT online pun perlu task, skenario, dan success criteria. Di maze, task yang harus diselesaikan pengguna disebut mission. Di UT kali ini, ada empat task yang ingin ditest:</p><ol><li>Verifikasi Akun Advokat Baru</li><li>Menjadikan Advokat sebagai Admin</li><li>Menugaskan Kasus pada Advokat</li><li>Mengubah Pengajuan Kasus</li></ol><p>Setelah menentukan task, susun skenario dan success criterianya. Contohnya kalau nomor satu kira-kira seperti ini.</p><p><em>Task:</em> Verifikasi Akun Advokat Baru</p><p><em>Skenario: </em>Farihin baru mendaftar sebagai advokat di advokasimu. Status akunnya sekarang ‘belum terverifikasi’. Cobalah untuk <strong>mem-verifikasi akun Farihin.</strong></p><p><em>Success criteria:</em> pengguna berhasil melakukan verifikasi akun dengan menekan button verifikasi pengacara di halaman detail Advokat. Path yang harus ditempuh adalah</p><p>halaman dashboard utama — <em>(klik tab advokat )</em>→ halaman daftar advokat — (<em>klik lihat detail)</em> → halaman detail advokat —<em> (klik verifikasi akun)</em> → pop up verifikasi — <em>(klik Ya, verifikasi)</em> → Done.</p><p>Selanjutnya kita perlu menentukan metrics. Untuk mengetahui tingkat keberhasilan, perlu suatu tolak ukur yang reperesentatif dan dapat diamati. Nah parameter yang akan diamati tersebut disebut metrics. Disini kami menggunakan empat metrics:</p><ul><li><em>average duration:</em> berapa lama user membutuhkan waktu untuk mengambil keputusan selanjutnya (pindah page/klik sesuatu)</li><li><em>misclick rate:</em> berapa persentase user klik di tempat yang tidak kita harapkan (salah klik)</li><li><em>success rate:</em> berapa persentase user berhasil menyelesaikan mission</li><li><em>give up rate:</em> berapa persentase user menyerah menyelesaikan mission</li></ul><h4>2. Menentukan Partisipan</h4><p>Kita lihat lagi personanya, yang akan menggunakan aplikasinya siapa ya? Kalau di web dashboard ini, yang pakai adalah staff MaPPi umur 20–30 tahunan. Jadi kita akan test ke orang dengan background yang sama. Target partisipan kita adalah staff MaPPi, petinggi MaPPI, orang-orang di range umur tsb.</p><h4>3&amp;4. Testing time!</h4><p>Saatnya melakukan testing dengan memberikan link UT ke partisipan. Jangan lupa jelasin untuk apa dan kasih tau bakal direkam juga. Kita juga memberikan <em>brief</em> di awal simulasi. Oya, jangan lupa minta data penggunanya seperti contohnya nama dan umur sebagai data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*H7rJfrx5l9hdOrPNPPCaDQ.png" /><figcaption>contoh mission task verifikasi advokat baru</figcaption></figure><p>Ini visualisasi gambaran mission task 1, yaitu Verifikasi Akun Advokat Baru.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YIcN6Q5UX0tnfTUfNeoFA.gif" /><figcaption>contoh mission task verifikasi akun advokat baru</figcaption></figure><p>Di Advokasimu proses UT-nya masih on the way, bakal diupdate lagi kalau ada <em>findings</em> baru. <em>Stay tuned.</em></p><h4>5. Analisis Hasilnya</h4><p>Setelah testing selesai, saatnya melakukan analisis. Analisis akan dilakukan berdasarkan metrics yang sudah kita tentukan di awal. Maze Design menyediakan report yang sangat super cantik dan lengkap! 😍😍 Mari kita bahas satu-satu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARPLGhKuPi6kgmdeJ69fSA.png" /><figcaption>Overview Page</figcaption></figure><p><strong>Overview page</strong> ini akan menampilkan informasi keseluruhan mission, status success, dan score usabilitynya. Disini sayang sekali ada 2 mission yang merah (give up) karena kesalahan teknis sehingga harus merefresh dan akhirnya misinya terlewat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*uzsKxI71_v_1Wyj-_ZZg7g.png" /><figcaption>Mission summary</figcaption></figure><p><strong>Mission Summary </strong>akan menampilkan informasi secara keseluruhan untuk satu mission. Ada informasi total testers, berapa persen click rate yang salah, durasi rata-rata perhalaman, success rate, dan bounce rate. Bisa dilihat juga user path journeynya. Ini part kesalahan teknis jadi banyak merah-merahnya huhu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*T2i2hhV5zgeRb8-rLzf8nA.png" /><figcaption>Usability Breakdown</figcaption></figure><p><strong>Usability Breakdown </strong>akan membahas behaviour pengguna lebih detail. Sebagai contoh ada 4 halaman yang harus dilewati pengguna. Di tabel dapat dilihat rata-rata detik yang dibutuhkan pengguna sebelum mengambil decision. Ada juga baris informasi misclick rate yaitu berapa persen pengguna memencet hal di luar ekspektasi kita. Berdasarkan gambar disamping, score usability kita bagus yey!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*wyA1-TG1wRbFnTvXlkloAA.png" /><figcaption>Optimal Path Analysis</figcaption></figure><p>Terakhir adalah <strong>Optimal Path Analysis. </strong>Disini diberikan analisis lebih detail untuk masing-masing screen beserta heat mapnya. Heat map merupakan visualisasi dari interaksi pengguna dengan sistem kita. Disini terlihat pengguna langsung mengklik di tempat yang tepat sesuai harapan kita. Terdapat juga informasi halaman mana saja yang sudah baik, perlu pengecekan, atau perlu revisi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*T5kek4XI_sn7O0btIWYfvQ.png" /><figcaption>Screen to rework, check, great</figcaption></figure><p>Dari report diatas, kita bisa analisis website kita sudah cukup baik atau belum. Kalau avg time tinggi, artinya pengguna butuh waktu untuk menentukan decision apa yang ingin diambil selanjutnya. Penyebabnya bisa banyak, mungkin terlalu banyak pilihan sehingga butuh waktu lama untuk menentukan, mungkin dia tidak tau harus apa, dll. Bisa jadi desain sudah baik, hanya perlu sedikit perbaikan.</p><p>Kalau misclicknya tinggi, bisa dilihat dari heatmap kecenderungan user seperti apa. Lalu kita bisa menganalisis penyebabnya. Mungkin flow kurang jelas, mungkin ada sesuatu yang misleading, dll.</p><p>Kalau give up percentagenya tinggi, perlu perhatian khusus. Akan berbahaya jika dia menyerah karena tidak tau harus berbuat apa karena kebingungan. Jika ini terjadi, perlu dilakukan analisis lebih lanjut. Mungkin ada beberapa halaman atau flow yang harus di-rework. Bisa juga user mengalami gangguan teknis seperti user saya. Jangan lupa komunikasi dengan usernya, tampung feedback dan saran dari mereka.</p><p>Setelah menganalisis behaviour pengguna dan penyebabnya, kita dapat mulai merumuskan alternatif-alternatif yang mungkin jadi solusi.</p><h4>6. Repeat!</h4><p>UX Research adalah proses yang iteratif. Buat dapetin desain yang paling sesuai, perlu proses <em>trial and error </em>yang ga sebentar. Selalu ada ruang untuk <em>improvements</em>. Setelah desain diperbaiki, ulangi lagi prosesnya. Lihat apakah <em>user journey-</em>nya jadi lebih baik setelahnya dan begitu seterusnya😊</p><p>Sekian cerita Usability Testing — Quarantine Edition. Memang proses testing ini melelahkan karena harus dilakukan berulang-ulang. Namun, dengan selalu melibatkan user akan membantu kita membangun produk yang tepat sasaran. Semangat para <em>UX researcher!</em> Semoga keadaan cepat pulih, jaga kesehatan, pakai masker dan jangan lupa cuci tangan ya. Semoga bermanfaat dan sampai jumpa lagi di tulisan berikutnya!</p><h4>Referensi</h4><ul><li>Referensi UI/UX PPL 2020</li><li><a href="https://www.userfocus.co.uk/articles/writing-usability-task-scenarios.html">https://www.userfocus.co.uk/articles/writing-usability-task-scenarios.html</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=999523a910e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Jangan dalam Clean Code]]></title>
            <link>https://medium.com/@elioranathasya/6-jangan-dalam-clean-code-2276e92b723?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2276e92b723</guid>
            <category><![CDATA[ppl2020]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 18:21:50 GMT</pubDate>
            <atom:updated>2020-04-13T18:21:50.352Z</atom:updated>
            <content:encoded><![CDATA[<p>Halo! Kalau kamu baca tulisan ini, kemungkinan besar kamu adalah seorang programmer. Dalam rangka menjadi seorang programmer yang baik banyak hal yang harus kita pelajari, salah satunya peraturan-peraturan atau <em>best practice </em>dalam mengoding<em>. </em>Berikut peraturan utama dan terutama yang selalu diingatkan berulang-ulang oleh para programmer seluruh dunia:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*_A_kpd0D3_K2ALaDZoXZ-A.png" /></figure><p>Iya, clean code.</p><h3>Clean code itu seperti apa?</h3><p>Ada banyak kriteria yang harus diperhatikan supaya kode kita bisa dibilang clean code. Hari ini kita bakal ngomongin 6 ‘jangan’ dalam clean code.</p><h4>1. Jangan ngasal ngasih nama</h4><p>Kata orang tua, nama adalah doa. Nama variabel, parameter, fungsi, dan semua yang memerlukan penamaan di kodingan pun demikian. Berikanlah nama yang <strong>representatif. </strong>Dalam sekali baca, kita bisa tahu maksud dari variabel/fungsi itu.</p><p>Coba lihat code form builder registrasi Advokat dibawah ini.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*3BiJI1bVXQTXF4OOuMqm1A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*p1N9DQ4F4AfwUP2SHWKhGg.png" /><figcaption>sebelum refactor (kiri) vs setelah refactor (kanan)</figcaption></figure><p>Dalam sekali lihat kita bisa menebak bahwa showNamaInput akan menampilkan input field untuk keperluan nama, showNoKTP untuk no KTP dan seterusnya. Namun terselip dropdownLayout() yang agak membingungkan dia akan menampilkan dropdown untuk apa ya di form ini?? Setelah direfactor, jadi paham bahwa itu untuk input jenis kelamin.</p><p>Ini akan sangat berguna buat kamu alias penulis kode dan juga orang lain. Kode jadi lebih mudah dimengerti dan akan mempermudah proses <em>debugging </em>jika ada kesalahan<em>.</em></p><h4>2. Jangan plin plan</h4><p>Jadi orang harus <strong>konsisten,</strong> katanya. Ternyata nulis kodingan juga begitu. Siapa sangka wording ternyata sangat amat penting di dunia per-<em>software</em>-<em>development</em>-an ini. Kemarin kami sempat pusing sendiri karena wording kita beda-beda banget. Diskusinya jadi susah, beresin kodingannya apalagi. Untuk membahasakan 1 entity kita punya banyak nama panggilan, mulai dari pihak tersangka, pihak langsung, pihak terkait, sampai pihak perwakilan. Pusing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*BP2ddw2mGF9hrOWSkcGfeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*ymLouFvz27j2F0UeuEaPsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*xP7H03n9PxClIdPOE3suug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/239/1*XcLKIs66mXf4cTstyjls6w.png" /><figcaption>contoh perbedaan wording yang bikin pusing</figcaption></figure><p>Penyebabnya banyak, misalnya ada perubahan dari kliennya (contohnya semua wording pengacara diganti advokat), kurang koordinasi setelah mengerjakan task masing-masing, ada salah nulis di figma, atau dari awal memang kita belum sepakat mau pakai wording apa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*nhsWQg-krlIBhU9ESLKkfw.png" /></figure><p>Selain penamaan variabel, penamaan file kita juga kurang konsisten. Kadang pakai camelCase, kadang snake_case. Kelihatannya hal sepele sih, tapi alangkah lebih baik kalau semua konsisten untuk mantain scalabilitynya kalau proyeknya makin besar (plus ga bikin pusing).</p><p>Ketika ada sesuatu yang ngga konsisten, tiap anggota tim bisa menangkap informasinya jadi beda-beda juga. Bisa miskom, bisa salah ngoding, bisa pusing. Yap kesimpulannya, <em>be consistent</em> itu penting banget.</p><h4>3. Jangan bikin fungsi yang handle banyak tugas</h4><p>Fungsi harus simple dan efisien. Satu fungsi baiknya hanya menjalankan satu tugas saja. Seperti dibawah ini contoh fungsi validasi form yang kita pecah-pecah sesuai tasknya. Mereka sama-sama melakukan validasi form, namun ada 3 task berbeda yang harus dilakukan. Jadi dipisahkan menjadi 3 fungsi berbeda pula.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*uubKpkBqgVEhPni3HhmJoQ.png" /><figcaption>contoh clean functions</figcaption></figure><h4>4. Jangan tulis komentar yang nggak perlu</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YaXWsXGVDMk4q8FjuUYkKw.png" /><figcaption>kebiasaan tidak menghapus unused comment</figcaption></figure><p>Siapa yang suka ganti-ganti kodingan tapi kode sebelumnya dicomment bukan dihapus?? Sayaaa. Hehe. Biasanya kalau ada error atau lagi coba-coba alternatif logic saya selalu comment kode awal. Jadi kalau setelah diotak-atik malah tambah parah, bisa balik lagi. Namun setelah sering direview teman saat Merge Request, sudah mulai berhenti kok. Kalau kita memanfaatkan fasilitas git commit dengan baik, tidak perlu ada yang dikhawatirkan lagi.😉</p><p>Diatas adalah satu dari banyak contoh komentar-komentar tidak perlu. Intinya adalah tulislah comment ketika dibutuhkan saja. Kalau bisa kode kita readable dan efisien sehingga sudah self-explanatory tanpa harus diberikan penjelasan tambahan.</p><h4>5. Jangan diulang-ulang</h4><p>Ada konsep clean code yang namanya <strong>DRY</strong> atau <strong>Don’t Repeat Yourself. </strong>Dari namanya sudah cukup jelas, jangan menulis kode yang sama berulang-ulang. Flutter merupakan component-based framework. Jadi kita dapat membuat elemen-elemen UI kita menjadi reusable component, lalu tinggal kita pakai componentnya.</p><p>Sayangnya kami ngga tau konsep itu pada awalnya. Jadi kami melakukan hardcode alias menulis hal yang sama berulang-ulang untuk setiap elemen. Satu file kami bisa sangat amat panjang seperti di bawah ini.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*SLx7g2Q-IbO2B8Dxu-yh1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/123/1*0COGs61m8zB0lk8BrImhgw.png" /><figcaption>kodingan 1 button (kiri) dan preview file dengan code berulang (kanan)</figcaption></figure><p>Setelah sprint berjalan dan belajar dari internet &amp; teman-teman lain, kami sadar ada yang salah dan harus diperbaiki. Akhirnya kami mulai membuat component dan pelan-pelan akan melakukan refactor terhadap kode-kode sebelumnya. Kode kami jadi lebih singkat alias secukupnya saja dan lebih <em>readable</em>. Semoga semua bisa belajar dari kesalahan kami ya. 😅</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*WkkWYU90cX9auGg8oFFBWg.png" /><figcaption>setelah memakai reusable component</figcaption></figure><h4>6. Jangan lupa ikuti style yang ada</h4><p>Biasanya ada kaidah atau style tertentu dalam menulis kode dengan suatu framework atau bahasa, namanya code formatting. Kaidah ini seputar aturan penulisan, seperti penggunaan tanda baca, whitespace, dan sebagainya. Ini contoh <em>before-after formatting</em> di Advokasimu:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*lGJ_1pP-w47UxmikZGbt8A.png" /><figcaption>sebelum formatting</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*KbVBwtlBZr305f5jPbeLqQ.png" /><figcaption>setelah formatting</figcaption></figure><p>Gambar kedua menurut saya lebih mudah dibaca dibanding yang pertama. Siapa sangka whitespace punya pengaruh yang sangat signifikan dalam proses memahami suatu kode.</p><p>Walau kelihatannya sepele, <em>code formatting</em> ini penting banget untuk menjaga <em>maintainability</em> dan <em>extensibility</em> kode kita. Jika kita menerapkan <em>code formatting</em> yang baik, akan sangat memudahkan tim dan orang yang mungkin akan melanjutkan proyek ini untuk mengembangkannya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*RpL62hpZPzMtHZJuCobY5Q.png" /><figcaption>friendly reminder @ merge request</figcaption></figure><p>Tidak usah khawatir perlu melakukan formatting ini secara manual, karena sudah banyak automasinya. Biasanya ada perintah khusus yang akan melakukan<em> code formatting</em> otomatis atau bisa menggunakan <em>plugin/extension. </em>Oiya, selain code formatting default kamu dan tim juga bisa menentukan style sendiri. Tujuannya sama: mempermudah kita semua ke depannya.</p><p>Setelah paham hal-hal yang harus diperhatikan dalam rangka clean code, sekarang:</p><h3>Gimana caranya biar clean code ga sekedar teori?</h3><blockquote>Dipraktekin.</blockquote><p>Bener sih, tapi singkat banget.. selesai dong <em>sectionnya?</em></p><p>Kalo gitu pertanyaannya ganti. Di <em>section</em> sebelumnya, cerita pengalamannya kebanyakan tentang kesalahan-kesalahan yang kami perbuat. Hal ini menunjukkan kalau clean code <strong>tidak semudah itu</strong> diterapkan.</p><p>Lalu,</p><h3>Gimana cara efektif menerapkan clean code?</h3><p>Nah, berdasarkan perjalanan Le Pepe selama ini ada beberapa pelajaran yang bisa dipetik.</p><h4>Research!</h4><p>Mempelajari musuh dan medan perang sebelum berperang adalah salah satu strategi yang bisa membawa kita ke pintu keberhasilan. Lho kok lebay tapi beneran analoginya begitu. <em>Research </em>sebaiknya jadi step 0 dari setiap langkah kita.</p><p>Bentuk research bisa macam-macam. Misalnya belajar bahasanya, belajar dokumentasi frameworknya, nonton tutorial You Tube, baca sharing orang di internet (kayak tulisan ini hehe), baca github orang, baca forum diskusi, atau tanya-tanya teman juga termasuk research. Kalau udah <em>research,</em> kita jadi punya gambaran step-stepnya apa aja, <em>best practice-</em>nya gimana, harus ngelakuin apa aja, dll. Pastinya bakal membantu banget ke depannya.</p><p>Proyek Advokasimu dibangun dengan menggunakan framework Flutter (dan Svelte). Keputusannya cepat banget, awalnya bahkan kita ngga nyangka bakal bikin mobile app. Karena transisi ini, kami jadi kurang banyak <em>research-</em>nya di awal.</p><p>Saya sendiri saat itu langsung fokus ke <em>how-to, </em>belajar gimana teknis ngodingnya. Setelah proyek berjalan, baru dapet info-info baru yang membuat sadar kalo ada <em>better way to do what I do now</em>. Gapapa. Sambil jalan, sambil belajar. <em>Research </em>harus selalu dilakukan, ngga berhenti di awal aja.</p><h4>Punya kesepakatan tim</h4><p>Menyatukan kepala sebagai sebuah tim akan sangat membantu tim bergerak ke arah yang sama. Untuk mencapai hal itu, perlu punya kesepakatan tim. Apalagi di awal proyek dimulai. Sepakati bersama dulu coding style, glossarium kata (wording), best practice coding yang mau diterapin, dan lain-lain.</p><p>Tidak berhenti disana, jangan lupa untuk <em>mantain </em>kesepakatannya. Misalnya untuk code bisa saling review di Gitlab, jadi kalau ada yang kurang sesuai bisa diperbaiki sedari dini. Untuk glossarium kata, bisa membuat page Wiki di Gitlab, file khusus di repository, atau mengacu pada prototype misalnya.</p><h3>Kenapa harus banget clean code?</h3><blockquote>Supaya nggak pusing.</blockquote><p>Becanda deh hehe. Beneran juga sih, daritadi di atas ceritanya pusing terus kan.</p><p>Menerapkan clean code == berbuat baik. Ke siapa? Ke diri sendiri, ke anggota tim lainnya, ke orang yang bakal ngelanjutin proyek itu, dan pembaca lainnya.</p><p>Dengan menerapkan clean code, kodingan akan lebih mudah dibaca, mempermudah <em>debugging, </em>mempermudah penyesuaian jika mau scale up, dan lain-lain. Jika dilakukan dari awal, tim akan lebih sedikit melakukan refactor (atau bahkan tidak perlu) di kemudian hari. Intinya, <strong>clean code memudahkan.</strong></p><p>Pesan yang bisa dipetik dari artikel ini adalah <strong>clean codelah demi kebaikan bersama atau kita harus bersiap untuk refactor di kemudian hari alias kerja dua kali alias capek lagi</strong>. Hehe. Lebih baik mencegah daripadi mengobati, bukan? Walaupun banyak peraturan, restriksi, hal-hal yang harus diperhatikan, di akhir akan memudahkan semua orang. <em>It’s not an easy job,</em> semangat <em>developers!</em></p><h4><em>Disclaimer</em></h4><p>Menulis semua ini bukan berarti saya sudah programmer paling clean code seluruh dunia, sharing pengalaman aja sambil belajar biar beneran bisa jadi programmer paling clean code seluruh dunia. Hehe, bercanda. Sampai berjumpa di tulisan selanjutnya ya😊</p><h4>Referensi</h4><p>Clean Code: A Handbook of Agile Software Craftsmanship, Robert C. Martin, Prentice Hall, 2008</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2276e92b723" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Agile Help Developer Team Grow]]></title>
            <link>https://medium.com/@elioranathasya/how-agile-help-developer-team-grow-d6875ba678a0?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6875ba678a0</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Tue, 10 Mar 2020 03:59:57 GMT</pubDate>
            <atom:updated>2020-03-20T08:34:45.208Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyKuftCbKvo6iSwfKNqLgA.png" /></figure><p><em>“Use agile, be agile,” </em>they say.</p><h3><strong>What is it with being Agile?</strong></h3><p>Agile is a set of principles in software development in which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional team and the users/customers. Be Agile means to be adaptive, flexible to changes.</p><h3><strong>Scrum</strong></h3><p>On PPL we apply Scrum as our software development framework. As it said on scrum.org, Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum facilitates the team to deal with unpredictability and solving complex problems. Scrum values five things the most, which are openness, courage, respect, commitment, and focus.</p><p>Scrum has a few events and here they are and how they can help us grow as a person, team, and develop our product better.</p><p><strong>Sprint</strong></p><p>A cycle in Scrum is called Sprint. Sprint starts with Sprint Planning, has a daily standup meeting, and ends with Sprint Review and Sprint Retrospective. On PPL one sprint has two weeks length, but it may vary.</p><p><strong>Sprint Planning</strong></p><p><em>Plan well, do well.</em></p><p>On this event, we choose which Product Backlog we want to take for the next sprint. We usually consider the priority (already prioritize it together with the client) or dependency.</p><p>After choosing the PBI, breakdown it to tasks, write the Definition of Done/the to-do list and then assign it. Definition of Done will be the guideline on how we do the task and when we can say the task is already done.</p><p>On the first sprint, we breakdown our PBI to little tasks then assign it to the team member. We got a little problem with how a task can’t stand independently alone because sometimes it has a dependency on other tasks. So some had to wait before they could start their task.</p><p>On the second sprint, we are trying something a little bit different. We list the task card not as detail as the first sprint. We categorized features so it has little dependency on others. But don’t worry, we still write the detail of the task on the card detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*avOOMVxFp2cR8Vh7D3LeGw.png" /><figcaption>Board</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_6GJLiDz27E6G0_T7dgrw.png" /></figure><p>Still working on which suit our team the best. Will update later when we already found the best method for us, stay tuned.☺</p><p><strong>Daily Standup</strong></p><p>(or more semiweekly standup)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*6CY7a6YGwaQ7Rj1U3kA39Q.png" /><figcaption>Reminder</figcaption></figure><p>Daily standup is a quick routine meeting for developer team. On this event, each team member tells the team what did she/he do since the last standup, the blocker, and what they are going to do next. Here we can have a discussion and get or give help to another team member on some difficulties that others may have. Agile value transparency and that&#39;s why knowing progress of all team members is important.</p><p>On PPL we do our daily standup twice a week. Le Pepe, my team, do it on Monday and Thursday. Our standup is being coached by our scrum master.</p><p>To be honest, this daily standup is one of the <em>why</em> for my work progress. I am more driven to continue working on my tasks so that I can deliver it to the team on the standup.</p><p><strong>Sprint Review</strong></p><p>It’s time to deliver our works for the last two weeks! The lecturer, scrum master, product owner, class assistant, and also the client will be there. Exciting, isn’ it?</p><p>We start with a quick presentation to give everyone a picture of what we’ve been working on these two weeks. We present the Product Backlog Item details and do a hands-on demo. It’s thrilling yet exciting to see our product on use for the first time!</p><p>Then we review the PBI one by one, going through test cases made by our Product Owner, and finally match it with the acceptance criteria. After that, the client can approve/reject the PBI according to the review (another thrilling yet exciting moment).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*EC0BAERdsZ3cb2u4FUJuig.png" /><figcaption>Preview of Our Sprint 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o02Df2296SE-a3bRdkil6A.png" /></figure><p>On this very first sprint, four of four PBI got accepted by the client. Yay! We got a few notes, but that’s okay. Cheers to another sprint!</p><p><strong>Sprint Retrospective</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H8AR6ru8119U7iOOvL5fHg.png" /><figcaption>Le Pepe Sprint Retrospective Board</figcaption></figure><p>In Sprint Retrospective, we evaluate ourselves as individuals and also as a team. There are four boards which are good, bad, start and stop. We list down bad things and good things we did in the last sprint. Then we talk about every sticky notes that are written on the board. We go from one board to the next board until all the sticky notes already been discussed. Our rule, everybody has to write minimum one sticky notes on every board.</p><p>This facilitates us to reflect, where did we go wrong? But also acknowledge what we did well so we can keep doing that. We talk about our struggles and how to solve them. We talk about our teamwork, appreciate each other, and ready to support each other. This event is so much more than technical review, this also tightens our bond as a scrum team.</p><p>After this retro, we hope to do better and be better on the next sprint.</p><p>We use metroretro.ioto do this cute sticky notes thingy bytheway. It has many features that make your retro more fun (ps: give it a try on that confetti button).</p><p>That’s the story about how we use and be Agile on our Advokasimu journey. See you in another topic!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6875ba678a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git: Tidak Perlu Takut Salah]]></title>
            <link>https://medium.com/@elioranathasya/git-tidak-perlu-takut-salah-a34f631c7273?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a34f631c7273</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Mon, 09 Mar 2020 13:54:28 GMT</pubDate>
            <atom:updated>2020-05-12T01:06:01.806Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGzF6FUxe4gUsCvjXwZ4SA.png" /></figure><p>Manusia banyak takutnya, apalagi mahasiswa. Apalagi mahasiswa yang baru pertama kali proyekan, dengan framework baru, tim baru, dan metodologi kerja baru di mata kuliah baru. Alias saya. Di minggu pertama implementasi proyek pengembangan perangkat lunak, perasaan ‘takut salah’ itu selalu ada. <em>Takut salah ngoding, takut nurunin coverage kelompok, takut bikin repository berantakan, takut bikin conflict, dan sebagainya.</em></p><p>Ternyata semua ketakutan teknis tersebut dapat ditangani oleh teknologi yang selama ini sudah umum digunakan. Perkenalkan, Git.</p><h3><strong>Tentang Git</strong></h3><p>Git adalah sebuah version-control system yang akan membantu me-manage proyek dan mencatat perubahan-perubahan dalam pengembangannya. Git menggunakan konsep snapshots. Setiap commit (menyimpan <em>state</em>), Git akan mengambil gambaran file terbaru dan menyimpan referensi ke snapshots tersebut. Jika file tidak diubah, maka Git tidak akan menyimpan file tersebut lagi, namun hanya me-link ke indentikal file yang telah disimpan sebelumnya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*n-5phDjyDbEcEgo6.png" /><figcaption>Git Snapshots (sumber: git-scm.com)</figcaption></figure><p>Git mempunyai semacam alur bermain, biasa disebut Git Flow.</p><h4><strong>Git Flow</strong></h4><p>Git mempunyai konsep branching untuk memanage sebuah proyek. Secara garis besar ada branch master, staging, hotfix, coldfix, dan fitur-fiturnya. Di mata kuliah PPL ini kita menggunakan penamaan PBIx (Product Backlog Item) untuk cabang fitur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*5DGpH6VrEEy06xwDHeGpSQ.png" /><figcaption>Git Flow (sumber: Panduan PPL 2020)</figcaption></figure><p>Fitur akan didevelop sendiri-sendiri di branch PBI. Tiap sprint branch tersebut akan mengajukan Merge Request, yaitu izin untuk menggabungkannya ke staging. Di merge request ini, teman sesama tim akan mereview codingan dan berdiskusi bersama memastikan bersih dari kesalahan. Jika sudah ok, akan diapprove dan di merge. Jika branch kamu masih progress, bisa ditambahkan label WIP (Work in Progress) untuk memberi tanda. Dengan memberikan label tsb, MR kamu tidak akan termerge karena diamankan oleh Git sendiri.</p><p>Dalam PPL ini, digunakan metodologi Test Driven Development atau TDD. Dimulai dengan commit [RED] berisi test yang belum diimplementasi. Dilanjutkan dengan commit implementasi dengan label [GREEN]. Jika sudah oke, bisa dimerge ke staging. Jika belum, bisa dilakukan [REFACTOR] yaitu perubahan-perubahan pada kode atau [CHORES] untuk commit yang bukan fungsionalitas. Label warna inilah yang divisualisasikan diagram di atas.</p><h3><strong>Tantangan Developer (S<em>st.. </em>dan Penyelamatnya!)</strong></h3><p>Para developer pastinya punya hambatan dan tantangan dalam bekerja. Hal-hal tersebut yang jadi awal rasa takut salah yang telah dibahas diatas. Mulai dari technical, internal, maupun eksternal. Namun untungnya, Git punya segudang fitur penyelamat yang akan memudahkan developer bekerja.</p><ul><li><strong>Kerja bareng developer lain</strong></li></ul><p>Membangun sebuah software bukanlah pekerjaan kecil. Dibutuhkan berbagai bentuk keahlian dan <em>man power, </em>sehingga biasanya developer bekerja dalam tim.</p><p>Gimana caranya banyak orang mengerjakan banyak fitur untuk suatu proyek <em>coding </em>bersamaan? Bagaimana kalau ada fitur yang dependen? Gimana cara tau progress orang lain?</p><p>Git punya jawabannya. Git memiliki konsep remote dan local repository. Remote repository ini adalah folder proyek yang tersimpan di server, yang akan jadi parent acuan. Sedangkan local repo adalah repo yang ada di device kamu sekarang. Tiap developer akan melakukan git clone dari remote repository untuk membuat local repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P72CZiTcY7A9CmBncy-BkQ.png" /><figcaption>Remote Repository Advokasimu</figcaption></figure><p>Untuk mengupdate local repository kita dengan perubahan terbaru di remote repository, kita bisa melakukan git pull. Sebaliknya jika ingin mengupdate remote repository dengan perubahan di local kita, kita dapat menggunakan git push. Kamu bisa menambahkan ‘origin nama-branch’ juga. Misalnya git push origin master jika kamu di branch master atau git push origin pbi-22-fiturku jika kamu di branch pbi-22-fiturku. This keep all team member on the same page.</p><ul><li><strong>…tapi tetap butuh space sendiri</strong></li></ul><p>Walaupun bekerja dalam tim, tetap saja tiap developer mendapat task yang harus diselesaikan sendiri-sendiri. Kadang bekerja di workspace yang sedang dikerjakan orang lain juga terasa tidak nyaman, takut perubahan yang kamu lakukan mempengaruhi pekerjaan orang lain.</p><p>Namun sekali lagi Git hadir sebagai penyelamat dengan git branch. Setiap developer dapat membuat branch sendiri-sendiri dengan git chckout -b nama-branch-baru sehingga bisa bekerja sendiri tanpa intervensi dan mengintervensi orang lain, tidak perlu tunggu-tungguan atau khawatir lagi.</p><p>Peraturan-peraturan Git Flow yang telah dibahas diatas mungkin memang membingungkan sebagai permulaan. Tapi perlu diingat mereka hadir untuk mempermudah, bukan untuk mengekang. Bersikaplah fleksibel dengan menyesuaikan peraturan tersebut untuk tim masing-masing.</p><p>Sebagai contoh, kemarin saya sangat terpaku bahwa branch yang boleh ada hanyalah yang tertera di panduan. Sempat membingungkan dan menghambat saya ketika harus bekerja di branch yang dikerjakan oleh beberapa orang lainnya. Namun sebenarnya tidak masalah membuat branch baru lagi untuk task/orang berbeda, <em>be agile.</em></p><ul><li><strong><em>“Duh, salah! dan makin salah. Pengen undo bisa gak ya?”</em></strong></li></ul><p>Git bekerja seperti checkpoint. Jadi developer bisa menyimpan progressnya dan melabelinya dengan sebuah pesan commit. Untuk melakukan commit, pertama kita add dahulu file-filenya dengan git add nama-file atau git add . (untuk semua file), lalu melakukan git commit -m &quot;pesan-commit&quot; atau git commit -m &quot;pesan-commit&quot; -m &quot;detail-pesan-commit&quot; jika ingin lebih panjang detailnya. Dengan demikian, perubahan-perubahan yang kamu lakukan ke file-file kamu tersimpan dengan rapi. Kamu bisa mengeceknya dengan git log.</p><p>Kadang-kadang, perubahan-perubahan yang kita lakukan tidak membuahkan hasil yang diinginkan. Bisa jadi memperkeruh keadaan sehingga rasanya ingin <em>unsend </em>atau <em>undo </em>perubahan-perubahan tersebut. Dengan Git, kamu bisa kembali ke checkpoint/commit sebelumnya. Tinggal lakuka<strong>n </strong>git revert commit-id. Tidak perlu takut salah lagi, karena kamu bisa membatalkan kesalahanmu. Hehe.</p><ul><li><strong>Review Bareng Tim dengan Merge Request</strong></li></ul><p>Di PPL ini, kami menggunakan GitLab. GitLab merupakan manajer repositori Git berbasis web dengan fitur wiki dan pelacakan masalah, menggunakan lisensi sumber terbuka, dikembangkan oleh GitLab<strong> </strong>Inc (dikutip dari Wikipedia).</p><p>Sebagai developer yang jam terbangnya belum banyak, membuat kesalahan adalah hal yang lumrah. Setelah bekerja di branch sendiri, saatnya menggabungkan pekerjaan pribadi ke staging dengan membuat Merge Request. Takut conflict dan takut membuat berantakan di awal minggu sekarang sudah hilang semenjak mulai memaksimalkan fitur Merge Request GitLab.</p><p>Saat mengajukan Merge Request, kita harus mendapatkan approval dari minimal dua teman sebelum bisa melakukan merging. Sebelum mendapatkan approval ini, teman kita akan mereview code kita dan memulai diskusi jika ada yang dirasa kurang tepat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqJTa_gqY_Ycy-flvdeJig.png" /><figcaption>Contoh Merge Request</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*PElBAlGstSM7qhARPmpT4Q.png" /><figcaption>Contoh Diskusi/Thread terkait Code Changes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dxM3Qv1Bp-Lar5WJ5BSEpg.png" /><figcaption>Contoh Activity di Merge Request</figcaption></figure><p>Dengan fitur ini, anggota tim saling membantu dan mereview pekerjaan teman lainnya. Jika ada yang dirasa kurang tepat, anggota tim dapat membuat thread baru dan menulis komentar, memberikan suggestion perbaikan, dll. Seluruh proses ini transparan sehingga semua anggota dapat melihat progress revisinya juga. Ketika semua sudah resolved, thread dapat ditutup dan Merge Request dapat diapprove sehingga dapat naik ke staging.</p><p>Tantangan dan hambatan akan selalu ada bagi para developer. Namun setidaknya untuk (banyak) beberapa dari itu, Git hadir sebagai penyelamat. Tidak perlu takut lagi, kita bisa memanfaatkan konsep dan fitur-fitur dalam Git untuk memaksimalkan produktivitas kita, bukan sebaliknya. Terimakasih, Git!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a34f631c7273" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git 101: Easy Cheatsheet]]></title>
            <link>https://medium.com/@elioranathasya/git-101-easy-cheatsheet-2f612eaac43f?source=rss-b25216e0025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f612eaac43f</guid>
            <dc:creator><![CDATA[Nathasya Eliora]]></dc:creator>
            <pubDate>Tue, 25 Feb 2020 05:16:04 GMT</pubDate>
            <atom:updated>2020-02-25T07:47:42.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDWWmJ2Tvr3uZu31FXL4gA.png" /></figure><p><strong>Apa itu Git?</strong></p><p>Git adalah teman baik para developer. Dikutip dari websitenya, Git merupakan sebuah distributed version control system gratis dan open source yang dapat digunakan untuk berbagai project. Git menyimpan perubahan-perubahan yang kita lakukan dalam suatu proyek sehingga kita dapat lebih mudah memanage proyek kita.</p><p><strong>Bekerja sebagai Tim dengan Git</strong></p><p>Git memiliki banyak fitur yang memudahkan developer bekerja sebagai satu tim untuk satu proyek yang sama. Proyek memiliki satu repository utama yang digunakan bersama (remote repository) dan tiap developer memiliki local repository di devicenya masing-masing. Tiap developer akan mengupdate remote repository sesuai pekerjaan yang ia kerjakan, dan semua anggota tim tetap mendapat update dengan mudah tanpa harus mengalami banyak konflik.</p><p>Misalnya di tim AdvokasiMu, kami saling bekerja sendiri di branch masing-masing. Lalu akan kami merge ke staging. Sehingga fixing konflik lebih mudah.</p><p>Yuk kenalan sama Git.</p><p><strong>Membuat Repository</strong></p><p>Proyek disimpan dalam sebuah repository. Untuk membuat git repository, kamu bisa melakukan berbagai cara.</p><ul><li><strong>Init</strong></li></ul><p>Kamu bisa membuat foldernya dahulu secara lokal, lalu melakukan git init dengan perintah:</p><blockquote>git init</blockquote><ul><li><strong>Clone</strong></li></ul><blockquote>git clone &lt;url repository&gt;</blockquote><p>Clone akan menduplikasi atau mengcopy sebuah remote repository ke lokal kamu. Selain file-filenya tercopy, originnya pun akan langsung teratur ke link url yang kamu clone.</p><p><strong>Memperbaharui Repository</strong></p><p>Untuk mengupdate local repository kamu supaya sama dengan remote repository, kamu bisa melakukan pull dengan perintah di bawah ini.</p><blockquote>git pull</blockquote><p>Jika kamu melakukan perubahan-perubahan terhadap file local, kamu harus mengupdatenya ke remote repository. Kamu bisa melakukannya dengan add-commit-push.</p><p>Pertama, add file-file yang kamu ubah satu persatu, atau langsung semuanya.</p><blockquote>git add &lt;nama file&gt;</blockquote><p>atau</p><blockquote>git add .</blockquote><p>Jika kamu lupa file apa saja yang kamu ubah, kamu bisa mengeceknya dengan</p><blockquote>git status</blockquote><p>Selanjutnya, commit file-file yang telah kamu add dengan:</p><blockquote>git commit -m “commit-message”</blockquote><p>Lalu push ke remote repository dengan:</p><blockquote>git push</blockquote><p>Sekarang perubahan yang kamu buat tercatat.</p><p><strong>Bekerja dengan Branch</strong></p><p>Branch adalah konsep percabangan di Git. Hal ini memungkinkan developer berbeda untuk bekerja untuk fitur yang sama tanpa konflik versi.</p><ul><li><strong>Mengecek kamu sedang berada di branch mana</strong></li></ul><blockquote>git branch</blockquote><ul><li><strong>Membuat branch baru</strong></li></ul><blockquote><em>git checkout -b &lt;nama branch baru&gt;</em></blockquote><ul><li><strong>Berpindah ke branch lainnya</strong></li></ul><blockquote>git checkout &lt;nama branch&gt;</blockquote><ul><li><strong>Menggabungkan branch ke branch lain (merge)</strong></li></ul><blockquote>git merge</blockquote><p>Jika kita bekerja dengan banyak branch, pada akhirnya kita akan menggabungkan branch-branch tersebut menjadi satu kesatuan. Aktivitas menggabungkan suatu branch ke branch lain dinamakan merging.</p><p><strong>Bermain dengan Perubahan</strong></p><p>Dalam mengembangkan sebuah proyek, pasti akan ada banyak perubahan yang terjadi. Git memiliki banyak fitur yang memudahkan developer saat harus dihadapkan dengan kasus-kasus tersebut.</p><ul><li><strong>Revert</strong></li></ul><p>Jika kamu ingin kembali ke commit sebelumnya, kamu bisa menggunakan ini.</p><blockquote>git revert &lt;id commit&gt;</blockquote><ul><li><strong>Stash</strong></li></ul><p>Kamu bisa membersihkan direktori aktif kamu sekarang dan kembali ke checkpoint sebelumnya dengan git stash. Namun perubahan-perubahan tersebut tetap tersimpan di stash list.</p><blockquote>git stash</blockquote><ul><li><strong>Rebase</strong></li></ul><p>Kamu bisa memindahkan commit-commit yang telah dilakukan di suatu branch ke branch lain.</p><blockquote>git rebase</blockquote><p><em>Referensi</em></p><p><a href="https://git-scm.com/book/id/v2/Memulai-Tentang-Version-Control">https://git-scm.com/</a></p><p><a href="https://www.freecodecamp.org/news/what-is-git-and-how-to-use-it-c341b049ae61/">An introduction to Git: what it is, and how to use it</a></p><p><a href="https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase">https://www.atlassian.com/git/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f612eaac43f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>