Izkata

14 ms·

241.
by Izkata 5mo ago
Here's the big one that was being passed around months ago, which nowadays usually gets dismissed out of hand because of when they did it (while ignoring the relative finding): https://metr.org/blog/2025-07-10-earl
242.
by Izkata 5mo ago
There's also a pattern based on the simple solution that used to be more common: One command-line program for updating and querying the current state, and a second GUI one that just acts as a dumb interface for the first one. Even as
243.
by Izkata 5mo ago
It's a relative abstract measure of case size that's the same across experience levels. A junior and a senior should both be able to agree that a given case is small/medium/large relative to the kind of cases their team
244.
by Izkata 5mo ago
The ones in those first two bullets made issues part of the repo so you'd clone/push/pull updates automatically with the normal git commands. They were trying to reduce friction with usage: Fewer new commands to remember&#x
245.
by Izkata 5mo ago
Pretty sure I've seen references to AI-only review already happening...
246.
by Izkata 5mo ago
Including a very awkward followup when he met the person his was based on.
247.
by Izkata 5mo ago
There was a small surge in popularity in distributed git issue trackers a bit over a decade ago, and all of them had some sort of problem baked in to the design that made them not very good. Two weeks ago I had listed out the problems I cou
248.
by Izkata 6mo ago
They're using the version from the top comment, not the post. It also switches the pre-increment to post-increment.
249.
by Izkata 6mo ago
> Imagine you get asked to build something ambitious, and you say: > “Sure, I’ll have the Speed version ready in 3 days. Then the Scale version in about 6 weeks.” > They get what they want, speed and momentum. You get what you want
250.
by Izkata 6mo ago
You're thinking of something else, Groups didn't exist until 2010 (though I thought it was a bit earlier, like 2008 - I thought they came out about the same time the Network pages went away, while I was still in college): https:&
251.
by Izkata 6mo ago
At least it wasn't Comic Papyrus...?
252.
by Izkata 6mo ago
For anything Lucene-based (Elasticsearch, Solr) this was a problem where some of the indexed data had to be transformed for another type of query to be efficient, and it put the transformed data into the Java heap then never released it. I
253.
by Izkata 6mo ago
"Groups" is New Facebook, the replacement for the Network pages. Used to be there was a whole section of the site meant for connecting with people at the same college/university as you, that you were automatically included in
254.
by Izkata 6mo ago
> e.g. to approve a MR you need to click a button that is actually a menu I think you're referring to the "Your review" button in the upper-right that's not always there, but there's a plain "Approve" b
255.
by Izkata 6mo ago
Likewise in the winter, as a kid in the 90s I remember my dad wondering if we'd have a white Christmas (wondering if snow would fall before Christmas or not). There's even songs from decades earlier about it. Whether we'd ge
256.
by Izkata 6mo ago
It's like the climate people never heard the fable of "The Boy Who Cried Wolf". It's exactly that.
257.
by Izkata 6mo ago
Look at GP to my comment again, the one I was clarifying: they're not talking about black hats or any other kind of hacker, they're talking about the original developers and preventing such vulnerabilities from existing in the fir
258.
by Izkata 6mo ago
They're saying to do that scan to every diff before release, to see if it finds anything.
259.
by Izkata 6mo ago
Because while you could get something that drives a dumb interface, by moving the work and data to the server it's not available for the emulation software to use.
260.
by Izkata 6mo ago
Python's pip predates npm, installs dependencies automatically, can include binaries, and the old-style packages could run arbitrary code during the install. Ruby gems are older than that, but I have no idea what capabilities it has&#x
261.
by Izkata 6mo ago
Out of curiosity, with it taking up that much of the message, is it the local file path on their computer?
262.
by Izkata 6mo ago
> Professional formatting, length, and clear prose are no longer indicators of care and work quality (they never were, but in the past, if someone drafts up a twelve page spec, at least you know they care enough to spend a lot of time on
263.
by Izkata 6mo ago
I read it as a comment on how bad journalism is nowadays, with the extensive prose instead of getting to the point.
264.
by Izkata 6mo ago
At least in English, this appears to be slang that only recently leaked out of its original context. I've never heard the term before and whatever they used to look it up probably had no results. The usual English term is "mid-lev
265.
by Izkata 6mo ago
Isn't this just... normal? Maybe they use it more often, but (also in the Midwest as other comments mention) these uses are all more common than an actual apology. But for a more distant example of the "I'm about to inconveni
266.
by Izkata 6mo ago
There's an in-between point that I think is better than either, but it can be more difficult to find the right balance: Direct contact with internal stakeholders (with the manager still somewhat involved to still have a good overall v
267.
by Izkata 6mo ago
Some of us are already experiencing that. For example I handed off an initial version of something some months ago, and the AI-generated stuff they came up with was a huge buggy mess of spaghetti code neither of us understood. Months later
268.
by Izkata 6mo ago
Sounds like a recipe for Star Trek holodeck malfunctions.
269.
by Izkata 6mo ago
Those are completely different from a tool you wrote yourself: Where do they get support when something goes wrong? This mindset has always existed in the area we're talking about, and not because it's sharing something to speed u
270.
by Izkata 6mo ago
I believe the theory isn't that one is better than the other, but that different models would make different mistakes, so you can be more confident in the places where the code and tests agree.

More ›