• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: October 18th, 2023

help-circle
  • Ubiquiti has had outages in the past that meant you couldn’t manage the equipment right in front of you.

    Even discounting the potential security implications of that kind of management, the rage I would feel in that situation is enough that I while my AP is nice, works great, I will never use any of their gateways.

    I’m using a 2.5g protectli with OPNSense now, and it’s easy to manage, and all local.





  • I’m working on moving to local control as much as possible for my smart home stuff. Switched to zwave for my thermostat from nest, excellent move, I don’t lose connection (and automations) randomly anymore.

    Also ripping all my optical media for jellyfin to avoid relying on these assholes deleting stuff from their streaming catalogs for tax breaks.

    It’s not just google, it’s all of these companies.


  • Google is not an endpoint if you wanna be a money-laden tech bro. To get real cash you gotta create a startup and grift some money out of VCs. To do that, it helps if you “innovated something totally new” at someplace with name recognition like Google.

    Everything except search and ads are simply practice grifts before the real grift. You cannot rely on any Google product to last for any length of time, even properties Google purchases will lose reliability as they fall into disrepair and neglect, see Nest.

    I used to love Google everything, I was on the wave beta. I was one of the first with a cr-48. It is sad for those of us that want to contribute to something big, cool, and impactful, watch for fuschia to implode next, I think it already started when they “had” to layoff “over hires.”

    One or two person teams don’t put a man on the moon. It takes a lot of really smart people working on very small specific things together to make world changing stuff happen, the culture of Big Tech is not conducive to “real” work anymore. It’s big grifts run by little grifters.





  • The short answer is “practice”

    The longer answer is, do it a lot. Listen in code reviews. When you investigate bugs, do actual root cause analysis, understand the problem, and understand how it got missed. Don’t stop learning, study your languages, study design patterns, be intentional in what you learn.

    I had good mentors that were hard on me in reviews. Developing a thick skin and separating criticism of you from criticism of your code will help a lot in terms of learning in reviews.

    Source: 10 years in the field. (Senior SW Eng. Focused on embedded systems and VnV)