It’s a recent development. First the LiDAR manufacturer leaked that they sold them to Tesla. Then several teslas had been spotted with LiDAR rigged on to their roofs. Then in a lawsuit an engineer admitted they’re training fsd with LiDAR

https://www.theverge.com/2024/5/7/24151497/tesla-lidar-luminar-elon-musk-sensor-autonomous

https://arstechnica.com/tech-policy/2024/05/tesla-must-face-fraud-suit-for-claiming-its-cars-could-fully-drive-themselves/

https://www.reuters.com/technology/luminar-says-tesla-is-biggest-customer-its-lidar-sensors-2024-05-07/

https://www.cdotrends.com/story/4083/lidar-u-turn-elon-musks-fools-errand-becomes-teslas-secret-weapon

Waymo doesn’t give a shit if their cars are ugly and can cover them in dozens upon dozens of cameras and sensors. They’re not selling them to consumers who care about looks, they are renting them to riders who don’t want to die on the short trip. They also only operate in a small region of the country with limited weather conditions and frequently stop service when weather is bad.

Tesla is run by an idiot who insists that a pair of cameras and a single lidar sensor that they keep deciding to disable can somehow magically always work in all weather and lighting conditions and is selling to consumers who don’t want an ugly car and expect to be able to operate their purchase at all times

Different constraints leads to different levels of success

I saw FFDI. Not much better.

IIRC wifi6 added the option for backplaning to be a different frequency, but not everyone implemented it. 6e even added 7ghz but basically nobody implemented it. So even with brand new equipment, you were super at the mercy of your end user devices and whether or not your mesh was physical or wireless and whether or not the mesh nodes themselves supported the same backplaning channels.

This will drive billions into refining the surveillance state. They now know they need genuine original human interaction and will do everything possible to capture everything from texts to cctv footage

OP is not entirely wrong. At least in Linux land you can now implement EDR like functionality entirely with EBPF without installing a fucking rootkit. So traditional EDR products are a grift if you are on the bleeding edge.

Management: Our consultants don’t know what ebpf or what immutable filesystems are so obviously your wizard magic is not better than crowdstrike. Also IT will be in charge of that one component and clickops it bypassing the entire CICD pipeline and sanity checking system you have. It’s for compliance which is our word for shut up or we fire you.

You usually run into issues if you are trying to use off the shelf tools and git providers. IMO GitHub and GitHub actions sucks hard for monorepo. The fact that all actions have to be stored in a single directory for example almost certainly is unmanageable rats nest waiting to happen at any sufficiently large business with a sufficiently complex product or set of products.

This is why companies like google run their own forms of git with custom wrappers to let you do things like pull a segment of the terabyte sized repo or run partial builds with tooling that basically runs some kind of graph against the changes. Bazel for example had to be invented to help solve that problem at Google and pants similarly for twitter (who also has a monorepo)

If you are willing to invest in using tools like bazel and own building all these complex wrappers then it can be fine. But if you want to off the shelf gitlab or GitHub actions and use your IDEs built in git tooling it’s not going to be for you. That’s the difference between what’s possible or a good idea at a medium shop vs a company with 40k engineers

In my experience at a company that just moved away from monorepo, half the off the shelf vendors and foss tools out there balk at you if you expect monorepo support. We moved away specifically because at our current company size it is more tolerable to have our different products separate and eat the occasional pain of mass pattern adjustments across the repos than to build out a team to manage the custom tooling required for a gig plus sized monorepo

Plus, even google doesn’t have a true monorepo. Chrome and Android are not in the same repo as search for example. Find your seams and manage them appropriately

This. We tried to ban windows and literally the ELT blocked it because they personally didn’t want to learn MacOS despite the entire engineering, product, and medical team being on it. We now keep having to pay more for audits and for security solutions for the 15 people refusing to get off windows in mostly the finance part of the company

One could argue the requirements have changed because the security and compliance part of the world finally caught up to modern software delivery concepts. Even the most dinosaur apps at compliant orgs are being dragged kicking and screaming into new CI/CD tools where applying governance and custody chains and permissions and approvals are all self documented automated hooks.

For me it’s that arbitrarily not pairing them gives a higher end experience than pairing them. You can play music over multiple by just selecting them all when you air play. The only difference is the lack to stereo, which if you have them all over your house you wouldn’t want anyway.

Meanwhile if you do pair them, then it’s stereo only. So if they are placed around the room, then arbitrarily you can’t hear some notes or vocals out of both speakers. Plus if you use Siri, for some reason only the left speaker speaks. We have an open concept kitchen and had one speaker in the counter and one in the living room on the tv stand and it was just overwhelmingly stupid to have only the speaker in the kitchen speak back.

It’s also stupid I can’t buy a single big home pod and pair it with 2-4 minis to make a 7.1 surround. Or even just pair more than 2 minis.

I was suggesting to do neither and run the container directly. Putting k8s on top of lxc is still completely stupid. Just run k8s bare metal to operate your containers.

Run docker within lxc within proxmox. This gave me an aneurism. You’ve lost the whole point of not actually virtualizing with containers by putting in two layers deep in virtualization. At this point your shit is so convoluted why don’t you just run kubernetes

Averages are fun. It’s likely Opsy roles do have the highest average. But it’s also very true that devs have the highest ceilings. There’s just very few devs making 600+ and the majority at 120-150. Then there is an absolute shit load of opsys making 160-200. So in ops you hit the ceiling super fast while the occasional dev just keeps rocketing to bullshit pay but the averages are what they are

(Hiring manager for devops. I get the raw data through a corporate data broker)

VPN is inherently not zero trust. You really should be moving to ZTN based tools

Seconding the other comment, lots of orgs picked .lan and then over the last few years have moved things into the cloud and .lan has become a meaningless soup since half the shit isn’t even on local network. Now it just means “needs a vpn or ztn to talk to”

Luckily my last three orgs finally bought a second domain for private dns. It’s quickly becoming a pattern that myorg.com owns myorg.tech or whatever for private traffic. Domains are cheap as fuck compared to everything else a business spends money on, it’s really silly how many people are using hacks for this