For a long time, I followed that path. But recently, I asked myself a hard question: When was the last time I felt the pure joy of building?

As an Engineering Manager, I got used to having the answers. Or, at least, being the person who guided others to them. So, when I accepted a Software Engineer role at Mercari US and moved to Japan, I wasn't just changing time zones. I was changing who I was at work. And honestly? It feels like taking a deep breath after holding it for years.

But growth requires discomfort. I live in Ginza, surrounded by stunning autumn leaves during the current season and incredible food, yet I feel the friction of the unfamiliar. I don't speak Japanese yet. I went from being a manager who communicated for a living to a resident who struggles to order dinner. It’s humbling. It reminds me that expertise is contextual. In the code, I am fluent. On the street, I am a toddler.

The hardest adjustment isn't the job or the language. It’s the silence in my apartment. My girlfriend is back in Indonesia. People say, "Distance makes the heart grow fonder," but mostly, it just makes you realize how much you miss the small moments. Loving Tokyo is easy, but being here without her is the tricky part.

I’m realizing that my "new chapter" isn't just about working or living in Japan. It’s about learning to integrate these fragmented parts of myself...

Over the past few weeks, I have been working through The Almanack of Naval Ravikant, and it may be the most useful book I have read this year. One idea in particular keeps echoing: Naval's claim that life is, at its core, a single-player game.

The phrase is provocative because it ­repositions the burden of progress. In a single-player game the decisive moves are internal while the external world provides only the scenery and occasional obstacles. Society, by contrast, trains us for the multiplayer mode: we learn to seek status, negotiate group norms, and read social cues. Both modes matter, but the multiplayer emphasis can obscure the obvious that the joystick still rests in your own hands.

Framing life as primarily single-player doesn't deny community but for me it clarifies responsibility. You cultivate judgment, discipline, and original thought first, then bring those assets to the multiplayer arena. Seen this way, self-development is not self-indulgence but it is the prerequisite for meaningful contribution. Naval's point is simple but radical: master the single-player mechanics, and the multiplayer rounds take care of themselves.

The reality is life is a single-player game. You're born alone. You're going to die alone. All of your interpretations are alone. All your memories are alone. You're gone in three generations, and nobody cares. Before you showed up, nobody cared. It's all single player.

Naval Ravikant

Subjectivity of Reality​

I once assumed reality was a single, unchanging snapshot identical for every observer. Naval showed me otherwise. A tree or a stone simply exists, but the moment I look at it, my mind overlays its own filter. My mood shifts the colors, and my memories supply the background score. What I perceive is no longer pure reality but reality plus me.

That insight was still humming in my head as I stepped out of Sinarmas MSIG Tower just after five-thirty, when the lobby still buzzed with people rushing for the elevators. My day at Ruangguru was done, but the commute was only beginning. I joined the steady stream of office workers moving toward the Dukuh Atas LRT. My backpack felt twice its usual weight: a laptop, a Mac mini I stubbornly insist on carrying, and a slim paperback titled How to Love Someone Without Losing Your Mind.

The platform was crowded, yet everything ran with the precision of habit—tap the card, file into the carriage, find any patch of floor space. When the doors closed, the train shuddered west to Bekasi. Outside, the skyline over Dukuh Atas shifted from solid blue to bands of orange and pink. Glass towers caught the light and flung it back in quick flashes.

Inside, most riders leaned into their phones. WhatsApp notifications popped up faster than thumbs could answer. Ride-hailing maps refreshed, showing red lines of traffic they were already planning to avoid. I opened my book instead, letting the first chapter pull my attention away from the carriage noise.

Same train, same rails, same sunset sliding past the windows yet every passenger was stitching together a different version of the evening. Jakarta reminded me of a truth I'd first learned months back in Tokyo, under winter neon and the razor-sharp air of Shibuya.

It was a clear January night, one of those Tokyo nights when the air feels sharp enough to cut ribbon, and I was meeting my best friend, Gabriel, and his partner, Assyffa, in Shibuya. A couple of days earlier, they had shared big news: they were expecting their first child. Gabriel had kept himself on a strict no-drinking rule during that stretch, but now the restriction was lifted, and he was eager to mark the occasion. He ducked with me into the FamilyMart below their hotel, came back with two Strong Zeros, and pressed one into my hand as if it were a trophy.

We carried the cans upstairs to their room, which overlooked the famous crossing. From a couple of floors up, the intersection looked like a time-lapse animation: five crowds converging, dissolving, and reforming each time the lights flipped. Gabriel clinked his can against mine and took the first sip he'd allowed himself in a couple of months.

Same city, same minute, but radically different headspaces. Gabriel was already talking about life in general and how overjoyed they both felt. Soon we were laughing about a mutual friend before pivoting somehow to raving about the unbelievably tasty Zunda shake from Sendai. I listened, nodded, and tried to match their joy, yet my mind hovered elsewhere on work in Jakarta, on a relationship that felt precarious, on the simple fact that after this toast, I would walk back to my place near Tokyo Tower alone.

Just before midnight, we said our goodbyes. Gabriel walked me to the station. I slipped through the underpass, boarded the last train bound for Onarimon, and let Official Hige Dandism's "Pretender" loop in my earbuds. I didn't yet know the woman I'd been seeing in Jakarta would end things a couple of weeks after I landed home, but the chorus, Kimi no unmei no hito wa boku ja nai ("I am not the one"), already felt uncomfortably accurate.

That night offered a clear lesson: we all breathed the same January air, drank the same cans of Strong Zero, and watched the same neon sweep of Shibuya Crossing, yet the meaning each of us attached to it was private. For Gabriel and Assyffa, Tokyo was an opening scene in the story of new life. For me, it was an interlude between an uncertain present and an even murkier return. Reality, I realized once again, is never a single photograph, but it is the raw image plus the caption each of us writes in our head.

Moments like these convince me that meaning isn't served to us on a silver platter, but we make it ourselves. That can feel terrifying, the way a blank page feels to a writer, until you remember a blank page is also pure freedom. Most of us first notice this freedom when life refuses to follow the checklist.

Picture a production bug that passes every test suite, ships, then appears again after the fifth "final" patch. You watch logs, rerun scripts, and wonder how many more late nights it will devour. In moments like this, the outside world is fixed, and you cannot wish the defect away, but your inner narrative is still malleable. You can label the bug a catastrophe, or you can treat it as the tuition you pay for mastery.

The same principle scales. A project timeline slips, a meeting derails, a teammate quits, and suddenly your sprint looks like spilled coffee. Reality hands you raw facts; interpretation is up to you. Between what happens and what you decide it means lies a narrow gap. Inside that gap you choose whether to react with frustration or curiosity, whether to blame circumstances or refine your craft

Calm focus starts here. When you recognize that the story is yours to edit, the blank page stops feeling hostile. It becomes a drafting table. Each thought you revise, each perspective you tighten, is another sentence in the manual you write for yourself. That manual is where real agency lives, and no external setback can seize it.

I picture life as a single-player adventure running on imperfect code. We don't pick our spawn point, birthplace, skin, those lines were compiled long before we pressed "Start." Yet the controller is still in our hands, and even the glitches can become hidden shortcuts. If I keep my view wide enough to marvel at the world's secret art direction and sharp enough to read the warning signs etched in its walls, every new level stops feeling random and starts feeling like an invitation to master its mechanics.

To be continued…

Audio Overview​

Recently, I stumbled upon the enchanting mystery of the four-leaf clover through someone who once brightened my world. During our last date, she gently introduced me to her affection for clovers, especially the rare and elusive four-leaf variety, and her gentle fascination quickly became my own. I'd always thought of four-leaf clovers simply as symbols of luck, but seeing them through her eyes revealed their deeper charm and beauty. It's astonishing how certain people quietly enter our lives and change the way we see things.

To me, she was the very essence of a four-leaf clover: wonderfully rare, quietly captivating, and softly unforgettable. Though our paths have now parted and we no longer speak, her genuine love for this delicate natural wonder left a lasting impression. I found myself drawn deeper into exploring the beautiful mysteries and history behind the symbolism of the four-leaf clover.

Guided by newfound curiosity, I unearthed fascinating details about the four-leaf clover. Each leaf beautifully symbolizes hope, faith, love, and luck, adding profound depth to my personal connection with this small, meaningful plant. It's more than mere luckk, for me it represents a heartfelt optimism and positivity.

Throughout history, the four-leaf clover has been revered across cultures as a powerful talisman. From ancient Egyptians blessing marriages to Celtic Druids who saw it as protection against negativity, the universal positivity surrounding this plant made me appreciate its simplicity and depth even more.

Meeting her felt exactly like discovering a rare four-leaf clover hidden among thousands of ordinary leaves, unexpectedly beautiful and deeply cherished. For me our encounter was a rare detour from the ordinary rhythms of life, leaving a profound, lasting impact on me.

Though our conversations have faded into silence, her heartfelt wishes linger with me. Just as the four-leaf clover symbolizes lasting positivity, her kind thoughts and quiet hopes have flourished into unexpected joys and blessings in my life. This reflection has taught me the enduring impact that brief yet meaningful connections can have.

This year, 2025, has held an unexpected abundance of blessings for me. Reflecting on it now, I feel deeply fortunate partly due to her gentle wishes and my newly awakened fascination with the four-leaf clover. While initially saddened by our separation, I've found warmth and reassurance in the symbolism of this precious plant.

Just as discovering one four-leaf clover often hints at more nearby, uncovering luck in one aspect of my life has encouraged optimism and openness towards the future. Sometimes, hope and fortune reach us through surprising avenues, reminding us to trust life's mysterious pathways.

As I look forward, guided by the symbolism of hope, faith, love, and luck, I'm reminded to remain open-hearted and curious. Each relationship, experience, and subtle discovery holds the potential to enrich and deepen our journey.

To the one who introduced me to this beautiful symbol, thank you. Though our paths no longer intertwine, the quiet beauty and meaningful lessons you shared continue to blossom within my heart.

Just like the four-leaf clover, life offers rare moments of beauty and promise. If we pause, look gently, and remain hopeful, perhaps our very own four-leaf clover is waiting patiently for us to discover it.

Four-Leaf Clover​

By Ella Higginson

I know a place where the sun is like gold, And the cherry blooms burst with snow, And down underneath is the loveliest nook, Where the four-leaf clovers grow.

One leaf is for hope, and one is for faith, And one is for love, you know, And God put another in for luck— If you search, you will find where they grow.

But you must have hope, and you must have faith, You must love and be strong – and so— If you work, if you wait, you will find the place Where the four-leaf clovers grow.

Audio Overview​

The lotus flower has always captivated me, not only due to its visual beauty but also because of the profound symbolism it embodies. Gracefully emerging from murky, muddy waters, the lotus symbolizes personal growth, resilience, and transformation, representing the journey toward achieving clarity even amidst life's most challenging situations. Its beauty reminds us that significant strength and wisdom frequently come from navigating and overcoming difficult circumstances.

“In the mud lies the promise of blooming. And for me, that promise has never been clearer.”

Over the past month, my own life has mirrored this metaphor in profound ways. I’ve encountered a series of powerful experiences and pivotal moments that have challenged my previous perspectives, illuminating essential truths. These experiences, though often uncomfortable, have been instrumental in shaping a deeper understanding of myself and the world around me. Each lesson has guided me to question and eventually release certain outdated beliefs and patterns, making room for growth, authenticity, and genuine happiness.

Speaking Negatively ​

I used to believe that venting negative feelings about past experiences, whether in relationships, friendships, or even professional connections, would help me move forward. However, I've come to realize that speaking negatively about someone or something I once valued only prolongs bitterness and resentment. For instance, many of my friends have suggested that moving on from a painful situation requires holding onto anger or resentment, believing that negativity would empower me to break free. Yet, I've learned that carrying negativity only holds me back further. Genuine forgiveness, quiet respect, and letting go with grace are far more powerful in fostering true healing and personal growth.

Problems without Solutions​

At times, life's difficulties seemed impossible to overcome, leaving me feeling stuck, especially when these issues were beyond my direct control. Recently, I encountered a significant challenge that threatened my livelihood due to external factors at work. Initially, this issue appeared overwhelming, as it stemmed from circumstances entirely outside of my influence. However, I've learned that every challenge carries within it a hidden solution, even if the solution isn't immediately clear or straightforward. For example, when your company struggles and job security becomes uncertain, the immediate response might be to contribute your best efforts to help improve the situation. However, if the challenges exceed your abilities or control, the solution might involve taking uncomfortable yet necessary proactive steps, such as seeking new job opportunities. In my situation, working in tech meant embracing this discomfort, revisiting job preparation strategies, diligently practicing coding through LeetCode, and thoroughly preparing for technical interviews to proactively address and overcome the obstacle.

Attachment​

I've discovered that attachment often stems from deep-rooted fears, such as the fear of loss, change, or uncertainty. When we cling too tightly to people, possessions, or specific outcomes, we unintentionally invite greater suffering into our lives because nothing in life remains static or permanent. Embracing life's constant changes and understanding its transient nature allows me to love genuinely without feeling the need to control or possess others. True peace and lasting happiness come from cultivating inner strength, acceptance, and self-awareness, rather than relying on external circumstances or relationships to fulfill or complete me.

Right Person, Wrong Time​

In the past, I often comforted myself with the belief that certain relationships failed because they occurred at the wrong time. This perspective gave me a way to rationalize disappointments and heartaches. However, I've since realized that every relationship, regardless of outcome, holds purpose and value.

Now, I understand that each encounter happens exactly when it should, providing lessons essential to my growth. Every interaction, whether joyful or painful, has contributed meaningfully to shaping who I am today. Thus, I've come to appreciate that there truly is no such thing as a "wrong time," only experiences that help us evolve.

Finding Wholeness in Another Person​

I no longer believe that another person can "complete" me. For a long time, I thought finding someone special would fill all my inner voids, making me whole and content. But repeatedly, this belief led only to disappointment and dissatisfaction because it placed unrealistic expectations on others to fix what was missing within me.

Instead, I've discovered the importance of cultivating self-love and focusing on my own personal growth first. By investing in myself, becoming self-aware, and developing inner fulfillment, I've learned that healthy and meaningful relationships naturally emerge when two individuals come together as fully realized, secure people. These connections are richer, deeper, and more lasting because each person contributes equally and authentically, rather than relying on one another to fill emotional gaps.

Much like the lotus flower, which grows beautifully from muddy waters, we too have the capacity to rise above challenging circumstances and transform our lives. By recognizing and releasing beliefs, behaviors, and emotional attachments that restrict our growth, we can open ourselves up to new perspectives and deeper understanding.

Embracing change, however uncomfortable it may be, enables us to stay authentic to our true selves, fostering genuine happiness and lasting peace. Through this courageous journey of self-discovery and acceptance, we not only overcome past struggles but also become stronger, wiser, and more fulfilled individuals.

Audio Overview​

A few years ago, I realized something unsettling that no matter what I achieved or acquired, the satisfaction was always temporary. I’d set a goal, work hard, reach it, and feel an initial surge of excitement but only to find myself asking, “What’s next?” almost immediately.

At first, I thought this was just ambition. But the more I paid attention, the more I noticed a pattern that was leaving me perpetually unsatisfied. Turns out, there’s a name for this. The hedonic treadmill which are the idea that no matter what happens, we eventually return to a baseline level of happiness, always craving more and more. If you’ve ever felt stuck in this cycle, you’re not alone.

The Never-Ending Chase​

I remember the first time I convinced myself this thing would finally make me happy. It was a brand new phone, the one I had been obsessing over for months. When I finally got it, I was thrilled but after a few weeks, it became just another object in my life. The excitement had vanished, and I was already thinking about what else I wanted next.

The same thing happened with achievements. I worked hard to land my "dream job," thinking it would feel like I had arrived. Yet, just a few months in, I found myself setting new goals, feeling just as restless as before.

This is the hedonic treadmill in action. We convince ourselves that once we get the next promotion, the next gadget, or the next trip, we’ll finally feel satisfied. But as soon as we achieve it, our mind moves the goalpost. And the chase starts all over again.

The Social Media Trap​

The problem was worsened by social media. Every time I opened Instagram, I saw people traveling to exotic places, buying luxury cars, and living what appeared to be their "best lives." It was an endless highlight reel, making me feel like I was falling behind and I needed to do more, have more, be more .

This created an unhealthy urgency. I started making decisions based on what I thought success “should” look like, rather than what actually made me happy. It felt like a race, one where I needed to catch up to everyone else who seemed to be winning at life.

At one point, I had a thought that really shook me: What happens if I rush through all the "big life moments" too soon? If I checked off all the major milestones in my 20s—traveling to dream destinations, buying expensive things, chasing achievements, would I still have anything meaningful to look forward to? The idea of reaching a point where nothing felt exciting anymore was terrifying.

That’s when I realized that living life as a speedrun wasn’t making me happy. It was just making me exhausted.

Learning to Slow Down​

The turning point came when I started making intentional choices instead of impulsive ones. Instead of constantly upgrading my life at every opportunity, I embraced the idea of pacing it out by leaving room for future excitement, rather than burning through it all at once.

Here’s what changed:

• I stopped upgrading everything immediately. My first car after getting a job was nothing fancy. In fact, I didn’t even buy a car until I actually needed one. At the time, it felt like a smart financial decision, but looking back, it also taught me something valuable: the joy of gradual progress. If I had rushed to get a luxury car right away, it would have set an unsustainable expectation for what I needed to feel satisfied. By starting with something simple and practical, I was able to appreciate each upgrade over time, making every step feel more meaningful instead of just another checkbox on the path to "success."

• I traveled without intention at first, but I learned to pace myself. In my early 20s, I was eager to check off every bucket list destination as soon as I had the time and money to do so. I jumped at every opportunity to travel, thinking that experiencing as much as possible, as quickly as possible, would make my life feel more exciting and fulfilling. But after a while, I noticed that the thrill of each trip faded faster than I expected. I started wondering if I kept going at this pace, would I eventually reach a point where I had already "done it all" before I even had a chance to truly appreciate it? That realization shifted my mindset. Instead of rushing through experiences, I decided to be more intentional, spacing out my travels and choosing trips that held deeper meaning at different stages of my life. Now, I still have incredible places left to visit, and the excitement of looking forward to new adventures hasn’t diminished.

• I learned to enjoy the journey, not just the goal. For the longest time, I saw my accomplishments as trophies things to check off a list so I could prove to myself (and maybe others) that I was moving forward. But once I achieved something, the satisfaction was always fleeting, and I felt the pressure to chase the next milestone immediately. Over time, I started shifting my perspective. Instead of focusing solely on the finish line, I began finding joy in the process itself whether it was learning a new skill, improving at my work, or simply growing as a person. By embracing the experience rather than fixating on the outcome, I found a deeper and more lasting sense of fulfillment.

This mindset shift completely changed how I approached life. Instead of expecting happiness to come from the next big thing, I started finding joy in the present without the pressure of constantly chasing more.

Final Thoughts​

Stepping off the hedonic treadmill doesn’t mean giving up ambition or settling for less. It just means understanding that more isn’t always better and that happiness isn’t something you’ll find at the finish line, because the finish line keeps moving.

True satisfaction comes from creating a life where joy isn’t just about achieving the next goal, but about appreciating where you are right now . If you’re constantly chasing, you’ll always feel behind. But if you learn to pace yourself, you’ll find that happiness isn’t something to be pursued but it’s something to be lived.

Recommended Resources​

1. How To Make The Most Out of Your 20s - Y Combinator: A YouTube video providing advice on maximizing personal and professional growth during your twenties. https://www.youtube.com/watch?v=H_XMqRhLhic

2. The Hedonic Treadmill - Personal MBA: An explanation of the hedonic treadmill effect and strategies for breaking free from its cycle. https://personalmba.com/hedonic-treadmill/

Audio Overview​

January 2025 was one of the challenging periods of my life. I found myself at a crossroads, faced with a difficult decision: should I fight to hold on to people who were ready to walk away, or should I let them go? At first, the thought of letting go felt like surrender, like giving up on something that once mattered. But as I reflected, I came to a life-changing realization when people choose to leave, it is not my responsibility to convince them to stay. True connections should never require force or persuasion, and holding onto someone who has already decided to leave only prolongs the inevitable. So, rather than clinging to what was slipping away, I chose to step back and let them go.

This perspective may seem counterintuitive at first, especially in a world that often emphasizes fighting for relationships, proving loyalty, and never giving up on people. However, I’ve learned that there's profound peace in allowing things to unfold naturally. Don’t fight to keep people who no longer want to be in your life.

This mindset doesn’t just apply to romantic relationships but it extends to friendships, family ties, and even professional relationships. Time and experience have taught me that when someone decides to distance themselves, it’s often a reflection of where they are on their own journey, not a measure of your worth. Clinging to relationships out of fear, insecurity, or obligation only leads to unnecessary pain. Instead, accepting that not everyone is meant to stay forever frees us to focus on the relationships that are genuine, mutual, and fulfilling.

The Inevitable Tide​

Have you ever truly succeeded in holding on to someone who was determined to leave? Has actively fighting to keep a person in your life whether in a romantic relationship, friendship, or any other bond ever led to a lasting, fulfilling connection? More often than not, the answer is no. Dr. Orion Tabban puts it plainly: "Fighting to keep someone in your life is ineffective. It just doesn’t work." When someone has already made the decision to walk away, any attempt to block their exit only intensifies their desire to leave. The more you resist, the harder they push to break free.

Dr. Tabban compares this dynamic to being in a cult easy to get in, but difficult to escape. When people feel trapped, they don’t reconsider their decision to leave but they only fight harder to reclaim their freedom. This is why he advocates for the complete opposite approach: relationships should be "hard to get into and very easy to get out of." The exit should always be open, not as an invitation for people to leave, but as a sign that their presence in your life is a choice, not an obligation.

This perspective resonates deeply with me because I’ve found myself on both sides of this painful reality. I’ve been the one desperately clinging to someone who was slipping away, convincing myself that if I tried hard enough, they might change their mind. I’ve also been the one who felt suffocated by another person’s attempts to hold on to me when my heart was no longer in it. In both situations, the struggle only caused more harm. Holding on out of fear, guilt, or desperation never strengthens a relationship it only creates tension and resentment.

Even if you do manage to convince someone to stay, as Dr. Tabban explains, it’s often a "Pyrrhic victory" a short-term win that comes at too great a cost. They may remain in your life, but not because they truly want to be there. Instead, their presence is driven by guilt, pity, obligation, or even fear of hurting you. These emotions are fleeting and cannot sustain a meaningful connection. Sooner or later, the underlying desire to leave will resurface, and the cycle of conflict and heartbreak will begin again.

The truth is, authentic relationships cannot be forced. Love, friendship, and human connection must be freely given, not demanded or coerced. When we fight to keep someone who wants to leave, we are not preserving the relationship but we are merely postponing the inevitable. The most powerful, self-respecting choice we can make is to let go with grace. When someone chooses to walk away, it’s not a failure but it’s a redirection, making space for the right people who genuinely want to be in our lives.

Fighting for the Wrong Things​

Often, our instinct to fight for a relationship isn’t just about love but it’s about fear. The fear of loss, the fear of rejection, and, in some cases, the fear that we are not enough. As Cara Bowen insightfully points out, we sometimes fight harder to be chosen than we fight for ourselves. We stay in relationships where we feel unappreciated, undervalued, or even disrespected, believing that if we just try harder and if we prove our loyalty, patience, and endurance maybe the other person will finally see our worth. But this is a painful illusion. Love, real love, "doesn’t require you to prove your fight. Love fights with you, not against you." In other words, the right person will stand beside you, not force you into a constant battle just to keep them in your life.

Bowen’s own experience highlights a common misunderstanding about love and effort. She recalls being accused of "not fighting hard enough" when a relationship ended, as if leaving was a sign of failure or weakness. But in reality, walking away is not always a form of surrender. It is often a redirection of our efforts and a conscious choice to fight for something different, something more aligned with our well-being. As she powerfully redefines it: "When I walked away from the relationship, I didn’t stop fighting. I just began fighting for something else. I stopped fighting for it to work out no matter what and started fighting for what was best for both of us." This shift in mindset is incredibly liberating. Instead of expending all of our energy trying to hold onto someone who is drifting away, we can redirect that strength toward something far more meaningful—ourselves.

Fighting for love does not mean sacrificing our own worth in the process. A relationship should never require one person to constantly prove their value while the other remains distant or uninterested. Love should be mutual, reciprocal, and full of shared effort. If we find ourselves in a dynamic where we are the only one holding on, it may be time to reevaluate what we are truly fighting for. Instead of desperately clinging to someone whose heart has already left, we can fight for our own self-respect, our well-being, and the love we genuinely deserve.

At the end of the day, the hardest but most rewarding battle we will ever fight is the one for ourselves. Walking away from something that no longer serves us is not a sign of failure but it is an act of self-love and strength. The moment we stop chasing after people who don’t value us is the moment we free ourselves to welcome those who will.

The Open Door and the High Precipice​

Dr. Orion Tabban offers a powerful analogy: imagine standing on the edge of a high cliff with no guardrail. The sheer awareness of the potential danger naturally makes people more cautious and mindful of their movements. In the same way, when people know that the "exit is always open and unobstructed," they tend to be more conscious of their actions within a relationship. They won’t take your presence for granted if they understand that you won’t desperately fight to keep them there "irrespective of what they say or do." This creates a different kind of respect. One that isn’t driven by fear or obligation but by the understanding that the relationship is a choice, freely made by both individuals.

However, this doesn’t mean playing emotional games or creating artificial distance to manipulate someone into valuing you. It’s about recognizing your self-worth and understanding that you deserve to be with someone who genuinely chooses to be in your life. If someone frequently threatens to leave or tests your commitment by walking away, it’s essential to remember Dr. Tabban’s straightforward advice: "If someone actually leaves, like they literally walk out then never, ever, ever chase them down." The foundation of a healthy relationship should never require you to beg for someone's presence. According to Dr. Tabban, "The bare minimum required to resume a relationship is that they have to walk back in."

In other words, love and commitment should be mutual. A person who truly values the relationship won't expect you to chase after them every time they choose to walk away. Instead of exhausting yourself trying to convince someone to stay, allow space for those who genuinely want to be there because the right people won’t need to be begged to remain in your life.

Fighting for Your Heart​

At the core of a fulfilled and healthy life is one crucial battle which are the fight for our own hearts. This means recognizing our inherent worth, setting firm boundaries, and having the strength to walk away from relationships and situations that stifle our growth rather than nurture it. Too often, we exhaust ourselves fighting to be seen, valued, or chosen by others while neglecting the most important commitment of all, the one we owe to ourselves. As Cara Bowen beautifully puts it, "You are worth fighting for, but don’t forget to fight for your heart and to walk away from something that is suffocating the beauty that’s within you."

Many people mistake letting go for giving up, but in reality, releasing something that no longer serves you is one of the bravest and most self-loving things you can do. Holding on to a connection that drains you, diminishes your self-worth, or fills you with constant insecurity does not bring happiness but it only prolongs pain. Walking away is not a sign of weakness; it is an act of profound self-respect. It is a declaration that you refuse to settle for less than what you deserve. By letting go, you create space not just for healing, but for new opportunities, new relationships, and deeper connections with people who genuinely cherish and appreciate you.

So, if someone in your life begins to pull away or makes the decision to leave, take a moment to acknowledge your emotions, but resist the urge to fight for someone who no longer wants to stay. Instead, let them go with grace. Wish them well, express gratitude for the time you shared, and remind yourself that their departure is not a reflection of your worth. Sometimes, people leave because their role in your story has come to an end, and clinging to them only keeps you from discovering the beautiful chapters still ahead.

The love, respect, and loyalty you desire should never have to be begged for and it should be given willingly. The people who are meant to be in your life will remain not because you fought to keep them, but because they genuinely value and choose to stay. You are not meant to chase love but you are meant to receive it freely, wholeheartedly, and without condition. And when you begin to fight for yourself instead of fighting to hold on to others, you open the door to the kind of love and relationships that truly make life meaningful.

Recommended Reading Materials​

1. Episode 460: Don't fight to keep people (you lose when you win): A podcast episode by Dr. Orion Tabban discussing the futility of fighting to keep someone in your life. It emphasizes the importance of letting go and allowing people to make their own choices. https://oriontaraban.podbean.com/e/episode-460/
2. You Shouldn't Have To Fight For Someone's Love: An article that highlights the importance of mutual effort and how love shouldn't feel like a constant battle. It encourages readers to recognize their worth and seek relationships where they are valued and appreciated. https://thought.is/you-shouldnt-have-to-fight-for-someones-love/
3. Love Is Not The Same In Your Twenties, And That's A Good Thing: An article discussing how our understanding of love evolves as we mature. It suggests that recognizing this evolution can lead to healthier and more fulfilling relationships. https://thought.is/love-is-not-the-same-in-your-twenties-and-thats-a-good-thing/

Audio Overview​

We live in an era where effort is becoming optional.

Craving a meal? Open Gojek or Grab, and it will arrive at your doorstep in 20 minutes. Need new clothes? A few taps on Shopee, and they’ll be delivered the same day. Feeling too tired to talk to someone? Just send a text or voice note. Life’s daily inconveniences are disappearing, erased by technology and smart solutions designed to make everything seamless and effortless.

At first glance, this sounds amazing. Technology is here to enhance our lives, saving us time and freeing us from tedious work. But the more I look around, the more I wonder. What are we doing with this newfound freedom? Are we using it to grow, improve, and challenge ourselves? Or are we becoming complacent and drifting toward an existence where struggle is minimized, and comfort is prioritized above all else?

Boomers complain that Millennials and Gen Z are lazy, entitled, unwilling to put in the hard work their generation endured. Meanwhile, motivational entrepreneurs preach hustle culture, while self-care advocates insist we need to slow down. And now, AI is stepping into the picture—promising to make life even easier, anticipating our needs before we even recognize them ourselves.

With AI tools like NotebookLM assisting with research, coding aids like Cursor speeding up software development, and generative models drafting emails and writing content, the line between productivity and mindlessness is blurring. We are moving toward a society where friction is eliminated altogether.

But here’s the burning question that keeps me up at night: Is a life without struggle truly fulfilling?

I recently came across an insightful article by Julie Zhuo titled Our Souls Need Proof of Work, and it resonated with me deeply. The idea she explores is simple but profound: we are wired for effort. Without it, we lose purpose, resilience, and genuine happiness.

Without effort, without discomfort, we risk living an empty existence.

What exactly constitutes hard work?​

In my view, hard work is deeply individual. It's whatever presents a genuine challenge to you personally and the tasks that push against your natural inclinations or comfort zones.

Some find it incredibly difficult to rise at 5 AM for an early morning jog, while others might accomplish this effortlessly but struggle terribly with speaking before crowds. Personally, exercising at the gym, running extended routes, and studying Mandarin all qualify as hard work for me. Each requires discipline and persistence that doesn't come naturally.

Certain individuals handle physically demanding tasks with remarkable ease but find mental activities extraordinarily challenging. Some excel effortlessly in social environments while others find them painfully uncomfortable. Hard work varies dramatically from person to person. It fundamentally involves pushing beyond your familiar boundaries into territory that demands more from you than you'd naturally give.

Therefore, consider this carefully: What genuinely challenges you? What makes you want to quit or avoid the task altogether?

Because that's precisely where your greatest opportunity for meaningful personal development exists. The resistance you feel marks the path toward your most significant growth.

Since childhood, I’ve always longed for comfort.​

As a kid, I found joy in simple things: new toys, sweet treats, and lazy Sundays spent on the couch watching cartoons. As I grew older, my desires became more refined but stayed the same at their core. A cozy home in a quiet neighborhood, a reliable car with comfortable seats, enough financial stability to buy what I wanted without worrying about my bank balance, and the freedom to travel wherever I wanted without stressing about vacation days or flight costs.

In Indonesia, people like me are called Anak Ambis (short for “ambitious kid”). I eagerly read articles and watched videos about tech professionals in Silicon Valley, fascinated by their luxurious homes in the California hills, their garages filled with the latest Tesla models, and their endless workplace perks, from gourmet cafeterias to nap pods. I often imagined myself in their position, planning my own path toward that life, where comfort wasn’t just something to have, it was a carefully designed way of living.

But there’s a reason people say, Be careful what you wish for. This phrase has lasted for generations because it carries an important truth.

Comfort is addictive. It can also be deceptive in ways you only notice once you’re already caught in it. Like quicksand disguised as soft carpet, it keeps pulling you in, step by step, making you believe you’re on solid ground until you realize you’re not.

The trap of ultra convenience​

Life is designed to eliminate friction. It's an invisible luxury woven into our daily routines, one we rarely question. Need food? Order online. Need a ride? Tap for a Gojek or Grab. Need entertainment? Scroll through an infinite feed of personalized recommendations. The modern world has systematically removed the small inconveniences that once punctuated our existence, replacing them with seamless digital solutions.

And it's only going to get easier. The AI revolution is leading us toward a world where our needs will be anticipated before we express them. Smart assistants will plan our schedules, draft our emails, summarize our meetings, even tell us which purchases we should consider. Hurdles that once required effort like thinking, planning, making decisions will quietly dissolve. We're approaching a reality where cognitive friction itself becomes obsolete, where algorithms silently handle the mental tasks we once struggled through.

At work, AI enhanced tools have already transformed my daily tasks. My productivity skyrocketed, but at the same time, there's a looming sense that something essential is slipping away. The satisfaction of solving complex problems, the growth that comes from overcoming obstacles, the pride in mastering difficult skills. These experiences feel increasingly rare in an optimized world.

When everything becomes easy, what is left to fight for? What becomes of human ambition when the path of least resistance is always illuminated? Perhaps the greatest paradox of our time is that in eliminating life's difficulties, we may be eliminating the very things that make life meaningful.

The sneaky thief of fulfillment​

Dopamine is the brain's anticipation chemical. It doesn't bring happiness, it fuels our desire for happiness. It's the neurological carrot dangling before us, pushing us forward with promises it never quite fulfills.

Every time we get what we want, dopamine surges but only for a moment. Then it crashes, leaving us craving the next hit. This biochemical rollercoaster explains why satisfaction is so fleeting and why we're constantly chasing the next reward.

Have you ever posted on TikTok and gotten 40 likes? At first, it feels amazing. Then, one day, one of your videos goes viral and you hit 10,000 likes! Incredible! But from that point on, every new post that gets just 200 likes feels disappointing, despite being five times your original benchmark for success.

Your expectations recalibrate with frightening efficiency. The neural pathways that once lit up at small victories now barely flicker unless stimulated by increasingly dramatic rewards. You can no longer derive joy from what once thrilled you like those 40 likes, that small promotion, or that modest achievement have become invisible, unremarkable. The hedonic treadmill accelerates beneath your feet, forcing you to run faster and faster just to maintain the same level of satisfaction, leaving you breathless in pursuit of diminishing emotional returns. Each new benchmark becomes ordinary with alarming speed.

Extreme comfort doesn't make us happier but i think it makes us numb. When we eliminate all challenges and discomfort from our lives, we inadvertently strip away the very experiences that give life its depth and meaning. The absence of struggle creates a peculiar void where satisfaction should be. Like muscles that atrophy without resistance, our capacity for joy weakens without occasional friction. We construct frictionless environments of convenience and ease, only to find ourselves drifting through them with a vague, unsettling sense that something essential is missing. The contrast necessary to appreciate the good moments, the small victories over adversity that once punctuated our days with genuine satisfaction.

Seeking discomfort for real growth​

Recently, I've started experimenting with intentional discomfort as a pathway to personal development not the superficial kind that feels good in the moment but the challenging practices that initially make you question your sanity:

• Cold showers instead of hot ones, when every cell in my body protests the shock of cold water against warm skin.
• Intermittent fasting instead of always indulging hunger pangs when they first arise, teaching myself the difference between actual hunger and habitual eating patterns.
• Waking up at 5 AM instead of rolling out of bed last minute, even on weekends when the temptation to burrow deeper under the covers is nearly overwhelming.

It wasn't easy at first. My body and mind resisted fiercely complaining, bargaining, and sometimes outright rebelling against these self-imposed challenges. But here's what I discovered through persistence and pushing past that initial wall of resistance:

Discomfort breeds resilience. The more I leaned into these daily challenges, the stronger I felt mentally and physically. Even when my company mandated four days in the office instead of remote work, I reshaped my routine, adjusting my commute, meal prep, and exercise schedule and now, I actually feel better for having adapted rather than complained.

Effort is the price of growth. Nothing worthwhile comes without struggle, and I'm learning to embrace that fundamental truth every single day.

We need struggle, not for someone else’s approval, but for ourselves.​

Struggle is not something to be avoided but embraced, not for external validation or fleeting rewards, but for personal growth and fulfillment. In a world increasingly optimized for convenience, where effort is becoming optional and friction is systematically removed, we risk losing something essential which are our resilience, sense of purpose, and capacity for joy.

True satisfaction doesn’t come from comfort alone but from overcoming meaningful challenges and pushing beyond our limits. Instead of chasing easy wins or external markers of success, we should intentionally seek discomfort, whether through physical discipline, mental resilience, or personal transformation. It is through struggle, not avoidance, that we grow into stronger, more fulfilled versions of ourselves.

Don’t grind for money, promotions, or prestige. Those highs fade fast.

Don’t chase easy wins . They’ll leave you emptier than before.

Instead, lean into the process. Pursue challenges that make you a better version of yourself.

For me, that means training for a marathon, reading daily, and chasing personal transformation. For you, it might mean pursuing a dream job in Japan, deepening relationships, or facing fears.

Whatever it is embrace the discomfort.

Lately, I’ve been reflecting a lot on the challenges of middle management, particularly after a conversation with a former coworker. Even though this individual isn’t a middle manager, their insights about feeling constant pressure from leadership really got me thinking. They described how leadership consistently pushes for higher performance and demands results, often without understanding the realities on the ground. It struck me that, while they bear the weight of these demands from leadership, middle managers face a similar pressure but from multiple directions.

Being middle management is incredibly challenging. You are expected to balance pressure from all directions above, below, and even from the sides. My experience comes from the tech industry, but I believe these observations resonate across multiple sectors. Middle managers are the glue that holds organizations together, but they are often underappreciated and left to face unique struggles. Sandwiched between company leadership and employees, they must navigate conflicting demands, limited authority, and, at times, an overwhelming sense of isolation.

In middle management, you constantly find yourself wedged between the high expectations of leadership and the needs of your subordinates. You're tasked with executing strategies from top management while simultaneously motivating and managing your team to deliver results. At times, you may agree with your team’s frustrations and concerns, yet you're still forced to put on a smile and enforce decisions that come from above, even when you didn’t have a hand in making them. It’s not uncommon for middle managers to find out about tough decisions such as budget cuts, reassignments, or new initiatives at the last moment, just like the rest of their team. This disconnection fuels a feeling of being left out or even powerless, yet you’re still tasked with being accountable for the success of your team.

The Many Pressures Facing Middle Management​

Middle managers face a unique set of challenges that stem from being positioned between upper management and front-line teams. This intermediary space creates a range of pressures that require constant navigation.

1. Top-Down Pressure:​

At the core of middle management's struggles is top-down pressure. Leadership has high expectations for performance, efficiency, and goal achievement. Strategic decisions are made at the higher levels, but middle managers are often left in the dark, tasked with implementing orders without being part of the decision-making process. For example, Jack Zenger and Joseph Folkman, in their studies of employee engagement, found that middle managers, particularly those with five to ten years of experience, are often disillusioned because they feel undervalued. They’re given tasks to execute but have little say in policy-making, causing frustration and disengagement. Many employees under middle managers don’t realize that these managers are frequently just as frustrated with the decisions from the top.

Middle managers, being closest to the workplace's actual dynamics, often have the most practical knowledge of what will and won’t work. However, they frequently find themselves informed about decisions after the fact and left to carry them out without the support or resources necessary for success. They are, in essence, expected to deliver results from policies in which they had no say.

2. Bottom-Up Frustrations:​

On the flip side, middle managers bear the brunt of employee frustrations. For example, in the study by Zenger and Folkman, middle managers are often seen as the “face of management,” and when things go wrong or decisions don’t make sense, employees direct their complaints at these middle-tier leaders. Team members may not be aware that many of their objections are shared by their manager. As Anicich and Hirsh describe in their research on role-switching, middle managers are stuck in a “vertical code-switching” dilemma, where they must alternate between being an authoritative leader and a deferential subordinate, often within the same day.

This constant shifting takes a toll on mental and emotional well-being, leading to high levels of stress and emotional burnout. Middle managers are expected to maintain their team’s morale and motivation, even when upper management decisions leave them just as frustrated and powerless. They absorb complaints from below and directives from above with very little control of their own.

3. Side-to-Side Politics:​

Middle managers also face significant peer pressure. Departments within organizations often operate in silos, and middle managers must compete with their peers for resources, recognition, and strategic visibility. Anicich and Hirsh emphasize that middle managers experience high levels of stress not only from above and below but also from their same-level colleagues. Whether it's negotiating resources, competing for development opportunities, or even juggling inter-departmental expectations, the middle manager experiences ongoing tension with little relief.

In highly competitive corporate environments, especially fast-paced industries like tech, collaboration often turns into a tug-of-war among middle managers, each vying for more bandwidth, budget, or visibility with leadership. If one department doesn’t deliver, the middle manager will feel the pressure from their leadership, even when the root cause of the issue is entirely external.

The Emotional Labor Involved​

One of the most unseen aspects of middle management is its emotional toll. Julie Zhuo, who became a manager at Facebook (now Meta) at the young age of 25, recalls her early experience feeling like she was "in over her head." Zhuo reflects on the constant emotional labor required to support her subordinates while projecting confidence to her higherups. Like many middle managers, Zhuo initially believed that leadership meant projecting unwavering authority, but she found that approach ultimately alienating. Over time, she realized that successful management was much more about fostering collaboration than rigid top-down decision-making.

Middle managers often feel emotionally drained by the tension of mediating between the frustrations of their team and the demands of their leadership. Eric Anicich and Jacob B. Hirsh argue that middle managers experience high levels of "role conflict," where they're often caught between incompatible expectations. They must be empathetic to their subordinates while projecting confidence and competence to their superiors. This emotional balancing act places middle managers at a higher risk for burnout and mental health issues, including anxiety and depression, compared to employees at either end of the hierarchy.

The Isolation of Middle Management​

Perhaps the most pervasive struggle faced by middle managers is the feeling of isolation. Both Zhuo and Zenger highlight how middle managers are often excluded from key strategic discussions. Many decisions are made at the executive leadership level, leaving middle managers responsible for enforcing and explaining these decisions, often without fully understanding them or having the opportunity to weigh in beforehand. The result is an overwhelming feeling of disconnect. You're expected to deliver results, but you’re not always given the tools or knowledge necessary to do so.

A study cited by Anicich and Hirsh involving over 21,000 employees revealed that middle managers reported higher rates of anxiety, stress, and burnout than those in lower or upper-level positions. This is compounded by the fact that middle managers lack the same support networks that senior executives or frontline employees might have available. Zhuo advises that in her own experience, middle managers need more access to leadership development and strategic involvement to feel less isolated and more connected to the larger mission.

What Can We Do to Improve Middle Management?​

In my view, the traditional approach to managing middle managers just isn't cutting it anymore. The ongoing pressures and emotional strain that come from being sandwiched between leadership and teams need to be addressed. Here’s what I think can be done to alleviate some of these challenges.

1. Bring Middle Managers into Strategic Conversations Early​

From what I’ve seen, one of the primary reasons middle managers feel disengaged is simply because they’re left out of major strategic decisions. As Jack Zenger and Joseph Folkman point out, this disconnection makes their job ten times harder. If leadership wants to get the best out of middle managers, they need to be brought into the conversation from the start. Whether it’s helping to shape company policies or providing feedback on new initiatives, direction will stick far better if middle managers understand and feel a part of the “why” behind these decisions. Giving them this sense of ownership fosters better implementation and ensures strategic objectives are grounded in the realities of the workplace.

2. Recognize and Reward the Emotional Labor of Middle Management​

Let’s face it, emotional labor is a huge part of a middle manager’s role and often goes unrecognized. These managers aren’t just managing tasks and project outcomes, they’re balancing the emotional well-being of their teams while meeting deadlines.

But unfortunately, this aspect of the job is often perceived as transactional something that just comes with the territory. This is where companies need to step up. Recognize the complexity of the role. We need to do more than just acknowledge it, we need to actively reward it. And by reward, I don’t mean just compensation, but through recognition, support systems, and creating work cultures that reinforce the value they bring. Providing mental health resources is also crucial because it helps middle managers cope with the stress and ensures their emotional well-being, which in turn benefits the entire team.

Conclusion​

Middle management is often one of the toughest, most thankless jobs in any organization. These individuals are tasked with balancing competing expectations, processing complex emotions, and producing excellent results despite limited authority and frequent isolation. However, the good news is that these challenges are not set in stone they can be managed and improved upon.

To make middle management more effective and sustainable, we need to start by rethinking the role. Empowering them with decision-making autonomy, involving them earlier in strategic discussions, prioritizing their own leadership development, building supportive peer networks, and recognizing the weight of their emotional labor are all essential steps. While these changes require deliberate effort from leadership, they are essential if organizations want to get the most out of their middle-tier management.

As Jack Zenger and Joseph Folkman have pointed out, middle managers aren’t disengaged because they lack ability they are disengaged because they aren’t managed well. The sooner organizations realize the centrality and importance of middle management, the sooner they can align themselves for sustainable success. After all, when middle managers thrive, so does the entire organization from the frontlines to the C-level.

Recommended Reading Materials​

While making this article, I consulted multiple reading materials and papers to gain deeper insights into the challenges of middle management and strategies to overcome them. These resources provided me with useful frameworks and data that helped shape my understanding of this complex role.

1. How to Become a Better Manager
2. Why Being a Middle Manager Is So Exhausting
3. Why Middle Managers Are So Unhappy
4. A Guide for New Middle Managers
5. The Psychology of Middle Power: Vertical Code-Switching, Role Conflict, and Behavioral Inhibition

The Role of Frontend Engineers in the AI Era​

The integration of AI into the realm of frontend development, especially with the advent of technologies like GPT-4, is reshaping the landscape of the field. This change prompts a crucial inquiry: what will be the role of frontend engineers in the next decade? It's easy to jump to conclusions and view the rise of AI as a threat to traditional roles. However, a more nuanced perspective reveals that this is not about the end of frontend engineering, but rather an evolution. As AI takes over more routine, templated tasks, frontend engineers are presented with the opportunity to shift their focus. Their role will likely transform, emphasizing more on creative problem-solving, strategic planning, and complex task management that AI cannot easily replicate.

The Transformative Impact of AI on Frontend Engineering​

In the AI-augmented future, frontend engineers will find their roles becoming more integral to the creative and strategic aspects of web development. AI tools, like GPT-4, will handle the coding of basic layouts and structures, allowing engineers to concentrate on innovative design solutions, user experience enhancements, and intricate technical challenges. This shift will demand a broader skill set from frontend engineers, including a deeper understanding of AI capabilities and limitations. Their expertise will be crucial in guiding AI tools to achieve desired outcomes, blending technical proficiency with creative vision. As AI handles more of the repetitive work, frontend engineers can explore new technologies, experiment with emerging design trends, and push the boundaries of what's possible in web development.

A Collaborative Future​

Looking ahead, the collaboration between frontend engineers and AI is set to redefine the industry. This partnership will not only make the development process more efficient but also open doors to unprecedented levels of creativity and innovation. Frontend engineers will play a pivotal role in steering this collaboration, leveraging AI to optimize workflows and implement cutting-edge designs. Their role will evolve to be more strategic and creative, focusing on areas where human insight is irreplaceable. In essence, the future of frontend engineering in the AI era is not about replacement but augmentation, where human ingenuity and AI efficiency come together to create a more dynamic, innovative, and exciting field of web development.

Balancing the Excitement and Apprehensions of AI Advancements​

The pace at which AI is advancing in frontend development is undeniably exhilarating. This rapid progression brings with it a host of new tools and methodologies that promise to revolutionize the way websites and applications are designed and developed. As AI technologies become more sophisticated, they offer frontend developers the ability to automate mundane tasks, experiment with innovative design concepts, and optimize user experiences in ways that were previously impossible. This surge of innovation opens up a world of possibilities, allowing for more creative freedom and efficiency in the development process. The excitement around these advancements stems from the potential they hold to elevate the field to new heights, offering developers the tools to push the boundaries of what's technically and creatively feasible.

However, with this rapid evolution comes a certain level of apprehension. The introduction of AI in frontend development disrupts established practices, challenging the traditional roles and workflows of professionals in the field. Such disruption can be daunting, as it requires developers to adapt to new tools and rethink their approach to design and development. But rather than viewing this as a threat, it's more productive to see it as an opportunity for growth and learning. This period of transition provides a unique chance for frontend developers to expand their skill set, embrace new technologies, and position themselves at the forefront of the industry. By adapting to these changes and learning to harness the power of AI, frontend professionals can not only secure their place in the future of web development but also contribute to shaping that future in innovative and exciting ways.

Boosting Productivity with AI: A New Frontier for Frontend Engineers​

The integration of AI in frontend development is not about replacing engineers but enhancing their capabilities. With AI's assistance, frontend engineers can significantly boost their productivity. Tasks like quick prototyping and deploying landing pages could be accomplished with minimal intervention, allowing engineers to focus on more complex and creative aspects of development.

AI as a Catalyst for Innovation at Ruangguru​

At Ruangguru, we are particularly excited about harnessing AI to redefine frontend development. Our vision is to leverage AI not just as a tool but as a partner in innovation. By integrating AI into our design and product teams, we can expedite the prototyping process, deploy landing pages swiftly, and achieve a level of efficiency previously unimaginable. This is the innovation we are eager to bring to the forefront – a synergy of AI and human creativity that pushes the boundaries of what's possible in frontend development.

The real game-changer, however, was my encounter with AirPlay 2. This feature epitomizes why I've become enamored with Apple's offerings. I have an array of speakers in my home, including multiple HomePods and the Samsung Q700A, all AirPlay-enabled. AirPlay 2's multi-speaker functionality has transformed my home into a symphony of sound. The ease with which I can fill every corner of my house with music is nothing short of enchanting. It's not just the technology itself; it's how it enhances the atmosphere of my home, making it more welcoming and lively.

But there's more magic in the mix, especially with the latest iOS 17 features. When friends visit, they can effortlessly add tracks to the speaker's queue, enriching our gatherings with their musical tastes. This seamless integration and shared control are what make AirPlay 2 so special to me. It's not just a feature; it's an experience, a testament to the thoughtfulness Apple puts into creating an ecosystem that's not only functional but also brings people together. This is why I've fallen deeply in love with the Apple ecosystem – it's not just technology; it's technology that connects, entertains, and simplifies life in the most delightful ways.

Harmonizing Spaces with AirPlay's Multiroom Audio Magic​

The wonder of multiroom audio, particularly through AirPlay, has transformed my home into a vibrant, melodious realm, limited yet enchanting in its reach. In my space, the magic unfolds specifically within the confines of my office and kitchen. Imagine classical tunes gently wafting through my office as I work, while upbeat pop rhythms pulse in the kitchen. This dual-zone symphony, seamlessly managed via AirPlay, creates a delightful juxtaposition of moods, catering to the different atmospheres of each room. The ability to play a podcast in the kitchen, keeping me entertained as I cook, and then effortlessly switch to tranquil instrumental music in my office is more than just a convenience – it's a daily luxury.

The charm of this setup lies in its incredibly intuitive control. AirPlay allows me to effortlessly orchestrate the audio experiences of these two spaces with just a few taps on my Apple device. Whether I'm syncing the two rooms to fill my home with a uniform melody or curating distinct soundtracks for each, the process is remarkably straightforward. This seamless control makes the system feel like an extension of my own senses, responding fluidly to my commands. Although my setup is limited to the office and kitchen, it never feels restrictive. Instead, it offers a perfect blend of functionality and enjoyment, showcasing how AirPlay's multiroom audio capability can transform even a segment of a home into a harmonious, melodious sanctuary.

Additionally, the multiroom audio feature through AirPlay isn’t just about playing different tunes in separate rooms; it’s equally adept at unifying the audio experience across spaces. On occasions when the mood strikes, I can have the same melodious song or an engaging podcast playing simultaneously in both my office and kitchen. This unified auditory experience creates a sense of cohesion and continuity throughout my home, making the transition from one room to another a seamless journey through the same sonic landscape. It’s almost like the music is following me, providing a consistent backdrop to my daily activities, whether I’m deep in work or bustling about in the kitchen. This ability to synchronize audio across rooms with such ease is a testament to the sophisticated yet user-friendly design of AirPlay’s multiroom capabilities.

Transform Your Gathering with iOS 17 Shared Playlists and Whole-Home Sound​

The introduction of iOS 17 has brought a delightful twist to the way music animates gatherings in my home. Now, anyone with an iPhone and a taste for tunes can contribute to the musical atmosphere. This shared music feature, in harmony with AirPlay's multiroom audio capability, has essentially transformed my living space into a dynamic, crowd-sourced jukebox.

Imagine this: friends walking in, iPhones in hand, each eager to share their favorite tracks. With a few simple taps, they add their chosen songs to the mix. This isn’t just about playing music; it’s about creating a collective musical journey, where each person's preferences contribute to the evening’s soundtrack. The beauty lies in the spontaneity and diversity of the playlist that evolves as the night progresses.

Coupled with the multiroom audio setup, this feature elevates the party experience to new heights. As each new song queues up, it doesn't just play in one room; it resonates throughout the entire house. Whether you're in the throes of a lively conversation in the living room or grabbing a snack in the kitchen, the music follows, unifying the party across different spaces. It's like having a personal DJ who understands the vibe of the room and tailors the music to fit the mood, except the DJ is a collective of your friends' musical tastes.

This isn't just a technological advancement; it's a social one. iOS 17's shared music feature, combined with AirPlay's multiroom audio, doesn't just change how we listen to music at parties; it changes how we interact, share, and enjoy moments together. It’s a testament to how technology can not only connect devices but also people, making every gathering a unique and memorable experience.

Unveiling the Technical Mastery of AirPlay 2​

AirPlay 2, unveiled by Apple in 2017 and enhanced for multi-room audio capabilities with iOS 11.4, stands as a testament to modern streaming technology. This sophisticated protocol suite is primarily designed for streaming audio, but it also supports video and photos, showcasing its versatility. At its core, AirPlay 2 relies on Apple's Bonjour technology for service discovery, employing multicast DNS (mDNS) and the zeroconf protocol. This allows AirPlay devices to discover each other seamlessly over a shared network, paving the way for effortless connection and synchronization.

The transmission of audio data in AirPlay 2 utilizes the Real-Time Protocol (RTP), a foundation that ensures reliable delivery of streaming content. The RTP packets, carrying the audio data, are encrypted using the ChaCha20-Poly1305 AEAD algorithm, a choice reflecting Apple's commitment to security. During the streaming setup, the sender shares the encryption key with the receiver through a SETUP RTSP request, establishing a secure channel for audio transmission. This encryption mechanism is vital, not just for real-time audio streaming used by platforms like Spotify and YouTube, but also for buffered audio streams, which are typical in Apple Music, where each RTP packet is methodically prefixed with its size.

Authentication in AirPlay 2 is layered and versatile, offering different methods based on the receiver's capabilities. The system primarily supports MFi (Made for iPhone/iPod/iPad) authentication and FairPlay authentication, with the older RSA method now being phased out. This approach to authentication ensures that only authorized devices can access the streaming content, adding an extra layer of security to the user's experience. In scenarios where authentication bits are not set, AirPlay 2 defaults to an error state, underscoring the necessity of authentication in maintaining a secure streaming environment.

AirPlay 2's approach to audio streaming is not just about secure transmission but also about offering an enriched user experience. The technology supports both real-time and buffered audio streaming, catering to different use cases and preferences. Real-time streaming is favored for immediate playback, while buffered streaming, where data is sent in advance, allows for a more stable and uninterrupted listening experience, especially beneficial for high-quality audio content. This flexibility in streaming methods ensures that AirPlay 2 can provide a smooth and high-quality audio experience regardless of the network conditions or the type of content being played.

In conclusion, AirPlay 2 is a remarkable blend of advanced streaming protocols, robust security measures, and user-centric features. Its ability to seamlessly integrate into the Apple ecosystem, while offering a secure, versatile, and high-quality streaming experience, marks it as a pivotal technology in the realm of digital media. Whether it's for multi-room audio setups or streaming your favorite show, AirPlay 2's technology ensures that your media is not only easily accessible but also delivered with exceptional fidelity and security.

AirPlay 2 and the Pinnacle of Audio Quality​

AirPlay 2 elevates the standard of audio streaming, boasting an impressive array of supported audio formats that cater to high-fidelity sound enthusiasts. The technology embraces a comprehensive range of formats, from the standard PCM to the more sophisticated ALAC (Apple Lossless Audio Codec), ensuring that every nuance and detail of the original recording is preserved. This range includes PCM formats with sample rates from 8000 Hz to 48000 Hz and bit depths of 16 or 24 bits, offering versatility for different audio qualities. Additionally, support for ALAC at both 44100 Hz and 48000 Hz in 16 and 24 bits ensures that lossless audio can be transmitted without any compromise in quality. This extensive support of audio formats underlines Apple’s commitment to delivering a superior auditory experience, making AirPlay 2 an ideal choice for audiophiles and casual listeners alike.

Moreover, AirPlay 2's capability extends to accommodate various AAC (Advanced Audio Coding) formats, including AAC-LC and AAC-ELD, which are known for their efficiency in streaming high-quality audio at lower bit rates. This makes AirPlay 2 adaptable for different network conditions, ensuring a consistent delivery of high-quality sound even in less than optimal streaming environments. The inclusion of the OPUS format, particularly beneficial for voice transmissions, further diversifies AirPlay 2's audio format repertoire. This meticulous attention to supporting a wide range of audio formats demonstrates AirPlay 2's dedication to delivering an exceptional listening experience, where every beat, note, and tone is conveyed with the utmost clarity and richness.

Our focus will be on leveraging the capabilities of GitHub Actions, including setup of QEMU for emulation and Docker Buildx for building images, along with caching strategies and security practices for Docker Hub integration. This guide aims to equip developers with the knowledge and tools needed to streamline their CI/CD pipelines, ensuring seamless deployment across varied computing environments.

name: Deploy Production
on:
  workflow_dispatch:
jobs:
  build-and-push-docker:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      - name: Cache Docker layers
        uses: actions/cache@v2
        with:
          path: /tmp/.buildx-cache
          key: ${{ runner.os }}-buildx-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-buildx-
      - name: Login to Docker Hub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Build and push
        uses: docker/build-push-action@v2
        with:
          context: .
          file: ./Dockerfile
          push: true
          tags: agasdrm/blog:latest,agasdrm/blog:${{ github.run_number }}
          platforms: linux/amd64,linux/arm64/v8
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache

Overview of Docker and GitHub Actions​

Docker has revolutionized how we build, share, and run applications by enabling them to run in isolated containers. These containers package up code and all its dependencies, ensuring that the application runs quickly and reliably in various computing environments.

GitHub Actions, on the other hand, is a CI/CD (Continuous Integration/Continuous Delivery) platform that allows you to automate your build, test, and deployment pipeline. It is seamlessly integrated into GitHub, providing an efficient way to apply DevOps practices without leaving the GitHub ecosystem.

The Importance of Multi-Architecture Builds​

With the growing diversity in computing hardware, it's become crucial to ensure that applications can run on different architectures. ARM64 and AMD64 are two prevalent architectures in use today. ARM64 is commonly found in mobile devices, newer desktops, and servers, while AMD64 (x86_64) is widely used in traditional laptops and desktops. Supporting both architectures ensures that your application can reach a wider audience and function in a broader range of environments.

Prerequisites​

Before diving into the process, ensure you have the following:

• A GitHub account - for accessing GitHub and using GitHub Actions.
• A Docker Hub account - for storing and managing your Docker images.
• Basic understanding of Docker - familiarity with Docker concepts like images, containers, and Dockerfiles.
• Basic understanding of Git and GitHub - knowledge of repositories, branches, commits, and pulls.
• Access to a code editor - like Visual Studio Code, Sublime Text, or any editor of your choice.

Understanding the Dockerfile​

A Dockerfile is a text document containing all the commands a user could call on the command line to assemble an image. Using a Dockerfile, Docker can automatically build an image that includes your application and its dependencies.

Key Components of a Dockerfile​

• FROM: Specifies the base image from which you are building.
• RUN: Executes any commands in a new layer on top of the current image.
• COPY: Copies files or directories from your project into the Docker container.
• CMD: Provides defaults for executing a container.
• EXPOSE: Informs Docker that the container listens on specific network ports at runtime.
• ENV: Sets environment variables.

Each instruction in a Dockerfile creates a layer in the image. When you change the Dockerfile and rebuild the image, only those layers that have changed are rebuilt. This is part of what makes images so lightweight, small, and fast when compared to other virtualization technologies.

In the next section, we will dive deeper into setting up our GitHub Actions workflow to automate the building and publishing of our Docker images for ARM64 and AMD64 architectures.

Understanding GitHub Actions​

GitHub Actions is a powerful automation tool that integrates deeply with GitHub, providing a platform for automating software workflows. It's particularly useful in implementing Continuous Integration (CI) and Continuous Delivery (CD) processes directly within your repository.

What are GitHub Actions?​

• Automated Workflows: GitHub Actions allows you to create custom software development life cycle (SDLC) workflows directly in your GitHub repository.
• Event-Driven: These workflows can be triggered by a variety of events within GitHub, such as push, pull requests, issue creation, or even a manual trigger.
• Customizable: GitHub Actions provides a wide range of built-in actions, but you can also create and share your own actions or use actions shared by the GitHub community.
• Containers and Virtual Environments: Actions can run in containers or virtual environments that you specify, ensuring consistency across different runs.

CI/CD with GitHub Actions​

In Continuous Integration (CI), code changes are automatically tested and merged into a central repository. Continuous Delivery (CD) extends CI by automatically deploying all code changes to a testing or production environment. GitHub Actions facilitates both CI and CD by automating these processes, enhancing software quality and development speed.

Workflow Syntax Explanation​

GitHub Actions utilizes workflows, which are defined by a YAML file stored in your repository's .github/workflows directory. These workflows specify the actions to be executed based on defined events.

Understanding the workflow_dispatch Trigger​

• Manual Trigger: The workflow_dispatch event allows you to manually trigger a workflow run. This is useful when you want to have control over when to run the workflow, as opposed to automatic triggers like push or pull requests.
• Inputs: You can define inputs for the workflow_dispatch trigger, allowing you to pass parameters to the workflow at runtime.

name: Deploy Production
on:
  workflow_dispatch:
    inputs:
      environment:
        description: 'Deployment Environment'
        required: true
        default: 'staging'

In this example, the workflow_dispatch is configured with an input named environment. When triggering the workflow manually, you can specify the environment to which you want to deploy.

Workflow Anatomy A typical workflow file consists of the following key sections:

name: A name for your workflow.
on: The event that triggers the workflow.
jobs: A set of jobs that the workflow will execute.
steps: Individual tasks that run within a job.
runs-on: Specifies the type of machine to run the job on.
uses: Refers to an action to execute as part of a step.

Preparing for Docker Build​

Before diving into the actual Docker build process, it's crucial to understand the role of QEMU in this workflow and how it's set up using GitHub Actions.

What is QEMU?​

QEMU (Quick Emulator) is an open-source emulator that performs hardware virtualization. It is a key tool in the process of running software that is built for one type of processor architecture on another. This capability is particularly important when dealing with Docker images intended for multiple architectures.

Role of QEMU in Docker Builds​

• Emulation of Architectures: QEMU allows us to emulate different processor architectures, such as ARM64, on machines that have a different architecture (like AMD64). This is vital for building Docker images that are meant to run on multiple architectures.
• Cross-Platform Compatibility: By using QEMU, we ensure that the Docker images built are compatible across different architectures, making our application more versatile and accessible.

Setting Up QEMU in GitHub Actions​

The docker/setup-qemu-action@v1 action is used to set up QEMU in the GitHub Actions runner environment. This action simplifies the process of installing and configuring QEMU for our build process.

- name: Set up QEMU
  uses: docker/setup-qemu-action@v1

In the workflow file, this step ensures that QEMU is correctly set up and ready to enable emulation for different architectures during the Docker build process.

Docker Buildx Setup​

Docker Buildx is an extended build feature of Docker that enables the creation of multi-architecture images.

Understanding Docker Buildx​

• Extended Features: Docker Buildx extends the capabilities of the standard Docker build commands, allowing for more advanced features, including building for multiple architectures from a single platform.
• Simplifying Multi-Arch Builds: With Buildx, you can easily build images for architectures like ARM64 and AMD64, even if your build environment is different.

Setting Up Docker Buildx in GitHub Actions​

The docker/setup-buildx-action@v1 action in GitHub Actions is used to set up Docker Buildx in the workflow.

- name: Set up Docker Buildx
  uses: docker/setup-buildx-action@v1

By including this step in our workflow file, we enable the GitHub Actions runner to utilize Docker Buildx for building multi-architecture Docker images. This step is critical in ensuring that our Docker images are built correctly for the desired architectures.

Caching for Efficiency in Docker Builds​

Efficient Docker builds often require a smart caching strategy. This section delves into the use of caching in Docker builds with GitHub Actions, particularly focusing on the actions/cache@v2 action.

Caching Docker Layers​

Caching is crucial in reducing build time, especially when dealing with Docker images. Docker builds can be time-consuming, primarily due to the downloading of image layers and rebuilding steps. By caching, we can significantly decrease this time.

How Caching Works in Docker​

• Layer Caching: Docker builds images in layers. By caching these layers, Docker can reuse them in subsequent builds, avoiding the need to rebuild identical layers.
• Impact on Build Times: Caching can drastically reduce build times, making your CI/CD pipeline more efficient.

Implementing Caching with actions/cache@v2​

GitHub Actions provides a caching action, actions/cache@v2, which can be used to cache dependencies and build outputs to improve workflow execution time.

- name: Cache Docker layers
  uses: actions/cache@v2
  with:
    path: /tmp/.buildx-cache
    key: ${{ runner.os }}-buildx-${{ github.sha }}
    restore-keys: |
      ${{ runner.os }}-buildx-

In this snippet, the caching action is configured to cache the Docker layers.

Cache Keys and Paths​

Understanding how to effectively use cache keys and paths is vital for maximizing the efficiency of your caching strategy.

Defining Cache Paths​

• Cache Location: In our workflow, the cache is stored in /tmp/.buildx-cache. This path is where Docker Buildx stores its cache data.

Cache Keys​

• Key Generation: The key for the cache is a unique identifier. In our example, it's a combination of the runner's operating system, buildx, and the SHA of the commit (${{ github.sha }}). This ensures that each build has its unique cache.
• Restoration of Cache: The restore-keys option provides a list of keys to try when restoring the cache. In our case, it attempts to find the most recent cache that matches the specified pattern.

Benefits of Effective Caching​

• Reduced Build Times: By reusing the cached layers, Docker can skip rebuilding unchanged layers, significantly reducing the overall build time.
• Improved Efficiency: Efficient caching leads to faster CI/CD pipelines, which is crucial for agile development and quick deployment cycles.

Docker Hub Integration in GitHub Actions​

Integrating Docker Hub with GitHub Actions is a key step in automating the Docker image build and push process. This section covers the essential steps for secure Docker Hub login and handling secrets within GitHub Actions.

Docker Hub Login​

Logging into Docker Hub from GitHub Actions is a crucial step to push the built images to your Docker Hub repository. This is where the docker/login-action@v1 action comes into play.

Importance of Secure Login​

• Security: Securely logging into Docker Hub ensures that your credentials are protected and your Docker Hub account is safe from unauthorized access.
• Automation: Automated login is essential for seamless CI/CD pipelines, enabling the automated pushing of Docker images to Docker Hub without manual intervention.

Implementing Docker Hub Login​

- name: Login to Docker Hub
  uses: docker/login-action@v1
  with:
    username: ${{ secrets.DOCKERHUB_USERNAME }}
    password: ${{ secrets.DOCKERHUB_TOKEN }}

In this step, the docker/login-action@v1 action is used to log into Docker Hub. The credentials are provided through GitHub secrets to ensure security.

Handling Secrets​

GitHub secrets provide a secure way to store and use sensitive information, like Docker Hub credentials, in your GitHub Actions workflows.

What are GitHub Secrets?​

• Security Feature: Secrets are encrypted environment variables that you can create in any repository or organization in GitHub. They are not exposed in log files or to unauthorized users.
• Usage in Workflows: Secrets can be used in GitHub Actions workflows to securely manage sensitive data like API keys, passwords, and Docker Hub credentials. Configuring and Using Secrets
• Adding Secrets: Secrets can be added to your GitHub repository under the settings tab. Once added, they can be referenced in your workflow file. Referencing Secrets in Workflows: In the Docker Hub login step, the username and password are referenced as ${{ secrets.DOCKERHUB_USERNAME }} and ${{ secrets.DOCKERHUB_TOKEN }}. This allows the workflow to use these credentials without exposing them.

Benefits of Using Secrets​

• Enhanced Security: By using secrets, sensitive information is kept secure and is not exposed in your workflow files or logs.
• Flexibility: Secrets can be easily updated in the GitHub repository settings without changing the workflow files.

Building and Pushing the Docker Image​

The culmination of our GitHub Actions workflow is the building and pushing of the Docker image. This section provides a detailed walkthrough of this process, highlighting the use of docker/build-push-action@v2 and explaining image tagging and multi-architecture support.

Building the Docker Image​

Building the Docker image is a critical step in the workflow. The docker/build-push-action@v2 action simplifies this process within GitHub Actions.

Using docker/build-push-action@v2​

This action enables us to build and push the Docker image to a registry like Docker Hub. It supports advanced features like multi-platform builds and caching.

- name: Build and push
  uses: docker/build-push-action@v2
  with:
    context: .
    file: ./Dockerfile
    push: true
    tags: user/myapp:latest, user/myapp:${{ github.run_number }}
    platforms: linux/amd64,linux/arm64/v8
    cache-from: type=local,src=/tmp/.buildx-cache
    cache-to: type=local,dest=/tmp/.buildx-cache

In this configuration:

• context specifies the build context (typically the root of the repository).
• file points to the Dockerfile.
• push set to true enables the pushing of the image to the registry.
• tags defines the tags for the built image.
• platforms lists the target architectures.
• cache-from and cache-to handle caching to speed up the build process.

Tagging and Multi-Architecture Support​

Tagging images correctly and supporting multiple architectures are crucial for a robust Docker deployment.

Tagging Images​

• Purpose of Tags: Tags are used to specify different versions of your Docker images. It's a best practice to tag your images with meaningful identifiers, like version numbers or environment names.
• Tag Syntax in GitHub Actions:

tags: user/myapp:latest, user/myapp:${{ github.run_number }}

Here, we use two tags - latest for the most recent build and a tag with the GitHub run number for specific builds.

Multi-Architecture Support​

Supporting multiple architectures ensures that your Docker images can run on various hardware platforms.

• Specifying Architectures: In the platforms field of the docker/build-push-action@v2, we specify the target architectures.

platforms: linux/amd64,linux/arm64/v8

• Benefits: This approach ensures that the built Docker images are compatible with both AMD64 and ARM64 architectures, broadening the usability of your application.

Conclusion and Best Practices​

We've now reached the end of our comprehensive guide on building and pushing multi-architecture Docker images using GitHub Actions. Let's recap the steps we've taken and go over some best practices and troubleshooting tips.

Review of the Process​

Our journey through this tutorial involved several key steps:

1. Introduction to Docker and GitHub Actions: We began by understanding the basics of Docker, GitHub Actions, and the need for multi-architecture builds.
2. Setting Up the Workflow: We then explored the workflow syntax in GitHub Actions and how to trigger workflows.
3. Environment Preparation: Setting up QEMU and Docker Buildx were crucial steps for cross-platform Docker builds.
4. Caching for Efficiency: Implementing caching using actions/cache@v2 improved our build times significantly.
5. Docker Hub Integration: We securely logged into Docker Hub using GitHub secrets, ensuring a secure pipeline.
6. Building and Pushing Images: Finally, we used docker/build-push-action@v2 to build and push images, tagging them appropriately and supporting multiple architectures.

Best Practices​

Following best practices can significantly enhance the efficiency and security of your Docker builds and GitHub Actions workflows.

Docker Builds​

• Use Multi-Stage Builds: This helps keep your images small and efficient.
• Leverage Caching: Proper caching can drastically reduce build times.
• Keep Images Secure: Regularly update and scan your images for vulnerabilities.

GitHub Actions​

• Keep Workflows Simple: Complex workflows are harder to maintain and debug.
• Secure Secrets: Always use GitHub secrets to handle sensitive information.
• Document Your Workflows: Clear documentation helps maintain and understand workflows.

Troubleshooting Tips​

Here are some common issues and tips for troubleshooting Docker builds and GitHub Actions workflows.

Docker Builds​

• Build Failures: Check for syntax errors in your Dockerfile. Ensure all necessary files are included in the build context.
• Long Build Times: Investigate caching strategies and consider optimizing your Dockerfile for better layer caching.

GitHub Actions​

• Workflow Errors: Review logs provided by GitHub Actions for specific error messages. Ensure all steps are correctly configured.
• Secrets Not Working: Double-check secret names in the repository settings and their references in the workflow file.

With this knowledge, you're now equipped to create efficient, automated Docker workflows using GitHub Actions. Happy coding!

The Origin Story​

Every great adventure starts with a vision. Mine was built with Docusaurus – a fantastic platform that makes documentation a breeze but also doubles up as a brilliant blog framework. It’s like having a Swiss Army knife, but for blogging. Neat, right?

Now, I must confess, I’m a bit of a neat freak when it comes to my digital life. So, naturally, my blog was dockerized. Think of it like packing your entire house into a single, magical suitcase – ready to move anywhere, anytime. This nifty trick made the migration process smoother than my morning espresso.

A Raspberry Homecoming​

Now, let’s talk about the star of our show – the Raspberry Pi 4. This tiny yet mighty device transformed from a hobbyist's plaything into the powerhouse behind my blog. Hosting a blog on a Raspberry Pi? Sounds crazy, right? But that's exactly what I did. In the quiet corner of my home, this little gadget hums with the life of my blog, proving that you don't need a massive server to make a big impact on the digital stage.

Tunnels and Clouds​

Navigating the complexities of the internet, especially when hosting a website or blog, requires a secure and reliable connection. This is where Cloudflared's Argo Tunnel comes into play in my setup. It's not just any regular internet connection – it's a fortified, encrypted pathway designed to ensure secure and efficient communication between my Raspberry Pi and the wider internet. Imagine a secret underground tunnel, hidden away from the chaos of surface traffic, providing a safe and speedy route for my data. This setup guarantees that my blog remains accessible and secure, avoiding potential cyber threats and ensuring uninterrupted service to my readers.

The domain of a blog is more than just a web address; it’s an integral part of its identity, its brand. For my blog, www.agas.dev is that digital signature, a unique identifier in the vast sea of the internet. Linking this domain to my Raspberry Pi hosted blog was an essential step in establishing its new home. By routing www.agas.dev through the Cloudflared Argo Tunnel, I’ve created a direct and efficient pathway for traffic to reach my blog. It’s akin to setting up a bespoke postal service, one that ensures prompt and secure delivery of content – my digital letters, if you will – to my audience without any detours or delays.

This journey of migration is not just about moving a blog from one hosting environment to another; it's about reimagining what's possible with technology. It's a blend of the old and the new – the tried and tested Raspberry Pi, a favorite among tech hobbyists, coming together with modern solutions like Cloudflared's Argo Tunnel to create a robust, home-based web hosting environment. This blend of technology demonstrates that with the right tools and a bit of ingenuity, you can create a powerful digital presence without relying on traditional, often expensive, hosting solutions.

In essence, this project is a testament to the power of small-scale, home-based technology solutions in a world that's increasingly moving towards decentralization and personal control over digital assets. Hosting my blog on a Raspberry Pi 4, connected securely to the internet through Cloudflared's Argo Tunnel, and accessible via a personalized domain, embodies a shift in how we approach web hosting and content delivery. It’s a shift towards more personal, customizable, and cost-effective solutions, proving that sometimes, the best way to move forward is by bringing things closer to home.

Docker, but Easier​

Handling Docker can be a bit like juggling digital cats. To simplify this, I turned to Portainer. It’s a graphical interface that brings simplicity and clarity to managing Docker containers. With Portainer, I could easily update, modify, and maintain my blog’s backend without diving into the command-line abyss. It’s like having a sleek, user-friendly dashboard for your car, making driving (or in this case, managing a blog) a breeze.

Counting the Costs​

Running a blog doesn't have to break the bank, and my setup is a testament to that. By moving to a Raspberry Pi hosted at home, I've slashed hosting costs without sacrificing performance. For a blog with modest traffic like mine, this is a game-changer. It's like discovering a secret recipe that makes your favorite dish not just tastier but also cheaper to cook.

You Are Here!​

If you're reading this, you've already become a part of this story. Whether you're accessing my blog directly from my Raspberry Pi server or via Cloudflare's cached version, you're experiencing the fruits of this home-grown, tech-savvy labor. Each click, each visit, is a nod to this unique journey from cloud-based to couch-based blogging.

One of the most notable features of the Navigation router is its seamless integration with React and React Native. Developers no longer need to worry about using different routing libraries for web and mobile development, which streamlines the development process and saves time.

Additionally, the Navigation router provides a seamless user experience. The navigation is 100% native on Android and iOS, ensuring that users feel comfortable and familiar with the navigation elements. On the other hand, developers using React can have whatever URLs they want, allowing them to build their UI as they see fit.

The Navigation Router's Unique Approach​

The Navigation Router offers a more native feel to web and mobile applications as it avoids using a single View in its codebase, rendering everything to its native counterpart. Additionally, the Router's use of a CoordinatorLayout provides native collapsing Toolbars and TabBars on Android, with the TabBar component being 100% native on both platforms.

In keeping with its focus on React, the Navigation Router makes every UI element a component. This includes TabBar and NavigationBar components, which can be easily updated using props in the same manner as other React components. Each scene has its own Navigation context, preventing the router from pushing the same scene twice even when double-tapping.

The Navigation Router's focus on the web also ensures that every single navigation is a URL. This provides automatic hyperlinks on all platforms, including for back navigation. Developers can customize the URLs as desired without changing any code, passing strongly-typed data without the need to parse to or from strings.

Overall, the Navigation Router's focus on providing a native, React, and web-friendly experience makes it an innovative choice for developers seeking to create seamless, high-performance applications across multiple platforms.

Using The Navigation Router on React Native.​

If you're a developer looking to create a high-performing, fully-native navigation experience for your React Native app, the Navigation router is the solution you've been searching for. This powerful library offers an out-of-the-box experience that rivals that of building a native app without React Native. With its TabBar component rendering to the native UITabBarController from UIKit or the BottomNavigationView from Android's Material Design library, users will feel right at home within your app.

To take advantage of the Navigation router's capabilities, it's important to note that it contains native code. Therefore, to create your application, you must use react-native init or a custom development build of Expo. But with its powerful features and seamless integration, the Navigation router is well worth the effort.

Quick Getting Started​

Install the required packages in your React Native project:

npm install navigation navigation-react navigation-react-native

cd ios && pod install && cd ..

The Navigation router is comprised of core utilities that are used by navigators to build the navigation structure for your app. Once you've completed this initial setup, you'll be ready to start writing code with the Navigation router.

Wrapping your app in NavigationHandler​

import React from 'react';
import {StateNavigator} from 'navigation';
import {NavigationHandler} from 'navigation-react';
import {NavigationStack} from 'navigation-react-native';

const stateNavigator = new StateNavigator([]);

const App = () => (
  <NavigationHandler stateNavigator={stateNavigator}>
    <NavigationStack></NavigationStack>
  </NavigationHandler>
);

export default App;

To ensure optimal performance in your React Native app, it's recommended that you only use the NavigationHandler once at the root level. Nesting multiple NavigationHandler components should be avoided unless there is a specific use case for doing so. With this in mind, you're now ready to build and run your app on your device or simulator.

Pro Tips​

To incorporate Material Design 3 into your Android app, you can configure a Material3 theme in styles.xml. Here's an example:

<style name="AppTheme" parent="Theme.Material3.DayNight.NoActionBar">

Enabling Fabric (The New Architecture)​

Enabling the new React Native architecture during pod install is the only difference in setup from the previous architecture.

cd ios && RCT_NEW_ARCH_ENABLED=1 pod install && cd ..

Summary​

The Navigation router is a revolutionary library that empowers developers to take control of their app's UI design by offering a groundbreaking approach to scene-based navigation for both React and React Native.

The Navigation router's integration with React and React Native makes it an innovative choice for developers seeking to create seamless, high-performance applications across multiple platforms. Overall, the Navigation router's unique features and powerful capabilities make it a must-have tool for developers looking to create high-performing and fully-native navigation experiences for their React Native apps.

The Navigation router is a worthy alternative to the popular React Navigation library. Its unique approach to scene-based navigation and native feel make it an innovative choice for creating high-performance apps across multiple platforms.

BrainAcademy build with React Native running on our existing native app.

Early last year, a small group of developers at Ruangguru began studying the feasibility of implementing React Native. React Native allows you to create iOS and Android apps in JavaScript using the declarative programming language of React. This leads in more concise, easier-to-understand code, faster iteration without a build cycle, and easy code sharing between platforms. You can ship faster and focus on the things that count, making your app look and feel fantastic.

Since its initial release, React Native has come a long way. It is being used not only in Facebook and Instagram, but also in a wide range of other businesses, from Fortune 500 corporations to hot new startups.

The Reasons​

We began investigating the use of React Native in early 2022 to allow product teams to release features faster through code sharing and faster iteration speeds, using techniques like Live Reload and Hot Reloading that remove compile-install cycles. As a result, the product engineering team is now able to deploy the same functionality on iOS and Android with a single codebase, and perhaps in the future, we will be able to ship the same React Native codebase to the web. So with React Native the App feature will be written only once.

Ruangguru universal frontend. A teaser for our single codebase multiplatform solution.

The feature created with React Native will be injected into the app at the same time working side by side with the existing native code. The cross-platform feature is developed and maintained by a single team. So there’s no longer a large panel of native engineer experts involved.

The Challenges​

When you integrate React Native into an existing native project, you may experience obstacles and additional effort that you do not encounter when you start from scratch. With this in mind, we chose to begin investigating these challenges by porting the most appropriate part of Ruangguru apps: the Brain Academy module.

Slow Communications Between Native and React Native​

If you look at the React Native layout, you’ll notice that it uses a Bridge to connect with native modules, which often results in a queue because these two sides are unaware of each other. Such a process may result in performance constraints that have a detrimental impact on the user experience.

However, with the introduction of the React Native re-architecture, the Bridge will be gradually phased out and replaced by a new component known as the JavaScript Interface (JSI). Ruangguru will utilize JSI to facilitate communication between the Native and Javascirpt Realms to overcome this challenge.

Start Up Performance​

Previously, React Native had a significant startup overhead due to the need to inject the JavaScript bundle into JavaScriptCore (the VM used by React Native on both iOS and Android) and instantiate native modules and view managers. This problem is dramatically reduced in 2022 thanks to the Hermes engine. Based on our testing the initial loading for React Native is very minimal.

Android Bundle Size​

The first issue was adding React Native as a dependency into an existing App would significant impact the binary size. But this would not only increase the binary size, but would also have a significant impact on the number of methods count. We ended up pulling in only the React Native pieces we required at the time and building our own implementations for those that relied on libraries we didn’t want to use.

However, this solution still adds megabytes to the app binary size. As a result, we will include the React Native module with the Dynamic Features Module. Because we made React Native an on-demand module, users will only need to download the React Native module when they need to use the feature. This significantly reduces the app install size.

Utilizing The New React Native Architecture​

This section will discuss how Ruangguru uses JSI, a component of the new React Native architecture, to make navigation events, sharing data, and resource synchronization considerably faster than before.

The Old Architecture

The Javascript and Main threads do not communicate directly under the old architecture, but rely on the Bridge. The existence of a serializable bridge results in wasteful copying rather than memory sharing between threads. Because everything runs asynchronously, there is no guarantee that the data will arrive on time or at all. Larger data transfers may be extremely slow. Native module features that need synchronous data access cannot be fully utilized.

The New Architecture

The new architecture completely removed the Bridge. Javascript can now store references to C++ Host objects and call their methods. Time-sensitive tasks, such as user interaction with the app, can be carried out synchronously, eliminating the need for serialization and deserialization during runtime.

Next Generation Native Module That Ruangguru Uses.

All Native Module that Ruangguru uses is using JSI the backbone of React Native’s new architecture.

Initializing a JSI module.

The process of initializing a JSI module differs from that of an ordinary React Native Module. We have an install method here that will be called once from the JavaScript realm to initialize the “connection.”

The JavaScript realm must first check to see if the module is appropriately installed; if the module is not present, the JavaScript realm will invoke the install method.

jsiRuntime.global().setProperty method.

Because we’re utilizing JSI, we’ll utilize the install method to initialize the native function we want to share between the Native and JavaScript realms. As you can see in the code, we use the jsiRuntime.global().setProperty method to share the function between the two realms.

So finally, to use this on the JavaScript Realm, we can simply use the method like the picture above. So, in short, with the new architecture, we eliminate the need for the old react native bridge, eliminating the waiting time for the Asynchronous method to resolve, and enable instant communication between the Native and JavaScript realm.

Results​

React Native enabled product teams to release features to both our iOS and Android apps more quickly.

Startup Time​

React Native cold startup on Android.

After enabling Hermes and preloading on react native bundle, we can achieve desirable startup time when switching pages from Native to React Native. Users should not be able to distinguish the loading time between a Native and React Native screen.

Navigation​

BrainAcademy Navigation example.

Navigation between React Native to Native screen and vice versa is rapid and should not be noticeable to the users. As shown in the demo above, the navigation from BrainAcademy live teaching list (react-native) to the live teaching front page (native) is as fast as usual native navigation.

In the example above we demonstrated the capabilities of Ruangguru React Native navigation.

BrainAcademy Home (RN) -> Live Teaching Front Page (Native) -> Cek Ombak (RN).

Dynamic Feature Module (Android)​

Dynamic Feature Module for BrainAcademy React Native.

Because BrainAcademy React Native is an on-demand module, users will only need to download it when they need to use the feature. With DFM enabled, we drastically minimize the cost of React Native on android.

The Future​

Every decision always involves trade-offs, and we recognize that there are no silver bullets when selecting a technology, but we believe the benefits exceed the drawbacks. We are very optimistic about Ruangguru’s future with React Native.

With the expected productivity increases, we may begin to build product feature teams with cross-functional team members collaborating to address current and future business difficulties. Soon, we will also investigate how to leverage React Native javascript ecosystem into the greater Web ecosystem. Because React Native leverage and use the existing web ecosystem, we are thinking of shipping the same codebase to the web.

We think that by implementing React Native, we will be on the most efficient and effective route to developing the Ruangguru family of apps that satisfy the demands of our customers.

Footnote​

Please visit our careers page if this blog article piqued your interest in what we’re doing.

Agastya Darma, Sean Urian and Jevi Saputra are Software Engineers working on the Core React Native team at Ruangguru.

Do You Need A State Management Library?​

For reasons of compatibility and simplicity, it's best to use React's built-in state management capabilities rather than external global state like Recoil. But as i said before React has certain limitations when it comes to a global state management.

• Component state can only be shared by pushing it up to the common ancestor, but this might include a huge tree that then needs to re-render.

• Context can only store a single value, not an indefinite set of values each with its own consumers.

• Both of these make it difficult to code-split the top of the tree (where the state has to live) from the leaves of the tree (where the state is used).

So When Should We Use A State Management Library Like Recoil?​

Applying a global state management is not so easy, it is a lot off hard work and it also takes time to implement. So, it is very important for you to know when to implement the state-management.

1. If your application contains a large number of components and a lot of requests are being sent to the back-end for data retrieval, then it becomes mandatory to implement the state-management, as it will boost the user experience and speed of the application to a great extent. With a global state, you don't have to fetch the same request multiple times as the data will already be "cached" from the first request and can be consumed by other part of your screen.
2. If you use redundant data throughout the whole app, for example, a list of customers is being used in the invoice creation and sales report generation then there is no need to fetch customers again and again from the database. You could simply just put the data in the global state.

What is it about Recoil.js that’s so appealing?​

Recoil feels just like React. The syntax is similar to React and it looks like a part of React API. Other than that, it has many other upsides like it solves the problem of global state management, shared state, derived data, etc. The team at Recoil make sure that the semantics and behavior of Recoil be as Reactish as possible.

The Recoil Concept.​

Recoil is an experimental state management library at Facebook, created by Dave McCabe. The reason why i like Recoil better than Redux is because Recoil solves all our complex state management problems but its configuration is surprisingly simple, unlike Redux. And we do not need to write much boilerplate code as we would have by using other state management library like Redux.

Installing Recoil​

As Recoil is a state management library for React, you need to make sure that you have React or React Native installed and running before getting started.

npm install recoil
// or
yarn add recoil

Core Concept of Recoil​

There are two core concepts of Recoil that you need to understand. This are Atoms and Selectors.

Atoms​

Atoms are units of state. They're updateable and subscribable: when an atom is updated, each subscribed component is re-rendered with the new value. They can be created at runtime, too. Atoms can be used in place of React local component state. If the same atom is used from multiple components, all those components share their state.

You can create Atoms with the atom function:

const countState = atom({
  key: 'countState',
  default: 1,
});

Atoms use a unique key for debugging, persistence, and mapping of all atoms. You can't have a duplicate key among the atoms. So because of that you need to make sure they're globally unique. And also like a React component state, they also have a default value.

To read and write an atom from a component, we use a hook called useRecoilState. It's just like React's useState, but now the state can be shared between components:

function CountButton() {
  const [countValue, setCountValue] = useRecoilState(countState);
  return (
    <>
      <h4>Count Value {countValue}</h4>
      <button onClick={() => setCountValue((value) => value + 1)}>
        Click to Increase Count
      </button>
    </>
  );
}

Selectors​

A selector is basically a piece of derived state, where ‘derived state’ can be defined as the ‘the output of passing state to a pure function that modifies the given state in some way’. So in short when these upstream atoms or selectors are updated, the selector function will be re-evaluated. Components can subscribe to selectors just like atoms, and will then be re-rendered when the selectors change.

const countLabelOddEventState = selector({
  key: 'countLabelOddEventState',
  get: ({get}) => {
    const count = get(countState);
    if (count % 2 == 0) {
      return `isEven`;
    }
    return `isOdd`;
  },
});

As you can see Selectors also have a unique ID like atoms but not a default value. A selector takes atoms or other selectors as input and when these inputs are updated, the selector function gets re-evaluated.

The get property is the function that is to be computed. It can access the value of atoms and other selectors using the get argument passed to it. Whenever it accesses another atom or selector, a dependency relationship is created such that updating the other atom or selector will cause this one to be recomputed.

Selectors can be read using useRecoilValue(), which takes an atom or selector as an argument and returns the corresponding value. We don't use the useRecoilState() as the countLabelOddEventState selector is not writeable (see the selector API reference for more information on writeable selectors).

Conclusion​

Personally i think Recoil is a great library but unless you have some specific problems regarding global state management, you don’t really need it. It's nothing that the developer’s world couldn’t survive without. You can even use Recoil partially in your application, exactly where you need, without having to adopt it for the entire application.

References​

Recoil Core Concepts.

Recoil.js — A New State Management Library for React.

So basically Metro Bundler works by taking your source code, all external library dependencies as well as static assets that you use and converting them, optimizing them, and packaging them into a single bundle that can be run by React Native.

What is Code-Splitting?​

Code-Splitting is a technique that allows developers to create multiple bundle files from existing code sources, so the resulting bundle is not just one but consists of many files which are commonly referred to as chunck.

By default, all your input files (source code, dependencies, and assets) are combined into one file. With Code-Splitting, the bundle will be divided into several parts called chunck. The main chunck (also known as the entry chunk) is commonly referred to as the main bundle.

Why Do You Need Re.pack To Code-Splitting?​

As explained above, by default React Native will use Metro Bundler to do JavaScript bundling. But unfortunately Metro Bundler cannot perform Code-Splitting technique by default. To be able to perform the Code-Splitting technique, we need a JavaScript bundler other than Metro Bundler.

What is Re.pack?​

Re.pack is basically a toolkit that allows you to use Webpack and its Code-Splitting functionality and use them on React Native.

Why Do We Need Code-Splitting in React Native?​

Single bundles aren't a bad thing, but as your app grows your bundle size will grow as well. Especially if you use a lot of third-party libraries you need to be very careful about the code that will be included in the application bundle so that you don't accidentally make your bundle so large that it takes a long time for React Native to load your application.

Increasing App Startup Time​

If you have performance issues in the application startup area Code-Splitting is a technique worth trying when you have those problems.

Moving code from a single bundle to multiple chunks of chunck if properly configured can make your React Native app to only load the required code snippets and delay loading of other code on startup. This really helps improve the startup performance of your application.

Modular Applications​

Apps that expose different functionality or different UI based on user details are examples of apps that would benefit greatly from Code-Splitting.

Let's take an example of an e-learning application like Ruangguru. With Code-Splitting, you will be able to separate student and teacher functionality in separate bundle files, so that the application only loads one of the bundles, this can improve startup performance by loading only code that is relevant to the user's needs.

Two other groups of apps where Code-Splitting plays a big role are super apps (like Gojek) as well as apps with mini app stores (like WeChat/Line). Instead of having multiple apps on the App Store and Google Play, you can combine them into one while streamlining development and simplifying management.

How to Use Re.pack for Code-Splitting in React Native​

How to use Re.pack? The first step to using Re.pack is to install the required dependencies:

npm i -D webpack terser-webpack-plugin babel-loader @callstack/repack
# or
yarn add -D webpack terser-webpack-plugin babel-loader @callstack/repack

After that, Create react-native.config.js (if this file is not in your project) and copy the content below:

module.exports = {
  commands: require('@callstack/repack/commands'),
};

Then configure XCode and Gradle to use the webpack-bundle command. By making this change you will replace the default Metro Bundler to Re.pack

• XCode: Add export BUNDLE_COMMAND=webpack-bundle to the Bundle React Native code and images phase of Build Phases in your XCode project configuration.

  export NODE_BINARY=node
  export BUNDLE_COMMAND=webpack-bundle
  ../node_modules/react-native/scripts/react-native-xcode.sh
  

• Gradle: Add bundleCommand: "webpack-bundle" into project.ext.react in android/app/build.gradle file, so it looks similar to:

  project.ext.react = [
      enableHermes: false,  // clean and rebuild if changing
      bundleCommand: "webpack-bundle",
      bundleInDebug: false
  ]
  

All configurations have been completed. Now you can use repack in your React Native application.

To run the development server you can use the command

npx react-native webpack-start

What are the disadvantages of Repack compared to Facebook Metro Bundler ?​

Of course there are some drawbacks when we use Code-Splitting with Re.pack instead of Metro Bundler. One of the biggest drawbacks is that we can't use Codepush anymore to do Hot Push code in Production Env.

Besides that at the time this article was written if you use Hermes with Re.pack then it can only convert Main Bundle to Hermes Bytecode, chunck files outside of Main Bundle will not be transformed into Hermes Bytecode.