Okay, I just wanted to vent: I'm on the Pro plan and I've not been able to use Argon for the past 4 days - every time I send a prompt I get downgraded to a Flash model.
Makes me consider cancelling the plan entirely.
768 karma · joined July 16, 2018
Makes me consider cancelling the plan entirely.
> A ‘colony’ of Formica polyctena was found in January 2013, during winter counts of hibernating bats in the underground bunker.
And all makes sense
Amazing how much money was wasted on these only to be staffed for years and then abandoned.
Interestingly this is a "Soviet" bunker in western Poland. A Warsaw Pact bunker?
Also, I didn't think that Soviet policy was to store nuclear weapons in Poland - not sure if this quote is accurate or if this was just more common than I had thought?
I can see this approach being useful across non-Go repositories too.
I wonder if it's the opposite (in fact blog posts to that tune were posted here more than once): if LLMs are supposed to be writing most of the code, and taking away the friction of actually writing the code, I guess it means one should pick the language based on project requirements and performance since any language is the exact same to work with.
It keeps segfaulting, takes a long time to actually start, I keep getting weird glitches whenever I have multiple panes open in a window (which is pretty much always the case), the tab bar is hard to style and I'm missing some of the macos features (like giving a tab a coloured pin).
It takes a mix of willpower / routine / systems / laws to keep people in check, otherwise we predictably go back to the path of least resistance.
1. Smaller PRs (that can be easily read) tend to receive more comments and nitpicks than a large change since it's easier for us to have all the PR context in our heads at the same time.
2. Most people are ego-tied to their code even if they pretend that they are impartial
3. Social dynamics around merging and reviewing code between senior/junior and older/newer employees
4. probably many more
At the same time I can't help but wonder that this is almost too much for us to cope, the LLMs are _too_ easy to use. I think we're very good at pretending there isn't a problem here but there is definitely going to be some cognitive decline happening.
We want to pretend like reading over the output of an LLM is nearly the same as us making those changes ourselves but I think there's a lot of value in those boring and manual steps. And most people (including me) will be too lazy to not eventually offload most things to the LLMs.
In a way this is similar to how watching a lecture tends to give one an "impression" of understanding that doesn't correlate with reality. We need hands-on work and some course work to get our monkey brains engaged.
I can only imagine what effects this is going to have in education.
E.g. I remember having lots of issues sharing smaller video files encoded with H.265 via both WhatsApp and Messenger. iMessage doesn't support H.265 (or at least it didn't work for me at the time).
Is this API-only or US-only for now?
Psoriasis, eczema and psoriatic arthritis being three that maybe you wouldn't think of when someone brings up methotrexate.
I have such fond memories of HOMAM3 and playing it in hot seat mode as a kid.
Interestingly the game is still massively popular in ex-Warsaw Pact countries. Although I think it’s having a resurgence in the US too.
2. Click on the hamburger menu in the top right
3. ???
It then gives me a hint on the area or a typical code flow that would hit the bug - whichever gives me less info. I can obviously ask for more hints as I read along.
Obviously all honour-code based since I could just ask it to fix the bugs itself. I think this is something that can't be fixed systemically - either you're going to bother reading and thinking through the code or not.
Other than that I guess reading the tests - to make sure they fail without the code / fix, to make sure the setup makes sense etc.
No idea what gating Argon like that does for them.
I tend to run the content through something like Luna to deslopify now.
This helps a bit though magit still feels very sluggish.
But... isn't this solving the problem by removing most of what makes it an issue in the first place? I imagine most people use ORMs for the SQL <-> native class data sync capability. And this assumes one would run the Acadia query instead.
FWIW I'm not trying to be negative, it's just my general impression is that these N+1 usually occur because people _want_ direct object access and _want_ to write loops, and _want_ to access fields and have the underlying SQL be sorted by the ORM.
My general feeling here is that this really needs to be fixed at the model level. All other solutions are mere hacks that work for a bit but all have drawbacks. It's either adding yet more context (which has variable rates of success) or piping to a different model to translate, or using a skill, or mentioning this per each prompt, or....
At this point I think it's in Opus's nature to talk like this, and given enough back-and-forth it will start to drift back to its classic mode, aka this incomprehensible "load-bearing seam" babble.