<?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 Ryan Gatchalian on Medium]]></title>
        <description><![CDATA[Stories by Ryan Gatchalian on Medium]]></description>
        <link>https://medium.com/@ryangatchalian?source=rss-25f5f15366cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*5ECX_T3vqTuuOVut.jpg</url>
            <title>Stories by Ryan Gatchalian on Medium</title>
            <link>https://medium.com/@ryangatchalian?source=rss-25f5f15366cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:40:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryangatchalian/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[Mathematical optimizations and insights for problem-solving]]></title>
            <link>https://medium.com/@ryangatchalian/mathematical-optimizations-and-insights-for-problem-solving-8e57c2094509?source=rss-25f5f15366cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e57c2094509</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[mathematical-optimization]]></category>
            <category><![CDATA[mathematics]]></category>
            <dc:creator><![CDATA[Ryan Gatchalian]]></dc:creator>
            <pubDate>Tue, 22 Mar 2022 13:59:05 GMT</pubDate>
            <atom:updated>2023-01-27T08:14:08.008Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*JZa3TozpHqNSpydCPtfBqw.jpeg" /><figcaption>Albert Einstein with his licking tongue</figcaption></figure><blockquote>“Sometimes, the obvious way of doing things is not always the best way.” -<a href="https://www.veritasium.com/about/">Derek Muller</a>, Ph.D. and CEO/Founder of <a href="https://www.veritasium.com/">Veritasium</a></blockquote><p>I was browsing Facebook during my leisure time today and an interesting math video from <a href="https://www.facebook.com/Bdh.abdelmalek/">Visual Math</a> came up. Obviously, this video originated from <a href="https://www.veritasium.com/">Veritasium</a> and the topic was about how people tried to calculate <strong><em>π</em></strong><em> </em>over the entire history of math. It’s a great watch and you can view the link below if you want to learn more about the topic.</p><p><a href="https://www.facebook.com/watch?v=656140419034912">Visual Math on Facebook Watch</a></p><p>When we face a certain problem, we often settle for what is <strong>convenient</strong>, <strong>easy</strong>, and <strong>practical </strong>for the time being. Perhaps, it is because of time or resource constraints, or we sometimes feel that <em>“overthinking is some sort of a mental torture”</em>. I know people living on either extreme. On one side, there are people who tend to <strong>overcomplicate things</strong>, while on the opposite side, there are these folks who always think of the <strong>obvious </strong>and do not want to stretch their brain cells even for a bit.</p><p>Putting <a href="https://online.jwu.edu/blog/personality-differences-and-effect-behavior-work"><strong>personality differences</strong></a> aside, <strong>living on either side</strong> of the spectrum is a serious thing we need to address. We either <strong>miss the opportunities</strong> of having <strong>better solutions</strong> when we settle for the practical and pragmatic, or we tend to <strong>lose sight of the big picture</strong> and the actual problem we are trying to solve. Especially when we are working at the <strong>forefront of technology and innovation</strong>, where <strong>mathematical challenges </strong>are commonplace, getting a <strong>good balance</strong> of <strong>pragmatism </strong>and <strong>ingenuity </strong>becomes necessary.</p><h3>Look for Patterns</h3><p>Let’s try to look at this simple problem:</p><blockquote>Write a program that computes the sum of all natural numbers from 1 to N, where N is a user input.</blockquote><p>Some coders might solve this requirement <em>literally</em>, like this:</p><pre>// NOTE: This is a JavaScript code<br>// Assume that N is a positive integer &gt; 1<br>function addConsecutiveIntegers(N) {<br>  let sum = 0;<br>  for (let i = 1; i &lt;= N; ++i) {<br>    sum += i;<br>  }</pre><pre>return sum;<br>}</pre><p>While this solution works, it is obviously not the best one. In fact, if your high school or college algebra is not yet rusty, you will realize that this is an <a href="https://www.khanacademy.org/math/algebra/x2f8bb11595b61c86:sequences/x2f8bb11595b61c86:introduction-to-arithmetic-sequences/a/introduction-to-arithmetic-sequences"><strong>arithmetic sequence</strong></a> where <strong>d </strong><em>= </em>1. This problem can be efficiently and mentally solved using the formula <em>N*(N + 1)/2</em>.</p><h3>Simplify expressions</h3><p><em>Not everyone is good at mathematics</em>, especially the pure ones like <strong>algebra </strong>or <strong>calculus</strong>. However, we <em>do</em> encounter situations wherein even a <strong>basic knowledge</strong> of these branches of math becomes indispensable.</p><ol><li>An Excel sheet with lots of <strong>complex formulas</strong> for computing a product inventory or a financial forecast could benefit from <strong>expressions that have been simplified</strong> beforehand.</li><li>Complex applications that involve <strong>intensive mathematical computations</strong>, like a <strong>numerical weather forecasting system</strong>, a <strong>robotic vacuum</strong>, or even the <strong>noise cancellation</strong> feature of our humble <a href="https://docs.microsoft.com/en-us/microsoftteams/teams-overview">Teams</a> or <a href="https://zoom.us/">Zoom</a> app, require <strong>optimized</strong> and <strong>simplified</strong> equations for <strong>high performance</strong>.</li><li>A <a href="https://www.tensorflow.org/tutorials/images/classification"><strong>data science application</strong></a> involving <a href="https://developers.google.com/machine-learning/glossary/#convolutional_neural_network"><strong>deep neural networks</strong></a> needs to run very fast in order to be usable on a front-end application or IoT solution.</li><li>A <a href="https://lifesciences.tecan.com/applications_and_solutions/drug_discovery"><strong>drug discovery application</strong></a> for <a href="https://pubmed.ncbi.nlm.nih.gov/34850817/"><strong>anti-COVID purposes</strong></a> or an <a href="https://www.amenclinics.com/services/brain-spect/"><strong>MRI brain scanning application</strong></a> requires intensive <strong>mathematical modeling</strong>. If not done right, <strong>running complex simulations</strong> or <strong>processing large images </strong>would require millions or even billions of years to complete. No one would benefit from such an impractical software application. The patient might have already died even before the doctor can get a proper diagnosis.</li></ol><p>Here is an example. Let’s take a look at this joke SQL interview problem I gave last week to my team:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/155/1*m0UdJqp1H2OZON8-REJbIA.png" /></figure><p>The puzzle is how to implement the formula above in SQL. Formulas like this often occur in the hard sciences and engineering. Obviously, we cannot compute <a href="https://mathworld.wolfram.com/ImproperIntegral.html"><strong>improper integrals</strong></a> like this in a <a href="https://math.stackexchange.com/questions/458656/a-computers-memory-is-finite-so-how-can-there-be-languages-more-powerful-than#:~:text=A%20computer%20has%20a%20finite%20memory.%20There%20are,process%20are%20those%20whose%20member%20strings%20are%20finite."><strong>finite computer</strong></a>, unless we are using a <a href="https://reference.wolfram.com/language/tutorial/SymbolicCalculations.html"><strong>symbolic math package</strong></a> like <a href="https://www.wolfram.com/mathematica/"><strong>Mathematica</strong></a>. Even then, software applications have their own limitations, so people usually turn to <a href="https://en.wikipedia.org/wiki/Numerical_analysis"><strong>numerical approximations</strong></a> instead.</p><p>So going back, if we will try to implement this in SQL, we can only approximate the equation by using an <a href="https://en.wikipedia.org/wiki/Iterative_method"><strong>iterative method</strong></a> until we reach an <strong>acceptable value</strong>, <em>if there is one</em>. If the <a href="https://mathworld.wolfram.com/ImproperIntegral.html"><strong>improper integral</strong></a> is indeed <a href="https://mathworld.wolfram.com/ConvergentSeries.html"><strong>convergent</strong></a>, we are guaranteed to approach a certain <strong>limiting value</strong> after around 100 or 1000 loop iterations. Otherwise, we have a <a href="https://www.wolfram.com/language/12/asymptotics/explore-a-divergent-asymptotic-expansion-asymptoticintegrate.html?product=mathematica"><strong>divergent integral</strong></a> and we might be approaching positive or negative infinity, going nowhere. It might even take a lifetime to compute such a kind of equation.</p><p><strong>The solution</strong>: Solve it by hand.</p><p>We would be surprised that the <strong>area under the left curve</strong> <em>converges </em>to <strong>1</strong> as the <strong>lower bound</strong> goes to -∞. In this case, we do not even need to code anything complex, unless we need a <em>variable </em>lower bound.</p><h3>Call a friend</h3><p>If you’re not a mathematician or if you feel the need to brush up, it would be helpful to approach a friend or a colleague who possesses creative thinking and great mathematical skills. <a href="https://en.wikipedia.org/wiki/Albert_Einstein"><strong>Albert Einstein</strong></a> needed someone like <a href="https://en.wikipedia.org/wiki/Marcel_Grossmann"><strong>Marcel Grossman</strong></a> and <a href="https://en.wikipedia.org/wiki/Michele_Besso"><strong>Michele Besso</strong></a> to fill in the gap while formulating his <a href="https://www.space.com/17661-theory-general-relativity.html"><strong>general theory of relativity</strong></a><strong>. </strong>Without this close friendship and great collaboration, Einstein would not even get famous for his seminal work. He could have endured greater rejection and criticism because his theory is <em>purely theoretical </em>and, thus, cannot be tested or proven during his time. Of course, many decades later, his ingenuity later paid off with <a href="https://asd.gsfc.nasa.gov/blueshift/index.php/2015/11/25/100-years-of-general-relativity/"><strong>recent developments</strong></a> in astronomy and astrophysics, at the expense of an almost forgotten contribution and legacy of his friends.</p><h3>Conclusion</h3><p>When we are faced with mathematical challenges, sitting down and thinking ahead before attempting any solution pays off a lot. Looking for general patterns, reducing the problem into simpler ones, and sometimes reaching out to a close friend can help us validate or rethink our solutions. It’s like planning a house or a bridge even before we start building one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e57c2094509" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unit testing is overkill, or it isn’t?]]></title>
            <link>https://medium.com/@ryangatchalian/unit-testing-is-overkill-or-it-isnt-f98421ead80d?source=rss-25f5f15366cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f98421ead80d</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <dc:creator><![CDATA[Ryan Gatchalian]]></dc:creator>
            <pubDate>Sun, 06 Mar 2022 05:58:31 GMT</pubDate>
            <atom:updated>2022-03-10T09:27:56.982Z</atom:updated>
            <content:encoded><![CDATA[<p>Demystifying myths about unit testing</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*i_PJzvJ1RYfItTx-roOOhA.png" /><figcaption>Running a test suite in <a href="https://jestjs.io/">Jest</a> framework.</figcaption></figure><p><strong>While I was reading </strong><a href="https://www.sqlservercentral.com/forums/topic/is-it-worth-writing-unit-tests#post-3672759"><strong>this amazing article</strong></a><strong> about the benefits of database unit testing using </strong><a href="http://tsqlt.org/"><strong>tSQLt</strong></a>, I got enticed by the comments section. This area contained a wealth of healthy [and unhealthy] exchange of comments (emphasis added) regarding TDD and, particularly, unit testing. Sadly, I got awestruck<strong> </strong>with one of the main themes there, which can be summarized by <a href="https://www.sqlservercentral.com/forums/topic/is-it-worth-writing-unit-tests/page/4">one comment</a> from Microsoft MVP <a href="https://www.bing.com/search?q=jeff+moden+mvp&amp;cvid=08838156a51f415cbc2f57cd8f5b5761&amp;aqs=edge..69i57j69i60.2808j0j4&amp;FORM=ANAB01&amp;PC=U531">Jeff Moden</a>:</p><blockquote>And, that’s why I don’t care for what people are calling “Unit Tests”. It doesn’t make sense to have two pieces of code to maintain and get both right.</blockquote><p><em>DISCLAIMER</em>: I have nothing against Jeff, and I even admire his contributions to the SQL Server community. His SQL code optimizations are truly amazing, and I strive to follow his recommendations when writing performant SQL code. He also clarified at a later reply that he is not entirely against unit testing and TDD. What he is against are issues that we will articulate below.</p><p>In case you do not know this guy, he is the one who coined the term <a href="https://www.red-gate.com/simple-talk/databases/sql-server/t-sql-programming-sql-server/rbar-row-by-agonizing-row/">RBAR</a>, pronounced as R-BAR. We would not explore this large topic here, so let’s go back to his comment. <strong>Maintaining two pieces of code</strong>, i.e. both the production code and the test code, is not only <strong>time-consuming</strong>, but also <strong>needs to be done correctly</strong> in order to reduce <a href="https://www.projectpractical.com/technical-debt/#:~:text=Technical%20Debt%20Definition.%20Technical%20debt%2C%20also%20known%20as,result%20of%20prioritizing%20speedy%20delivery%20over%20perfect%20code.">technical debt</a>. Jeff Moden is right here. I myself also experience these challenges at times, especially when I have <strong>tight deadlines</strong> or if the team <strong>does not yet embrace</strong> a TDD and/or DevOps mindset. This is one argument against TDD and unit testing, and is also an early deterrent to those who consider adopting it in their teams or the entire organization.</p><p>However, if you have been doing TDD for quite sometime, you might notice that unit testing is not all about test automated and writing test code. So let’s dispel this misconception about unit testing.</p><h3>Regardless of whether we automate or not, we still need to write (or create) unit tests.</h3><p>Humans are <a href="https://www.health.harvard.edu/mind-and-mood/forgetfulness-7-types-of-normal-memory-problems">prone to forgetting</a> what they have done before, and we developers are no exception. At times, we might be creating code without writing <strong>formal tests</strong>, but that does not mean we do not have any test cases in mind. However, the issue with <a href="https://en.wikipedia.org/wiki/Tacit_knowledge#:~:text=Tacit%20knowledge%20can%20be%20defined%20as%20skills%2C%20ideas,or%20how%20it%20can%20be%20valuable%20to%20others.">tacit knowledge</a> like this is we <a href="https://www.verywellmind.com/explanations-for-forgetting-2795045">might be able to forget</a> it later on. When we need to do <strong>regression testing</strong>, we will not be able to <strong>repeat all the tests</strong> we did before and we might miss out something.</p><p>I know that not everyone works with SQL and databases in general. As such, let’s use <a href="https://www.stackscale.com/blog/popular-programming-languages-2021/">JavaScript</a> instead so everyone can relate.</p><p>Let’s take a look at this JavaScript code:</p><pre>function add(a, b) {<br>  return a + b;<br>}</pre><p>We have been doing this kind of arithmetic since elementary grade level. This mathematical operation has become second nature to us that it permeates our daily activities. As such, one would argue that writing lots of unit test code for this rather simple code is an overkill. We would also assume that JavaScript interpreter or whatever language we used to implement this function will do its job properly, isn’t it? What else can go wrong here?</p><p>Let’s say a new developer jumps into the project and suddenly did this without checking the original code:</p><pre>const a = { name: &#39;John Doe&#39; };<br>const b = { name: &#39;Bob Dylan&#39; };</pre><pre>// Add the two items<br>add(a, b);</pre><p>If we went too far with the <a href="https://agilemanifesto.org/">Agile Manifesto</a> by not having a written documentation of what the <strong>add()</strong> function is supposed to do, then we have a problem here. We cannot assume that future team members are aware of what we have done in the past, so it is our job to do the <strong>knowledge transfer</strong>. That can be done personally, through written documentation, or via a comprehensive automated test suite. On the other side, that <em>“other developer”</em> can be the “<em>[future] us”</em>. We might have jumped into a different project and the original design is not fresh to us anymore. We might have forgotten that <strong>add()</strong> is indeed a mathematical function.</p><p>Given the nature of <strong>dynamic languages</strong> such as JavaScript, Python, etc. and <strong>declarative languages</strong> such as SQL, we cannot always assume that the interpreter will know our <strong>code intent</strong>. In this case, what the original developer has in her mind is that we will use this function to add two numbers, not to combine two objects.</p><p>Let us take a look at this revised example:</p><pre>const a = { name: &#39;John Doe&#39;, escapeBugCount: 5 };<br>const b = { name: &#39;Bob Dylan&#39; escapeBugCount: 7};</pre><pre>// Add the two items<br>add(a.escapeBugCount, b.escapeBugCount);</pre><p>Upon inspection, this code will now work because the inputs are <strong>numeric data</strong>. So, at the back of our mind, we have at least these <strong>test cases</strong>:</p><ol><li>Input <em>a</em> must be a number (and nothing else)</li><li>Input <em>b </em>must be a number (and nothing else)</li><li>Input <em>a</em> must not be <strong>undefined</strong> or <strong>null</strong></li><li>Input <em>b</em> must not be <strong>undefined</strong> or <strong>null</strong></li><li>Return value is <strong>NaN </strong>(i.e. invalid result) when either <em>a</em> or <em>b</em> is <strong>undefined</strong> or <strong>null</strong></li><li>Return value is the <strong>sum </strong>of <em>a</em> and <em>b</em> when they both have <strong>valid numeric values</strong></li></ol><p>Whether we write these unit tests using a <strong>test framework</strong> like <a href="https://mochajs.org/">Mocha</a> or <a href="https://jestjs.io/">Jest</a>, or we do <strong>manual testing</strong>, we still need to be <strong>explicit</strong> about the <strong>expected behavior</strong> of our code. Computers can only infer about our best intentions, but they sometimes fail in that area. Type inferences have limitations, API data could not be retrieved because of network issues, and so on. Our code needs to anticipate these <strong>exceptional scenarios</strong>. The only way to prevent <strong>unwanted behavior</strong> in these situations is by <strong>creating test cases upfront</strong> and have a <strong>conscious QA mindset</strong>.</p><p>We also <strong>need to be disciplined</strong> as developers who do not hand-off buggy code to QA just because we are thinking <em>“it’s their job to catch [my] bugs”</em>. In real-life projects, these bugs can be <strong>costly to repair</strong>, especially in the case of applications being used to transact payments, generate payroll, or launch <a href="https://priceonomics.com/the-typo-that-destroyed-a-space-shuttle/">NASA rockets</a>. These human errors can even take lives of innocent people.</p><p>While some would argue that <strong>developers are not QA</strong>, we cannot deny that we can become <strong>[better] developers</strong> if we learn QA tasks, like testing. This is especially true in an <strong>authentic DevOps culture</strong>, wherein the boundaries between <strong>job descriptions are blurring</strong>. Of course, we are not expected to do everything a QA does. It is because <strong>QA people are wired differently</strong> and that <strong>makes them excellent</strong> at what they do — serving as a <strong>gatekeeper of code quality</strong> and as a check-and-balance to developers. Nevertheless, wearing a QA hat at times can help <strong>reduce our bugs</strong> and force us to <strong>write simple code</strong>.</p><p>In our case, the benefit of having <strong>automated unit tests</strong> instead of executing them manually is that <strong>we can repeat the process</strong> without taking too much of our time. This takes us to another conclusion about testing and software development in general.</p><h3>Investigating bugs is more time-consuming than actual bug fixing.</h3><p>When we have unit tests in place, the <strong>extra time spent</strong> writing them is still less than the time wasted with <strong>finding a hidden bug</strong> in production. While the code [and the tests] are still in the <strong>hands of the developer</strong>, finding and <strong>fixing bugs are still convenient</strong>. However, when the application gets into production, the <strong>code that was not unit-tested</strong> might have already <strong>generated lots of bad data</strong>, thus making it <strong>more difficult to identify</strong> what went wrong.</p><p>One argument is that <strong>unit test code often gets larger</strong> than the code being tested. Revising them every time we change something in production code just to make them pass (GREEN light) also seems like a waste of time. The truth is that, whenever we find ourselves editing the tests <a href="http://blog.cleancoder.com/uncle-bob/2016/03/19/GivingUpOnTDD.html"><strong>every single time</strong></a>, we are doing TDD incorrectly. In fact, we have what is called <a href="https://blog.cleancoder.com/uncle-bob/2017/10/03/TestContravariance.html"><strong>fragile tests</strong></a>, and even those who have formal training in TDD do not get unit testing right.</p><p>Now, assuming that our unit tests are not fragile, tasks like bug replication, bug fixing, and code refactoring should not take too much of our time. In fact, if our unit tests are <strong>stable </strong>and <strong>detailed</strong> enough, we can say that they are “<em>written only once, ran many times”</em>. That saves our time making the code more stable and reliable, with very few bugs creeping into production.</p><p>Unit tests can also <strong>increase our confidence</strong> in the code. Other people can jump into the project because the unit tests serve as <strong>living documentation</strong> and <strong>good reference</strong> for expected behavior. <strong>Knowledge transfer</strong> then becomes easier and would require fewer meetings. In turn, <strong>bug fixing tasks</strong> will be less frequent. Most important, they reduce the possibility of our <strong>reputation</strong> being tainted because of <strong>failed software delivery</strong>.</p><h3>Conclusion</h3><p>Software development folks might have differing views about unit testing. A lot of negative comments about it stem from the fact that opponents might have received bad information or training about it, or they have not tried it even once for a real-life project. They might have given up too early while learning the practice and got frustrated, and did not have the opportunity to reap its benefits at large.</p><p>On the contrary, the benefits of this practice far outweigh the cons, <strong>if done correctly</strong>. We can find a lot of good resources online, and we just have to find them. Lastly, great mentors who have hands-on experience of TDD can support and guide us in writing better tests [and better code], and help dispel TDD myths that circulate online.</p><p>I hope you enjoy this article. If you have any other ideas, feel free to comment here. Please be respectful of each other’s views so we can have a healthy discussion and exchange of ideas. Lastly, if you want me to write an interesting topic, feel free to drop a message so we can see if we can discuss that topic.</p><p>Have a great day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f98421ead80d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why WordPress themes must be responsive]]></title>
            <link>https://medium.com/@ryangatchalian/why-wordpress-themes-must-be-responsive-ffaaca68ede8?source=rss-25f5f15366cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffaaca68ede8</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Ryan Gatchalian]]></dc:creator>
            <pubDate>Sat, 19 Nov 2016 00:19:44 GMT</pubDate>
            <atom:updated>2016-11-19T00:19:44.156Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever purchased a premium theme that looks right on a desktop but surprisingly, you noticed that it looks horrible on your tablet or mobile phone? Well, you’re not alone. Mobile friendliness is very important, not because it is a hype, but because it is a necessity supported by <a href="http://blog.searchmetrics.com/us/2016/06/15/mobile-friendly-here-to-stay/">usage analytics</a>.</p><p>Imagine you’re on a distant island with no WiFi, only data service. Or you’re travelling while inside a bus and suddenly recalled that you have a final online exam due an hour later. Your agony must wait until you reach your next destination three hours later. And all you have is a smartphone or a tablet. Now, if the online exam site sucks on mobile devices, you will not be able to see or answer the exam questions properly, right? Perhaps, the label for the checkbox lies outside the screen and you cannot read it. Then you will not be able to finish the exam. How frustrating, isn’t it?</p><p>This situation alone underscores the importance of having a responsive WordPress theme, right from the start. As a tip, you must test any theme on mobile devices and at different screen resolutions before purchasing one. Even those with Bootstrap or Zurb Foundation as the underlying CSS framework should undergo manual inspection. Free starter themes like the <a href="https://roots.io/sage/">Sage</a> theme from <a href="https://roots.io/">Roots</a> and <a href="http://themehybrid.com/hybrid-core">Hybrid Core</a> offer responsive layouts out of the box. The default WordPress <a href="https://wordpress.org/themes/twentyfifteen/">Twenty Fifteen</a> and <a href="https://wordpress.org/themes/twentysixteen/">Twenty Sixteen</a> themes are also mobile-first and are open for further customization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffaaca68ede8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discipleship in Unexpected Places]]></title>
            <link>https://medium.com/@ryangatchalian/discipleship-in-unexpected-places-7dc1f3090a6?source=rss-25f5f15366cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dc1f3090a6</guid>
            <category><![CDATA[bible-reading]]></category>
            <category><![CDATA[discipleship]]></category>
            <category><![CDATA[church]]></category>
            <category><![CDATA[fellowship]]></category>
            <category><![CDATA[christianity]]></category>
            <dc:creator><![CDATA[Ryan Gatchalian]]></dc:creator>
            <pubDate>Wed, 06 Jul 2016 22:11:01 GMT</pubDate>
            <atom:updated>2016-07-09T01:57:08.086Z</atom:updated>
            <content:encoded><![CDATA[<p>What comes to your mind when you hear the word ‘discipleship’? Maybe you are thinking about modules to complete or programs to attend. You might also associate the term with rigorous training, coaching, or mentoring. Or you suddenly recall your cell group leader following up on your consistency with daily devotion and writing journals.</p><p>Yes, you are right. All these things are part of discipleship. But do you wonder how discipleship looks like in the trenches? Let me share with you some of my experiences of discipleship that happen in places and situations you might not expect.</p><h4>Hanging out with church friends at a 7/11 store near you</h4><p>Having <em>informal</em> conversations with your friends opens up opportunities for sharing your life experiences, both as a Christian and as a normal person. This informal<em> </em>fellowship setting lets anyone learn from the group and confide personal struggles without being misjudged, condemned, or betrayed. Living a life together like that depicted in Acts 2:42 seems like a mission impossible in a fast-paced society. But even in 21st century, it is a must for authentic fellowship of the disciples.</p><p>Fellowship and discipleship are often recreated artificially in the form of cell groups, discipleship programs, and church activities. Yes, they can help, but they can never be a substitute for authentic discipleship that can be only experienced through organic personal relationships. Eating together at a burger shop or any food stall outside the church premises can be a good way to ease the tension and break the <em>“this is a church activity”</em> or <em>“this is just another cell group session”</em> mindset. Great idea yet simple, right?</p><h4>When you read your Bible</h4><p>Or should I say, “when the Bible reads <em>you</em>.” The Bible is not a trivia book, but a mirror that tells you <em>prophetically</em> what you should and what you should not do as a Christian. Read the book of Jonah and you will learn what will happen when you turn away from your life mission and complain to God if He shows mercy on people that He should have punished. Go to the book of Lamentations and see if you can relate to Jeremiah’s struggles. Or take a look at the story of King David’s and Jonathan’s lifelong friendship. Do you still find yourself loyal to your closest friend? Or do you have some betrayal, gossiping, and backstabbing tendencies, just like Judas Iscariot? Are you ill-tempered and melancholic, just like the great Apostle Peter? The Bible will surely tell you, and you must act accordingly if you want to become a true disciple of Christ.</p><h4>Your everyday experience</h4><p>Yes, you’re not misreading anything here. Your daily struggles and joys in life will teach you a lot about who Jesus Christ is and what is His role in your spiritual journey. Look at your blessings. Did these things teach you how to be grateful to God instead of being boastful or prideful? Now look at your trials in the past three to six months. Did these situations make your faith stronger? Did you become more dependent on God or turn out to be rebellious and resentful?</p><p>These are just some of my personal experiences, and I know you also have your own. Please share your stories so that we can learn from each other.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dc1f3090a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>