‘Morale is at an all-time low’: Ex-Googler writes scathing latter slamming layoffs and ‘eroded’ culture::An ex-Googler wrote a 1,500-word letter criticizing the firm and CEO Sundar Pichai’s lack of “visionary leadership.”
‘Morale is at an all-time low’: Ex-Googler writes scathing latter slamming layoffs and ‘eroded’ culture::An ex-Googler wrote a 1,500-word letter criticizing the firm and CEO Sundar Pichai’s lack of “visionary leadership.”
IIRC the Google Wi-Fi app had some extremely simple selection process in the port forwarding that allowed you to review the device list with IPs and select for port forwarding. The app would then carry the pf rule regardless of dynamic DHCP. Seems very simple functionality that now requires multiple steps to achieve. I’m sure in the product management meetings they assumed the new Nest users were too dumb to handle such logic or just overlooked the functionality in general to speed the migration from Google Wi-Fi to Google Home. Seems like a great mini case study for poor product management.
Ah, you’re right. It does work with dynamic addresses.
It works like this for me, currently:
Gotcha, maybe it’s the fact I’m running iOS, I can’t get any type of rule or DHCP assignment options to show up. Just the same two options for telemetry and Nest. Oh well, thanks for the help. I’m getting my new router Tuesday and should be off to the races!