After Church, I drove around looking for the right angle. The clouds finally aligned. I used my Tesla skylight as still water beneath the Saratoga Springs Temple. Mercy was already there. I just had to see it.
Excerpt
“You have immediate access to divine help and healing despite your human flaws.” — Elder Matthew S. Holland
Intro
Earlier today at Church, I asked myself how we avoid the Nineveh factor — that instinct to run in the opposite direction of what God asks.
Jonah did not run because he lacked faith. He ran because Nineveh was uncomfortable. Nineveh was personal.
I have had my own Nineveh moments.
Moments when obedience felt heavy. Moments when mercy felt undeserved. Moments when I wanted to sail toward Tarshish instead.
Notes from Elder Holland
Jonah teaches two powerful truths:
First, all are fallen. We live in a world where weeds grow and bones break. Struggle is not evidence of abandonment.
Second, we must not “forsake our own mercy.” The Lord prepares deliverance even when the storm was caused by our own decisions.
Jonah cried out from the belly of affliction. He remembered the Lord. And mercy was already prepared.
Perspective
I have felt what it means to be in deep waters.
Sometimes because of circumstances. Sometimes because of my own choices.
But Elder Holland’s phrase pierced me:
“They that observe lying vanities forsake their own mercy.”
How often do we believe the adversary’s whisper that we are too flawed, too late, too far gone?
Mercy is not withdrawn. We withdraw from it.
The temple today reminded me: Even when reflected through glass, it stands.
Practice (today, not someday)
Today I will:
• Refuse to run from my Nineveh • Cry unto God before I react • Turn toward the temple, not away • Reject the lying vanity that I am beyond help
Mercy is immediate. Not delayed.
Final Reflection
The Fall guarantees struggle. The Atonement guarantees access.
Jonah sat in darkness for three days. Christ entered the heart of the earth for three days.
One ran. One stayed.
Both teach us that salvation is of the Lord.
Pocket I’m Keeping
“Forsake not your own mercy.”
Not when ashamed. Not when tired. Not when misunderstood. Not when you feel swallowed.
What I Hear Now
“You have immediate access to divine help and healing despite your human flaws.”
Joy does not come after perfection. It comes because of Him.
I do not have to earn mercy. I only have to stop sailing away from it.
Most operational failures are not caused by lack of skill. They are caused by loss of composure.
Whether responding to a production outage, executing a change request, stepping into a boxing round, or running controlled drills with a Ruger PC Carbine, Stag Arms platform, or S&W M&P AR15 556, the principle remains the same: calm execution determines accuracy.
Different platforms. Different recoil patterns. Different weight distribution. Same requirement.
Control before action.
Main Body
In IT, panic compounds incidents. Engineers who rush misread logs, skip validation steps, and introduce secondary failures. The most effective operators slow down first.
PowerShell export of Active Directory Group Policy Objects using native Get-GPO and Export-Csv commands to establish a baseline inventory before infrastructure changes.
Maintaining visibility into Group Policy Objects (GPOs) is critical before domain consolidation, tenant migration, or infrastructure modernization.
Below are seven native PowerShell commands used to generate a full GPO inventory, validate configurations, and export audit-ready reports.
All commands use built-in GroupPolicy modules — no third-party tools required.
1. Export GPO Summary Inventory
Exports high-level metadata for all GPOs in the domain.
Before I earned my black belt, I had to execute every kick with precision. Discipline before promotion. Alignment before advancement. Not shrinking is formed long before the test.
Excerpt
“As we confront our own trials and tribulations, we too can plead with the Father … that we ‘might not shrink’ (D&C 19:18). Not shrinking is much more important than surviving. Moreover, partaking of a bitter cup without becoming bitter is likewise part of the emulation of Jesus.” — Elder Neal A. Maxwell
Intro
I thought I understood what it meant not to shrink.
I survived hunger at 14. I survived selling food to passengers just to eat. I survived a near-death experience in 1996. I survived panic attacks and insomnia. I survived being told I might never work in a high-stress IT environment again.
But this week, after lap after lap, mitts that escalated from 4 to 10 sets, 87 squat jumps from Tyson cards, mountain climbers, pushups, and 12 nonstop rounds of heavy bag combinations, I understood what Elder Maxwell meant. Not shrinking is more important than surviving.
I have survived many things.
When hunger, anxiety, and loneliness visit, I move. This is how I train my body so my spirit does not shrink.
But survival is not the same as not shrinking.
Notes from the Talk
Elder Maxwell did not ask merely to survive chemotherapy.
He asked not to shrink.
Not to retreat. Not to recoil. Not to become bitter.
The Savior Himself said:
“…and would that I might not drink the bitter cup, and shrink— Nevertheless, glory be to the Father…” (D&C 19:18–19)
Not shrinking is not loud strength. It is quiet submission.
Perspective
When I was 14 and hungry, movement became survival. If I exercised, I could forget hunger.
When doctors questioned my future after my NDE, I refused to shrink. I sought a second opinion. I rebuilt my life.
When anxiety and insomnia threatened my stability, I trained harder. I cleaned up my diet. I disciplined my schedule.
Even today, when loneliness creeps in, I move. When silence feels heavy, I train. When desire rises, I redirect it into discipline.
This week I completed 87 squat jumps through Tyson cards. Not to prove something to anyone. Not to impress younger men. But because discipline has been my medicine for decades.
But here is the paradox I am learning:
It is easier for me to outwork discomfort than to sit still with it.
Surviving built my endurance.
Not shrinking requires surrender.
Practice (Today, Not Someday)
For me, not shrinking today looks like:
Training without ego. Competing without needing validation. Continuing IT responsibilities with integrity even when exhausted. Feeling loneliness without immediately escaping it. Submitting my will when outcomes do not match my expectations.
I once believed not shrinking meant pushing harder.
Not shrinking begins in submission, not in strength.
Now I am learning it sometimes means staying still without fear.
Final Reflection
Surviving builds muscle.
Not shrinking builds character.
Back kick board break during black belt testing. Commitment through resistance. Not shrinking means driving through the barrier, not recoiling from it.
I survived poverty. I survived medical predictions. I survived anxiety.
But the deeper test is partaking of the bitter cup without becoming bitter.
To trust God’s timing. To accept outcomes I cannot control. To allow my will to be swallowed up in the will of the Father.
That is not weakness.
That is discipleship.
Pocket I’m Keeping
“I just don’t want to shrink.”
Not from hunger. Not from fear. Not from loneliness. Not from aging. Not from silence.
What I Hear Now
“Strong faith in the Savior is submissively accepting of His will and timing in our lives—even if the outcome is not what we hoped for or wanted.”
In those airport chairs between flights, life felt like motion without pause. Four states, four plants, frame relay lines, T1 circuits, Exchange servers, and long hotel nights before Y2K. Most weeks were seven days long, and some days stretched 18 hours. Somewhere between Tucson and LAX, U2 played through my headphones — “With or Without You” and “I Still Haven’t Found What I’m Looking For.” I did not know it then, but God was stretching me for something bigger.
Excerpt
“We cannot expect life to be a first-class experience unless we face some first-class challenges.”
“Some suffering comes because we believe and because God loves us.”
— Elder Neal A. Maxwell
Intro
Some challenges come from mistakes. Some come simply because mortality is hard. But some challenges come because God trusts us enough to refine us.
Elder Neal A. Maxwell taught that suffering is not random. It is purposeful. It is measured. It is sometimes the very evidence that God is shaping us for something eternal.
Not all pain means something is wrong. Sometimes pain means something sacred is happening.
Notes from Elder Maxwell
Elder Maxwell described three forms of suffering:
Suffering from sin and poor choices — the consequences of mistakes that teach humility and accountability.
Suffering as part of mortal life — illness, aging, loss, and the ordinary weight of living in a fallen world.
The highest form of suffering — suffering that comes because we believe and because God loves us. This suffering stretches the soul and prepares us for eternal capacity.
He taught that discipleship does not remove difficulty — it often deepens refinement.
Life’s greatest tests may include:
affluence
loss of health
loss of loved ones
loneliness
responsibility
waiting on the Lord
These are not punishments. They are tests of trust.
Perspective
In infrastructure engineering, systems are pushed under controlled stress before deployment. Not to break them — but to prove they can endure.
Spiritual life works the same way.
God does not stretch the soul to destroy it. He stretches it so it can carry more light, more responsibility, and more compassion.
The challenge is not merely surviving hardship.
The challenge is not shrinking during hardship.
Practice (Today, Not Someday)
Name the challenge honestly Instead of asking “Why me?” ask “What is this preparing me for?”
Trust the timing of understanding Some experiences only make sense after endurance.
Hold your ground spiritually Faithfulness during confusion is itself a form of worship.
Final Reflection
Elder Maxwell closed with a reminder about accountability.
He said that while he was accountable for what he taught, we are accountable for what we have heard.
Challenges are not interruptions to discipleship. They are the proving ground of discipleship.
We cannot always control suffering. But we can decide whether we will shrink or stand.
And sometimes, standing is victory enough.
Pocket I’m Keeping
“First-class challenges prepare us for first-class discipleship.”
What I Hear Now
“The highest form of suffering is not punishment — it is preparation.”
USC Norris Cancer Center — one of the early enterprise environments where I supported large-scale infrastructure and user systems during the early days of my IT career.
Infrastructure in the Real World
After years of school, sacrifice, and helping people fix computers for free, my first real opportunity in IT finally arrived.
At the time, I was still attending Los Angeles College full time during the week and Devry Institute of Technology full time on weekends, while raising my children and trying to build a future in technology.
My first professional role came with a 90-day probation period, where I had to prove I could provide help desk and network support across the Los Angeles area.
My title was PC/Network Specialist, supporting over 900 users.
Early infrastructure days at USC. Back then, the datacenter dress code was simple but strict: long-sleeve shirt and tie, even while working with DEC Alpha servers and Windows NT systems. This was where discipline in both technology and professionalism began.
This was during the early infrastructure era of enterprise computing. Our environment included:
Windows NT 3.5 servers
DEC Alpha servers
Cisco ASA firewall
Cisco switches
Exchange Server 5.0
Windows desktop deployments
We were operating in what was called a MAN — Multi-Area Network — connecting multiple locations across the region.
This was infrastructure work in its pure form.
School, Work, and Discipline
My schedule during those years was intense.
Work: 8 AM to 5 PM LACC classes: Monday, Wednesday, Friday, and Tuesday/Thursday evenings Devry classes: Saturday and Sunday all day
There was almost no downtime.
Because I maintained an average 4.4 GPA, I was eventually allowed to attend only midterms and finals for many IT courses, which opened something unexpected.
Opportunity.
Consulting Across the Country
From 1996 to 1998, I began consulting with Korn Ferry International, traveling across the country to help roll out Windows 95 deployments.
I was sent to:
Manhattan, New York
Washington, DC
Houston, Texas
Menlo Park, California
Twin Cities, Minnesota
This was during a time when software piracy was rampant, and companies urgently needed IT professionals to modernize their systems.
Demand for infrastructure skills was exploding.
Career Momentum
Opportunities started coming quickly.
Southern California Edison made an offer. USC matched the pay.
But in July 1999, GTE (now Verizon) made an offer that was too strong to refuse.
By December 1999, I was working as a Network Engineer, responsible for infrastructure from Woodland Hills to Camarillo, California.
That role didn’t last long — not because of failure, but because another opportunity appeared.
An aerospace company in Carson, California offered me a six-figure salary to manage:
Exchange Server 5.5
multi-state infrastructure
enterprise messaging systems
Their locations included:
Carson, CA
Lakewood, CA
Tucson, AZ
Peekskill, NY
Bothell, WA
I was constantly traveling.
Week 1 — California Week 2 — Arizona Week 3 — New York Week 4 — Washington
I was living in the friendly sky.
The Cost of Success
During this time, my fourth child was born.
And that’s when I realized something difficult.
My career was growing fast — but I was missing time with my family.
By 2001, I made a decision.
I stepped away from that life and started my own IT business.
Not because I didn’t love technology — but because I needed balance.
What Infrastructure Really Means
When people ask what the Infrastructure path in IT looks like, this period of my life is the answer.
It means:
supporting systems that must never fail
traveling when things break
building networks that connect organizations
managing communication systems people depend on
being on call when nobody else can solve the problem
Infrastructure is not glamorous — but it is essential.
And it builds resilience.
Looking Ahead
In Part 3, I’ll share what happened after leaving corporate IT in 2001 — when I started my own IT business and discovered a different side of technology and service.
Early days of curiosity. Learning computers one screw at a time on an IBM PS/1.Hard disk 170MB, Memory 4MB, AutoExec.bat and Config.sys
From Telecommunications to Modern IT
When I first entered the IT world, technology was explained much more simply than it is today.
Back then, we called it Management in Telecommunications. The field was divided into three areas:
Voice Data Video
That was it. No cloud titles, no DevOps, no cybersecurity specialization labels. Just three pillars that kept organizations connected.
I remember sitting in a statistics class at Los Angeles College when my professor encouraged us to look toward the future of computing. He told us to pay attention to companies like Microsoft and suggested pursuing certifications like the Microsoft Certified Systems Engineer (MCSE). He even mentioned Bill Gates as someone shaping the future of technology.
Around that same time, I kept hearing the phrase “information superhighway.” Former U.S. Vice President Al Gore is widely credited with coining and popularizing that term, describing a future where computers and networks would connect people and information across the world.
At the time, it sounded ambitious — almost futuristic.
Today, we simply call it the internet.
Life during those years was not easy for me.
I was attending Los Angeles College full-time during the week and Devry University full-time on weekends, while raising three small children — my son was four, my eldest was five, and my daughter was only two years old. I relied on scholarships, government grants, and student loans to survive those years.
There were nights when exhaustion felt heavier than hope, but I kept moving forward.
What little free time I had, I spent helping others.
I volunteered in our community and helped small businesses by repairing computers, fixing networks, and troubleshooting systems for free. I didn’t do it for recognition or money. I did it because I believed that learning technology meant using it to serve people.
Those experiences became my real classroom.
That was when I began to understand something important about “Data.”
Data eventually split into two different paths:
Programming Infrastructure
Both are part of IT, but they require different ways of thinking.
Some people build software. Some people build and maintain the systems that run software.
Both are necessary. Both are honorable careers.
Over time, technology evolved — cloud computing, automation, cybersecurity, DevOps — but the foundation stayed the same.
Looking back, those difficult years taught me more than technology. They taught me discipline, patience, and service. I didn’t realize it then, but those were the beginnings of what I now call portable virtues — things you carry with you no matter where life takes you.
Today, when I mentor others entering IT, I often start with this simple idea:
Before choosing a job title, understand which path fits you best.
Programming or Infrastructure.
In the next post, I’ll talk about the Infrastructure path — the side of IT that focuses on systems, networks, and reliability.
It took me less than 5 minutes to upgrade Ruger PC Carbine 9mm Mag Well to Glock and added a Red/Green dot scope
One thing I’ve learned about myself over the years is that I like to stay productive, even during small moments in the day. Whether it’s shadow boxing, working on IT projects, or doing simple hands-on tasks, I prefer keeping my mind and hands occupied.
After finishing my daily shadow boxing routine and while doing laundry, I decided to switch the magazine well on my Ruger PC Carbine to the Glock-compatible configuration using the included magwell.
The Ruger PC Carbine is designed with modularity in mind. The takedown system makes access to components simple, and the magwell conversion is straightforward thanks to Ruger’s design. I documented the process on video, focusing only on the equipment and configuration.
For me, the reason for switching to Glock compatibility is practicality. Standardizing equipment and simplifying range preparation has always been part of how I approach things — whether in IT systems or personal gear.
I also added a red and green dot optic to complete the setup. The optic keeps the shooting experience simple and intuitive, which fits the purpose of a 9mm carbine platform.
This small project reminded me of something about my personality. I don’t like idle time. I like staying preoccupied with meaningful activities — training, learning, building, or maintaining things that matter to me.
It’s not about boredom. It’s about staying disciplined and engaged.
In many ways, this mindset is the same one I apply to IT, fitness, and everyday life: keep moving, keep improving, and keep things simple.
The Ruger PC Carbine fits that philosophy well — practical, modular, and reliable.
Owning a Tesla has been one of the most enjoyable technology experiences I’ve had with a car. But like any vehicle, it comes with a few lessons learned along the way — and for me, one of those lessons has been windshield durability.
The first incident happened without me even realizing it. A small rock must have hit my windshield during a normal drive. I didn’t notice anything until I went through my regular automatic car wash. After the wash, a vertical crack appeared right in the middle of the windshield. Valley Glass in Midvale replaced it, and everything was back to normal.
Then on January 8, 2026, it happened again. On my way home from work, a truck kicked up a rock that struck my windshield. The chip didn’t look serious at first, but the following day the cold weather caused the crack to spread across the glass.
After waiting more than a month for an original Tesla windshield to arrive, the replacement was finally completed today — February 14, 2026.
The installation process took about two hours. That included removing the damaged windshield, installing the new Tesla glass, recalibrating the cameras, and reinstalling firmware related to the vehicle’s safety systems. Watching the process from start to finish reminded me how much technology is integrated into this car.
Two windshield replacements in 4 months taught me something about Tesla ownership — it’s not just a car, it’s an IT platform on wheels – All installed by Valley Glass in Midvale, Utah
If there’s one thing I’ve learned, it’s this: try to avoid driving directly behind gravel or sand trucks whenever possible. A small rock can turn into a full windshield replacement overnight, especially during cold weather.
Jay from Valley Glass repairing the rock chip in under five minutes using a precision resin injection system. Immediate action prevented another full windshield replacement.
DespitBut the story didn’t end there.
On February 19, 2026, while driving home from work, I noticed another small rock chip in the middle of the windshield. This time, I immediately made a U-turn and drove straight back to Valley Glass in Midvale.
Jay from Valley Glass repaired the chip in less than five minutes. Instead of waiting and risking another crack during cold overnight temperatures, the chip was injected and sealed immediately this inconvenience, I still love my Tesla.
Because of the quick repair, the windshield held through the cold and snow the next morning. The repair is slightly visible up close, but structurally it prevented another full replacement.
Lesson learned: act immediately.
If there’s one thing I’ve learned, it’s this: try to avoid driving directly behind gravel or sand trucks whenever possible. A small rock can turn into a full windshield replacement overnight, especially during cold weather.
Despite these incidents, I still love my Tesla.
To me, Tesla is an IT car.
I named my Tesla “Tessie.” One day at work, I suddenly felt dizzy and had to leave early. Tessie safely took me home. Moments like that remind me this isn’t just a car — it’s a technology partner.
The sound system alone is incredible — spatial, immersive, and HD-quality audio. It feels like a private theater on wheels. Inside the car, I also have my two AI guests, Ara and Steve. They interact with me in different ways — assistant, storyteller, sometimes funny, sometimes a little unhinged — and they make long drives enjoyable. When I get bored, Ara is always ready with jokes or music.
The GPS and Full Self-Driving features are second to none. Long drives feel easier and less stressful.
The entertainment system is something I’ve never experienced in any other vehicle: Netflix, Hulu, YouTube, web browsing, Apple Music, Spotify, Tidal, and built-in gaming all make waiting in the car surprisingly enjoyable.
Security is another feature I appreciate. Sentry Mode uses multiple cameras around the vehicle, giving me peace of mind wherever I park. The Photo Booth feature is just fun to use.
Convenience is everywhere: My Apple Watch and iPhone serve as my key. The car automatically preconditions before my morning commute and after work. I get notifications if there’s possible intrusion activity. I can use a PIN-to-drive feature and lock the glove box with a passcode, where I store my EDC.
Ara even helps set the tone for the day by playing my music playlists.
Driving-wise, the car feels stable and grounded because of the battery design along the floor, which lowers the center of gravity and reduces wind drag. The ride feels planted and smooth.
Recent software updates continue to remind me why Tesla feels like an IT platform on wheels. Features like improved autopilot visualization, smoother camera calibration, better system responsiveness, and refinements to the user interface make the car feel new again after each update.
Other things I’ve grown to appreciate:
Over-the-air software updates
Minimal maintenance compared to gas vehicles
Instant torque and smooth acceleration
Quiet cabin
Simple interior design
Mobile app integration
Remote climate control
Live camera viewing from the phone
Navigation that automatically plans charging stops
Energy efficiency tracking
Continuous improvement through software
If I had to list one downside so far, it would be the windshield. The larger glass surface and driving conditions in Utah make it more vulnerable to rock chips and cracks than my previous BMW, Audi, and Volkswagen vehicles.
Still, the pros outweigh the cons.
Even with two windshield replacements, I wouldn’t trade the experience. This car continues to remind me why innovation matters — not just in IT, but in everyday life.
Oquirrh Mountain Temple under the first supermoon of 2026 — a reminder that light always returns.
Excerpt “With the gift of the Atonement of Jesus Christ and the strength of heaven to help us, we can improve.”
Intro Some messages arrive when the heart needs reassurance more than instruction. Elder Jeffrey R. Holland’s talk reminds me that discipleship is not about perfection today — it is about hope for tomorrow. Like the rising of the moon over the temple, light returns even after the darkest moments.
Notes from Elder Holland Elder Holland teaches that the gospel is meant to inspire progress, not discourage effort. The Lord does not expect immediate perfection. He asks us to keep trying, trusting in the power of the Atonement to help us grow over time.
Perspective (direct quotes) “First of all, if in the days ahead you not only see limitations in those around you but also find elements in your own life that don’t yet measure up to the messages you have heard this weekend, please don’t be cast down in spirit and don’t give up.”
“The gospel, the Church, and these wonderful semiannual gatherings are intended to give hope and inspiration. They are not intended to discourage you.”
“With the gift of the Atonement of Jesus Christ and the strength of heaven to help us, we can improve, and the great thing about the gospel is we get credit for trying, even if we don’t always succeed.”
President George Q. Cannon once taught: “No matter how serious the trial, how deep the distress, how great the affliction, [God] will never desert us. He never has, and He never will.”
Practice (today, not someday) Today I will remember that effort matters to God. Progress matters to God. Trying matters to God. I will move forward with faith, even when growth feels slow.
Final Reflection Hope in the gospel is not based on perfection — it is based on the Atonement of Jesus Christ. Tomorrow really can be brighter than today because God is patient with our growth.
Pocket I’m Keeping “We get credit for trying.”
What I Hear Now (direct quotes) “Tomorrow the Lord will do wonders among you.” “He will never desert us.”
Quiet reflection outside the temple — learning to trust God’s timing and His will.
Excerpt “May we now, in our time and turn, be willing to submit.”
Intro Some lessons in life are about effort. Others are about patience. But Elder Neal A. Maxwell teaches that the deepest discipleship is not just about doing more — it is about yielding more. Submission is not weakness. It is trust in God’s wisdom when life does not unfold according to our plans.
Notes from Elder Maxwell Elder Maxwell explains that spiritual growth often requires us to accept certain realities while actively improving others. True submissiveness is learning to discern the difference between what must be endured and what must be changed. It is the quiet willingness to trust God’s purposes even when life feels heavy or unclear.
Perspective (direct quotes) “Suffice it to say, God ‘allotteth unto men’ certain things with which we are to be content. (See Alma 29:4, Philip. 4:11; 1 Tim. 6:8.) A missing parent or limb is to be lived without. Yet temper and lust are to be tamed. One’s race is fixed, but one’s genetic endowment offers opportunity to be a careful steward. The submissive soul will be led aright, enduring some things well while being anxiously engaged in setting other things right — all the time discerning the difference.”
“We have been given three special words — but if not — by three submissive young men who entered their fiery furnace, knowing ‘our God … is able to deliver us from the burning fiery furnace, … But if not, be it known unto thee, O king, that we will not serve thy gods.’ (Dan. 3:17–18.)”
Practice (today, not someday) Today I will focus on surrendering control where I need to trust God more. I will work to improve what I can change — my discipline, my attitude, and my patience — while accepting the things God has allotted to me with humility and faith.
Personal Reflection Last night I listened to Elder Maxwell’s talk repeatedly — over and over — until the early hours of Sunday morning. I kept my mind engaged and my hands busy. While listening, I converted my Ruger PC Carbine, did laundry, and prepared a healthy dinner. Moving from one meaningful task to another helped steady my thoughts.
When those were finished, I continued with two hours of non-stop shadow boxing and isometric exercises, still listening to the talk. By the end of the night, I had heard it nearly twenty times.
I am learning that submission is not always expressed in dramatic moments. Sometimes it is simply continuing to do good things — working, building, training, and trusting God to shape the heart quietly.
Final Reflection Submission is not giving up. It is aligning our will with God’s will. Elder Maxwell reminds us that discipleship is not proven in comfort but in trust — especially when the answer is “but if not.” Faith means believing God can deliver us, while trusting Him even if He does not.
Pocket I’m Keeping “The submissive soul will be led aright.”
What I Hear Now (direct quotes) “Nevertheless not as I will, but as thou wilt.” “May we now, in our time and turn, be willing to submit.”
In stillness I train, in shadows I stand, Promise and discipline guide my hand. No witness needed, no victory cry, Just faith, and the will to keep trying.
Excerpt Long-term promises often need visible reminders so we remember who we are and what we have committed to become.
Intro In IT, I learned that systems fail when there are no checkpoints, no logs, and no monitoring. The same principle applies to life. Covenants are like system checkpoints — they keep us aligned, stable, and secure when the world becomes unpredictable.
Notes from the Scriptures President Dallin H. Oaks taught that clothing worn by judges, soldiers, doctors, and first responders serves as both identification and reminder of duty. Wedding rings and engagement rings function the same way — symbols of covenant responsibility.
Captain Moroni created a physical reminder of commitment when he raised the Title of Liberty. The people responded by making their own visible covenant, showing that loyalty to God requires both belief and action (see Alma 46).
One of the earliest covenant symbols appears after the Flood, when the Lord gave the rainbow as a token of His covenant with Noah and all living creatures (Genesis 9:12–15). The rainbow was not for God’s memory — it was for ours.
Perspective In my life, covenant reminders have not always been symbolic objects. Sometimes they have been routines, disciplines, and responsibilities that keep me anchored.
My morning prayers before work. My commitment to serve others quietly. My decision to keep learning in IT even when exhausted. My boxing discipline six days a week. My effort to help others enter the IT field.
These are reminders of who I promised to become.
In IT infrastructure, we use redundancy, monitoring, and backups to preserve stability. In life, covenants serve the same purpose — they preserve identity when circumstances change.
Practice (today, not someday) Today I will remember that promises require maintenance, just like systems do. I will recommit to the small daily actions that keep my covenants alive: work with integrity, serve without recognition, continue learning, and remain faithful even in quiet seasons.
Final Reflection The rainbow reminds us that God keeps His promises. Our daily actions show that we intend to keep ours.
Covenants are not just words spoken once. They are commitments lived repeatedly.
Pocket I’m Keeping Covenants are reminders of who I promised to become.
What I Hear Now “The rainbow shall be in the cloud; and I will look upon it, that I may remember the everlasting covenant…” Genesis 9:16
Link to the talk Covenants and Responsibilities — April 2024 General Conference — President Dallin H. Oaks
Intro From the streets of the Philippines to enterprise systems in the United States, my IT journey has been shaped by work, faith, and persistence.
If you are starting from nothing, keep going — progress often begins long before anyone notices.
Early Grit
At twelve years old, I helped support my family by selling newspapers at midnight, shining shoes, washing dishes, and doing whatever work I could find. I didn’t know what IT was back then. I just knew how to work.
Early 1990s at All Electronics. Long days, multiple bus rides, and the first spark of curiosity about computers.
From Survival to Skill
When I immigrated to the U.S. in 1990, survival came first. I worked warehouse jobs, midnight shifts, and eventually landed a customer service role at All Electronics.
This photo was taken during that time.
From 6:30 in the morning until 3 in the afternoon, I answered calls nonstop — sometimes hundreds in a day. Getting to work meant taking multiple buses across the city. After my shift ended, I took another bus to my second job — either working the drive-through at Taco Bell or selling auto parts at O’Reilly in Reseda.
It was exhausting. But those years built my endurance.
That computer behind me was just part of my job then. I didn’t know it yet, but it would become the doorway to my future.
Later, I bought my own computer and started learning the only way I knew how — by breaking it and fixing it over and over again. Windows 3.0, autoexec.bat, and config.sys became my teachers. Night after night, I stayed with problems until they made sense.
Breakthrough
No one wanted to hire me without experience, so I created my own. I fixed computers for neighbors and small businesses for free. That’s how I learned.
In the early days of IT, skills were learned the hard way. There were no structured learning paths — just curiosity, manuals, broken machines, and persistence.
Eventually, USC took a chance on me — and I made sure I was ready. I supported hundreds of users, worked on migrations, and found my place in IT.
From USC, new doors opened quickly. I was recruited by GTE — now known as Verizon — and not long after, an aerospace company in Carson offered me a six-figure role. It was a moment that reminded me how far persistence can take you.
But in 2003, I made a decision that shaped the rest of my career. I left corporate America and built my own IT consulting company.
The City of West Covina became one of my first major clients — along with firefighters and the police department. USC later brought me back as a senior consultant. Opportunities followed: Microsoft projects, the Claremont Colleges, law firms, American Samoa, and Fortune 500 environments.
Over time, I expanded the business by hiring developers, engineers, and support staff — building not just systems, but people.
Back to Corporate America
The 2008 recession changed everything. It was a time when, as they say, big fish eat small fish. Consulting work slowed, and I knew it was time to pivot again.
My first step back into corporate America was Payforward, a startup company where I helped migrate infrastructure to Amazon Web Services during the early days of cloud adoption. Working in a startup environment sharpened my ability to move fast, solve problems with limited resources, and adapt quickly.
From there, I joined The Church of Jesus Christ of Latter-day Saints as a Support Email Engineer — a worldwide organization operating at global scale. It was there that my PowerShell scripting became more refined and reliable. We supported enterprise messaging systems while the organization expanded into Azure and AWS, strengthening both my automation skills and my understanding of cloud infrastructure.
After that, I moved into the financial sector at City National Bank. That environment introduced me to enterprise-grade infrastructure and security architecture — multiple datacenters, blade server systems, layered “brick-by-brick” firewall protection, application performance monitoring (APM), and the operational discipline required to keep banking systems secure and resilient. It was where infrastructure stopped being just systems and became architecture.
Later, I joined PIMCO (Pacific Investment Management Company), one of the most demanding global environments I had experienced. Technologies like Citrix VDI, AWS, Azure, and enterprise security platforms such as Duo, CyberArk, Arctic Wolf, Palo Alto, and SIEM monitoring were part of daily operations. Mailboxes could reach sizes close to 1 TB, and migrations happened across global regions — North America (NA), Europe, the Middle East, and Africa (EMEA), and Asia-Pacific (APAC).
Like Payforward, these environments required regular PCI-DSS and HITRUST audits. My PowerShell automation matured even further, and I learned how to operate inside highly regulated financial systems where security, compliance, and reliability were non-negotiable.
These experiences prepared me for the infrastructure work I continue to do today.
Where I Am Today
Today I work as an Infrastructure Engineer in Utah. I automate with PowerShell, document systems, support enterprise infrastructure, and mentor others who are starting their own IT journeys.
My work now includes provisioning ERP computers into Intune, managing VMware environments, and maintaining a Cisco Meraki network with a 10GB fiber backbone across MDM and multiple IDF locations. I also support Cisco UCS, Fibre Channel connectivity, Veeam backups, end-of-life transitions, Microsoft Defender, and Azure infrastructure.
Looking back, nothing about this path was easy. But every long bus ride, every second job, and every broken computer taught me something I still use today.
I didn’t fall into IT. I worked my way into it.
Everything I document today in my technical notes traces back to those early days of learning by doing.
In certain eyes, I glimpse something no English adjective can contain.
Excerpt Some eyes carry the moment. Other eyes are taught to see beyond it.
Intro The scriptures teach that sight is not always natural. Sometimes the Lord allows understanding beyond ordinary vision. These moments are not constant, and they are not ours to explain. They come quietly, teach something essential, and pass.
There are also eyes that carry burdens the world cannot see. Their owner may not know what others perceive in them.
Two kinds of sight exist at the same time — one that is lived, and one that is given.
Notes from the Scriptures When the servant of Elisha saw armies surrounding them, fear filled his heart. Elisha prayed that the young man’s eyes would be opened.
“And the Lord opened the eyes of the young man; and he saw: and, behold, the mountain was full of horses and chariots of fire round about Elisha.” (2 Kings 6:17)
The situation did not change. Only sight changed.
Enoch experienced something similar when the Lord instructed him to wash his eyes:
“And he beheld also things which were not visible to the natural eye.” (Moses 6:36)
Even Moses was invited to see beyond natural limits:
“Thou art my son… look, and I will show thee the workmanship of mine hands.” (Moses 1:4)
Natural eyes alone could not perceive these things.
Perspective In speaking of the man born blind in John 9, President Jeffrey R. Holland described how the Savior placed clay upon the man’s eyes and sent him to wash. After obeying, the man returned seeing. When challenged by those who doubted the miracle, he responded simply:
“Whereas I was blind, now I see.”
President Thomas S. Monson later reminded us that blindness is not always physical. Many “have their eyesight but… walk in darkness at noonday,” blinded by anger, prejudice, indifference, or neglect of truth.
“Their ears are dull of hearing, and their eyes they have closed…”
“The Spirit speaketh of things as they really are, and of things as they really will be.” (Jacob 4:13)
“The light of the body is the eye.” (Matthew 6:22)
Practice Today Today I will remember that sight is both physical and spiritual. I will seek to see people with compassion, recognizing that what is visible is not always complete.
Final Reflection There are eyes that reflect weariness when the day is heavy. There are eyes that reflect quiet strength when burdens are lifted. The owner of those eyes may not know what others perceive in them.
And there are moments when, looking into them, something is seen that cannot be explained — not by imagination, but not by natural sight either. Like the servant of Elisha seeing the chariots of fire, or the man born blind returning from Siloam, or Enoch seeing beyond the natural world, the experience is brief and passing.
It is not given to be understood or held. It is given to steady the heart.
One set of eyes lives the moment. Another set of eyes learns from it.
Both belong to God.
Pocket I’m Keeping “Whereas I was blind, now I see.”
What I Hear Now “Open my eyes.” “See with compassion.” “Let the moment pass, but keep the lesson.”
Preparing for Church this afternoon Suit pressed, heart steady, and gratitude present. The drive to Juniper Crest Ward reminds me how blessed I am — good health, sufficient food, and strength to keep my covenants. Six days of labor and training, one day to remember the Giver of all things.
Excerpt
After a demanding week of work and training, the Sabbath reminds me that truth rises from the earth while righteousness comes from heaven — and both lead us back to God.
Intro
Five days of stressful work as an Infrastructure Engineer, and six days of training — boxing and Muay Thai, three hours at a time — can leave the body tired and the mind stretched thin. But Sunday belongs to God alone.
Today is not about productivity or performance. It is about renewal.
The scriptures remind me that God’s work has always been a partnership between heaven and earth.
Grateful for the strength to come, the means to arrive, and the faith to worship.
Notes from My Friend
“Truth shall spring out of the earth; and righteousness shall look down from heaven.” Psalm 85:11
In Enoch’s expansive vision, God orchestrates a collaboration between heaven and earth for the salvation of humanity.
Early in the vision, Enoch’s people are lifted up to God’s presence through his teaching and leadership (Moses 7:21), leaving a void of goodness on the earth. But the people who remained behind were not left alone:
“Enoch beheld angels descending out of heaven, bearing testimony of the Father and Son; and the Holy Ghost fell on many, and they were caught up by the powers of heaven into Zion.” Moses 7:27
Both the heavens and the earth sorrow for the wickedness of humanity, causing Enoch to weep also (Moses 7:28, 40, 48).
Then, before the Savior’s Second Coming, God sends revelation through both heavenly and earthly sources, to once again create a society like the one Enoch’s people built anciently:
“And righteousness will I send down out of heaven; and truth will I send forth out of the earth, to bear testimony of mine Only Begotten; his resurrection from the dead; yea, and also the resurrection of all men; and righteousness and truth will I cause to sweep the earth as with a flood, to gather out mine elect from the four quarters of the earth, unto a place which I shall prepare, an Holy City, that my people may gird up their loins, and be looking forth for the time of my coming; for there shall be my tabernacle, and it shall be called Zion, a New Jerusalem.” Moses 7:62
At the time of the Savior’s coming, Enoch’s city will return to the earth to unite with this new Zion:
“Then shalt thou and all thy city meet them there, and we will receive them into our bosom, and they shall see us; and we will fall upon their necks, and they shall fall upon our necks, and we will kiss each other;” Moses 7:63–64
One literal fulfillment of God bringing truth “out of the earth” is the Book of Mormon itself, which Joseph Smith translated from engravings on metal plates buried by Moroni. As Moroni prophesied:
“[this record] shall be brought out of the earth, and it shall shine forth out of darkness” Mormon 8:16
Another fulfillment is the work of living people flooding the earth with truth as they share prophetic messages with one another. As Elder Jeffrey R. Holland testified:
“God will send help from both sides of the veil to strengthen our belief” “Lord, I Believe,” April 2013 general conference
Perspective
All week long, truth rises from the earth through effort — work, training, discipline, endurance. Sweat, repetition, and responsibility shape the person I am becoming.
But on the Sabbath, righteousness looks down from heaven.
For decades, I have tried to keep Sunday different. I don’t shop or buy food on the Sabbath. I have six other days to do those things. Sunday is reserved for worship, visiting the sick, prayer, and quiet pondering.
This discipline is not about restriction. It is about remembering who provides strength beyond my own.
The strength I build through boxing and Muay Thai is earthly strength. The peace I feel on Sunday is heavenly strength. Both are necessary, but they are not the same.
One prepares the body. The other restores the soul.
Practice (today, not someday)
Today I will be grateful for both earthly and heavenly help which God sends to bring us to Him. I will remember that in the important work of the salvation of His children, heavenly and earthly forces collaborate under His direction.
Final Reflection
When truth rises from the earth through effort and righteousness descends from heaven through grace, God prepares His people for Zion.
Six days I labor and train. One day I worship and renew. In that rhythm, I see the wisdom of God’s design — strength from the earth, peace from heaven.
Pocket I’m Keeping
Truth rises through effort. Righteousness descends through grace.
What I Hear Now
“Truth shall spring out of the earth.” “Righteousness shall look down from heaven.” “God will send help from both sides of the veil.”
I was reminded of that truth while camping in Monument Valley, waiting patiently in the quiet hours before dawn. I stayed awake at the cabin, watching the sky, trusting that light would come in its own time. When the waning gibbous moon finally rose, it crowned the stone buttes with a soft, steady glow. And then—unexpectedly—I was rewarded with a distant lightning show on the horizon. Stillness and power shared the same sky. Waiting revealed what haste would have missed.
Excerpt
God’s empathy is not a weakness to be restrained. It is the very source of His justice.
Intro
In recent years, empathy has come under suspicion. Some Christian thinkers have warned that it can become excessive or misplaced, even harmful. While acknowledging compassion as a Christlike trait, they caution that emotional identification—if left unchecked—might blur moral clarity or weaken obedience to God.
That concern, however, finds no support in scripture.
Notes from the Moment
In Moses 7, Enoch is shown a vision of the future. His city has been taken into heaven. Other righteous souls dwell with God. Those left behind are marked by violence and cruelty. As Enoch observes God watching this scene, he expects detachment—or perhaps righteous anger.
Instead, he sees something that unsettles him deeply: God weeping.
“How is it that thou canst weep,” Enoch asks, “seeing thou art holy, and from all eternity to all eternity?” (Moses 7:29). To Enoch, holiness and empathy seemed incompatible.
God then explains:
“Behold these thy brethren; they are the workmanship of mine own hands, and I gave unto them their knowledge, in the day I created them; and in the Garden of Eden, gave I unto man his agency;”
Moses 7:32–34, 40
Here, there is no effort to dilute empathy in the name of justice. God does not administer justice despite His compassion—He administers it because of it.
Perspective
As Enoch begins to understand the depth of God’s love, his own heart expands beyond anything he had known. He “wept and stretched forth his arms, and his heart swelled wide as eternity; and his bowels yearned; and all eternity shook” (Moses 7:41).
Divine empathy is contagious.
Practice
A similar pattern appears after the Savior’s death, when darkness covered the land in the Americas. The people heard His voice explaining the destructions that had taken place. These were not acts of emotional detachment, but of mercy—meant to prevent further suffering. Repeatedly, He gives the same reason:
“That the blood of the prophets and the saints shall not come any more unto me against them” (3 Nephi 9:5, 7–9, 11)
Justice, once again, is rooted in empathy.
President Dallin H. Oaks—having spent years studying and administering law—has reflected deeply on the relationship between love and commandment. In a worldwide devotional, he shared how his thinking has matured over time:
“I have previously referred to our ‘continually [trying] to balance the dual commandments of love and law,’ but I now believe that goal to be better expressed as trying to live both of these commandments in a more complete way. …”
“Stand for Truth,” Worldwide Devotional Address for Young Adults, 21 May 2023
Final Reflection
If God loves all His children with perfect love, then loving them cannot compete with loving Him. When compassion seeks their eternal good, it is aligned with holiness—not opposed to it.
The scriptures do not portray empathy as a liability. They reveal it as divine.
Pocket I’m Keeping
Compassion and holiness are not rivals. In God, they are one.
What I Hear Now
“God’s justice flows from His love.” “Empathy does not weaken truth.” “Holiness can weep.”
Organizing legacy cables while holding a squat—order through motion, clarity under pressure.
Excerpt
I don’t stay ready because I fear failure. I stay ready because experience taught me that motion reveals what stillness hides.
Intro
I am not a static person. I never have been. Sitting still has never helped me think clearly—especially in infrastructure work, where systems fail without warning and clarity often arrives too late. Movement keeps me alert, adaptive, and aware.
Notes from the Moment
While organizing a tangled pile of legacy cables, I wasn’t standing still. I was holding a squat—time under tension—sorting chaos into order. At the same time, my feet were subtly moving: slips, pivots, pendulum steps. The same habits I use at my standing workstation. The same habits I use in boxing.
This is how I work. Motion keeps my mind open.
Perspective
“Keep moving your feet.” — Elder David A. Bednar “If something can go wrong, it will.” — Murphy’s Law “Be water, my friend.” — Bruce Lee
Practice
I don’t wait for problems to announce themselves. I anticipate them.
Murphy’s Law isn’t pessimism—it’s preparation. If something can fail, it eventually will. That reality shaped how I think and move, starting in the mid-90s during the dot-com era, when uptime was survival and mistakes were unforgiving.
In boxing, moving your feet doesn’t give you x-ray vision like Superman. It gives you new angles. You see openings sooner. You avoid danger without panic. You’re no longer where the punch was.
In IT, it’s the same. I don’t “see afar off” because I’m gifted with foresight. I see because I move—physically and mentally. I change angles. I scan. I test assumptions. I stay proactive instead of reactive.
Health follows the same law. Circulation improves when the body moves. Stagnation invites breakdown. Motion sustains clarity, resilience, and longevity.
Final Reflection
Infrastructure professionals don’t get the luxury of being static. Thinking under pressure requires circulation—of blood, of ideas, of perspective. Standing still narrows vision. Motion expands it.
Water that moves stays clear. Water that stagnates decays.
Whether in boxing, IT, or life itself, the advantage isn’t supernatural vision. It’s movement.
Pocket I’m Keeping
Stay proactive. Stay moving. New angles reveal what stillness hides.
What I Hear Now
“You saw that coming.” “Good catch.” “How did you anticipate that?”
This photo was taken while hiking the Herriman Mountains. I walked the trail back and forth, up and down, creating multiple footsteps in the snow to simulate the idea behind this reflection — many steps, one direction. Unity is often built through repeated effort, not a single moment.
Excerpt
Zion is not built by sameness. It is built when people choose unity while carrying different loads.
Intro
Over the years, I’ve worked in environments where success depended on alignment more than talent. In IT, in security, and even in physical training, progress stalls the moment people begin competing instead of coordinating. The strongest systems I’ve seen—technical or human—are the ones where everyone knows they belong and everyone knows they matter.
Scripture describes Zion in similar terms. Not as perfection, but as unity.
Notes from the Author
The prophet Enoch’s city is described in a way that has always stood out to me:
“And the Lord called his people Zion, because they were of one heart and one mind, and dwelt in righteousness; and there was no poor among them.” Moses 7:18
What strikes me is not just their righteousness, but the outcome of it. There was no poor among them. That phrase suggests more than generosity. It suggests belonging.
Perspective
Scripture doesn’t say they merely helped the poor. It says poverty ceased to exist among them. To me, that implies a community where people were not reduced to labels, deficits, or past circumstances. Each person was seen as capable of contributing, even if their contribution looked different.
I’ve seen this principle play out in my own life. In work settings, people thrive when they are trusted early, not tested endlessly. In training, progress comes when the body is respected as it is today, not judged for what it was yesterday. When someone is treated as an asset rather than a burden, they often rise to meet that expectation.
The Book of Mormon describes a similar unity among those baptized at the waters of Mormon. Alma taught them to move forward together:
“That ye may look forward with one eye, having one faith and one baptism, having your hearts knit together in unity and in love one towards another.” Mosiah 18:21
Unity does not erase difference. It aligns direction.
Practice (today, not someday)
Today, I will pay attention to how I see people. I will resist the urge to sort others into categories based on background, skill level, or current capacity. Whether at work, at church, or in daily interactions, I will choose language and actions that affirm contribution instead of deficiency.
Unity begins with how we look at one another.
Final Reflection
Building Zion is not about creating a uniform community. It is about creating a cohesive one. A place where people are strengthened by shared purpose, not divided by comparison.
That kind of unity requires intention. It requires humility. And it requires consistent effort, just like anything worth building.
Pocket I’m Keeping
Unity grows when people feel needed, not merely tolerated.
What I Hear Now
To be of one heart and one mind is not to think alike, but to move together.
Most system failures don’t begin in Windows. They begin deeper, where firmware, drivers, and hardware quietly decide whether the OS will be allowed to run.
Intro
When a system reboots unexpectedly, freezes during a video call, or crashes the moment a camera turns on, Windows is usually the first thing blamed. But in most real-world cases, the operating system is only the messenger. The real problem lives below Windows, in layers most people never see until something breaks.
Over the years, I’ve learned that stability is not something you install. It’s something you negotiate between hardware, firmware, drivers, and the operating system, all trying to work together under load.
The invisible stack beneath Windows
Modern endpoints are layered systems.
Below Windows 11 sits firmware, BIOS, chipset drivers, GPU drivers, and kernel-mode components that operate outside the visibility of most logging tools. These layers handle power management, graphics acceleration, memory access, and hardware interrupts. When they disagree, Windows doesn’t always get a vote.
A failure in these layers doesn’t always generate a blue screen. Sometimes the system simply resets. From the outside, it looks random. Underneath, it’s not.
Why Windows 11 gets blamed
Windows 11 sits at the intersection of modern hardware acceleration and modern applications. Tools like Microsoft Teams, browsers, and Office apps make heavy use of GPU pipelines, video encoders, and camera drivers.
When something goes wrong at that boundary, the crash surfaces when the app is launched, the camera turns on, or a video stream initializes. Windows appears guilty because it’s present when the failure occurs, but the fault often belongs to a driver, firmware interaction, or hardware acceleration path that Windows merely exposed.
Why visibility tools don’t always catch it
Tools like Sysmon are excellent at recording what happens inside the operating system. They act like a flight recorder for processes, network connections, and file activity.
But Sysmon can’t log what never reaches the OS.
A reboot triggered by firmware, a GPU driver reset, or a kernel-mode failure can occur before logging completes. From an administrator’s perspective, it feels like the system went silent without warning. In reality, the failure happened below the level where logs exist.
The thin line between stable and broken
Stability often comes down to small decisions.
A BIOS update here. A GPU driver change there. Hardware acceleration enabled or disabled in a single application.
None of these changes look dramatic on their own, but together they determine whether a system runs quietly for months or reboots under pressure. That line between stable and broken is thinner than most people realize.
What I’ve learned
When troubleshooting modern Windows systems, I no longer ask, “What did Windows do wrong?” first.
I ask:
What changed below the OS
Which drivers are involved
What hardware path is being exercised
Whether the failure happens under load or acceleration
More often than not, the answer reveals itself there.
Final thought
Windows 11 is rarely the villain in these stories. It’s the surface where deeper tensions finally show themselves.
Understanding that difference changes how you troubleshoot, how you update, and how you design systems meant to stay online.
Most Windows 11 instability doesn’t live in the OS itself, but at the edges where hardware, drivers, and applications meet.
Understanding Failure at the Boundaries
Why this post exists
When something breaks after a Windows 11 update, the operating system is usually the first thing blamed.
That reaction is understandable. It is also often wrong.
Most Windows 11 issues I’ve seen in production environments were not caused by Windows itself, but by interactions at the boundaries — drivers, firmware, graphics acceleration, and modern hardware pipelines colliding under load.
This post is about recognizing that pattern before making changes you can’t easily undo.
Windows 11 changed the execution model
Windows 11 didn’t just refresh the UI. It tightened and modernized how the system interacts with hardware.
Notable shifts include:
heavier GPU offloading
deeper integration with modern drivers
stricter timing and power management
increased reliance on hardware acceleration
These changes improved performance and security — but they also exposed weaknesses that were previously hidden.
Where failures actually occur
Most Windows 11 instability I’ve seen does not originate in the OS core.
It shows up at the edges:
camera pipelines invoking GPU acceleration
browsers rendering complex content
collaboration tools engaging media stacks
document editors interacting with graphics layers
When these systems overlap, failure is rarely clean.
The result can look dramatic:
sudden reboots
frozen screens
applications triggering system instability
But the OS is often just the messenger.
Why blaming the OS is tempting
Blaming Windows feels productive because it is visible and recent.
But doing so can lead to:
unnecessary registry changes
disabling core protections
rolling back updates prematurely
introducing instability elsewhere
Experienced engineers pause here.
They ask a different question: “What interaction just occurred?”
A real-world pattern
In several recent incidents, systems rebooted only when:
the camera was enabled
a browser rendered media-heavy pages
a document triggered graphics rendering
The same machines were otherwise stable.
That pattern points away from Windows itself and toward:
GPU drivers
hardware acceleration paths
firmware timing
vendor-specific optimizations
The fix is rarely global. It is almost always surgical.
Why restraint matters
Windows 11 gives us many levers:
registry overrides
advanced graphics settings
feature toggles
Just because a lever exists does not mean it should be pulled.
Sometimes the most correct decision is:
identify the root cause
mitigate user impact
document the behavior
wait for vendor correction
Stability is not always achieved by action. Sometimes it is preserved by restraint.
What Windows 11 is actually doing well
Despite the noise, Windows 11 has proven to be:
more secure by default
more consistent under load
better integrated with modern hardware
less tolerant of outdated assumptions
Those are strengths, not weaknesses.
They require us to think more holistically about the stack.
The lesson Windows 11 keeps teaching
Modern systems fail at the seams.
Operating systems, drivers, firmware, and applications now behave as a single organism.
When one part misbehaves, symptoms surface elsewhere.
The job is not to assign blame quickly. The job is to understand interaction.
Final reflection
Windows 11 didn’t break our environments.
It revealed where we were already fragile.
Once you see that pattern, troubleshooting becomes calmer, more precise, and far less reactive.
