hosted voice M365 cloud environment on a VLAN + CRM Ubiquiti UniFi for approx 1kSF office Firewall / MDR / EDR / Automated patching / SaaS backup / MFA Intrusion detection primarily through Intune policies SaaS Protect / Backupify + Windows Backup and Restore None redundant servers, portability, teams integration / less app fatigue, b2b SMS, portal administration can't think of any risk from the telecom infrastructure. More on reddit.com

When AT&T was split into the Baby Bells, the national infrastructure (microwave and later fiber) remained AT&T More on reddit.com

The problem is that most of what people get exposed to early in their computing experiences is the stuff that runs on top of the network. Gaming runs on top of the network, which leads to server administration and Linux exposure and database systems and software development and the like. That's the most common path into advanced computing for most people, and the network is just something that sits between them and what they're trying to do. When the network breaks, it's usually well outside of the control of what they're able to influence so they don't get exposed to it. Even within my IT program I went through (admittedly close to 20 years ago at this point), the routing and switching classes were 400 level classes - not because they were inherently more difficult, but because conceptually people just hadn't been introduced to the topics and most people would take other paths away from it. I regularly see people asking about why networking is so hard and the answer is that it largely isn't, it's just that you're introduced to everything else first without being introduced to the networking concepts until much later in life. If you don't have the networking background, telecom largely becomes an afterthought. If you do develop an interest in networking, you usually start learning what you can get your hands on - you're buying a lab with gray market switches and routers to test enterprise solutions because, again, that's where most people will go. The problem for getting people into the telecom field is that most people don't go out and homelab stuff like DSLAMs and CTMS terminals or GPON OLTs or DWDM line systems because it's a lot of work and a lot of cost to get into a small niche. So what are the paths to getting into telecom? It's usually going through a NOC or doing field work. Having been in the field early in my career, most of the field techs are basically limited to installing and they need to be motivated to move into field engineering, and frankly most people just aren't that interested in learning it. It's a job to them and they're not inherently looking at how to dig into the knowledge but instead are focused on how they can do their day to day stuff as easily as possible. A fiber splicer is interested in how to do fiber splicing better but often doesn't get exposed to the gear that's running over the fiber. Installers are often out there running fiber and racking up gear but rarely interfacing with the equipment as well. People have to want to climb that ladder, and you'll find that a lot of people in life just want to be somewhere comfortable. More on reddit.com

We can! But if you’re talking wireless, wired, full access you need wireless spectrum, fiber backhaul, build outs, permits, hardware, and people. It’s a multi decade investment and that’s assuming you can even acquire the wireless spectrum to use. And then just maybe we turn a profit. At that point we’ll be the best, most advanced carrier and some user will post on Reddit 3.0 (that pays us to host them) how great we are but they miss the old Verizon (that we put out of business) because they were at least affordable. More on reddit.com