Creatively Different Builds

1,250 Square Meters. 30+ Devices. No Logic. WHERE IT STARTED The property has around 1,250 square meters — house, offices, storage, and a store. At any given time there are 20+ active devices on the network. On busy days that number climbs to 30. TVs, phones, tablets, PCs, POS systems, security cameras, and everything in between. The original setup was a collection of repeaters with no logic behind them. Each one doing its own thing, creating its own network, fighting with everything else. The result: devices losing connection constantly, having to manually switch WiFi every time you moved across the property, IP conflicts between wired and wireless devices, and zero visibility into what was actually happening on the network. This wasn't a simple home network anymore. It hadn't been for a long time. It needed a proper solution. The Decision: Skip the Easy Option. WHY OPNSENSE The ISP router does what ISP routers do — basic connectivity, no real control. For a netwo...

  The Laptop Had Speakers. The Desktop Didn't. WHERE IT STARTED When I was on the Lenovo Legion, audio was solved. Built-in speakers, done. But my daily work includes construction sites — loud environments where you need to hear clearly, protect your hearing, and still be reachable. International work trips added to that. I needed something for the street, for the plane, for the noise. That's when I bought the TOZO Crystal Pod. And I still have them. Still use them. That purchase was never a mistake — I just kept solving new problems as the setup evolved. The Crystal Pod Solved the Street. Not the Office. PROBLEM #1 The Crystal Pod works exactly as intended for outdoor use. Construction sites, travel, loud environments — they isolate well, they're compact, and the battery lasts long enough that running out mid-day isn't a concern. The problem came when I moved to the desktop and started using them at the desk. The isolation that made them great outside made them impract...

  My Daughter's Tablet Was Collecting Dust. WHERE IT STARTED I bought an Amazon Fire 7 Kids tablet in November 2022. It did exactly what it was supposed to do — durable, controlled, something a kid could actually use without destroying. My daughter used it for years. Then she grew up, the tablet got more boring than what she needed, and somewhere along the way it ended up in a drawer, covered in dust, completely dead. I found it months later and figured it was done. Plugged in a charger anyway. It turned on. Fully functional. I paid $55 for it in 2022. My daughter used it for two years. And now it runs my entire desk. I Wanted a Macro Pad. I Didn't Want to Buy One Blind. THE PROBLEM From November 2025 I'd been researching how to add more ergonomics to my desk setup. The PC came together fully at the end of February. But coming from the Lenovo Legion that burned out, I wanted more control over the functions I use constantly. A macro pad made sense. The problem: I...

This Isn't a Typical Home Network. WHERE IT STARTED Most network guides assume you're covering one house. I'm covering a property — house, storage area, offices, and a store spread across roughly 1,250 square meters (13,450 sq ft). Three access points, 20–24 active devices at any given time, and no direct access to the ISP router. When I set up Moonlight to stream games from my office to my bedroom, I realized fast that the network was going to be the hard part. Not the software. Not the hardware. The network. Four Networks. Zero Coordination. Complete Chaos. THE PROBLEM Before I fixed it, this is what I was working with: the ISP router doing its own thing, and each access point creating its own separate network on top of that. Four different networks on one property. Every AP wanted to run its own DHCP server. That meant IP conflicts constantly — especially between devices connected by LAN in the office and devices on whatever subnet the nearest AP decided to assi...

The Keyboard Broke. That's How This Started. WHERE IT STARTED My Lenovo Legion's GPU connection burned out. Not worth the repair. I stripped the drives and moved on — but I still needed a keyboard and mouse while building the new desktop, and I wasn't in the mood to manage cables on top of everything else. The Logitech MK270 wireless combo made sense. Fast, affordable, no extra dongle mess. I used it for about a year. It did exactly what it was supposed to do — until it didn't. After a Year, the Keyboard Started Fighting Back. WHAT BROKE THE DEAL It wasn't sudden. Shift started requiring more force than it should. Then Enter. Then Space. Keys that should register on a light press started needing deliberate pressure — the kind where you notice you're pressing instead of just typing. I don't know if it was dust, wear, or just the cost of a budget keyboard. But it was consistent, and it was spreading. The mouse was a different issue. The MK270 mouse w...

Remote Gaming Was Always the Goal. THE BACKSTORY Before Moonlight, I was a GeForce Now user. Cloud gaming on someone else's hardware was simple, with no setup or maintenance. You just connect and play. It worked, until it didn’t. GeForce Now isn’t available in Bonaire. Plus, with over 20 devices sharing the same network, the latency made it unplayable. So, I stopped paying.  But the idea never left. Playing from the couch, from bed, or anywhere in the house without moving hardware has been the goal for years. Moonlight is the version of that idea I can control. My hardware, my network, my rules. Moonlight Looks Easy. The Network Isn't. WHERE MOST GUIDES STOP Every Moonlight setup guide covers the same steps: install Sunshine on the host PC, install Moonlight on the client, pair them, and done. However, those guides do not address what happens when your network pushes back.  This is the part that nobody documents: the actual issues I faced while setting up Moonlight ac...

The GPU Upgrade That Didn't Feel Like One. WHERE IT STARTED I had a Lenovo Legion 5 Pro for three years. RTX 3060, solid machine, handled everything I threw at it — 3D rendering, design work, gaming. Then the GPU connection burned out. Not worth microssoldering, not worth the repair cost. I stripped the NVMe drives and moved on. What I had left was an old i5 with 16GB RAM and a GTX 1070. Not ideal, but functional. That became my workstation while I bought parts piece by piece to build something proper. First purchase: an RTX 5060. That's where the problems started. A New GPU in an Old Machine. Big Mistake. THE FIRST PROBLEM I installed the RTX 5060 in the old i5 build expecting a performance jump. What I got instead was FPS dropping to the floor the moment I opened any game. The GPU wasn't the bottleneck. The CPU was — and the thermal paste on that old i5 was completely dry. A $7 thermal paste swap from a local store dropped temperatures enough that I could actually play. N...

Same Desk. Same Machine. Not Enough Freedom. THE PROBLEM I work at a desk. My gaming setup IS my work setup — same machine, same room. An i7-14700F paired with an RTX 5060, built for 3D design, rendering, and gaming. But long work sessions have a cost: when the day is done, the last thing I want is to walk back into the office just to play or fix something quick. My office and bedroom are close to each other. But close isn't the same as there . Some nights my wife is watching her shows. Some mornings I'm up before 6am and don't want to wake anyone. The office felt like the only option — and that got old fast. The solution wasn't buying a second PC. It was building the right system around the one I already had — so I can use it from anywhere in my home without moving a single cable. Here's exactly what I built, what I use, and how it works. If your situation is anything like mine — one powerful machine, multiple spaces, shared living — this might work fo...