<?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 Nia on Medium]]></title>
        <description><![CDATA[Stories by Nia on Medium]]></description>
        <link>https://medium.com/@niamutiara?source=rss-2c9eab358b1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DWrGDuRKZjy0m5Nv.jpeg</url>
            <title>Stories by Nia on Medium</title>
            <link>https://medium.com/@niamutiara?source=rss-2c9eab358b1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:32:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@niamutiara/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[5 Tips to Get Stronger Despite Having a 9-5 Job]]></title>
            <link>https://medium.com/@niamutiara/5-tips-to-get-stronger-despite-having-a-9-5-job-84aeb5fdae4f?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/84aeb5fdae4f</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Wed, 30 Jul 2014 09:41:32 GMT</pubDate>
            <atom:updated>2014-07-30T10:49:06.099Z</atom:updated>
            <content:encoded><![CDATA[<p>5 Tips to Get Stronger Despite Having a 9-5 Job</p><p>Since the advancement of technology, we are so immersed in our work. We forget about our body…until one day it complains.</p><p><strong><em>Bad joints, bad back, neck pain, headache, etc.</em></strong></p><p>These happens just because of staying in the same posture and body adapting to the posture. Sports can help, but again it can restrain our body too, especially if posture is bad.</p><p>I’m no expert on this posture thing, but I got plenty problems with my body, just like everybody else.</p><p>After experimenting, I find these are ways to help ease problems due to bad postures.</p><ol><li><strong>Sleeping on the floor</strong><em> </em>or Japanese Futon helps supporting good back posture. You can feel this especially if you have problems with your lower back, upper back or knees. This can be painful on your lower back at first, but it is worth to get the pain because you’ll get stronger afterwards!</li><li><strong>Massaging the body using </strong><a href="http://www.tigertailusa.com/"><strong>foam roller</strong></a><em> </em>is useful for releasing tender muscles. The roller works well for legs and arms. With the rollers, you can save money from going to massage therapists (and getting the wrong massage spot!). <a href="http://www.do-it-yourself-joint-pain-relief.com/">You can even learn lots of massage techniques for free here</a>.</li><li><strong>Reducing usage of phone (and other electronic devices)</strong><em> </em>prevents us from adding more strain to the neck and back.</li><li><strong>Moving around and not staying in the same position</strong><em> </em>tells the body not to remember just one posture for the day. Sit on different chairs (a <a href="https://en.wikipedia.org/wiki/Exercise_ball">gym ball</a>!), take stairs, jump, and walk around! It sounds counterintuitive, but a little exercise actually boost our focus.</li><li>If you have enough budget, <strong>go to gym and get a personal trainer to help you train your muscles</strong><em>. </em>As we age, our joints get weaker and our energy gets drained faster. Training muscles compensates the weaker body to stay young and fit.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84aeb5fdae4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Haze from Indonesia]]></title>
            <link>https://medium.com/i-m-h-o/haze-from-indonesia-182994fff11b?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/182994fff11b</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Mon, 17 Jun 2013 09:48:09 GMT</pubDate>
            <atom:updated>2013-06-18T08:25:07.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>I occasionally see haze in Singapore, not when I am back home. Apparently, the haze problem has been there for ages.</h4><p>The haze problem in Indonesia could usually be caused by outdated-yet-very-cost-saving farming practice: <em>slash and burn</em>. There are actually preventive actions already executed, like <a href="http://www.berita2.com/lingkungan/masalah-lingkungan/1345-denda-pembakar-hutan-dianggap-untungkan-pengusaha.html">fines</a> and <a href="http://en.wikipedia.org/wiki/ASEAN_Agreement_on_Transboundary_Haze_Pollution">agreements</a>. As of now, more effort seems to be needed from the multiple parties to solve the haze problem.</p><p>One way to prevent this is to update the farmers with safer methods of farming. Unfortunately, nobody can be very sure if they want to be updated. Nobody can be sure if government or business owners want to help updating the farmers.</p><p>Wait, before I continue going on circle of negativity…<strong>what is the root cause? Who are the people to blame?</strong></p><p><a href="http://blogs.wsj.com/searealtime/2012/06/20/southeast-asian-haze-whos-to-blame/">This article can explain</a>, and I have my own opinion too.</p><p>A cyclic causality has been formed by multiple parties such that this problem is very hard to conquer. The farmers need to be updated, but the business owner/government doesn’t seem to help. The government needs to facilitate and regulate farming properly, but there are of course money-related shortcuts available to bypass lots of things. I wouldn’t know what business owners are thinking other than profits.</p><p>I believe there are multiple ways to solve this problem, but again, it is very very hard to solve.</p><h4>Farmers</h4><p>Since haze is quite hazardous for health, I question why farmers want to work as farmers. They actually breathe in the more pollutions than neighbouring countries.</p><p>If some of the farmers could be entrepreneurs, they would think a bit more… There are other job options that don’t require them to sacrifice their own health, and the jobs might pay better. Some examples are restaurant owners, engineers, bloggers and sailors. But…nobody can be sure if the farmers want career change.</p><h4>The Government</h4><p>I am not too sure what it is doing. Tell me more about it. I heard the government applies some rules related to forest burning thing. And? Who knows.</p><h4>Business Owners</h4><p>Indeed, slash and burn is one of the cheapest methods to build more areas for farming. Do the business owners pay enough for the farmers health insurance? Do they aware of long term effect of this outdated practice? As far as I know, these people care a lot about getting profit and cutting cost.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=182994fff11b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/haze-from-indonesia-182994fff11b">Haze from Indonesia</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RedDotRubyConf 2013]]></title>
            <link>https://medium.com/@niamutiara/reddotrubyconf-2013-d7fb15e06fb7?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7fb15e06fb7</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Sun, 16 Jun 2013 16:14:11 GMT</pubDate>
            <atom:updated>2013-06-16T16:24:31.908Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s one of the best events I’ve ever attended.</h4><p>I am not sure what would be a phrase to explain how cool this event was. I sense that <a href="http://www.reddotrubyconf.com/">RDRC 2013</a> organizers spent huge effort to execute detailed plans for the event.</p><p>Below are a few points that I found extremely satisfying.</p><ol><li><strong>Impressive talks<br><em>The speakers</em></strong> were great, awesome, and inspiring. Most of them came up with hilarious jokes or very interactive presentations. The topics had healthy range of hardcore Ruby to non-coding-related stuff. <em>One thing that was pretty cool: Lots of people clapped after specs passing.</em></li><li><strong>Well-planned sequence of talks</strong><br><strong><em>Sequence of talks were very well-planned.</em></strong> The sequence had a pattern which I can encounter in another kind of event. I always find the pattern effective for keeping audience focused; apparently, it’s also true for conferences.<br><strong><em>Also, the talks were very on time. </em></strong>Although the overall event on day 2 was a little bit late by 5-10 minutes (in the middle of the day), it was still on time. 5-10 minute drag is neglectable for events.</li><li><strong>Job board!<br></strong>That was pretty cool and useful, knowing how things are on every Ruby meetup :)</li><li><strong>Diverse speakers and attendees</strong><br>Very similar to the previous RDRCs, people from various continents (America, Europe, Asia, Australia) flew to Singapore for this event.</li><li><strong>WiFi<br></strong>It worked for a while, and was useful for looking up open source projects the speakers talked about. The live tweets were fun too.</li><li><strong>Lots of swag<br></strong>I’m always satisfied with the swag since the first RDRC.</li><li><strong>Food and beverage<br></strong>The food was ok, though there were less choices of drinks. I wouldn’t care so much about those because the talks were really good! Also, despite having lots of attendees, the venue was quite clean.</li><li><strong>Good location<br></strong>It was relatively reachable, although it’s not near the city.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7fb15e06fb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Square Name Card]]></title>
            <link>https://medium.com/@niamutiara/my-first-square-name-card-6a4af077958e?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a4af077958e</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Fri, 17 May 2013 07:25:48 GMT</pubDate>
            <atom:updated>2013-05-17T07:26:26.160Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing for printing is hard.</h4><p>Nothing is ever easy for me, I guess. Most of the time, I learn the hard way. That includes this one. This is my first attempt to make name card look slightly different at the first glance.</p><p>I am actually pretty satisfied with my first try designing a square name card and paying somebody else to print it out. Maybe I can pay more to get better result, but I think there are two important things I have to understand below (right after collecting my name cards!)</p><h3>Cutting Paper is not Equal to Cropping Pictures</h3><p>Though name card paper is cut with machine, proportion can’t be really exactly square. This is because putting printed cards to the name card cutting machine is manual effort.</p><p>Cropping is aided by a computer, so it is easy to make exact measurements. We can give constrain for sizes and voila!</p><h3>Contents are Most Likely Pinned to the Left Side on Paper</h3><p>I hoped print will be exactly symmetrical. And… that is totally a wrong thing to hope for.</p><p>Name card content is most likely pinned to the left side or right side. It depends on how the person print the name card. When printing and cutting paper, there is no such thing as automatic snapping to the center like in Sketch or Photoshop.</p><p>I should never ever play with symmetry on paper. I should have play with edges and paper textures instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a4af077958e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exact Estimation]]></title>
            <link>https://medium.com/@niamutiara/exact-estimation-2412bc056f8c?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2412bc056f8c</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Fri, 17 May 2013 06:47:33 GMT</pubDate>
            <atom:updated>2013-05-17T06:47:33.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8h20jFbUoiuClCfd.jpeg" /></figure><h4>Performing good software estimation is difficult.</h4><p>Before software engineers start coding to develop a feature, estimation is usually conducted to measure when the feature will be done. There should always be one finish line where the feature is done. Yet, estimating is so hard for some people that projects become delayed…possibly forever.</p><p>Don’t get me wrong. I am bad at estimating. I admit the fact that I often miss out requirement details upfront when estimating. I do over-estimate or under-estimate certain features. I rarely get estimations exact. I am trying to get better at estimating. A few ways to get better at it are to read someone else’s code, practice coding a lot, and try measuring my own speed.</p><p>On the other hand, there are people who say yes to all features and are optimistic that everything can be done without fleshing out requirement details. Or, there are people say no to all features because they take all their time to flesh out requirement details for a couple of months. I could be one of them too, at times. Although, I have low boredom tolerance such that I will go nuts if I am one of them for enough time.</p><p>Let’s set things straight. Here are few things that can help estimation.</p><h3>Knowing Common Happy and Sad Cases</h3><p>Common happy and sad cases are usually simple. These days, great software handles sad cases (errors!) really nicely. Knowing these typical cases need reading someone else’s code or observing someone else’s software.</p><p>Let’s take one simple feature as an example. Say, login. <strong><em>Start with happy case</em></strong>: User is successfully logged in. <strong><em>The sad case</em></strong> could be due to the user’s fault: User enters invalid field (email, password, etc.). <strong><em>Another sad case</em></strong> could also be due to the server’s fault: There is internal server error, or the server is unreachable because of gateway problem.</p><p>Take another not-as-simple feature like registering user through Twitter account. Again, do the same thing. <strong><em>Happy case</em></strong>: User account is not created yet, user is already signed in via Twitter and user is successfully registered. <strong><em>Sad case</em></strong>: User account is already created, user is not logged in via Twitter yet, internal server error occurs, or server is unreachable because of gateway problem.</p><p><strong>Simple?</strong></p><p>Maybe. This is not quite like defining clear cut requirements for every single features up front for a couple of months to years. If that happens in a project until there is no feature being shipped, it becomes waterfall methodology. Possibly, such project is hard to get anywhere in fast pace. It is going to be trapped in confusion of feature and idea bloat.</p><p>Remember, happy and sad cases are simple to describe. Take one simple feature, then define simple happy and sad cases. Never take too long (months to years) and delay shipping all other features to decide on that.</p><h3>Fix Important Bugs, Make a Core Feature Work Really Well</h3><p>If you do the previous stage above properly, you’ll be dealing with really small things or edge cases on this stage. Perhaps the login page looks jittery. Maybe there are defects seen by managers, but you developers don’t see that as defects. Things are right on schedule, but lots of small things need attention.</p><p><strong>Start prioritizing those small things.</strong></p><p>There should be things that are important, and will make the product stands apart from competitors. There are obvious things that have to be fixed and are critical. Those are small things that need bigger attention.</p><p>Since time is limited, there will be bugs not being addressed. That is alright, as long as the core feature work really well.</p><h3>Minimize Features, Throw Away Clutters</h3><p>Revisit the features again. It is fun to work on projects or start-ups. It is really exciting to have ideas and grow them in the project backlog.</p><p>Let’s have a sanity check, what problems are actually being solved? Do they exist? Do lots of people need feature X? Do lots of people use feature Y? To answer those questions, guessing by market research, intuition or gut feeling is needed before implementing feature. In addition, analytics complements the initial guess right after the feature is implemented.</p><p>To me, more features means more clutter and more unneeded things. When it comes to programming, more clutter can lead to more misestimation. When it comes to user experience, more feature means they have to do more small decision making when using the product. Too much small decision making can lead to <a href="http://en.wikipedia.org/wiki/The_Paradox_of_Choice:_Why_More_Is_Less">paradox of choice</a>.</p><p><strong>You can help software engineers and users by saying NO to some features.</strong></p><p>It is hard to make good software estimation. Yet, I find people can miss the above three aspects. It doesn’t matter what their degrees or specialty are; people just disregard these three points.</p><p>I do forget some of those things to, at times. I am trying to remember.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2412bc056f8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Fonts Pairing]]></title>
            <link>https://medium.com/@niamutiara/google-fonts-pairing-51345771b870?source=rss-2c9eab358b1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/51345771b870</guid>
            <dc:creator><![CDATA[Nia]]></dc:creator>
            <pubDate>Thu, 16 May 2013 02:16:42 GMT</pubDate>
            <atom:updated>2013-05-16T02:16:42.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*w5JcovSF7Z3tzu9c.png" /></figure><h4>I was stuck trying to understand font pairing. Apparently, Google Fonts has lots of examples!</h4><p>I am learning a bit about web design, particularly typography. A few topics that I think important are vertical rhythms and font pairing.</p><p>Recently, I was happy with trying out vertical rhythms on <a href="http://nyan.catcyb.org/">my blog</a>. At this point, I still can’t use exact measurements given by vertical rhythm calculators yet, but I think I’ll get to that later. I’d let my eyes decide without calculating for now.</p><p>While vertical rhythm is essential for building pleasantly readable sites, good font pairing can make sites stand out from other. Everyone can use custom fonts from TypeKit, FontSquirrel, Google Fonts, and other similar services. Everyone can use different fonts in one page too. However, it is easier to make font clashing than deciding on good fonts combination. At least, for me, I find it hard to pick custom fonts’ pairing.</p><h3>Enter Google Fonts</h3><p>I didn’t like Google Fonts. I was totally lost because Google Fonts has lots of choices. Now, not anymore. As a starting point, there are <a href="http://sachagreif.com/google-webfonts-that-dont-suck/">suggestions on which Google Fonts look alright</a>. Another starting point that I like is to pick Google Fonts looking similar to operating system fonts (Palatino or Helvetica).</p><p>If I want a serif font for my site body, what should be the headers’ font? Google Fonts can help you with that. There is a pairing tab that can take away your confusion of choosing a matching font. My problem is solved, and I am happy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51345771b870" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>