<?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 Ferico Samuel on Medium]]></title>
        <description><![CDATA[Stories by Ferico Samuel on Medium]]></description>
        <link>https://medium.com/@ferico55?source=rss-8922102dfc90------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jKcD4H3d8JKwAR5O.</url>
            <title>Stories by Ferico Samuel on Medium</title>
            <link>https://medium.com/@ferico55?source=rss-8922102dfc90------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:51:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ferico55/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[Kanban for Everyone]]></title>
            <link>https://medium.com/tokopedia-engineering/kanban-for-everyone-f02fffe49914?source=rss-8922102dfc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/f02fffe49914</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ferico Samuel]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 09:59:16 GMT</pubDate>
            <atom:updated>2019-12-18T02:40:54.844Z</atom:updated>
            <content:encoded><![CDATA[<h4>If Kanban is powerful enough for a team, why not for a person</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loxqw6or7vLetIGOJr5ncA.jpeg" /></figure><p>If you’re working in an agile team, you must have been introduced to Kanban Board. This board has been around for a very long time. Making the first debut in the Toyota production line in the late ’40s. In an agile environment, this particular board tells pretty much everything happening in the team. Who’s working on what and the status of that task. It also tells the backlog that needs to be done. With this very open information, everybody can contribute even better and spark discussion &amp; suggestions within.</p><p>This is a very common practice, we don’t have to dig deeper into that. We have been using Kanban for a very long time and most of us aware that it is very powerful. Tech companies rely on this particular task management tool very much! I guess they’ll break if this tool is taken out.</p><p>Well, the main point is how if use the same powerful tool for personal use? If the Kanban is powerful enough to spark productivity in a team, how about a smaller scope? We will dive deeper into personal usage in this post. Let’s start by listing why do we need to implement Kanban for our life.</p><h4><strong>Prioritization</strong></h4><p>Prioritization itself is hard! We as workforces in the ever-growing industry tend to have multiple tasks at hand all the time. We juggle a lot of things, keeping track of many tasks. Our brain is very limited hence the number of tasks we are able to keep in mind at a time. This will be much more frustrating when tasks come with a different priority. Some need to be done right now, others need to be done as soon as possible or some specific deadline.</p><p>The problem arises when we are thinking of what we should do next. Most of the time, we jump right into a task that is recently in our minds or concerns us most. We simply forget our past week assignment until it is too urgent that it floats into the surface. We simply lack the capability to objectively measure the importance of each task in our head.</p><p>This gets worse if the task does not has an explicit deadline. We tend to forget about those tasks and move on to one that marked ‘due tomorrow’. This goes with tasks marked as ‘nice to have’ and ‘low priority’. They simply got forgotten. We often keep delaying getting those tasks done until it is not relevant anymore.</p><h4><strong>Human often trapped by emotion</strong></h4><p>We, humans, are very prone to our own emotions. Many things can’t be described by logical thinking or any reasoning. We do a lot of things by following our ‘gut’, coming out straight from our ‘heart’. And this very same reason affected our decision making and prioritization even worse!</p><p>When we see somebody does a thing that is ‘cool’, we often want to copy that very same thing. That kind of how we decide what to do, hurt our prioritization. What actually needs to be done postponed for us to pursue what somebody else did. This is a simple thing that we often do, especially if you’re a competitive person.</p><p>Another more human kind of problem is when we faced with personal issues. We simply can’t focus on the day we are having problems with our spouse, children, or simply unable to get good night sleep. This also applies to our outside work life. Our ‘bad day’ in the office makes us really grumpy at home.</p><h4><strong>We have a lot of things to juggle!</strong></h4><p>Nowadays, task is more collaborative than ever! We often have to wait for output from another team or person in order to continue our work. Even worse, we often forget tasks that need to be done by others. We simply forget those tasks and moved on. This becomes disastrous when the other side put the task on ‘low priority’ and keep postponing the delivery.</p><p>With much pressure from every other side, the need to be productive is very high. It is normal for a worker to feel pressurized from every side. And also very normal for us to have a moment like ‘Crap! I forgot about that’ when somebody asks for an update. It is common to avoid being seen by anybody because we simply have a lot of ‘debts’ to be paid.</p><h3><strong>The solution</strong></h3><p>The Kanban board comes to help! By putting our tasks to a board with appropriate status for each, we can easily spot what needs to be done, we can organize ourselves better. By looking at this board, we can get a glimpse of how hectic we will be and make a better decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*9yP1f8FFDpFmJZWDTL-4eg.png" /><figcaption>My Personal Kanban Board</figcaption></figure><p>My personal board is divided as seen above. I have ‘Today’ column which is filled in early in the morning as part of my daily planning. Throughout the day, I will try to accomplish all I’ve committed to being done today. And every time a new task comes in, I will judge the importance. Is it worth to risk my pre-set target for the day for this task, can it wait for another day? Most of the time, the answer is yes.</p><p>Another column that helpful is the ‘Waiting’ column. Tasks that depend on others goes into that column. This is for me to track every dependency I have and for me to get back to them periodically later on. Some columns are simply there because I am a developer. My developed features need to be tested by QA, therefore, the column ‘Testing’. So does with ‘In Review’ is for PRs that are still waiting to be reviewed by peers.</p><h4><strong>Extra Thought</strong></h4><p>For me, separating your work-life from your ‘real’-life sounds silly. We only have 1 super important undividable life. Some people tend to keep work matter to stay only in the office and so with living matter. This thing simply won’t work since our issues at home will directly affect how we work and vice versa. Take an example of you having a child that is sick and you can’t get enough sleep last night. Wouldn’t you be that grumpy guy along the day? This applies to the other direction too.</p><p>Therefore, I’m proposing that we use the same Kanban board for both work and live tasks. Put everything from doing code, until buying milk into the same board help reduce our cognitive load juggling from one side of life into another.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f02fffe49914" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokopedia-engineering/kanban-for-everyone-f02fffe49914">Kanban for Everyone</a> was originally published in <a href="https://medium.com/tokopedia-engineering">Tokopedia Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Integration Journey of Tokopedia iOS Team]]></title>
            <link>https://medium.com/tokopedia-engineering/continuous-integration-journey-of-tokopedia-ios-team-de23b9009d82?source=rss-8922102dfc90------2</link>
            <guid isPermaLink="false">https://medium.com/p/de23b9009d82</guid>
            <category><![CDATA[tokopedia]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Ferico Samuel]]></dc:creator>
            <pubDate>Mon, 10 Jun 2019 06:50:44 GMT</pubDate>
            <atom:updated>2019-12-18T02:59:32.218Z</atom:updated>
            <content:encoded><![CDATA[<h4>Join our journey implementing continuous integration into our development workflow since the very beginning up to today. We do it incrementally through different seasons.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*79XA9H6lVJS7AcvFifzwsw.jpeg" /></figure><h3>Manual Era</h3><p>Way back then before we even know what CI/CD is, just like living in the stone age, we’re doing all manually. We do compile directly to our testing device, re-download provisioning profile after registering a new device, took a while archiving and upload to iTunes Connect and so on. Sound familiar, eh? I believe most of us would do this, especially in our early stages of building an iOS app.</p><p>Back then, our team size is just a few, so taking those extra time doing those kinds of works doesn’t hurt anybody. Moreover, we are not forced to keep publishing updates; we control our releases.</p><p>All of those steps just okay, up until our team grows, codebase grows, and archive start took forever to finish, let alone slow or unstable connection during upload. Initially, we’re enjoying those extra free time waiting for our machine to complete the process until it took too long and we start bored waiting and waiting and waiting.</p><p>And then the team start to grow, more people joining the team, our product also growing at an incredible rate! Everything turned upside down in an instant. Product owners start pushing us to release more often with even more features packed in. All these manual steps start to be a burden more than ever. And then, we met Fastlane. It feels like a bit ray of daylight shuns upon us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/194/0*IBATFD9M4C39QftX" /></figure><h3>Hosted CI Comes to Rescue</h3><p>Now with Fastlane in hand, we can run our iOS development phases smoother and more consistent! Moreover, we start incorporating CI on the cloud to aid us from wasting precious time. In the beginning, the only workflow automated is for upload release build to iTunes Connect, preparing for submission.</p><p>We are very excited! We can now do another (hopefully) more meaningful work than waiting for the archive to be done. And since that time, we keep improving our hosted CI integration and adding more and more lanes.</p><p>Up until now, we depend on our hosted CI so much. We build a debug mode app and upload them to HockeyApp on every push (now that’s what we call CI) and use the build result for some merging rules on GitHub. We do run DangerCI to enforce our believed code standards and wait for the build to be successful before the PR can be merged.</p><p>We are now more productive than ever! We can share the build result in HockeyApp to our remote co-workers. We have freed a ton of times building and archiving our app 🤘🤘</p><h3>Our Hosted CI ‘Overwhelmed’</h3><p>And the hiring frenzy starts! Our team grows, our throughput increased, more importantly, these great people are very productive! We bombard our hosted CI with jobs until our build has to be put on the queue. Our hosted CI started to billed us for extra build times used per month as we exceed the build time in our subscription! We did upgrade the plan, though. However, we have to tell the team this issue to help us minimize the cost by not pushing to often. The release pipeline is starting to fail on the stripping bitcode phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M4IbNP3kJpsF2IH0" /></figure><p>Besides that, a hosted CI build starts to be too long, almost 50 minutes. We tried many different approaches to solve this too, which I believe will be discussed in another post. Let’s focus on the CI itself; for now, it took forever! We become impatient waiting for a new build. Now we’re back to the age where we have to wait for the build. But, it runs on the cloud instead of our local machine.</p><p>With high hiring target in hand, double the current team size by the end of the year 😱 our hosted CI doesn’t sound like a wise choice any longer.</p><h3>Transition Phase</h3><p>While enduring the pain, we started our ‘side project’ of installing Jenkins. We read many articles written by some tech giants that says that they have a MacMini farm to run their automated build. We want to do the same, we gathered 3 of our still living MacMini and installed Jenkins there.</p><p>The main reason why we moved out to Jenkins is that Jenkins is scalable, we can add as much worker (I love the word ‘slave’ more) as we like. These slaves can be configured from the single control point, and we utilize resources it has as much as we can (see why I think ‘slave’ is more appropriate?). Above all, we only have to invest in the hardware cost, operational yes but summed up much less compared to hosted CI providers.</p><p>We experienced many setups and ended up with a MacMini as Jenkins server and added another iMac and MacPro as a slave. We also installed Grafana on every slave so we can monitor their health, and again the MacMini become the server for Grafana. Now, whenever builds are starting to wait for each other, we can easily add new slave. Now that our Jenkins are stable and can do all the work that was done in hosted CI, we are confident to kissing hosted CI our final goodbye.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A_DjKKC3FMdFUF5-" /><figcaption>Our Grafana Dashboard</figcaption></figure><p>Plus, we add much more capability into our Jenkins, we can now run a full UI Test on our app, which took nearly 5 hours to complete without hesitation every midnight. We also implemented several automated builds like testing release build, automated AppStore release workflow, etc. Above all, our debug build time reduced to about 20 minutes from almost 50 minutes 🤘!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*Ce5YBkkLcv-gSRZ_pyGmJw.png" /></figure><h3>Lesson Learned</h3><p>Finally, I would say that implementing CI as early as possible is a wise move. You won’t feel much impact early on, but you’ll thank your past-self for doing the extra mile early. For those with a limited budget, there is a viable option, try Bitrise (not sponsored). They got a free plan that will enable you to free up your local machine from doing that build. More importantly, drive yourself for doing what it takes for a result. Get started early and adapt accordingly. Make it happen and make it better 🤘🤘!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de23b9009d82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokopedia-engineering/continuous-integration-journey-of-tokopedia-ios-team-de23b9009d82">Continuous Integration Journey of Tokopedia iOS Team</a> was originally published in <a href="https://medium.com/tokopedia-engineering">Tokopedia Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>