HN user

thedance

613 karma
Posts3
Comments453
View on HN

Here's a don't: don't bring some BS document for the fired person to sign. They have no reason to do so and shouldn't feel pressured to execute something like a non-disparagement agreement, unless it comes with a big checks stapled to it.

The backlit display on the Tesla 3 is wayyyyy too bright for night driving, even at its lowest backlight intensity and in night mode. It is like they intentionally ignored all available human factors research. Tesla is not alone here. Many automakers these days have too-bright interiors for night driving.

At least in the US models of the Fit there's no difference in the interior trim levels. I think part of the confused nature of this discussion is that Honda never shipped the touch-only dashboard that this article is talking about in the US market. The Fit and as far as I have seen every model Honda sells in the US has always had real knobs and switches for the climate controls. The touch climate controls were available in Japan and elsewhere.

ETA:

Non-USA interior: https://img.sm360.ca/images/article/the-honda-way/58810//the...

USA interior: https://file.kelleybluebookimages.com/kbb/base/evox/StJ/1082...

Why do I need my camera to have GPS? In what situation would I be equipped with a camera and not my phone, which certainly has a GPS? This seems like the same instinct that makes OEMs put mobile modems in laptops, as if I would ever have my laptop but not my phone to which to tether it.

Reading the blog post (haven't read the paper yet) makes it sound like this technique might apply to fuzzing. If this thing seeks out and exploits novel states in a large state space, that's the kind of direction you want in your fuzzer too.

Yeah but it’s a press release. What I’m telling you is if you walk to this site today, they’re still working on it and far from being done.

Building houses in factories doesn't really solve a big problem. We're actually really, really good at building on-site. Just look at the experience of Factory_OS and their building that was "built in 10 days"[1]. While it may be the case under a narrow interpretation, it's also the case that the project spent a year in site prep, 5 years in planning and permitting, and six months after "building" it they are still detailing and finishing and are another 6 months away from occupancy.

https://factoryos.com/press/housing-development-erected-in-w...

Zoom is a wall-to-wall security disaster. When my company switched to it about a year ago one of my colleagues showed me how to force any Zoom room, anywhere on the planet, in any organization, to join our meeting. I just don't think it was architected for privacy and security, and you can't add those things later, so you should be prepared for a years-long trickle of this kind of news.

Example: hoisting the condition `if buf[i] < 0x80 ...` out of DecodeVarint into DecodeTagAndWireType speeds up the included microbenchmark by over 10% on my machine, just because it eliminates the function call for tags 1-15 (these are the magical tags, if you are using protobufs in a performance-sensitive context).

You can beat the pants off this, even though it beats the standard proto library. Most of the time here is being spent calling out-of-line functions through Go's stack calling convention because the Go compiler hates inlining. For example, DecodeTagAndWireType is CALLing DecodeVarint, even though that's really where you want it to have been inlined.

If your use case is really simple, and you want the fastest possible proto decoding, you can hand-roll it pretty easy.

  message point { fixed32 x = 1; fixed32 y = 2; }
Then your code is structured such as
  var x uint32
  var y uint32
  for len(buf) > 0 {
    switch buf[0] {
    case (1<<3) & 5: // Field 1, type fixed32
      x=binary.LittleEndian.Uint32(buf[1:])
      buf = buf[5:]
    case (2<<3) & 5: // Field 2, type fixed32
      y=binary.LittleEndian.Uint32(buf[1:])
      buf = buf[5:]
    default:
      // Freak out somehow
  }
Improve the exception hardness of this code to the extent that it suits your use case.