kvmet

I'll second this. I have found some that use a different button but usually one of them cancels it so feel free to try them all. I think I've found only one that couldn't be at least muted in this way.

But then why not wait a few extra days and then have something to write down in the "Reason" box on his pink slip? Even if this turns out to be true it still smells like incompetence.

For typical Ethernet sure. Although there are newer standards that can use a single pair (1000Base-T1). They are very range-limited though and not what you would normally install in your house.

https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-T1

This concept is also in-line with Lean/Six-Stuff and identifying "wastes". Overproduction (analogous to over-engineering) is usually considered the worst type of waste because not only are you making something you don't need, you're spending effort that could have been used on something that you _do_ need.

I can tell you from personal experience that if you have four names it will turn "First Second Third Last" into "Firstsecondthird Last" (I usually fly Delta).

I asked a checkin agent to fix it but they said it will start rejecting my ID if they change it at all.

Really? I have had horrible issues on OneDrive if my connection is bad. Including extremely frustrating things like reverting files to older versions and completely deleting all of my local work. Admittedly, that was ~3 years ago before I switched to GDrive.

Knots are typically used for aviation. Also different planes have their own optimal speeds for efficiency that the airlines aim for so if you know the airframe you can derive what they are most likely targeting. You can also compare the value to the filed flight plan and see if it is similar.

I have a touchscreen laptop for work and the only real use I've found is testing the behavior of touch-only HMIs.

I have a different but related rule for emails: Only one important thing per email and it has to be as close to the top as possible. If you're sending a list of questions, put them in priority order and don't be surprised if only the first one gets answered.

Also avoid making statements on anything debatable if focusing on that will give them an excuse to ignore the rest. For example I was talking to my doctor's office asking if they could move my appointment to some time in the next two weeks rather than the 15th (8 weeks away at the time). The response I got was, "Your appointment is on the 12th." And then they stopped responding.

I'll spare you my rant on why I don't like InfluxDB lol.

In the end it depends how much data you're dealing with. If you're only ingesting dozens to hundreds of records per second per writer you might actually like AWS Time stream. If you're dealing with a million + rows per second from a low number of writers (e.g. scientific data) then you probably want Influx or Timescale. If you want to host it yourself and you have less than 1TB of data then Influx is okay or if you want it cloud hosted then Influx may be a good option.

If you need full control, scalable, TB or PB of data, etc. Then Timescale is great but it's definitely more work.

Many dentists ago for me but they got a new contraption that could measure enamel thickness. They waved this wand around in my mouth and told me that I was in need of (4) fillings. Now I have always had thin enamel so it's not unusual to need some fillings but I didn't trust this process at all so I told them I'd mull it over and call back. Waited 6 months for next cleaning and mysteriously I didn't need any fillings at all despite having no work done.

I don't think it is necessarily done intentionally, but it's good to be a tiny bit skeptical especially when new factors are involved.

I work with control systems and have a similar mantra: "You can't overcome physics with software." It's super common to have someone ask if a mechanical/human/electrical/process issue can be fixed with software because people believe that programming time is free. Sometimes it's not even that it's impossible to do in software, but adding unnecessary complexity almost always backfires and you'll wind up fixing it the right way anyway in the end.