<?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 Ajeng Sugiarti on Medium]]></title>
        <description><![CDATA[Stories by Ajeng Sugiarti on Medium]]></description>
        <link>https://medium.com/@ajengs?source=rss-a1dfe583d1a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_x2Yo3RzsnHnqLXrxUvsvg.png</url>
            <title>Stories by Ajeng Sugiarti on Medium</title>
            <link>https://medium.com/@ajengs?source=rss-a1dfe583d1a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:26:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajengs/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[Retro Session on What You’ve Learned]]></title>
            <link>https://medium.com/@ajengs/retro-session-on-what-youve-learned-35b2b3e62ab3?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/35b2b3e62ab3</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Mon, 12 Mar 2018 20:43:38 GMT</pubDate>
            <atom:updated>2018-03-12T20:43:38.138Z</atom:updated>
            <content:encoded><![CDATA[<p>How much time do you spend on learning something? Was it time well-spent?</p><p>Sometimes people only need a short amount of time to learn new things, other time, other people might need longer time. It depends on your method of learning and perhaps also on what you’re learning. But on a more important note, the thing that we should give attention to is how effective is our learning process? And for that, it’s always a good thing to spend a bit of our time to have some retrospective session.</p><p><strong>What have you learned? What does that change you? </strong>As in, you learn in order to grow, and you’re growing by changing yourself. And what do you want to do next with that newfound knowledge, also what do you want to learn next?</p><p>The first and second questions are so closely related, because when what you’ve learned doesn’t change you, then most likely you’re doing it wrong. First feedback.</p><p>So either you’re learning the wrong things, or you’re using the wrong way. Let’s take example of how I learned something really new the last week.</p><p>Initially, I had this aversion when dealing with everything related to software operation (the Ops in DevOps). So learning DevOps is like entering a whole new different dimension when a lot of things are alien and strange to me. But forcing myself to do exactly that, stepping outside of my comfort zone, really helped me to change immensely.</p><p>When before I just had this notion of,</p><blockquote>“I’ve completed my work on developing something, now please do your magic with your powerful server machines. And if some alien messages come out, please talk to them in your encrypted languages, because I have no idea what they’re saying.”</blockquote><p>Now, well, I still have very little clue on what the messages mean, <em>(hey, it’s only been a week, and we have Google for that actually)</em>. But at least that week changed my whole perspective of holding myself back to understand and find out what the hell is going on with the machine. And it’s very powerful.</p><p>When you feel the impact of your learning process, then it means you’re moving in the right direction. Now comes the question whether the result of your learning or your level of understanding, are not as you expected. That only means, either you can try much much harder or you can try different methods of learning. As you’re growing and trying new things, you will also know what works for you.</p><p><strong>Next question for the retro session is, what to do next?</strong></p><p>Back to the example, like I said earlier, learning DevOps is like entering a whole new different dimension. And imagine having that new dimension to explore and play around with. So I’ve <em>“learned Linux the hard way”</em>; I’ve learned why we need CI; I’ve learned that deploying your app manually is a pain in the .. nvm; then I learned how we can actually bring the pain forward and minimize the effort.</p><p>But does that enough? Of course not. Because I learned all those things, I know that there are so many things out there that I don’t know, but I should use and explore so it can help me in improving my skill and productivity.</p><p>Like what is actually happening when we invoke a command and get a server running; how are some nodes connected to each other; how do we monitor each process and performance and understand what’s going on there; what other powerful things that a machine can do and what other powerful things we can make them do. And basically just how things work, inside.</p><p>So ask yourself, do the things you learned inspire you to move forward and learn more? Set a goal for yourself on what are you planning to learn next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35b2b3e62ab3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Communication Tips Programmer Should Practice]]></title>
            <link>https://medium.com/@ajengs/8-communication-tips-programmer-should-practice-6cf9550e732f?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cf9550e732f</guid>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Sun, 11 Mar 2018 06:39:23 GMT</pubDate>
            <atom:updated>2018-03-11T06:39:23.848Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>A good idea is an orphan without effective communication. — The Pragmatic Programmer</blockquote><p>Developers do not only communicate with machine. But we also have to understand user’s requirement, work and collaborate with team mates, document and explain our intent, etc. We spend a great deal of our professional life communicating with other people. This is one of the most important skills developers (and all other people) should have.</p><p>Here I compiled a list of some tips from <em>The Pragmatic Programmer</em> to improve our communication skill.</p><ol><li>Know what you want to say. It’s better to plan out what you want to say and write an outline of it. That way, it can become more structured. And if you feel the outline does not express your point well, refine it until it does.</li><li>Know your audience. Form a strong mental picture of your audience. Find out what they’re looking for in this conversation, and express them in a way that closest to their domain of knowledge.</li><li>Choose your moment. Be sensitive about other people’s situation. A simple question “is this a good time to talk about…?” won’t hurt.</li><li>Choose a style. Related to knowing your audience, choose the style that will suit them. Does your audience prefer short, straight to the point explanation? Or do they need long conversation with small talk here and there to get comfortable?</li><li>Make it look good. Just because your idea is good, does not mean you can express it in a sloppy way. Choose correct words, pay attention to punctuation, grammar, and spelling.</li><li>Involve your audience. Imagine having created long documentation and turns out the user does not conform to some points of it, and you have to redo the work again. That’s why it is important to get feedback and make sure your idea is aligned with your peers/ user.</li><li>Be a listener. Even when the time when you are the one deliver the information, if you don’t want to listen to your audience, they won’t listen to you! You can make them involved and listen to them by asking them questions, turning meeting into dialog, etc.</li><li>Get back to people. Always answer and reply queries for you. Whether it emails, voice mails, texts, etc. Sometimes it’s easy to forget, but make sure to get back at them as soon as you see or remember the message.</li></ol><p>These 8 tips look like some simple no-brainer ones. But in reality it’s hard to follow them. Have them on your post it notes so you can practice it daily until it becomes natural and instinctive to you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cf9550e732f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide for A New Hired Programmer]]></title>
            <link>https://medium.com/@ajengs/guide-for-a-new-hired-programmer-b786a1d93e79?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b786a1d93e79</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Sat, 10 Mar 2018 06:48:20 GMT</pubDate>
            <atom:updated>2018-03-10T06:48:20.340Z</atom:updated>
            <content:encoded><![CDATA[<p>When you join a team, especially if you are fresh graduate, you might face some confusion and uncertainty. The amount of questions popping up in your head is overwhelming and you don’t know where to start. If you experience this, maybe these 4 simple tips could help you get started.</p><p><strong>Get to know your product. </strong>If you are placed in a particular product team, understand and simulate that product end-to-end. You don’t have to know the inside working of it yet, but at least you understand the flow of the business.</p><p><strong>Read documentation. </strong>Good teams know the importance of documentation and knowledge management. Read through them and see if you can understand the materials. Ask for the thorough documentation. And if your team does not have one, then there is no choice but to go to next tips.</p><p><strong>Talk to product manager and product designer. </strong>You might want to talk to them separately. They tend to give you different insights and point of view, so it’s better to learn one at a time so it won’t be confusing. And also make sure to talk to other stakeholder, user, or even customer to get more insights.</p><p><strong>Study the business dashboard. </strong>If your company/ team is open about their data (and they should, because you’re their employee), you could open and read their business intelligence data. That way you could get more insight in business point of view. You could also base your questions to other stakeholder on this. And who knows, maybe you could get fresh ideas out of it.</p><p>These steps should help you get started and know what and where to look for when you first join a team. Make sure to always be assertive and don’t hesitate to ask questions to your seniors! Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b786a1d93e79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Improve Your Code Orthogonality]]></title>
            <link>https://medium.com/@ajengs/how-to-improve-your-code-orthogonality-71344f29afab?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/71344f29afab</guid>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Wed, 07 Mar 2018 20:40:20 GMT</pubDate>
            <atom:updated>2018-03-07T20:40:20.153Z</atom:updated>
            <content:encoded><![CDATA[<p>Orthogonality in computing refers to independence and decoupling. Two or more things are orthogonal if changes in one do not affect any of the others. A well designed system components should be orthogonal to each other. A model should be orthogonal with the view, one should have to be able to change database without affecting the interface, etc.</p><p>Having your code to be orthogonal could mean increasing in productivity. Every change could focus only to a small chunk of code, making it faster to develop and test. It could also reduce the risks inherent in any development. If a part of the modules is bad, the risk of symptoms to be spread is small, because each code is isolated. It also make it easier to test, making sure bug rate is low.</p><p><strong>Keep your code decoupled. </strong>When writing a module, don’t reveal unnecessary information to the other. And don’t rely on other module implementations. Apply the rule of “<em>Tell, Don’t Ask!</em>” Tell what you need, don’t ask for the tools to implement it.</p><p><strong>Avoid global data. </strong>Global variable makes infinite state machine. The amount of state change you could get from a global data is uncontrollable. When one access a global data, it ties itself to other components that share that data. Thus, decoupling intensifies.</p><p><strong>Avoid similar functions</strong>. If you see some functions that look similar, maybe it’s time to implement a certain design pattern to handle it. Don’t duplicate concept.</p><p>Make sure to always be critical of your code. Always aim for your code to work first, but also keep working to improve its structure and orthogonality.</p><blockquote>“Just because something works, doesn’t mean it can’t be improved.” — Shuri (Black Panther, 2018)</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71344f29afab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Strong Foundation for Your Company]]></title>
            <link>https://medium.com/@ajengs/building-strong-foundation-for-your-company-54ce4b1135bc?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/54ce4b1135bc</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 20:01:15 GMT</pubDate>
            <atom:updated>2018-03-06T20:01:15.977Z</atom:updated>
            <content:encoded><![CDATA[<p>When you see the company page of <a href="https://www.google.com/about/our-company/">Google</a>, you’ll know why they can succeed to this point. They have this quote printed as the very first thing people could notice.</p><blockquote>Organize the world’s information and make it universally accessible and useful.</blockquote><p>That’s their mission.</p><p>So what is mission and why is this important? A <strong>mission statement</strong> is a concise explanation of the organization’s reason for existence. It describes the organization’s purpose and its overall intention.<a href="https://www.shrm.org/resourcesandtools/tools-and-samples/hr-qa/pages/isthereadifferencebetweenacompany%E2%80%99smission,visionandvaluestatements.aspx">[1]</a> Google has this same exact purpose over the years. Constant. Everything that Google did and made are for the sake of bringing them closer to that goal.</p><p>For continuous, ongoing purpose and focus, it is generally imposed that organizations do not change their mission statement. Changing the statement brings lots of baggage with it. Not only it will disrupt the focus of the company and the direction it’s moving, but also break the dynamic of the organization the if not executed properly.</p><p>The next thing we can note on Google’s company page is the link that introduces us to their <a href="https://careers.google.com/#_ga=2.24900979.899373550.1520362351-1588174733.1520362351"><strong>culture</strong></a>. Google is a tech company. And they give their engineers freedom, responsibilities, and ownership to the products. One of the <a href="https://archive.nytimes.com/www.nytimes.com/imagepages/2011/03/11/business/20110313_sbn_GOOGLE-HIRES-graphic.html?ref=business">good behaviors</a> that they practice is “<em>do not micromanage</em>”.</p><p>Despite its massive size, all employees have the opportunity to lead. Thanks to its flat organizational structure, Google could encourage all employees to speak up and vocalize their points of view. That and together with their <a href="https://www.businessinsider.in/Googles-HR-boss-explains-the-companys-4-rules-for-hiring-the-best-employees/articleshow/51048044.cms">hiring policy</a>, ensure that innovation can be achieved faster because ideas are pouring from every direction. Not just from the top level management.</p><blockquote>It doesn’t make sense to hire smart people and then tell them what to to, we hire smart people so they can tell us what to do. — Steve Jobs</blockquote><p>And then of course, we could also notice their <a href="https://www.google.com/about/our-commitments/"><strong>commitments</strong></a>. Just like vision, they create mental image of the future state that the company wishes to achieve. A <strong>vision</strong> statement should challenge and inspire employees. What achievements do you want for your company? What should the company commits to do to achieve the goal? Because Google has this strong and constant mission, all of their commitments are moving towards that direction: organize information, make it accessible and useful.</p><p>Those 3 points — mission, culture, and vision, can form strong foundation for any company to succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54ce4b1135bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plan Better, Collaborate Smoother]]></title>
            <link>https://medium.com/@ajengs/plan-better-collaborate-smoother-697a0bc66b0?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/697a0bc66b0</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Mon, 05 Mar 2018 18:35:17 GMT</pubDate>
            <atom:updated>2018-03-05T18:35:17.820Z</atom:updated>
            <content:encoded><![CDATA[<p>When we’re facing a new set of problems, we tend to panic and stuck in this <a href="https://www.urbandictionary.com/define.php?term=tunnel%20minded">tunnel-like</a> mind. This is especially hard when you work in a team. Because not only you have to come up with some solution to the problem, you also have to make sure <em>every single</em> member of the team understand the problems and move into the right direction.</p><p>Don’t just blindly attack the problem alone. Here are the simple steps to follow to help us get started on a working solution.</p><ul><li>Understand problem and solution. Make sure that everyone on team understands the problem. What should we do/ make? Why should we make it? What are we trying to solve? And if there’s any hypothesis on a solution, deliver it to the whole team. State the options available. This way everyone can be on the same page and move toward the same direction.</li><li>Sharing knowledge. Now that everyone is on the same page, one member might be better at something than the other. Start collaborating on sharing the knowledge needed. What do we know now? What do we have? So time won’t be wasted on searching for knowledge that is already within the team.</li><li>Better planning. This sounds generic, but true nevertheless. When everyone has understood the context, we can start dividing the tasks. Who responsible for what? How’s the matrix for each task? Decide on milestones. Time box on each task. Short iteration is generally better. So we can get feedback soon and improve faster.</li><li>Research. We have the problems, we have the hypothesis, now we have to validate it and make it happen. What if we don’t know how to do it? <em>Google is your friend. </em>No kidding. Everything is on the internet right now. You only have to find a specific keywords for each problem. For something technical, googling things should probably help you get the job done. And even for non-technical or some absolutely new stuff, you should at least get to know about how to start working on it.</li></ul><p>Now make it work! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=697a0bc66b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Teach When You Need to Learn]]></title>
            <link>https://medium.com/@ajengs/teach-when-you-need-to-learn-1fa338181903?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fa338181903</guid>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 19:29:21 GMT</pubDate>
            <atom:updated>2018-02-27T19:34:50.005Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most effective ways to learn is by teaching what we’ve learned to others. By teaching what we’ve understood, we can re-organize our knowledge, rearranging them so it can improve our understanding further. And most of the times, when we explain what we know in words, we can find knots and gaps in our own thinking. We can even encounter some “<em>aha!”</em> moment there. That also helps to store the knowledge in our memory better.</p><p>For people who are not yet confident teaching in front of people, or doesn’t have anyone to teach, stay calm. There are several ways of doing “teach what you learn”.</p><ul><li>Write. It could be a blog, journal, summary, anything. Write what you’ve understood, and explain it in your own words. Explain so that someone who might read it (future you, perhaps) could understand it easily.</li><li>Record. If you’re not sure you can explain it to other people, try to record yourself explaining it and then listen to it. Does it make sense? Try to explain with your own words as well. It could also help when you encounter something difficult to understand. Rephrase it over and over again until it makes sense to you.</li><li>Make a video. Some might say it’s overkill. But this way you can kill more birds with one stone (don’t kill birds for fun, please). You might not have anyone to teach now, but the video might be able to help other people who’re starting to learn as well. Plus you also get the benefit you could get from writing and recording.</li><li>Discuss. When you have peers learning together with you, you’re in luck. Discuss with them and exchange your notes. Explain what you’ve understood, and listen to them as well. The amazing thing is you might fill each other’s gaps and expand your understanding.</li><li>And of course, teach other people directly. You can help other that’s just starting to learn to get to your level. They can be your juniors, your friends who have the same interest as you, or you can find communities and meet new people who need help.</li></ul><blockquote>“While we teach, we learn,” — <a href="https://en.wikipedia.org/wiki/Docendo_discimus">Seneca the Younger</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fa338181903" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do Not Depend on Your Code Coverage]]></title>
            <link>https://medium.com/@ajengs/do-not-depend-on-your-code-coverage-84b77d41b039?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/84b77d41b039</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[code-coverage]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Sun, 25 Feb 2018 19:49:00 GMT</pubDate>
            <atom:updated>2018-02-25T20:06:24.031Z</atom:updated>
            <content:encoded><![CDATA[<p>Code Coverage testing is determining how much code is being tested <a href="http://atlas-softquality.com/faqanswer3.html">[1]</a>. 100% coverage doesn’t mean your code is all test-covered, though. We have to know is it C0, C1, or C2?</p><ul><li>C0 <strong>Statement coverage — </strong>Has each line of the source code been executed?</li><li>C1 <strong>Branch coverage — </strong>Has each control structure (such as an if statement) evaluated both to true and false?</li><li>C2 <strong>Condition coverage — </strong>Has each boolean sub-expression evaluated both to true and false (this does not necessarily imply decision coverage)?</li></ul><p>But take note that high code coverage does not necessarily mean your test is good.</p><blockquote>Test coverage is a useful tool for finding untested parts of a codebase. Test coverage is of little use as a numeric statement of how good your tests are. — <a href="https://martinfowler.com/bliki/TestCoverage.html">Martin Fowler</a></blockquote><p>When we focus too much on the achieving code coverage, things can go wrong. For example, some people might force hard coded value just to pass a test. Or worse, remove assertion entirely. More importantly, high code coverage does not mean your code is bug-free either. So we should not depend solely on the code coverage to be satisfied with our code.</p><p>Sure, code coverage is a nice tool when we practice TDD. Low code coverage gives us a sign that we’re not testing enough code. But be careful to not depend on the thought that high code coverage means high quality code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84b77d41b039" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When To Use Exceptions]]></title>
            <link>https://medium.com/@ajengs/when-to-use-exceptions-69fbd0725f43?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/69fbd0725f43</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Wed, 21 Feb 2018 04:31:00 GMT</pubDate>
            <atom:updated>2018-02-21T17:45:27.360Z</atom:updated>
            <content:encoded><![CDATA[<p>Most widely-used programming languages support exceptions. It makes the flow of control clear, sometimes.</p><p>Consider this:</p><pre>retcode = OK;<br>if(socket.read(name) != OK) {<br>  retcode = BAD_READ;<br>} else {<br> processName(name);<br> if(socket.read(address) != OK) {<br>   retcode = BAD_READ;<br> } else {<br>   processAddress(address);<br>   if(socket.read(telNo) != OK) {<br>     retcode = BAD_READ;<br>   } else {<br>     ...<br>   }<br> }<br>}<br>return retcode;</pre><p>And this:</p><pre>retcode = OK;<br>try{<br>  socket.read(name);<br>  processName(name);<br>  socket.read(address);<br>  processAddress(address);<br>  socket.read(telNo);<br>  ...<br>} catch {<br>   retcode = BAD_READ;<br>   Logger.log(&quot;Error reading individual: &quot; + e.getMessage());<br>}<br>return retcode;</pre><p><em>Codes are taken from The Pragmatic Programmer (2000)</em></p><p>I said sometimes, not always.</p><p>We should be careful on when to use it. Use exceptions only when in <em>exceptional</em> situations. It’s because programs with exceptions suffer from all the readability and maintainability problems of classic spaghetti code. Also, these programs break encapsulation: routines and their callers are more tightly coupled via exception handling (The Pragmatic Programmer: 2000).</p><p>But what is exceptional situations? How do we decide if one is exceptional enough or not?</p><blockquote>Exceptional cases are cases not covered in business rule. We don’t know what to do about it.</blockquote><p>For example, you don’t know what to do when your database driver is not working. Use exception there. But if the business requirement says that when the user gives string while they expect integer, display some messages. It means it can be handled by a simple error handler.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69fbd0725f43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beautiful Code]]></title>
            <link>https://medium.com/@ajengs/beautiful-code-c76544f0a50b?source=rss-a1dfe583d1a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c76544f0a50b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[clean-code]]></category>
            <dc:creator><![CDATA[Ajeng Sugiarti]]></dc:creator>
            <pubDate>Sun, 18 Feb 2018 18:13:32 GMT</pubDate>
            <atom:updated>2018-02-18T18:13:32.605Z</atom:updated>
            <content:encoded><![CDATA[<p>Programming is art. Just like any other art, it can be defined as beautiful. We’ve heard of “Clean Code”, but what is “Beautiful Code”?</p><p><strong>Liberating. </strong>Beautiful code not only makes you happy and content by looking at it, but also emits freedom. It liberates you to modify, scale, add functionality, and experiment in any way without fearing to break it.</p><p><strong>Increases your choices.</strong> Bad code reduces your choices. The options to optimize it would be limited, if any. Beautiful one, on the other hand, gives you a number of choices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c76544f0a50b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>