Neat idea. Why logs, and not metrics too? You can characterize an accurate "baseline" system behavior through a combination of system level and userspace metrics. This profile would offer more depth than what you'd otherwise piece together with userspace logs.

Agreed! Metrics are a high priority, especially since working to increase the available context around each anomaly we flag.

Logs were a natural starting point because that’s where developers often spend a significant amount of time stuck reading & searching for the right information, manually tracking down issues + jumping between logs across services. In a way, just finding & summarizing relevant logs for the user gave people an easier time debugging.

But metrics will introduce more dimensions to establish baseline behavior, so we're pretty excited about it too.

I tend to use logs the least when debugging production issues. I realize that's a personal anecdote, so I see your point.

At this point a Musk tweet is likely priced into the asset

Yeah. It’s especially frustrating when recipes list ingredients like flour by volume.

Depending on how one stores and scoops, there can be a 25% weight difference between what is on the recipe and what is on the bowl :/

That's TC though, can't think of a company that pays this much in base.

130k base salary is comparable to a new grad or mid level SWE in the bay.

For many companies, that TC is very liquid. Some don't even have 1-yr cliffs anymore and tech stocks aren't exactly hurting these days.

It doesn't really need to be taken to Twitter. There's almost zero benefit in publicly shaming your colleague like this.

Twitter is also (but isn't the only) tabloid social media. It promotes the sharing of sensational and one-sided content that is scant on details. I know we're supposed to be critical about what we read, but my first instinct was to assume Henry was a bad guy.

It would have been better to see this discussion in a forum or mailing list or anywhere that is designed for an actual longform discussion. Even if in public longer more detailed discussions can capture the nuance.

It's an example of how real life pricing deviates from Black-Scholes. At the same time the pricing is correct in a sense that tail risks are greater than would be expected from a random walk.

For a moment there I thought was gonna be written by Richard Branson.

I must be shallow but these massive feature-rich updates they produce continue to make me want to use VSC less. I just don't want to have all these features I know I'll never use baked into my code editor

>I know I'll never use

Well, let's see.

Improved tree navigation - you'll use that.

Improved shorcut configurartion - you'll use that.

Faster terminal rendering - you'll use that.

Better debugging - you'll use that.

Annotations on tabs (e.g. tab has modified content git-wise) - you'll most likely benefit from that.

Terminal profiles - you might not use that. For many it will make their work several keystrokes lighter.

And so on...

It's not like they add some exotic features. If you don't have a use for any of that, sure use Joe, Vi, whatever...

You can turn a lot of it off, I had to do that for this and MS Edge recently. Or you can just us Vim.

Which is a shame. I can think of an handful of records that sound exactly like their cover art and I believe that detail helps tie the record together

If you want to appreciate the album art then purchase the LP. A tiny JPEG on AM or Spotify UI is never going to cut it for anybody who is interested in inspecting the cover art. These tools are designed for background listening