[snakeyjake]

>I know many people on HN hate the idea of RTO

The six months we were WFH were the worst six months of my career. Nothing got done.

Granted, I am in a specialized field and most of my work requires calibrated equipment in purpose-built labs but so many people just wanted to sit at home and click around on Digikey and complain about SolidWorks being slow on their laptops.

I could never do the kind of engineering that doesn't result in a physical object that exists in the real world. The group photo at the end, standing next to a new thing that nobody else on Earth has ever seen, makes dealing with all of the PMPs worth it.

edit: and software guys need to put on some god damned clothes and come into the office, too. I'm not paid enough to troubleshoot over email or slack the hacked-together nightmare of a virtual environment that "works on my machine" but throws ten thousand errors when set up on a test stand.

[AlotOfReading]

I can't relate to the sentiment here. I also do the kind of work that results in physical objects in the real world. Conservatively, 95% of that work can be done with an SSH connection or the postal system. Most of the rest are fine with a webcam to a bench somewhere. The remaining day every 3 months or so I'm fine meeting in-person, but I don't want to organize my life around it.

My experience is that the infrastructure you need to do effective remote work is also the same infrastructure you need to debug issues in the field, so you may as well build it upfront.

[snakeyjake]

How do you measure temperatures on each board revision after it comes back from SMT fully populated to make sure there are no shorts as you do initial system bringup over SSH and a webcam?

I am unaware of any remotely-controlled temperature probes.

Just last month we had a board come in to I&T with a short on the N1V5 rail and due to me, the designer, actually being there I knew it could only be in a handful of locations so I took the thermal camera and swept the board, found a hot component, and then found a solder ball beneath the pins of the IC and sent it back for rework.

I only found it by realizing that specific component almost never fails and never fails short anyways, then knowing that it has a bottom thermal dissipation pad where any excess solder application can squeeze out, and then rotating the microscope to its maximum deflection and peeking underneath the component at an angle of 55-60 degrees. https://imgur.com/a/1hFBNEL

30 minutes. Compared to days of back and forth and waiting online.

Techs don't know the board and the components, that's not their job. Engineers do-- that's their job.

Or is doing that basic and simple engineering work "for the schmucks to dumb to wfh?"

I can see it now. Me sitting at home squinting at a webcam feed shouting "ok move it over to the left, a little more, a little more" debating in slack like a moron with all of the other prima donnas too important to drive in to work as my techs cuss me out for being such a loser.

My techs don't do anything unless I do it first, document it, do it again to check the documentation, and then observe them doing it to make sure my documentation covers everything. And I mean everything, from short tests to the final cleanup of the workstation.

[AlotOfReading]

You mail it or come in for those few days you need to verify things. Are you spinning new revs every day or something?

Honestly, I don't mind if you want to work in the office. Maybe it makes your job easier, but what I've found is that for the tasks I do it just adds a commute for no reason.