2,217 karma · joined January 17, 2018
(i agree that maybe OP pointing that out is nitpicking, but to steelman the case, such inaccuracies are what code review would find and are the subtle bugs that might pass a code review and break prod)
> easily identifiable problems
sent me down. as soon as I parsed that line I stopped reading, and I tabbed back over to spot them
> people are sleeping on the ChatGPT Work/Codex
just in general. I find it to be far superior (imo) for all tasks atm. Claude just overdoes things in writing, coding, architecture, etc
> One caveat: my experience comes mainly from working on infrastructure and developer tools at large companies, on teams where engineers have a lot of bottom-up autonomy to influence their roadmaps. In a more top-down environment, there may simply be less room to work this way.
I wonder if the overall trend in tech is that engineers are experiencing less bottom-up autonomy and more top-down controlled environments. I would be curious to see how many tech companies (or the average engineer's experience) have changed from being tech led where engineers have autonomy to being more product management led. My suspicion without evidence is that the overall engineering autonomy has decreased over the years as the culture of tech has (in my opinion) shifted away from tech focus to more business, management, product focus with engineers just as the widgets who are tasked with fulfilling the goals of business, management, product.
all hypothesis, only anecdata
Two things to flag:
edit: as I keep reading the paper, I keep noticing some common sentence construction patterns, stylistic choices, and other little tics that I find frustrating because they are the very same things that I've been working on a few "writing-style skills" to get rid of
I don't think that the claim of "the Nasdaq is misusing their institutional trust" is a controversial claim. Moreover, one of the things that people choose when they (401k, pension funds, passive investors) is institutional mechanisms that prevent potentially mispriced items from entering their portfolios.
IMO claude, chatgpt/codex, etc should be able to optimize the PDF use case to be extremely token efficient as it's a very obvious use case. But when I start to explain to my wife/friends why it burns through so much quota, I find myself thinking "why should they have to understand this aspect of it". to me, that the details of PDF parsing and extracting are relevant to users (instead of solved such that you don't have to pay attention to it) shows how these tools are not nearly as "ready" as they are made out to be. I may be preaching to the choir on this one, but just my 2c
Perhaps it's all moot as the usage you get from a subscription plan will eventually no longer be subsidized. Also, I have to wonder about what layers of coordination done externally to a model can be persistently better than within tool coordination? Like, with an anthropic feature like agent teams, I feel like it might be tough to beat anthropic native coordination of various Claude sessions because they might have better internal tool and standards awareness, which makes feeling like plugging something like this more difficult unless one's goal is to plug something like this into an open source model.
Geniunely curious how other people are thinking about this!!
Edit: I actually see that this tool claims that it can run within your existing Claude Code subscription, so now I'm extra interested.
IMO the GP is touching on removing regulatory burdens (more traditionally republican/conservative ideas) and adding in funding/care via medicare for all etc (democrat position). the combination of reducing/improving/simplifying regulatory burdens while increasing government spending seems to be a combination of ideas that hasn't been winning enough support. afaik, Ezra Klein in his book Abundance is one of the only voices trying to push this balance.