What tickled me into making the comment above had nothing to do with whether adoption rate was used by the author (or is used generally) to mean market penetration or the rate of adoption. It was because a visual aid that is labeled ambiguously enough to support the exact opposite perspective was used as a basis for clearing up any ambiguity.

The purpose of a time series chart is necessarily time-derivative, as the slope or shape of the line is generally the focus (is a value trending upward, downward, varying seasonally, etc). It's fair to include or omit a label on the dependent axis. If omitted, it's also fair to label the chart as the dependent variable and also to let the "... over time" be implicit.

However, when the dependent axis is not explicitly labeled and "over time" is left implicit, it's absolutely hilarious to me to point to it and say it clearly shows that the chart's title is or is not time-derivative.

I know comment sections are generally for heated debates trying to prove right and wrong, but sometimes it's nice to be able to muse for a moment on funny things like this.

Yes. The title specifically is beautiful. The charts aren't nearly as interesting, though probably a bit more than a meta discussion on whether certain time intervals align with one interpretation of the author's intent or another.

It really is a beautiful title.

> Prices for a TC2 start at €44.500 excluding taxes (€53.854 including 21% btw/Dutch tax).

A large impact on the extent to which WFH may need to come at a discount is specialization: If you're easily replaceable with an in-office worker, why would the company deal with remote? If you're not so easily replaceable, the company is more likely to be willing to work with you on your terms.

There's generally been a large disconnect between the job market in the tech sector and the rest of the economy, at least until a few years ago. There's now much more of a bifurcation within the tech job market, where rank-and-file and entry level software engineers are suffering while experienced and specialized software engineers may be doing better than ever. This plays into the RTO/WFH discussion because some people may not have the option to get their preference at any discount, or given either option in the first place.

This ends up being very effective with interpolation between known viewpoints, and hit-or-miss extrapolation beyond known viewpoints.

Obligatory Jobs monologue on marketing people:

https://www.youtube.com/watch?v=P4VBqTViEx4

I managed to eke out a couple more years after Pebbles were discontinued by finding replacements on ebay. If this is a low volume run, I'm contemplating the opposite—whether I can justify not buying multiple while I still can.

One pattern I bump up against from time to time is the delta between using a perfectly defensible technique for a given use-case (safe delimiters when constructing an input for a specific function) versus a desire to have each decision be driven by some universal law (e.g. "if you're streaming data between services, using null bytes as delimiters might not be safe if consuming services may truncate at null bytes, so NEVER use null bytes as delimiters because they can be unsafe")

It's not even a matter of one "side" being right or wrong. You can simultaneously be right that this is perfectly safe in this use-case, while someone else can be right to be concerned ("need to consider possible") because the code will forever be one refactor or copy/paste away from this concatenated string being re-used somewhere else.

What was so ruinous about implicit returns? That's one of the things I missed most when leaving CoffeeScript. ECMAScript only partially adopted it (single statement fat arrow functions) which probably muddies the waters for people trying to learn and understand the language's behavior.

Since it's optional for the caller to use or assign the return value of a function, I don't see much problem with functions defaulting to returning something. Maybe it just fits with my personal preference of functions returning a value and not having side-effects..

Seems like the answer to this would be no. Starliner's risk was elevated, not guaranteed to fail. The presence of a flight-proven option was the limiting factor.

I had a funny one a while back (granted this was probably ChatGPT 3.5) where I was trying to figure out what payload would get AWS CloudFormation to fix an authentication problem between 2 services and ChatGPT confidently proposed adding some OAuth querystring parameters to the AWS API endpoint.

Maybe the title should get a [2021] because it sounds like the market has cooled substantially in the last year or so.

The article doesn't seem to take into consideration market cycles, assuming market rate always goes up at a rate that outpaces cost-of-living comp adjustments. While this may be the case more often than not, how are companies supposed to absorb market downturns? A salary reduction, if legal (?), seems almost as bad as redundancy except you risk being saddled with disgruntled workers who might decide to jump ship at the next moment that is convenient for them.

Maybe obvious for anyone with more of a pulse on the latest in the LLM space, but it was new to me and took some digging to get more context.

[0] https://arxiv.org/abs/2210.03629