We use Node.js, so all we need to do is run a script initializing Otel before running the app. We set this up following the docs a few years ago, and haven’t had to change it much since then.
I think their point is that there's business value in the usage data and linear is using that value in a way that benefits them but not the customers they got it from.
It reminds me of matt levine's reframing of insider trading where it's not about fairness it's about theft. You're supposed to get secret insights and use them to get an edge. What you can't do is get an edge for yourself with secret insights that your employer got.
So it roughly comes down to "that data is valuable and rightfully belongs to the originating company." Which then makes this a contract diligence type situation.
My company uses Linear. The data presented in this blog post is worthless to me and the company. It can be crudely summarized as “agents and agentic development processes are conducting more Linear operations.” Duh!
> Anyone else finds the LLMs version control discipline lacking?
No? How do you define discipline? Claude code knows how to read and write commits. My team just granted it limited force push access a week ago. We’ve taught it to make more human-friendly commit messages.
I think a useful question here is “what is a good commit?”, specifically at the MR stage. I don’t care what commits look like on your local machine.
I tend to like to treat commits at that stage as complete, atomic thoughts.
“This commit is a refactor of this function name”
“This commit defines all the data classes we’ll use”
“This commit writes the new function and all its tests”
“This commit injects the new code into the old path with a feature flag”
“This commit fixes the tests that broke from that change”
Some of these would be better served as separate MRs entirely; but I imagine my idea stands.
I have the technical acumen and money, but zero desire or time to spend ripping discs. It's far too easy to raid the "five dollar bin" at MoviesAnywhere (like I used to do at Wal-Mart and Best Buy).
Licensing issues like Sony's aside, the studios did MoviesAnywhere right. I can buy the disc (often used) and redeem the code, or buy digitally, and download/stream everywhere that matters to me and my family.
If you already have Elasticsearch, it makes sense to continue utilizing it.
Saying, “just use SQLite” completely dismisses the idea that this is a _shared_ memory across teams. The ability to easily connect to the remote service and have everything “just work” pays dividends when you have dozens or hundreds of users.
I’m literally laughing at the root comment’s idea of proposing we replace ES with SQLite and imagining how that architecture review would go. Not everyone is doing MB/GB scale workloads.
that would be a pretty frail architecture too, I think I recall ES even saying not to rely on it for data persistence. Every time I've worked with ES it was always backed by some other database used as a source of truth.
This is a important bit of information which either gets lost or ignored for convenience at times. Other side of it is the fact that this open up the door to keep two data stores in sync which is a much bigger battle for a lot of small companies or teams
The current administration doesn’t care about climate change, or believes it’s a hoax. Given this, they see no need to fund research and data gathering that tells them otherwise.
No, they are attacking any and all forms of data collection that can be connected to climate change - even if it's not specifically for climate change.
Records of environmental data are a huge pain in the ass for those invested in fossil energy and adjacent industries.
The truth is hurting business and they seem to be going on a rampage actively killing it at the roots. Stop collecting and recording data, destroy and hide the existing data and close the institutions.
This is not true, most people care about climate change, even in the US (https://climatecommunication.yale.edu/visualizations-data/yc...). Maybe you think "if they care then why are they still driving/flying/eating meat/whatever" and I sympathize, but climate change is not an issue that will be solved by individuals taking responsibility, in the same way that wars still happen even when the vast majority of the population oppose them.
If you're wondering why they don't at least vote for someone who cares about climate change, I don't know. But claiming people don't care at all is not true and is self-defeating, because it makes people who do care think "I guess I'm in the minority, there's no point in trying".
>I guess I'm in the minority, there's no point in trying
Thats exactly how it is.
Look at the current politics discourse. Even now, in the presence of ordinary people, there can be a conservative who supports Trump, but you are supposed to be "nice" to them, because its all just political opinions, and those ordinary people are removed from the real destruction of lives that the current administration carried out for many people.
Same with global warming. People are far removed from the real effects, so most people just don't actually care.
And in the same way that all the anti vaxxers who got covid and urged others to take the vaccine before they died, people need to get hit over the head with reality before they start to care.
The only way forward that doesn't involve mass famine/death is some low level societal control that forces people to behave for fear of real consequences.
> Honestly, at this point, having natural disasters with destruction and death is probably the only way to make people care
We already have them. People just claim they're chance effects with no connection to climate change.
The problem with refuting it is that they are chance events, there's no way to definitively say "this was caused by climate change", because it's always possible it would have happened anyways. It's the upwards trend in frequency and severity that we can definitively point and say "that's caused by climate change", but that's too abstract for most people to understand.
I follow the [gateway deployment pattern](https://opentelemetry.io/docs/collector/deploy/gateway/). Everything sends telemetry to our gateway, which exports to ClickHouse (formerly Datadog).
We use Node.js, so all we need to do is run a script initializing Otel before running the app. We set this up following the docs a few years ago, and haven’t had to change it much since then.
reply