I've done the "work from home" option off and on since 1980. At PacBell I had an on-call site support job with a 25 mile one-way commute. Ops called one night and I used my old Bell 103 modem (foam ear cups for the phone handset) and my H9 terminal to dial in and fix the problem faster than I could get dressed. That got a thumbs up from ops and my boss. Much faster resolution. At the office I had a VT100 and 212A dialup modem, so there was little to be gained driving in.
Today, I work from home with team members spread from Hawaii to New York. The corporate VPN, 1 Gbps fiber optic network connection and an i7 laptop with 64 GB RAM are suited to the task. I'm building microservices that run in a kubernetes cluster for my customer. My place on the team reflects having been a team member of each of the 30 systems that are being migrated from dedicated server to microservice containers. Internal knowledge of the apps helps in the migration to the new execution framework. As a bonus, I work on another part of the project doing AI/ML to replace human analysts. The intent is to do what the humans do as well or better in a much shorter time frame. Getting the answer faster is the aim. The quality of the human output is fine, but takes too long in a "live" scenario.
You are the exemplar of the remote, work from home worker. But I am always suspicious of Government workers who are working from home. Especially Federal ones. They have a great scam going.
You know that Washington DC is a ghost town these days during the Monday-Friday workweek. -— Opinion D.C.’s downtown is comatose. Here’s how to revive it. -——
https://www.washingtonpost.com/opinions/2022/11/23/dc-downtown-renovation-remote-work/?outputType=amp
(READ the comments. These Federal workers never want to report to their office again)