You know what’s bad DX? Your company’s product having a massive security breach, people stop using it, and having to lay off all the software engineers
I wonder how doctors feel about people consulting ChatGPT. I know a doctor who can't stand people getting medical advice from quacks on TikTok, but that's probably a different problem/pattern
Thanks for calling that out. I went through and extracted a good handful of those. It’s not a short list. It’s a handful.
“””
The subsidy era is not winding down gracefully. It is showing cracks everywhere.
…
the question is not whether they got a good deal. The question is how long that deal survives.
…
A developer running three or four concurrent coding agents is not consuming 3x or 4x the tokens of a chat conversation. It is an order of magnitude more
…
These are not experiments anymore. They are load-bearing workflows.
…
That is not a rounding error. That is a line item that needs its own budget code.
“””
Consultants or professional services folks will be working in their company’s GitHub account and several clients. Requires managing lots of git/GitHub accounts
We should be able to pin to a version of training data history like we can pin to software package versions. Release new updates w/ SemVer and let the people decide if it’s worth upgrading to
I’m sure it will get there as this space matures, but it feels like model updates are very force-fed to users
我很高兴能在 DuckDB 中使用支持 ADBC 的连接，而且我感觉这将成为更多的用例。