<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Jercicho Pascua</title>
    <description>The latest articles on Forem by Jercicho Pascua (@jercichop).</description>
    <link>https://forem.com/jercichop</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F961295%2Ff9e76d65-bebf-4c05-a971-821c8ad07960.jpg</url>
      <title>Forem: Jercicho Pascua</title>
      <link>https://forem.com/jercichop</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jercichop"/>
    <language>en</language>
    <item>
      <title>✨ Self-Reflection – Year 2025 Back to Basics – Rediscovering the Joy of Hands-On Coding &amp; Delivering Real Impact</title>
      <dc:creator>Jercicho Pascua</dc:creator>
      <pubDate>Thu, 04 Dec 2025 20:08:38 +0000</pubDate>
      <link>https://forem.com/jercichop/self-reflection-year-2025-back-to-basics-rediscovering-the-joy-of-hands-on-coding--11p1</link>
      <guid>https://forem.com/jercichop/self-reflection-year-2025-back-to-basics-rediscovering-the-joy-of-hands-on-coding--11p1</guid>
      <description>&lt;p&gt;As 2025 comes to a close, I look back with gratitude and pride. This was the year I consciously chose to go “Back to Basics” – rolling up my sleeves, writing code again, solving problems myself, and reconnecting with why I fell in love with technology in the first place.&lt;/p&gt;

&lt;p&gt;Instead of always reaching for the newest framework or vendor solution, I asked myself:&lt;/p&gt;

&lt;p&gt;“Can I build this myself? Can I make it simpler, faster, and cheaper?”&lt;/p&gt;

&lt;p&gt;Most of the time, the answer was yes — and the results speak for themselves.&lt;br&gt;
💡 This year reminded me that innovation doesn’t always mean complicated architecture; sometimes it’s just caring enough to fix things properly.&lt;/p&gt;

&lt;p&gt;🚀 Key Results Delivered in 2025&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Cost Avoidance Through In-House Innovation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I repeatedly challenged the question:&lt;br&gt;
“Do we really need to spend this money?”&lt;/p&gt;

&lt;p&gt;By building working prototypes myself and demonstrating them to stakeholders, I convinced architecture and procurement teams that we could deliver equal or better solutions internally.&lt;/p&gt;

&lt;p&gt;➡️ Outcome: Significant licensing costs avoided, while keeping full control and flexibility in our hands.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Dramatically Improved System Processing TAT&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Thanks to targeted tuning and smart optimizations:&lt;br&gt;
➡️ Processing TAT improved by &amp;gt;40%&lt;br&gt;
This enabled the business to onboard more partners and capture market opportunities faster.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Production Stability &amp;amp; Efficiency Gains Across the Board&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I consistently focused on resilience and operational excellence:&lt;/p&gt;

&lt;p&gt;Enhanced multiple SQL jobs&lt;/p&gt;

&lt;p&gt;Implemented permanent fixes for recurring incidents&lt;/p&gt;

&lt;p&gt;Continuous improvements to dashboards for better visibility&lt;/p&gt;

&lt;p&gt;Strengthened production discipline&lt;/p&gt;

&lt;p&gt;Faster incident detection&lt;/p&gt;

&lt;p&gt;Better runbooks&lt;/p&gt;

&lt;p&gt;Reduced operational toil through small but impactful automation&lt;/p&gt;

&lt;p&gt;Improved overall system performance and stability&lt;/p&gt;

&lt;p&gt;Many of these were never assigned projects.&lt;br&gt;
They started with:&lt;/p&gt;

&lt;p&gt;“I noticed something and I couldn’t let it go.”&lt;br&gt;
That, for me, was the real win.&lt;/p&gt;

&lt;p&gt;🌟 Values &amp;amp; Behaviors I Demonstrated&lt;br&gt;
✔ Ownership &amp;amp; Initiative&lt;/p&gt;

&lt;p&gt;I didn’t wait for permission. If something was broken, slow, risky, or expensive — I fixed it or proposed a better way.&lt;/p&gt;

&lt;p&gt;✔ Cost Consciousness &amp;amp; Pragmatism&lt;/p&gt;

&lt;p&gt;Proved again that we don’t always need expensive vendor tools.&lt;br&gt;
Sometimes the best solution is a few hundred lines of clean, well-tested code written by someone who cares.&lt;/p&gt;

&lt;p&gt;✔ Customer-First Mindset&lt;/p&gt;

&lt;p&gt;Every change answered one question:&lt;br&gt;
“How does this help the business grow or serve customers better?”&lt;/p&gt;

&lt;p&gt;Faster bureau processing → more loans approved → happier customers and partners.&lt;/p&gt;

&lt;p&gt;✔ Technical Craftsmanship&lt;/p&gt;

&lt;p&gt;Going back to basics meant:&lt;/p&gt;

&lt;p&gt;Writing code again&lt;/p&gt;

&lt;p&gt;Debugging at 2 a.m. when needed&lt;/p&gt;

&lt;p&gt;Testing thoroughly&lt;/p&gt;

&lt;p&gt;Documenting properly&lt;/p&gt;

&lt;p&gt;Leaving systems better than I found them&lt;/p&gt;

&lt;p&gt;✔ Courage to Challenge the Status Quo&lt;/p&gt;

&lt;p&gt;I pushed back on vendor recommendations when I knew we could do better internally — with confidence and evidence.&lt;/p&gt;

&lt;p&gt;🧠 Innovation &amp;amp; Efficiency – The Real Story&lt;/p&gt;

&lt;p&gt;This year proved that real innovation doesn’t always require GenAI, microservices, or expensive licenses.&lt;br&gt;
Sometimes it’s simply:&lt;/p&gt;

&lt;p&gt;Looking at legacy code with fresh eyes&lt;/p&gt;

&lt;p&gt;Asking “Why do we still do it this way?”&lt;/p&gt;

&lt;p&gt;Changing one configuration&lt;/p&gt;

&lt;p&gt;Rewriting one job&lt;/p&gt;

&lt;p&gt;Building a quick prototype&lt;/p&gt;

&lt;p&gt;Saving hundreds of thousands in licensing&lt;/p&gt;

&lt;p&gt;Simple. Effective. Impactful.&lt;br&gt;
And honestly — deeply satisfying. 😄&lt;/p&gt;

&lt;p&gt;❤️ The Biggest Lesson of 2025&lt;/p&gt;

&lt;p&gt;Going “Back to Basics” was the best professional decision I made.&lt;/p&gt;

&lt;p&gt;I rediscovered the pure joy of solving problems with code.&lt;br&gt;
I learned that I don’t need to be the smartest person in the room —&lt;br&gt;
I just need to:&lt;/p&gt;

&lt;p&gt;Care more&lt;/p&gt;

&lt;p&gt;Dig deeper&lt;/p&gt;

&lt;p&gt;Ship faster&lt;/p&gt;

&lt;p&gt;Build with heart&lt;/p&gt;

&lt;p&gt;In a world obsessed with the next shiny tool, there is real power in mastering the fundamentals:&lt;br&gt;
reading logs, understanding data flows, writing scripts, and delivering things that work today and cost less tomorrow.&lt;/p&gt;

&lt;p&gt;🔭 Looking Ahead to 2026&lt;/p&gt;

&lt;p&gt;With AI assistants now at everyone’s fingertips, the bar is higher than ever.&lt;br&gt;
But I’m carrying the same mindset forward:&lt;/p&gt;

&lt;p&gt;Start simple&lt;/p&gt;

&lt;p&gt;Question assumptions&lt;/p&gt;

&lt;p&gt;Build it yourself first&lt;/p&gt;

&lt;p&gt;Only buy or complicate when truly necessary&lt;/p&gt;

&lt;p&gt;Thank you to the stakeholders, managers and team for trusting me, challenging me, and giving me space to innovate.&lt;br&gt;
2025 reminded me why I chose this profession in the first place.&lt;/p&gt;

&lt;p&gt;🙏 Special Thanks&lt;/p&gt;

&lt;p&gt;To my amazing wife for inspiring me every day, and to my two daughters who give me strength and purpose. You are my constant motivation. ❤️&lt;/p&gt;

&lt;p&gt;I end the year tired — but happy — and excited to code again tomorrow.&lt;/p&gt;

&lt;p&gt;Back to Basics worked in 2025.&lt;br&gt;
Let’s keep that spirit alive in 2026. 🚀&lt;/p&gt;

</description>
      <category>coding</category>
      <category>joy</category>
      <category>softwaredevelopment</category>
      <category>happiness</category>
    </item>
  </channel>
</rss>
