<?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 Edy Sudarto on Medium]]></title>
        <description><![CDATA[Stories by Edy Sudarto on Medium]]></description>
        <link>https://medium.com/@edysudarto00?source=rss-e35726256a54------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bZM88TBNGnt2N6zfVc0LEg@2x.jpeg</url>
            <title>Stories by Edy Sudarto on Medium</title>
            <link>https://medium.com/@edysudarto00?source=rss-e35726256a54------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:55:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edysudarto00/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[Clean Code, useful or useless ?]]></title>
            <link>https://medium.com/vidio/clean-code-useful-or-useless-2058d28f6d77?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/2058d28f6d77</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[programming-tips]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sun, 17 Jul 2022 13:48:54 GMT</pubDate>
            <atom:updated>2022-07-18T01:44:37.754Z</atom:updated>
            <content:encoded><![CDATA[<h3>Clean Code, useful or useless ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BRkkEYd3o8iw9d34" /><figcaption>Photo by <a href="https://unsplash.com/@srosinger3997?utm_source=medium&amp;utm_medium=referral">Samantha Gades</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Hello World!</blockquote><p>That’s the first program for most software engineers (if not all) that was written when we first started to learn coding.</p><p>From there, we started to take interest to figure out how to make other stuffs to work. In that journey, we will later find our first ever bug and try to solve it. Then, some of us will continue to take programming further as their career or as a hobby and some of us might think that programming is not for them so they choose to leave it.</p><p>For people who still continue programming especially as their career like myself, we will usually try to find something to improve our skills to climb to higher level. One of the improvement concept that I found back then is called clean code.</p><p>What exactly is clean code ?</p><blockquote>Code is clean if it can be understood easily — by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability. -Uncle Bob</blockquote><p>Of course, there are always some people who are pros and cons to that concept. Some of the words from people who are cons to it that I remembered are like below.</p><blockquote>Why bother with writing clean code when we can just go write as we pleases as long as it works in the end ? -Anonymous</blockquote><blockquote>Trying to write clean code is just a hassle, it will slow you down because your care for the code that takes an extra effort is useless. -Anonymous</blockquote><blockquote>To be able to write a code that people can’t understand but you is the ultimate level of coding cause it makes you feel special. -Anonymous</blockquote><p>I’ve met these statements in my programming career not long after I knew about clean code. In this article, I’ll try to show you whether clean code is actually useful or useless but I am not gonna tell you about clean code in detail cause it is too long, you can just explore it yourself later.</p><h3>Example</h3><p>Here, let me show you something.</p><p>Take a look at the code snippet below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aD_zqczAF4qFe3psLiyohQ.png" /></figure><p>Now take a look at the other code snippet below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o2cjvmcHjLbOGybgWR4sDQ.png" /></figure><p>Now after looking at both of them, which one of the code snippets that you think you were able to understand it easier ? Which one would you prefer to have in your codebase ?</p><p>I bet the answer to both questions must be the latter one. Because as you can see, even when you haven’t looked at the details, the function name has clearly told you what is its intention and the details is there to confirm what it does. That is actually only one of the many clean code practices called <strong>meaningful names</strong>. Imagine if you have to face codes like the former one, I bet you will scratch your head most of the time trying to figure out its intention and it will automatically lower the team morale too.</p><p>So, instead of writing cryptic codes, we try to write a descriptive code with meaningful names that can be understood by others easily. It resonates to what clean code means on the earlier section above which it to make it to be understood easily by everyone on the team.</p><h3>Testimony</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ipvj8inn0f8IbLjJ" /><figcaption>Photo by <a href="https://unsplash.com/@josuemichelphotography?utm_source=medium&amp;utm_medium=referral">Josue Michel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Taking care of your code is similar to taking care of your room or house. If everything is messy, it’s hard to understand what’s going on in the code and it’s hard to find things when you need it. But if you tidy it up and keep it clean then everything will be so organized that when you need something you can get it fast and easily because you know where to look for.</p><p>At this moment when writing this article, I’ve practiced clean code for more than 3 years in my career and with confidence I can tell you that clean code is indeed<strong> useful</strong>.</p><p>By writing clean code, it improve both my working life and code quality. It helps me and the team to deliver things faster and able to debug issue faster which benefit the company. I have never been this less stressful when working with a big project. Because in the past, usually adding some new feature or bug fixing will always take quite a while cause it’s hard to understand how the existing code works beside how complex the system was. So if you are part of the team that says clean code is useless, you might want to think again.</p><p>If you said you did it and it didn’t help, maybe it’s because you are doing it wrong or you are doing it alone. Because cleaning a huge codebase for a team is not a single person responsibility but it’s supposed to be the whole team responsibility. Because if a single person trying to clean a big mansion by themselves, they will surely get overwhelmed. But it will be different story if all the person who lives in it also takes part to clean it.</p><h3>Closing</h3><p>My advice is if you want to improve yourself as a software engineer, then practicing clean code is definitely one of the way I recommend as it has direct impact to your works. What you see in this article is only little portion of what clean code can do to yourself, you can try explore more about it and I bet you will love it. It takes time to practice, but it will be worth the while cause that’s what I’ve felt after all these 3 years practicing it.</p><p>Lastly, for y’all out there who read this, stay safe and stay hydrated ! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2058d28f6d77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vidio/clean-code-useful-or-useless-2058d28f6d77">Clean Code, useful or useless ?</a> was originally published in <a href="https://medium.com/vidio">Karena Kita Vidio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experiencing XP has changed my life as an iOS Engineer]]></title>
            <link>https://medium.com/vidio/experiencing-xp-has-changed-my-life-as-an-ios-engineer-cacbef1805cd?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/cacbef1805cd</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sat, 16 May 2020 10:53:08 GMT</pubDate>
            <atom:updated>2020-05-19T07:25:00.886Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MM4IoVO-MVPuP1cM" /><figcaption>Photo by <a href="https://unsplash.com/@kiwihug?utm_source=medium&amp;utm_medium=referral">Kiwihug</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever been so bored cause you feel your skills don’t grow anymore ?</p><p>Well, in my case i have.</p><p>The problem is i actually know that i can still improve my skill but i don’t know how and what exactly i should do to improve it. I explored some best practices, found out about testing tutorial but the resources are insufficient. Even if i try to do the testing stuff, i don’t even know if i am doing it in the right way or not and it didn’t seem possible to be implemented in my work at that time.</p><p>I could say maybe i was stuck for too long in my comfort zone. So there was a time where i finally decided to move out of that zone, trying out something new where i have the confident that i can learn and grow from that experience in order to become a great iOS engineer.</p><p>So what i actually ended up with ?</p><p>Well yes, it’s the XP culture in <a href="https://www.kmkonline.co.id/who-we-are">KMK</a> here that becomes the answer for me to be able to improve my skills and make me feel a different programming experience that i never had before.</p><p>So, what is XP ?</p><blockquote>Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team. -Agile Alliance</blockquote><p>And here is another definition from one of three founders of XP.</p><blockquote>Extreme Programming is a discipline of software development based on values of simplicity, communication, feedback, courage, and respect. It works by bringing the whole team together in the presence of simple practices, with enough feedback to enable the team to see where they are and to tune the practices to their unique situation. -Ron Jeffries</blockquote><p>Both of the definitions are pointing to the same goal, <strong>towards a better software development</strong>. Because i have been in a situation where software development really stressed me out where any changes i made will definitely break the app in the other parts thanks to the coupled messy codes, this is something like a ray of hope for me.</p><p>Now i have been experiencing XP for more than a year in KMK and i want to share it to you how it has changed my life as an iOS engineer.</p><p>Here are some of the changes where i will mention some of the XP practices (hope you have heard it or you may read them in my previous blog posts) in it such as pair programming and TDD (Test Driven Development).</p><h3>Programming becomes more fun and less stressful</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljuz1EQwZlPgLKJV6q3Thw.png" /></figure><p>Usually when doing programming alone when i feel stuck or annoyed about a problem, i will feel depressed alone. But thanks to pair programming, now i will feel stuck and annoyed <strong>together</strong> <strong>with my pair</strong> since it’s a shared problem now, hahaha. Well, it’s either that or my pair can give me another insight about it (and vice versa) and now we are able to solve the problem together making it feels less stressful. How excellent is that !</p><p>When you have a good and compatible pairing partner, it’s always fun to have a discussion to solve the problem you have in front of you while deepen the relationship in the team. Furthermore, it will also improve the code quality that you produce because it’s the work of art by combining two great minds. I even ever have this thought in my mind while looking at the code that we produce, <strong>ain’t this a magnificent piece of art we got here.</strong></p><p>Another factor that makes programming fun is when i do TDD, there is always a moment where red (means failing) test exists and i will try my best to make it green. The moment where i was able to make the test green again, i will have this accomplished feeling similar to the moment when i have cleared an annoying obstacle in a game. So it almost feels like i am doing both gaming and programming at the same time.</p><p>Now the fact that looking at those green tests are making me feel less stressful when working is also because i can know that i didn’t break anything since the last code change that i made. <strong>The test is there to cover me.</strong> Well i still need to do sanity check for the UI/UX stuff but when the logic part is already covered, it already lifts up a lot of weight from my mind.</p><p>I still remember the moment where i need to test everything out manually from the front to the end to make sure i didn’t break anything everytime before i check the code in. It makes me feel anxious and exhausted at the same time, really uncomfortable.</p><p>Thanks to that, now i always keep in mind that <strong>writing test is not something that i should do because the company told me to do it but because i know it is the right thing to do</strong> <strong>to be a great iOS engineer</strong>. This can also apply to you if you want to be a great software engineer.</p><h3>Constant growth</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h_ler4VjiDcK1iEZ" /><figcaption>Photo by <a href="https://unsplash.com/@veeterzy?utm_source=medium&amp;utm_medium=referral">veeterzy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Ever since i worked in KMK, i feel like i have learnt and grown so much compared to the first when i came here. You just can’t stop growing and learning here when they keep on pouring all those knowledge into you everyday, hahaha.</p><p>But I am really happy and feel blessed to be able to work in a team of so many high skilled, hunger for knowledge and supportive people. Well, you know they said that if you want to become clever, you need to surround yourself with clever people too so you can be influenced by their habits. That’s what i am currently doing now and i think it kinda works (of course i try to keep up with them myself).</p><p>In KMK, i learned how to actually become a great iOS Engineer. I would say the time when i still know nothing about testing and have no idea how to actually write clean code is the time when i was still a complete amateur who just jump into iOS programming, well i did just start my career in Batam for 2 years though.</p><p>Because of the XP practices such as pair programming, TDD, and clean code, i am able to produce some high quality code now. Indeed i am still in progress towards becoming a great iOS Engineer but at least i already improved some of my skills and still trying to keep up with my teammates here.</p><h3>Improved communication skill</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ABfpdg8wVwgs4aF0" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I used to be a more passive person cause that was my nature and my comfort zone. I also feel like i was unable to convey my thoughts properly to people most of the time whether it’s towards technical or non technical people and i think my documentation skill was below average too.</p><p>I do agree that communication skill is one of the most important factor to have a good collaboration either in our internal team or across teams. It also contributes to the success of the team and the product we produce. Which is why i choose to move out of my comfort zone and try to improve my communication skill here in KMK.</p><p>Since i joined KMK, my communication skill is being tested everyday for most of the time in many opportunities. Let’s just take one example about it which is by doing pair programming. If i am not able to convey my thoughts or concerns when pairing, then the pairing will definitely not working.</p><p>Because pairing demands two way feedback means there are supposed to be some active and reactive exchange of words happening in there. If we are unable to understand each other, it will have a bad impact on the code that is written and the pairs because we don’t have the same goal in our mind. It might be better to work solo than pairing if that keeps on happening for a long time without any improvement happens.</p><p>I do admit at first when i was still trying to learn about the new codebase, frameworks and the culture, it’s really hard for me to convey my thoughts at all because i have no idea how the code even works because of the lack of knowledge. I ain’t gonna give some opinion that i have no idea how it will fit into the code because i was not even sure how the existing code works. So i was all blank that time.</p><p>But thanks to the support of my pair partners and my mentors who are really patient to teach and guide me to the right path and the awesome team who are really supportive to help me grow, i am finally able to fit into the team now. Now i am able to convey my thoughts more properly when communicating in internal teams and across teams even though sometimes i still messed up. I also learned and still improving on how to do a more proper documentation and how to use better wording choice when talking to technical and non technical people.</p><h3>Closing Thought</h3><p>All these changes that happen to me are reflected by XP values which are simplicity, communication, feedback, courage, and respect. To be able to find a team who shares the same value and be disciplined about it, is not that easy for sure. I would say for me to be able to grab this chance, it needs the combination of luck, fate, and courage. I think this is one of the best choices i have ever made in my life, giving myself chance to experience all of this because i don’t think i can find it anywhere else in this country.</p><p>There are actually a lot more stuffs that i want to talk about XP that gives many positive impact in my career life but i decided to just stop at here so i won’t make the post longer than this and potentially lose your interest to read this post. Maybe i will talk about it again in another blog post.</p><p>And last but not the least, i want to say thank you for each of you who spend your precious time to read this post.</p><p>Wish you have a nice day ahead ! Stay healthy and stay awesome, ya ! 😎</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cacbef1805cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vidio/experiencing-xp-has-changed-my-life-as-an-ios-engineer-cacbef1805cd">Experiencing XP has changed my life as an iOS Engineer</a> was originally published in <a href="https://medium.com/vidio">Karena Kita Vidio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A deep thought about TDD]]></title>
            <link>https://medium.com/@edysudarto00/a-deep-thought-about-tdd-f9a53ab54acd?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9a53ab54acd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[thoughts]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sat, 29 Feb 2020 19:48:03 GMT</pubDate>
            <atom:updated>2020-02-29T19:48:03.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2gPqLhABFEiuaOXF" /><figcaption>Photo by <a href="https://unsplash.com/@dtravisphd?utm_source=medium&amp;utm_medium=referral">David Travis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever done something routinely in your life and at one time you suddenly began to question the reason why you are doing it (again) ?</p><p>If you have, then i am glad to hear that.</p><p>Why ?</p><p>Because the fact that you questioned about the purpose of something that you invest your time into, means that you want to understand what do you want to achieve with it. And that’s a good thing.</p><p>Just so you know, i am not gonna explain about how to do TDD here. It will be about sharing my thought of TDD concept as the title said and how interesting it is because i can connect it to other careers out there.</p><p>Before we started, we need to have the same basis in our mind so you can understand what i am trying to tell you here. What kind of basis ? Definitely about what is TDD.</p><blockquote>TDD or Test Driven Development is a development technique where you must first write a test that fails before you write new functional code.</blockquote><p>Yes right, write a test that fails for codes you haven’t written then write the functional code for it.</p><p>If it doesn’t make sense for you now, it’s okay. I hope you can try finish up reading this article because i gonna talk bit about why it makes sense to me and many other people out there.</p><p>TDD itself is something unheard for many software engineers. Even when they heard it, some of them think it doesn’t make sense and the rest think it does. For people who think it makes sense, some of them do it because they have to (the management rules force them to accept it or they just think it is cool) and the rest understand what it really means to do TDD.</p><p>Me myself have been doing this for more than a year now. Of course, i started off as someone who never heard about TDD before. I once was having a hard time when accepting it for the first time as someone who never written tests at all. But when i learnt and finally understood (with the help of my team and given learning resources) about what’s the purpose of TDD and how to do it properly, i can accept it as a whole now.</p><h3>TDD in Software Engineering</h3><p>So let’s start with the purpose of TDD existence in software engineering practices. It is actually related to code design and unit testing, places where people usually are having hard time with. There are few reasons that i found from the internet and based on my experience that become part of the purpose of TDD:</p><ol><li>People tends to feel less motivated (or forgot) to write tests after the implementation because the feature is already done and that’s what everyone cares about.</li><li>People tends to write just-because-it-is-the-rule tests not with the intention to cover their logic in the implementation but only as a requirement by management which defeats the purpose of testing.</li><li>Unit Testing becomes a hassle because of complex and coupled implementation codes which makes people tends to skip it (or the complex part).</li><li>Some people think writing tests is a waste of time, it’s better to just focus in writing the “real code” by thinking it was profitable that way.</li></ol><p>So those 4 reasons are the problems i found which can be solved using TDD. It’s like having a hero arise to stand up for us against the villain, TDD arise to stand up against bad design of code and bugs. We can never make them all gone but we can fight it, we can minimalize the bad code design and bugs in our project than just letting it go wild in it.</p><p>So why i said TDD will solve those problems ? Well, i will explain it one by one by referencing the numbers of each problems stated above and how it will solve it.</p><ol><li>If you always write the tests first before the implementation, then you have no chance to forget or feel less motivated to do it because that’s the first thing you have to do before writing the implementation. Simple, right ? Let’s hop to the next one then.</li><li>What is the purpose of testing ? For me, it’s to make sure every code that was written will be working fine and when something breaks, i can know why and where right away. As the codebase getting larger and larger, there is no way i can keep writing code without breaking anything as a normal human. That’s why i need testing (and maybe you too). Having TDD to make sure i run test frequently are giving me the assurance of i am not breaking anything while writing new code or refactoring. Writing tests becomes something i do, not because of a rule but because i know how it will benefit me now and in the future like how i know saving my money is good for my future. So will you do the same ?</li><li>By doing TDD, we will start writing simple thing for testing. It makes us to only think about the simplest design possible to make this feature works because we just focus on what do we need to make it work and how it should work. This is a bit tricky when you are just starting on TDD but when you already get the grip of it, it will really helps on how you should think about your code design so it won’t be that complex and coupled. Having a new perspective on code is really a great thing to experience, trust me because it does.</li><li>Talking about profitable, i disagree with this. Think about when your codebase is so large that adding a new feature will always break the existing features. I have experienced building an iOS project till a moment that we think it’s too hard to add anything into it anymore. Because adding a feature will cause many bugs to appear and it takes a few days to make the app stable again. So we just suggested a revamp on the app and write it from zero. Just imagine if those hours we used to revamp the app to be used to write a new feature or improving the app itself, i think it might be more profitable for business for sure than spending it for the revamp. High maintenance cost and slow progress for the updates are the enemies for every manager out there.</li></ol><p>There is actually much more deeper and more clear explanation about how TDD will helps in software engineering and how to do TDD, but i am not the most suitable person to do it now so i’ll leave it to your curiosity to find them.</p><h3>TDD in Other Careers</h3><p>I read a thread once shared by my colleagues about some people who thinks TDD is useless or something similar. Then there is this interesting part where they (the one who breathe in TDD) discuss about TDD concept relation in other careers.</p><p>First is TDD concept in accounting. There is a system called double-entry bookkeeping in accounting where every transaction will affect at least two accounts (one for debit and one for credit) which the end result should be the same aka in balance. If both sides are not balance then it means there is an error occurred when the accountant was doing the equation. Doesn’t it sound similar like TDD concept where we write codes on the implementation and test side when writing new code, making sure both works properly. When the test fails then there must be some error in our code.</p><p>Another example is TDD concept in medical surgery. Doctors always wash their hands and sterilize the tools before doing a surgery. Why would they do that ? Maybe it’s obvious to you. Of course it’s to kill the germs to prevent infection when the surgery happens. Then isn’t that the same thing we can apply in software engineering too ? We try to “kill” the bugs in our app before it can cause “infection” in our codes later by doing TDD. We write tests to cover the logic so when any bug appears, we can detect it fast and kill it before the code deploys in production.</p><p>Maybe some of you would think those two examples is something that they have to do because it is the standard practices globally. But something like that was built because there is a (good) reason behind it. Because they know what kind of bad thing will happen if they don’t do that, they understand why it is bad to not following that practice.</p><h3>Closing Thought</h3><p>There is a big difference between people who knows how to do something and people who also understands the reason why they do it. By doing something we don’t understand even though it is a good thing, we might ended up feeling we are doing something useless or we might even doing it the wrong way.</p><p>As a creature who can think and always keep on learning, i hope we’ll always grow up to find reasoning behind every actions that we take especially in our career as a professional.</p><p>Please do give your clap(s) below if you think this article has given you something useful in your life.</p><p>Thank you and have a great day !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9a53ab54acd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Myths about Programmer]]></title>
            <link>https://medium.com/@edysudarto00/7-myths-about-programmer-f29716d78620?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/f29716d78620</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sat, 21 Dec 2019 16:46:06 GMT</pubDate>
            <atom:updated>2019-12-21T16:47:13.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RkEpYDiBb-sZjKyI" /><figcaption>Photo by <a href="https://unsplash.com/@maxcodes?utm_source=medium&amp;utm_medium=referral">Max Nelson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For all of these years since i learnt about the existence of programmer till i become one of them, i have found and heard so many things about them, ermm.. sorry i should say “us” now. So some “assumptions” about them has been bothering me for quite a while and i think i want to clear things up so the programmer image will change slowly into the right path. This is just something that i write in my spare time not some scientific research or something, this is based on my experience so if you are not agree with it then it’s up to you.</p><p>So maybe some of you might want to ask why it is 7, why not 10 or 20 myths ? Nothing special or too deep about the number, i just personally feel 7 is a unique number and reminded me of lucky seven when you hit a jackpot in the arcade centre. Also i have only been able to think up to 7 myths only so let’s keep it at that for now.</p><p>Before we continue, if you are not a programmer, i hope this post will open up your mind with some truths about programmer whether you have heard them or not. If you are a programmer yourself, let’s see if this post describes you or not. So, please enjoy and let’s pump in some more knowledge to your awesome brain.</p><h3>1. Being Programmer is too stressful</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1T8lk7YpQwenhMf6" /><figcaption>Photo by <a href="https://unsplash.com/@punttim?utm_source=medium&amp;utm_medium=referral">Tim Gouw</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I think any work can be stressful if you don’t do it well at the moment and especially you don’t really have any interest in it. I was once working in a non programmer job which is also my first job when entering college life. Didn’t like it because i didn’t really have any interest in it but i wanted to gain some experience working in a company while studying in a college. So as a newbie i made many mistakes of course, i could say that almost everyday at that time was so stressful for me. But i did learn a lot from there and it was thanks to them that i am here now in this moment.</p><p>Now being a programmer myself, my everyday here aren’t that stressful compared to my first job working experience. I love my job now and i also have gain many skills and experience relevant to it which helps a lot for me to go through my everyday works. I think the only time where programmer feel stressed a lot is when they are faced with a bug out of nowhere and they have no clue where to find it let alone how to solve it.</p><p>If one were to face that kind of thing almost everyday, anyone will feel too stressful of course. So in order to prevent that, we can write tests to cover our code and reduce the possibility for the bugs to appear and for having no clue where they comes from. So being a programmer is <strong>NOT</strong> too <strong>stressful</strong> but it just depends on the programmer’s choice, way of work and environment.</p><h3>2. Programmer is a shut-in type and quiet person</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PUDebj6LD2Oe_4WA" /><figcaption>Photo by <a href="https://unsplash.com/@jefflssantos?utm_source=medium&amp;utm_medium=referral">Jefferson Santos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This must be because of the picture of that guy who always sits in dark room wearing headphones and typing on his keyboard as if he was hacking into some site. No, no, no, programmer is not a shut-in type and quiet, it just because of the person’s personality. Some people might have problem to socialize with others and going out into crowded place but it doesn’t mean that every programmer will behave like that.</p><p>I have some friends that told me sometimes that they were surprised that i could talked a lot with them, because they thought i was supposed to be some typical programmer who won’t talk much to people. Sorry if i disappointed you guys, that’s just how i am if we get along. I also need to talk quite a bit when i am working in the office too afterall. Why ? Because i am not just doing some usual programming that you see everyday but i am doing “pair programming” where i work with another programmer and communicating with them when writing codes.</p><p>If you haven’t heard about pair programming you can read it in my previous post <a href="https://medium.com/p/415b22f66d16">here</a>. I also do like hang out with my friends when available so i am one of the living proof that programmer is not a shut-in and quiet person, it really depends on the personality.</p><h3>3. Normal people can’t understand what programmer is saying</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F9mgLbe9ETH6EOVh" /><figcaption>Photo by <a href="https://unsplash.com/@benwhitephotography?utm_source=medium&amp;utm_medium=referral">Ben White</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For sure, i heard and read a lot about how words that comes out from a programmer’s mouth or mind are not understandable by “normal” people (this means non-programmer people they said). By saying “normal” people, it indicates that programmer itself is like another type of people who speak another language that only their kind could understand. But hey, that’s not true. If programmer words are not understandable, then how the heck they could work together with other people that are not programmer ? Think about it.</p><p>I also have colleagues that were already married and even have kids. Guess what, their partner is <strong>NOT</strong> a programmer. How can they live with someone if they don’t understand the words coming out of their partner ? No, don’t say it’s because the power of love or something, please just save that for your romantic drama fantasy. You need to communicate properly so you can understand each other unless you are psychics, full stop. Also you are now reading a post written by a programmer and if you understand at least some of it then that proves it.</p><h3>4. Programmer can fix your computer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9wm-NDGMSyEYm2On" /><figcaption>Photo by <a href="https://unsplash.com/@mariana42?utm_source=medium&amp;utm_medium=referral">Mariana B.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is one of the famous myths that many people knows, usually it is correlated to our family or relatives that has something wrong with their computers or smartphones and come to us to seek for help. “So i heard that you are programmer, can you help me to fix my computer cause it’s not working since this morning?”. The answer is absolute big <strong>NO</strong>, we are programmer not computer technician.</p><p>This is proof that many people still see if you are related to IT stuffs, it means that you can fix any computer or even hack into it. The truth is, programmer knows how to write code to build a program, we can’t fix your computer if the screen is broken or the OS is failing. You need to go take that to the computer technician where that is their specialty. It’s almost like you are telling a dermatologist<strong> </strong>to check your flu just because they are doctors too. We can’t fix your computer but maybe we can help search it over internet for you and try but not because we are a programmer.</p><h3>5. Programmer writes incomprehensible code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vAPnePMdpv_szXmt" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>“The harder someone try to read your code the cooler you are as a programmer”. So apparently, some people think that to be a great programmer you should be able to build something awesome and write the code in a way that you are the only one who can read it so your worth will be high. Because no other people can change the code without breaking anything except you. Unless they are some high intelligent person that can understand your “encrypted” code even with those efforts you have put in.</p><p>Clearly that is not the mindset one supposed to have if you are working with other people. If you are working on the project alone as it is personal and don’t want anyone else to work on or understand them then it’s up to you (don’t complaint if in the next 6 months you re-read your code and don’t understand a bit about them though). But if you are working with other people, the easier a person to read your code the better you are seen as a programmer.</p><p>Because teamwork will work if the communication is running properly, this means through the code too. Of course that is what i am doing everyday in the office, writing my code in a way that is easier to be understood by other people.</p><h3>6. Being programmer is easy, just copy paste from the internet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_pWVBVVo05g-g3tP" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=medium&amp;utm_medium=referral">Annie Spratt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is actually a contradiction with myth number 1 but i have read and heard this quite a bit in the internet too so i want to clear things up here. The way it says almost like they are saying being a graphic designer is easy, you just copy that image and put some color there and put it together and there you go a poster for your film.</p><p>If you don’t get it, sorry i’ll rephrase it with clearer example. Imagine if you are making a film poster about warm family christmas movie, you don’t just put an image of smiling pumpkin there with black background with some figure grinning like a psychopath standing in the rain and thunder outside of a house grabbing some knife. That doesn’t sound like a warm family christmas movie for you, does it ? They need to find the correct image, background and color to match the theme that is requested so they can give a proper film poster.</p><p>Just like graphic designer, programmer don’t just copy paste the code from the internet. We need to have the knowledge to determine what we need to find and which part of code that we can and we need to use to adapt it in our project. Sometimes we might even have think about how to make it work in our project cause the environment are just too different. If you just randomly copy paste everything from the internet without adjusting to your project’s code, be assured that there will be many times where they won’t work as you expect to or they might not even compiled.</p><h3>7. Programmer has no life</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fFlie7BAbw5wrNid" /><figcaption>Photo by <a href="https://unsplash.com/@e_sykes?utm_source=medium&amp;utm_medium=referral">Ethan Sykes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is probably one of the most popular myth about programmer. When you heard about programmer what kind of image that was shown in your head ? Is it someone who has to work in front of the computer all day through the night ? Someone who has no enough time to rest or even hang out so they have no life ? I once had those images in my head in the past, just when i first heard about programmer. Not just because i heard it, saw it but i also experienced it when trying out to be one in my early year.</p><p>But then at one time, i realized that that is not the case at all. The root cause is <strong>NOT</strong> being the programmer itself as if it is some kind of curse occupation but instead the choice that i made. I chose to write messy code without any tests, i chose to work in a way that i have to do overtime when my code fails me most of the time. And because the company policy states that you have to finish your work before the deadline or else.</p><p>So, since that time i was trying and still actually to improve myself to write cleaner code, writing tests and work in a company where their policies support work life balance which i have the right to have. And now here i am in a company who supports work life balance, no deadline driven development, and an awesome team who also supports to write cleaner code and writing tests (and many more) so we will have much more stable program leads to no overtime working. Finally, i have a life now as a programmer. :)</p><h3>End of myths</h3><p>So after reading the list of the myths above, have the programmer image in your mind changed now ? I do hope so if the image previously doesn’t fit the one i write here. Well, i hope you get something from this humble post of mine either knowledge or you feel a bit entertained.</p><p>If you guys have another myth or don’t agree on one of the myths above, feel free to write in the comment section.</p><p>Thank you for reading and stay awesome ! :D</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f29716d78620" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mengenal dasar RxSwift]]></title>
            <link>https://medium.com/vidio/mengenal-dasar-rxswift-fbb3e53e1967?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbb3e53e1967</guid>
            <category><![CDATA[indonesia]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[bahasa-indonesia]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[rxswift]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sun, 24 Nov 2019 16:25:11 GMT</pubDate>
            <atom:updated>2019-11-24T16:25:11.849Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GAGnxwhb4NpBqTgu" /><figcaption>Photo by <a href="https://unsplash.com/@emilep?utm_source=medium&amp;utm_medium=referral">Émile Perron</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sepengalaman saya selama melakukan iOS <em>programming</em> sebelum ke Jakarta, saya hanya mengenal <strong>Completion Handler</strong> untuk menangani proses <em>asynchronous</em> seperti proses pemanggilan API. Itu adalah satu-satunya teknik yang dikenalkan kepada saya dan teman saya yang lain saat mempelajari iOS <em>programming</em>.</p><p>Kalau prosesnya tidak banyak sih masih syukur, masih gampang dibaca dan di <em>maintain</em>. Tapi kalau udah menyangkut beberapa proses, sudah mulai kewalahan. Contoh saya pernah ketemu kasus dimana UI nya di <em>update</em> jika dan hanya jika 2 <em>request</em> API tertentu sudah selesai. Kalau dulu saya <em>handle</em> nya membentuk chaining request untuk 2 API tersebut. Jadi kalau <em>request</em> pertama selesai baru manggil <em>request</em> kedua dan bila <em>request</em> kedua selesai barulah saya memperbaharui UI nya. Yep, <em>simple minded</em> dan mungkin ada cara yang lain namun saya hanya terpikir cara itu yang paling gampang dan <em>straight forward</em>.</p><p>Namun saat saya mulai bekerja di Jakarta, saya cukup bingung awalnya karena dalam project iOS yang dibangun tidak memakai Completion Handler secara langsung melainkan menggunakan library yang namanya <strong>RxSwift</strong>. Disinilah saya mulai mengenal RxSwift, ibarat namanya mengenal hal-hal baru awalnya saya kesulitan memahami bagaimana cara kerjanya dan merasa RxSwift sangat merepotkan dan membingungkan.</p><blockquote>Tapi seperti kata pepatah <strong>“Tak kenal maka tak sayang”</strong>, jadi saya mencoba mengenal lebih dekat apa itu RxSwift dengan bantuan teammate.</blockquote><p>Lalu sekarang, saya sudah jauh lebih memahami RxSwift dibanding saya yang dulu. Bahkan saya sangat senang menggunakannya dan bisa dibilang merasa sering dimanjakan oleh RxSwift karena fitur-fiturnya yang sangat membantu dalam menulis kode yang deklaratif untuk menangani proses <em>asynchronous</em> dan lainnya. Namun seperti yang saya tulis sebelumnya, butuh waktu dan tenaga untuk memahaminya agar bisa mengapresiasi RxSwift. Saya juga sadar bahwa ada orang di luar sana seperti saya dulu yang belum begitu mengenal dan memahami apa itu RxSwift.</p><p>Pada suatu ketika, saya pernah menyebut <strong>RxSwift</strong> dan menanyakan pendapat temen saya mengenainya saat lagi <em>hangout</em> bareng. Dia merespon seperti ini “<em>Ohh iya, saya pernah coba, RxSwift itu yang ini kan...(menjelaskan apa yang dia tau</em>)” dan diakhiri “<em>Tapi saya tidak begitu mengerti sih bagaimana cara pakainya</em>”.</p><p>Dari penjelasannya saya sadar, bahwa dia tidak begitu memahami cara kerja RxSwift dan apa tujuan RxSwift itu dibuat. Saya pun membuat tulisan ini dan berharap semoga tulisan ini dapat dicerna cukup mudah sehingga anda yang membaca tulisan ini bisa lebih mengenal RxSwift di jalan yang benar. Namun yang saya bahas di sini hanya <em>basic concept</em> dari RxSwift.</p><h3>Jadi apa itu RxSwift ?</h3><p>Tadi sudah saya singgung sedikit di atas bahwa RxSwift itu adalah <em>library</em> yang membantu kita dalam mengatur penanganan proses <em>asynchronous</em>. Sesuai dengan namanya, <em>library</em> tersebut digunakan dalam bahasa pemograman <strong>Swift</strong>. Dia ini anaknya <a href="https://github.com/dotnet/reactive"><strong>Rx</strong></a>, nah kalau mau tahu Rx itu apa bisa dibaca sendiri ya soalnya terlalu panjang kalau mau saya bahas dalam tulisan ini.</p><p>Dalam RxSwift, ada 2 object yang akan selalu kita temukan di setiap proses yaitu <strong>Observable</strong> dan <strong>Observer</strong>. <strong>Observable</strong> ini perannya sebagai <em>source</em> yang memberikan data dengan cara seperti memancarkan sinyal. Sedangkan <strong>Observer</strong> berperan untuk menangkap sinyal tersebut sehingga bisa mendapatkan data dari si <strong>Observable</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t_XLn7UwV8hchQMB" /><figcaption>Photo by <a href="https://unsplash.com/@jamie452?utm_source=medium&amp;utm_medium=referral">Jamie Street</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Bila digambarkan dengan cara lain, cara kerjanya seperti di aplikasi Medium ini. Misal anda mem-<em>follow</em> akun saya di Medium maka anda telah membentuk sebuah <strong>Observer</strong>. Sedangkan akun saya di Medium menjadi <strong>Observable</strong>. Saat saya memposting tulisan baru, maka anda akan mendapat notifikasi dari Medium mengenai tulisan baru saya. Notifikasi berisi informasi tulisan baru saya itu adalah contoh data yang dipancarkan seperti sinyal. Selama anda masih mem-<em>follow</em> saya, bila saya memposting tulisan baru lagi, anda akan mendapat notifikasi yang baru lagi juga.</p><p>Kalau begitu cara kerjanya, apakah cara kerja <em>unfollow</em> akun Medium juga berarti <strong>Observer</strong> berhenti menangkap sinyal dari <strong>Observable</strong> ? Jawabannya BENAR dan TEPAT sekali !! Seperti sistem <em>follow</em> dan <em>unfollow</em> di Medium, anda bisa memilih untuk tidak lagi menangkap sinyal dari sebuah <strong>Observable</strong> yakni dengan cara membuang <strong>Observer</strong> tersebut atau <em>term-</em>nya itu di <strong>dispose</strong><em>. </em>Bila tidak di <strong>dispose</strong> maka nanti <em>object-</em>nya akan tetap hidup di memori dan menyebabkan <em>memory leak</em>.</p><h3>Contoh Observable dan Observer</h3><p>Berikut saya berikan contoh dalam bentuk kode sampel mengenai penggunaan RxSwift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1V8KdVGST9QOIlL2zb-sig.png" /><figcaption>Contoh pembuatan Observable (link yang ada hanya contoh dan tidak benar-benar ada)</figcaption></figure><p>Hal pertama yang paling jelas dan paling penting adalah tentunya meng-<em>import</em> si RxSwift biar fitur-fiturnya bisa dipakai di <em>file</em> tersebut. Dalam contoh <strong>struct TitleProvider</strong> di atas dapat di lihat bahwa saya membuat sebuah Observable bila fungsi <strong>getCurrentTitle</strong> dipanggil.</p><p>Di dalam <em>block</em> ada implementasi <em>request</em> API. Di dalam <em>Completion Handler </em>nya saya menggunakan fungsi <strong>onNext</strong> untuk melempar datanya kepada Observer. Bila terjadi <em>error</em> saya juga melempar <em>error</em> tersebut kepada Observer menggunakan fungsi <strong>onError</strong>. Kita perlu mengembalikan <em>object</em> <strong>Disposables</strong> agar Observer nantinya dapat di <strong>dispose</strong> untuk berhenti menerima data dari Observable ini.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsvbjPt1rQfRECh0PgL__A.png" /><figcaption>Contoh Observer yang melakukan subscribe pada Observable</figcaption></figure><p>Lalu pada <strong>TitleReceiver</strong> saya membuat Observer saat fungsi <strong>setupCurrentTitle</strong> dipanggil. Dapat dilihat bahwa saya melakukan <strong>subscribe</strong> pada Observable hasil dari fungsi <strong>getCurrentTitle</strong>. Lalu saya mengisi 2 <em>block</em> yang ada di sana yaitu <strong>onNext</strong> untuk mengolah data yang diterima dan <strong>onError</strong> untuk menangani <em>error</em> yang terjadi.</p><p>Sebenarnya ada lagi dua <em>block</em> tambahan secara <em>default </em>namun juga <em>optional</em> yaitu <strong>onCompleted</strong> yang dipanggil bila menerima sinyal <strong>onCompleted</strong><em> </em>dari<em> </em>Observable<em> </em>dan <strong>onDisposed</strong> yang dipanggil bila Observer telah ke <strong>dispose</strong>. Cuma untuk onCompleted dan onDisposed sangat jarang saya pakai jadi tidak saya cantumkan pada contoh biar lebih fokus pada hal yang lebih sering dipakai. Bila onCompleted atau onError kepanggil maka Observer akan otomatis men-<strong>dispose</strong> diri sendiri.</p><p>Mungkin ada yang berpikir kalau misalnya perlu melakukan subscribe pada beberapa Observable apakah jadi harus membuat dan memegang beberapa variabel <strong>Disposable</strong> di dalam suatu <em>object</em> ?</p><p>Tenang karena RxSwift menyediakan alternatif untuk keadaan seperti itu yakni dengan menggunakan <strong>DisposeBag</strong>. Pada setiap Observable yang di <strong>subscribe</strong>, panggil fungsi <strong>disposed(by:</strong>) dan masukkan <em>object</em> DisposeBag yang telah dipegang di <em>object</em> <em>parent</em> pada fungsi tersebut. DisposeBag akan memegang semua Disposable yang telah didaftarkan menggunakan fungsi tersebut dan bila object yang memegang DisposeBag telah hilang dari memori maka DisposeBag akan secara otomatis men-<strong>dispose</strong> semua <strong>Disposable</strong> yang dia pegang sehingga tidak terjadi <em>memory leak</em>. Berikut contoh penggunaan DisposeBag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mvQMZlhN09P3izXPrAA8cQ.png" /><figcaption>Contoh penggunaan DisposeBag</figcaption></figure><p>Untuk satu proses saja mungkin belum kelihatan efeknya, namun bayangkan bila sekian banyak proses Completion Handler yang ada di project anda diganti dengan <em>style</em> seperti ini, kode anda menjadi lebih deklaratif dan lebih mudah dibaca. Anda tidak perlu khawatir nama argumen pada Completion Handler tidak sama atau deklarasi argumen error yang <em>optional</em> yang harus anda tangani karena tidak ingin mengotori kode di bagian depan bila tidak diperlukan. Dengan menggunakan RxSwift, kode anda menjadi lebih rapi dan deklaratif.</p><h3>Penutup</h3><p>Bagaimana sampai disini ? Apakah mampu memahami implementasi minimal dari RxSwift ? Apa yang saya tulis di atas baru sebagian kecil dari sekian banyak kemampuan RxSwift yang sebenarnya. Banyak lagi fitur-fitur menarik dan sangat membantu dari RxSwift bila anda ingin mempelajari lebih lanjut seperti penggunaan <strong>zip</strong>, <strong>drive</strong>, <strong>combineLatest</strong>, dll. Tapi yah harus memahami dasarnya dulu baru bisa mencoba yang lebih <em>advanced </em>biar tidak pusing nantinya.</p><p>Awalnya saya ingin menulis banyak hal namun karena saya tidak mau tulisan ini terlalu panjang, jadi saya akhiri dulu di sini. Mungkin pada tulisan berikutnya baru akan saya bahas yang lebih dalam, dengan asumsi sudah pada mengerti konsep dasar RxSwift bila ada yang tertarik. Kalau ingin membaca sendiri dokumentasinya bisa coba dibaca <a href="https://github.com/ReactiveX/RxSwift">di sumbernya</a> langsung.</p><p>Bila ada feedback atau kritik ataupun koreksi bisa disampaikan dengan menulis respon di bawah ini.</p><p>Terima kasih telah meluangkan waktu anda yang berharga untuk membaca tulisan sederhana ini.</p><p><em>Stay awesome and see you next time </em>!! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbb3e53e1967" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vidio/mengenal-dasar-rxswift-fbb3e53e1967">Mengenal dasar RxSwift</a> was originally published in <a href="https://medium.com/vidio">Karena Kita Vidio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dari “single” menuju “pair” programming]]></title>
            <link>https://medium.com/@edysudarto00/dari-single-menuju-pair-programming-a67efd385cf3?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/a67efd385cf3</guid>
            <category><![CDATA[pair-programming]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sun, 21 Jul 2019 07:15:36 GMT</pubDate>
            <atom:updated>2019-07-21T08:19:10.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1DdJK4gTVnn1Ka_LpcItg.png" /><figcaption>Artikel ini merupakan versi bahasa dengan sedikit penyesuaian dari artikel originalnya versi english di <a href="https://blog.kmkonline.co.id/from-single-to-pair-programming-415b22f66d16">sini</a></figcaption></figure><p>Apakah anda merasa anda mampu untuk melakukan <em>“Pair Programming” ?</em></p><p>Apakah anda merasa anda mampu untuk ber-transisi dari “<em>single” </em>menuju <em>“pair” programming</em> ?</p><p>Sebelum saya membahas lebih dalam, istilah <em>“Pair Programming” </em>sendiri sebenarnya terdengar cukup asing bagi kebanyakan programmer dan termasuk saya sendiri bila anda menanyakan istilah tersebut kepada saya lebih dari setengah tahun yang lalu. Namun itu saat sebelum saya pindah untuk bekerja di perusahaan baru saya di sini yang melakukan <em>pair programming</em> secara penuh sebagai budaya mereka. Saya menemukan bahwa sebenarnya <em>pair programming</em> itu cukup menyenangkan dan memuaskan namun juga sangat sulit untuk dilakukan.</p><p>Sebelum kita melanjutkan cerita mengenai pengalaman transisi saya, alangkah baiknya bila kita menyamakan konsep terlebih dahulu. Mungkin sebagian besar anda yang sedang membaca ini masih belum mengenal apa itu <em>pair programming </em>seperti yang saya katakan di atas karena memang budaya ini masih terdengar cukup asing bagi banyak programmer. Namun bila anda sudah paham mengenai itu maka silahkan melanjutkan membaca ke bagian “Sang Pemicu”<em>. </em>Untuk yang masih belum, jangan khawatir karena saya akan mencoba menjelaskan hal tersebut di bagian selanjutnya dengan bahasa yang semoga dapat lebih mudah dimengerti dengan harapan anda akan mendapatkan gambaran yang lebih jelas mengenai <em>pair programming</em>.</p><h3>Yuk “kenalan” dengan <em>Pair Programming</em> !</h3><p>Bila anda mencarinya di mbah Google, biasanya si mbah bakal ngasih tau kalau <em>pair programming</em> itu adalah sebuah aktivitas dimana terdapat 2 programmer yang mengerjakan suatu hal di depan satu komputer (tidak berarti harus satu keyboard dan satu mouse ya). Lah, bagaimana cara kerjanya kalau kayak gitu ? Pasti pada bingung kan. Nah sebelum imajinasi anda meluas hingga ke alam semesta (kalau yang udah tolong dibalikin lagi), saya akan memberikan penjelasan yang jauh lebih mudah dipahami daripada keterangan di atas sekarang.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uqm5_Zg1yKyrsbHJ" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Kalau disuruh untuk membayangkan, saya akan membayangkan <em>pair programming</em> itu seperti bermain jungkat-jungkit di taman bermain. Anda memainkannya dengan dua orang (itu jumlah minimal pemain yang disarankan) dan masing masing dari anda akan mendapat giliran untuk mendorong permukaan tanah menggunakan kaki anda sehingga sisi anda akan naik dan sisi di seberang anda akan turun. Sama halnya dengan <em>pair programming</em>, akan ada giliran untuk siapa yang akan menggunakan keyboard untuk menulis kode program. Jadi tidak seperti dua orang yang menulis kode secara bersamaan layaknya balapan, bisa kacau balau dunia pemograman kalau seperti itu caranya.</p><p>Untuk tekniknya sendiri, ada 3 teknik yang biasanya sering dipakai dalam <em>pair programming</em>. Saya akan mencoba membahas satu per satu berdasarkan pemahaman saya dan apa yang saya temukan dari internet.</p><ol><li><strong>Driver dan Navigator (Traditional style). </strong>Dalam teknik ini, <em>driver</em> adalah orang yang akan menulis kode dan <em>navigator</em> adalah orang yang melakukan <em>review</em> dengan mengikuti perkembangan dari kode yang ditulis oleh sang <em>driver </em>dengan memperhatikannya. Mereka berdua dapat berkomunikasi sebelum dan saat proses pembahasan mengenai cara untuk menyelesaikan tugas yang sedang dikerjakan. Namun teknik ini sulit bila anda masih sangat baru dengan <em>pair programming </em>dikarenakan teknik ini sangat bergantung pada bagusnya alur komunikasi berjalan. Saya sendiri sering kehilangan konteks dan jadi tidak fokus lagi pada kode yang sedang ditulis saat mencoba menjadi <em>navigator</em> untuk pertama kalinya.</li><li><strong>Driver dan Navigator (Strong style).</strong> Saat mengerjakan sebuah tugas, sang <em>driver</em> akan menjadi orang yang menulis kode di layar dan sang <em>navigator</em> akan memberikan penjelasan dan membimbing <em>driver</em> akan ide untuk menyelesaikan tugas tersebut. Menurut saya, teknik ini jauh lebih baik daripada yang pertama karena kedua pihak dapat menjadi aktif dan komunikasinya lebih terasa disini. Bila sang <em>driver</em> memiliki ide dan mau mengimplementasikannya maka dia harus bertukar peran dengan pasangannya dan menjelaskan idenya sedangkan pasangannya (si <em>driver </em>baru) akan menulis kodenya.</li><li><strong>Ping-Pong Pairing.</strong> Teknik yang satu ini adalah teknik yang unik dimana ia dikombinasikan dengan TDD dan menurut saya teknik ini hanya akan bekerja bila pasangannya tahu dan mengerti mengenai TDD. Pada intinya, dalam teknik ini salah satu dari mereka berdua akan mulai dengan menulis tes yang gagal lalu memberikan keyboard kepada pasangan mereka untuk membuat tes tersebut hijau dan melakukan refactor. Lalu pasangan tersebut akan menulis tes yang gagal dan memberikan keyboard kembali kepada yang pasangan yang memberikannya keyboard di awal untuk membuat tes tersebut hijau dan melakukan refactor. Lempar balik giliran seperti ini yang menjadi alasan mengapa ia disebut teknik “Ping-Pong Pairing”. Putaran terus berlanjut hingga tugas yang dikerjakan selesai dan lakukan putaran baru bila mengerjakan tugas yang baru.</li></ol><h3>Sang Pemicu</h3><p>Setiap programmer memulai karirnya bekerja dalam budaya “<em>single programming”</em>. Yang saya maksud dengan <em>“single”</em> di sini adalah saat ada proyek/produk perangkat lunak, masing masing programmer yang mengerjakannya akan diberikan tugas yang berbeda beda sehingga anda akan bekerja sendiri pada tugas anda sendiri satu per satu. Itulah mengapa saya menyebutnya sebagai <em>“single” programming.</em></p><p>Saat setiap programmer yang telah terbiasa melakukan <em>“single programming”</em> ditawarkan untuk mencoba “<em>pair programming”</em>, kebanyakan dari mereka akan khawatir tentang bagaimana hal tersebut bisa bekerja. Yah tentu saja mereka akan khawatir tentang itu. Coba saja anda bayangkan bila kebebasan anda untuk menulis kode di komputer anda saat anda sedang duduk di sudut ruangan atau di atas sofa sambil mendengarkan lagu favorit anda di Spotify sembari tidak membiarkan siapapun untuk mengganggu konsentrasi anda atau memberi tahu anda bahwa ada cara lain untuk mengerjakan tugas tersebut, di ambil dari anda. Lalu muncul seseorang yang duduk di sebelah anda, sambil tersenyum dia menjelaskan kepada anda mengenai idenya dan memperhatikan anda menulis kode setiap hari. Saya yakin itu tidak terasa menyenangkan bukan.</p><p>Tentunya saya dulu juga salah satu orang yang menikmati <em>“single programming”</em> sejak hari pertama saya menjadi seorang programmer hingga suatu ketika saya mendapat tawaran untuk bekerja di ibukota. Saya sesungguhnya merasa senang namun juga bimbang saat mendapat tawaran ini karena saya jadi harus pindah jauh dari kampung halaman untuk merasakan pengalaman TDD dan <em>Pair Programming </em>yang dimana terasa sangat “asing” bagi saya.</p><p>Jadi intinya, saya harus meninggalkan zona nyaman saya untuk mencoba hal-hal baru ini (TDD dan <em>Pair Programming</em>) dimana saat itu saya bahkan tidak yakin apakah saya akan cocok dengan budaya ini. Namun entah mengapa, saya seperti mendengar ada suara di dalam lubuk hati saya yang beresonansi layaknya suara dalam hati yang biasanya anda lihat dalam drama atau film. Suara itu mengatakan bahwa <strong>“Saya ingin mencoba kesempatan ini karena ia terlihat menarik, walaupun bila nantinya memang tidak cocok bagi saya maka tidak apa-apa. Setidaknya, saya memiliki keberanian untuk mencoba mengambil resiko untuk mendapatkan pengalaman dari kesempatan ini karena saya merasa saya tidak dapat menemukannya dimanapun lagi di negara ini”</strong>. Jadi saya mengambil tawaran tersebut, mengikuti interview dan untungnya saya lolos dan diterima untuk mencoba masa percobaan. Dan mulai dari saat inilah, perjalanan saya dimulai.</p><h3>Pengalaman Masa Percobaan (Probation)</h3><p>Saya rasa ini adalah masa percobaan saya yang paling berat yang pernah saya alami selama bekerja. Lingkungannya terlalu berbeda dari tempat kerja saya sebelumnya. Saya memulai hanya mengetahui sedikit mengenai arsitektur, TDD dan <em>pair programming</em> di sana. Jadi setiap hari, saya harus membaca buku, belajar dan beradaptasi (untungnya perusahaan menyediakan sumber belajar secara gratis).</p><p>Sebagai pengetahuan anda, saya mengalami kesulitan melakukan <em>pair programming</em> dalam bulan pertama. Saya merasa saya selalu kebingungan saat melakukan <em>pair programming</em>. Adanya seseorang yang duduk disebelah anda menulis kode dan memperhatikan anda menulis kode seharian setiap hari masih terasa aneh bagi saya. Dan anda juga perlu berbicara satu sama lain atau anda akan merasa canggung atau bahkan anda sudah tidak peduli lagi pada kode yang ditulis.</p><p>Saya ingat saat itu sedang mencoba teknik <em>Driver</em> dan <em>Navigator</em> <em>(Traditional style)</em>. Namun karena saya masih baru, saya kebanyakan menjadi pasif. Karena terlalu banyak hal baru yang harus saya tangani, saya berjuang untuk mengikuti apa yang terjadi setiap hari di tempat kerja. Dan benar saat itu saya pernah berpikir “mungkin saya tidak cocok untuk mencoba <em>pair programming. </em>Mungkin setelah masa percobaan selesai, perjalanan saya di sini juga akan berakhir”.</p><p>Namun syukurnya saya tidak dibiarkan sendirian, di perusahaan kami ada sebuah budaya sesi mengobrol seperti curhat dimana anda dapat berbicara mengenai masalah anda dengan seorang senior di luar kantor dan tentunya masih dalam jam kantor. Baik mengenai masalah dalam bekerja di perusahaan atau tanggapan mengenai tim atau bahkan bila anda membutuhkan nasehat mengenai kehidupan asmara anda karena kami memiliki beberapa senior yang sudah menikah, saya yakin mereka cukup bijak untuk memberikan nasehat untuk itu atau setidaknya bertukar pendapat. Ini bukan candaan loh ya, ini bisa saja benar karena itu yang mereka katakan kepada saya saat pertama kali mengenalkan sesi ini. Anda dipersilahkan untuk mencoba sendiri jika tidak percaya pada saya namun anda harus bergabung dengan perusahaan kami terlebih dahulu, hehe.</p><p>Jadi melanjutkan untuk sesi “curhat” tadi, saya menjelaskan mengenai masalah saya tentang kesulitan dalam menyesuaikan diri saya terhadap TDD dan <em>pair programming</em> dengan harapan saya akan mendapat nasehat sebagai bantuan. Senior saya lalu menjelaskan kepada saya bahwa <em>pair programming</em> belum tentu dapat dilakukan oleh semua orang, beberapa orang bahkan jauh lebih baik untuk bekerja sendiri. Kunci utamanya adalah komunikasi dan membuat diri anda nyaman terlebih dahulu dengan pasangan anda (pasangan <em>pair</em> maksudnya, bukan pasangan yang lain ya). Coba untuk melakukannya dengan perlahan daripada mencoba menyerap semuanya sekaligus dikarenakan setiap orang memiliki kecepatan dan kemampuan belajar masing-masing. Jadi dalam beberapa minggu kedepan, mereka akan mencoba untuk membantu saya dengan merotasi <em>pair </em>dengan pasangan <em>pair </em>yang lain dimana pada akhirnya saya merasa lebih cocok dengan pasangan <em>pair </em>baru saya. Beliau juga memberi saya nasehat bahwa dalam <em>pair programming</em> itu seharusnya ada <strong>komunikasi dua arah antar pasangan <em>pair</em></strong> bukan cuma satu arah dan menyarankan saya untuk mencoba teknik <em>pair programming</em> yang lain. Jadi, pada akhirnya saya mencoba untuk terus melanjutkan dan beradaptasi pada lingkungan kerja. Saya mengatakan pada diri saya untuk terus mencoba hingga akhir masa percobaan dan melihat apakah semua berjalan baik atau tidak pada akhirnya.</p><p>Pelan namun pasti, saya menuju semakin dekat dengan akhir dari masa percobaan. Setelah sesi “curhat” tersebut, saya mencoba teknik <em>pair programming</em> yang lain bersama pasangan <em>pair</em> saya, yakni <em>Strong Driver </em>dan <em>Navigator style</em> dan <em>Ping-Pong Pairing</em> karena saya sudah mulai sedikit mengerti bagaimana TDD bekerja selama saya disana dan akhirnya merasa lebih nyaman karena saya ternyata lebih bisa berkomunikasi dengan baik menggunakan metode tersebut.</p><p>Sesuai nasehat dari senior saya, saya mencoba untuk melakukannya dengan perlahan dan membuat diri saya nyaman dengan TDD dan <em>pair programming</em> dengan melihat pada sisi “menyenangkan”nya dimana anda bisa berdiskusi dengan pasangan <em>pair</em> dan kadang malah mendapatkan ide yang lebih bagus yang belum pernah terpikirkan sebelumnya. Terkadang, kita hanya ngobrol santai membahas hobi kita masing-masing saat kita sedang istirahat dan mengetahui pendapat mereka tentang <em>pair programming</em> dan hal menyenangkan lainnya.</p><p>Terkadang kita bakal menemukan situasi dimana kita memiliki pendapat yang berbeda dengan pasangan <em>pair</em> kita dan tidak dapat menemukan titik tengah. Biasanya kita akan mencoba menggunakan kedua pendapat tersebut dan melihat manakah yang lebih cocok atau mencari orang lain yang kita anggap cocok untuk menjadi penengah tergantung dari kasus yang sedang dihadapi (seperti Product Manager atau Senior Engineer atau bahkan Team Lead).</p><h3>Kelulusan Masa Percobaan</h3><p>Setelah masa percobaan selesai, saya mendapat hasil yang mengatakan bahwa saya lolos masa percobaan dan senior saya melakukan review mengenai performa saya selama 3 bulan di sini. Beliau mengatakan bahwa saya telah mampu berkembang dan beradaptasi dengan baik meskipun saya masih punya banyak ruang untuk berkembang namun sudah di langkah awal yang baik dimana saya merasa senang setelah semua upaya yang telah saya kerahkan. Dari sisi saya, pengalaman <em>pair programming</em> itu tidak mudah sama sekali namun sangat menarik. Tapi sekarang saya sudah menikmati TDD dan <em>pair programming</em> karena di sana ada para senior yang sangat pintar dan bersedia untuk membantu anda berkembang apalagi efek dari <em>knowledge sharing</em> dari <em>pair programming</em> itu sangat besar. Dan tentunya sangat menyenangkan.</p><p>Akhirnya, saya tetap bekerja di sana hingga saat ini. Saya rasa saya baru bekerja lebih dari setengah tahun namun sepertinya saya akan bertahan disana untuk beberapa tahun ke depan. Dan hingga hari ini, saya sudah melakukan <em>pair programming</em> bersama lebih dari 4 orang berbeda. Saya sangat menikmati <em>pairing</em> bersama masing-masing dari mereka karena saya belajar banyak hal dari pasangan <em>pair</em> saya sembari mengembangkan diri saya sebagai seorang individual dan seorang programmer profesional.</p><p>Saya merasa saya sudah berhasil melakukan transisi dari “<em>single”</em> menuju <em>“pair” programming</em> meskipun saya belum menguasainya. Namun jangan salah menafsirkannya karena saya masih bisa melakukan <em>single programming</em> bila dibutuhkan. Tujuan dari <em>pair programming</em> bukan untuk mengurangi kemampuan anda saat bekerja sendiri namun malah meningkatkan kemampuan anda, memaksimalkan <em>knowledge sharing</em> sehingga anda dapat menghasilkan hasil yang lebih baik saat melakukan pemograman sendirian.</p><p>Saya telah belajar banyak hal yang dapat saya dapatkan saat <em>pairing</em> namun tidak saat melakukan pemograman sendiri. Apalagi, saya adalah orang yang selalu percaya kata pepatah <strong>“dua kepala lebih baik daripada satu” </strong>dan juga saya senang berdiskusi mengenai suatu hal dengan orang lain dan mencari solusi terbaik tergantung pada keadaan dan kebutuhan yang ada.</p><p>Apakah anda merasa anda mampu untuk mencoba pengalaman TDD dan <em>pair programming</em> seperti saya disini ? Apakah anda adalah orang yang tertarik untuk terus belajar dan menerima kritik ? Apakah anda ingin memiliki kesempatan untuk merasakan sesi “curhat” dengan seorang senior yang akan menjadi pendengar yang baik dan bahkan memberikan anda nasehat atau solusi atas masalah anda termasuk kehidupan asmara anda ? Jika jawabannya iya untuk minimal 2 pertanyaan pertama di atas, maka dengan tangan terbuka anda dipersilahkan untuk bergabung bersama kami di <a href="https://www.kmkonline.co.id/careers.">sini</a>.</p><p>Apapun pilihan anda, saya ingin mengucapkan semoga berhasil untuk kita semua.</p><p>Cheers !! 🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a67efd385cf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From “single” to “pair” programming]]></title>
            <link>https://medium.com/vidio/from-single-to-pair-programming-415b22f66d16?source=rss-e35726256a54------2</link>
            <guid isPermaLink="false">https://medium.com/p/415b22f66d16</guid>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[pair-programming]]></category>
            <dc:creator><![CDATA[Edy Sudarto]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 10:51:17 GMT</pubDate>
            <atom:updated>2019-07-14T15:36:47.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1DdJK4gTVnn1Ka_LpcItg.png" /></figure><p>Do you think you have what it takes to do “Pair Programming” ?</p><p>Do you think you can migrate from “single” to “pair” programming ?</p><p>Well, in the first place, “Pair Programming” itself is something that is unknown for most programmers and to me if you reach out to me more than half a year ago. That was until i moved to my new company here who do a full “pair programming” as their culture. I found that pair programming is actually quite fun and satisfying yet also difficult.</p><p>But really, what is “pair programming” exactly ? If you already understand what it is you may skip to “The Trigger” section to read my transition experience from single to pair programming. But if you don’t, worry not, cause i’ll try to explain it to you in the next section hopefully in a comprehensible way so you may get a better picture of it.</p><h3>Say “Hello” to Pair Programming</h3><p>If you searched it on Google, pair programming is an activity where there are 2 programmers working on a single computer. Yes, that’s right, mate. 2 people working on a single task on single computer (not necessarily single keyboard and single mouse though). How does that even work, right ? Hold on my tea, fella because now i am going to give you a better explanation than the one above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oYvBUMlpdOAbP5RY" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If i have to imagine it, i would imagine pair programming like playing “seesaw” in the playground. You play it with 2 people (that’s the standard minimum players count) and there will be a time where each of you get a turn to push the ground with your feet so your side will go up and the others go down. Just like pair programming, there will be a turn for who will take over the keyboard and write code with it so it’s not like two people writing code at the same time, all hell will break loose if that’s to be the case.</p><p>For the technique itself, there are 3 techniques that are usually used in pair programming. I’ll explain it based on my understanding and what i found from the internet.</p><ol><li><strong>Driver and Navigator (Traditional style)</strong>. In this technique, the driver is the one who will write the code and the navigator is the reviewer trying to keep up with the progress from the driver by observing them. Both of them may communicate before and during the process on how to solve the task on hand. But this technique is hard if you are still new to pair programming since it depends on how well the communication is going. I usually find myself losing the context and interest when being the navigator when trying out for the first time.</li><li><strong>Driver and Navigator (Strong style)</strong>. When working on certain task, the driver will be the one who write the code on the screen while the navigator explain the idea to the driver and guide them on how to solve the task. Personally this is better than the first one because both of them get to be active and the communication really kicks in here. If the driver has an idea and would like to implement it, they should swap the role with their partner and explain their idea while their partner (new driver) writing out the code.</li><li><strong>Ping-Pong Pairing</strong>. This one is a unique technique combining with TDD and personally i think it will only work if the pair knows and understand about TDD. Basically, in this technique one of them will start to write a failing test then pass the keyboard their partner to make it green and refactor. Then their partner will write failing test and pass the keyboard again back to them to make it green and refactor. This passing moment is the reason why it is called “Ping-Pong Pairing”. The loop continued until the task finished and start a new loop when they are working on a new task.</li></ol><h3><strong>The Trigger</strong></h3><p>Every programmer starts working in a “single programming” culture. What do i mean by “single” is when there are software project/product, each of the programmers that is developing the features was given different task hence you will be working alone on your own task at a time. Which is why i called it “single” programming.</p><p>When every programmers who already getting used doing “single programming” are being offered to try “pair programming”, most of them are likely to be worried on how is that going to work. I mean of course they will. Imagine that your freedom to write the code on your computer while you are sitting in the corner or on a sofa listening to your favorite playlist in Spotify while letting no one disturb you or telling you there is another way to solve a task, are being taken away. Then you have this person who are sitting beside you, smiling and trying to explain their idea and watching you writing the code everyday. It doesn’t seem to be a pleasant feeling, right.</p><p>I was also indeed one of the people who enjoy “single programming” since the day i started out to become a programmer until i got this offer to work in the capital city. I actually felt happy but a bit hesitant when i got this offer since i have to move far from my hometown to experience TDD and Pair Programming which is so “alien” to me.</p><p>So basically i have to leave my comfort zone to try out these new things (TDD and Pair Programming) which at that time i am not even sure if i am gonna fit into this culture. But somehow, deep inside my heart there is an internal voice resonating just like what you watch in dramas or films. It is saying that “<strong>I would love to try this out because it seems interesting, even if it ends up not fit for me then it’s ok. At the very least, i have the courage to take the risk to gain experience from it because i don’t think i can find it anywhere else in this country</strong>”. So i take the offer, join the interviews and fortunately accepted to try the probation period. And from here on out, the journey begins.</p><h3>Probation Experience</h3><p>This is probably the hardest probation period i have ever felt. The culture was way too different from my previous workplace. I started out knowing so little about the architecture, TDD and Pair Programming there. So everyday, i need to read a book, learning and adapting (thankfully the company provides learning resources for you for free).</p><p>To tell you the truth, in the first month i am having a hard time doing pair programming. I felt like i was lost for most of the time when doing pair programming. The weird feeling of having a person sit next beside you writing code and observing you writing code for the day everyday. And you kinda need to talk to each other or it will be awkward or you might even have no interest in the code anymore.</p><p>I remember trying out traditional driver and navigator technique at first. But as i am new, i am kinda passive most of the time. Because of too many new things to handle, i am struggling to keep up everyday at work too. And yes at that time i thought “maybe i am just not fit to try pair programming. Maybe after the probation period, this might just be the end of the journey for me here.”</p><p>But thankfully i am not being left alone, in our company there is this chat session culture where you can talk about your problems with a senior outside the office. Whether it’s about working issue in the company or feedback for the team or even if you need advice about your love life, since we have some seniors who already married, i bet they are wise enough to give you advice for that or at least exchanging opinions. No it is not a joke, it could be true since that’s what they told me. You are welcome to try it out yourself if you don’t believe me but you need to join our company first, hehe.</p><p>So continuing on the session, i explained about my problems about having a hard time adjusting myself to TDD and Pair Programming in the hope of getting advice. My senior then explain to me that pair programming might not be for everyone, some people might ended up best to work alone. The key point is communication and to make yourself comfortable first with your partner. Try to take it slow rather than trying to absorb all at once since each of us has our own pace and learning capability. So in the next few weeks, they would help me to rotate pair with another partner which i ended up felt more comfortable. He also giving me advice about pair programming where it should be <strong>two-way communication between partner</strong> not just one-way and advise me to try another technique in pair programming. So, I ended up keep on going to keep up and adapt myself to the work environment. I said to myself to try until the very end of the probation period and see if it works out or not.</p><p>Slowly but surely, approaching the end of the probation period. After that chat session, i tried another technique in pair programming with my partner, which are Strong Driver and Navigator style and Ping Pong Pairing since i kinda understand how TDD works as the time flies and i felt more comfortable eventually because i am able to communicate better with it.</p><p>As my senior said, i tried to take it slow and making myself comfortable with TDD and pair programming by looking at the “fun” side where you can discuss your idea with your partner and sometimes ended up with a better idea that you never thought before. Sometimes, we are just having fun discussing about our hobbies when we are taking a break and get to know how they feel about pair programming and a lot of other fun stuffs.</p><p>Well, sometimes we might faced this situation where we are having different opinion with our partner and can’t find satisfying solution for both. Usually we end up trying both of them and look which one suits better or find another person who we think suitable to be our middle man depends on the case (like Product Manager or Senior Engineer or even Team Lead).</p><h3>Probation Graduation</h3><p>After the probation period ended, i got the results that said i passed the probation and my senior conducted a review about my performance for the first 3 months. They said i have been doing well growing and adapting in the company even though i still have much room to improve but it has been a good start which makes me happy after all of those efforts. From my side, the pair programming experience is not easy at all but an interesting one. But now i am enjoying the TDD and Pair Programming since there are seniors who are so smart and will be willing to help you grow not to mention the effect of knowledge sharing by pair programming is so great. And it’s fun.</p><p>So, I ended up staying to work there until now, i think it has only been more than half a year but i feel like i might be staying there for a few years. And today, i have been pairing with more than 4 people. I enjoyed pairing with each one of them as i learnt many things from my partner while growing myself as a person and a professional programmer.</p><p>I think i have successfully transitioning from “single” to “pair” programming even though i haven’t mastered it yet. Don’t get me wrong because i am still able to do single programming when needed though. The point of pair programming is not reducing your potential when working alone instead it is improving you, maximizing knowledge sharing so you can produce better results when you are programming alone.</p><p>I have learnt many things that i could get while pairing but not when programming alone. Not to mention, I am also the type of people who always believe that <strong>“Two heads are better than one”</strong> and to add it up, i love to discuss things with other people and reaching out the best solution possible depending on the circumstances.</p><p>Well, if you think you have what it takes to try TDD and Pair Programming experience as I do here, if you are someone who are keen to learn and receive critics, and you wanna have the privilege on having chat session with a senior who will be your good listener and even giving you any advice on your problems including your love life, you are welcome to join us at <a href="https://www.kmkonline.co.id/careers">https://www.kmkonline.co.id/careers</a>.</p><p>Whatever your choice is, i wish good luck for us. Cheers !! 🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415b22f66d16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vidio/from-single-to-pair-programming-415b22f66d16">From “single” to “pair” programming</a> was originally published in <a href="https://medium.com/vidio">Karena Kita Vidio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>