The latest articles on DEV Community by Mateo Silva (@mateossb). https://dev.to/mateossb https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3874475%2Faaa0b4ba-0fe5-42eb-81ba-ed9905d98d9d.jpeg https://dev.to/mateossb en Mateo Silva Tue, 12 May 2026 04:51:56 +0000 https://dev.to/mateossb/desktop-as-a-service-daas-the-good-and-the-bad-29a3 https://dev.to/mateossb/desktop-as-a-service-daas-the-good-and-the-bad-29a3 <p>At my job we use Citrix for Desktop as a Service (DaaS) — basically instead of running everything on a local machine, we log into a virtual desktop that lives on a remote server. I've been using it for a while now and overall it's been a solid experience, but it definitely has its ups and downs.</p> <h2> The Good </h2> <p>The best part is flexibility. I can log in from pretty much anywhere and have my full work desktop ready to go. There's also a security benefit — nothing is stored locally, so if a device gets lost or stolen, no company data is at risk. And when someone new starts, IT doesn't have to spend hours setting up a machine. They just create an account and that person is good to go.</p> <h2> The Bad </h2> <p>It's not all smooth though. The performance can feel sluggish sometimes — I think they could allocate more resources to the servers because basic tasks shouldn't feel slow. Anything graphics-heavy is rough too — Google Maps, websites with a lot of animations, anything with heavy visuals just crawls. Printing is another pain point. It's noticeably slower than printing from a local machine and sometimes it just doesn't cooperate.<br> And the worst part — when the server goes down, everyone stops working. It doesn't happen often, but when it does there's nothing you can do but wait. That's the trade-off of having everything centralized.</p> <h2> Final Thoughts </h2> <p>DaaS makes a lot of sense for most day-to-day work, but it's not perfect. If you need performance or you rely on anything graphics-intensive, you're going to feel the limitations. Still, the convenience and security make it worth it overall.</p> cloud performance productivity security Mateo Silva Sun, 12 Apr 2026 06:21:49 +0000 https://dev.to/mateossb/why-my-nintendo-switch-2-cant-find-the-wifi-and-what-im-doing-about-it-1lf https://dev.to/mateossb/why-my-nintendo-switch-2-cant-find-the-wifi-and-what-im-doing-about-it-1lf <p>So I recently picked up a Nintendo Switch 2, and before I could even download my first game, I ran into a networking problem that's taught me more about WiFi than any textbook has so far.</p> <p>The Objective</p> <p>Simple enough — connect my Switch 2 to my home WiFi and start gaming.</p> <p>The Hurdle</p> <p>The Switch 2 couldn't detect my WiFi network. After some digging, I found out this is a known bug — the console struggles to discover networks when the signal is too strong nearby. My Xfinity gateway is in the same room, so being too close was actually part of the problem.</p> <p>I tried everything I could think of: splitting the 2.4GHz, 5GHz, and 6GHz bands into separate networks, changing the security mode between WPA2 and WPA3, creating new SSIDs, and digging into the Xfinity gateway's advanced settings through the browser. None of it worked.</p> <p>I escalated — had Xfinity replace the gateway, then had Nintendo replace the Switch 2 itself. Same problem both times. At that point, it became clear this is a software-level bug on Nintendo's side.</p> <p>Living in an apartment complex makes it worse. The Switch 2 seems to get overwhelmed by the dozens of WiFi networks broadcasting from neighbors on every side, which is likely why apartment dwellers are getting hit the hardest.</p> <p>The Workaround (For Now)</p> <p>Here's the weird part. If I walk to my apartment door, the Switch suddenly finds my network. I can connect and then move anywhere in the apartment — the connection holds. But if I dock the Switch to play on TV (which uses Ethernet) and then undock it, the WiFi drops and I have to walk back to the door again.<br> So my current flow is: walk to the door, connect, walk back, play. It works, but it's not a permanent solution.</p> <p>What's Next</p> <p>I'm planning to add a TP-Link access point (EAP225 or EAP670) connected to the gateway via Ethernet, with its own SSID, WPA2-PSK security, and a fixed channel — a network I fully control that might behave differently with the Switch's firmware.</p> <p>What I've Learned</p> <p>A stronger signal isn't always better — device firmware matters just as much.<br> Methodical troubleshooting matters. Isolate variables one at a time before drawing conclusions.<br> ISP gateways trade user control for simplicity, which can box you in.<br> Sometimes the problem isn't your network — you can do everything right and still be waiting on a firmware fix.</p> <p>I'll follow up once the access point is set up, or once Nintendo drops an update. Whichever comes first.</p>