Tootfinder

How to tell a vibe coder of lying when they say they check their code.
People who will admit to using LLMs to write code will usually claim that they "carefully check" the output since we all know that LLM code has a lot of errors in it. This is insufficient to address several problems that LLMs cause, including labor issues, digital commons stress/pollution, license violation, and environmental issues, but at least it's they are checking their code carefully we shouldn't assume that it's any worse quality-wise than human-authored code, right?
Well, from principles alone we can expect it to be worse, since checking code the AI wrote is a much more boring task than writing code yourself, so anyone who has ever studied human-computer interaction even a little bit can predict people will quickly slack off, stating to trust the AI way too much, because it's less work. I'm a different domain, the journalist who published an entire "summer reading list" full of nonexistent titles is a great example of this. I'm sure he also intended to carefully check the AI output, but then got lazy. Clearly he did not have a good grasp of the likely failure modes of the tool he was using.
But for vibe coders, there's one easy tell we can look for, at least in some cases: coding in Python without type hints. To be clear, this doesn't apply to novice coders, who might not be aware that type hints are an option. But any serious Python software engineer, whether they used type hints before or not, would know that they're an option. And if you know they're an option, you also know they're an excellent tool for catching code defects, with a very low effort:reward ratio, especially if we assume an LLM generates them. Of the cases where adding types requires any thought at all, 95% of them offer chances to improve your code design and make it more robust. Knowing about but not using type hints in Python is a great sign that you don't care very much about code quality. That's totally fine in many cases: I've got a few demos or jam games in Python with no type hints, and it's okay that they're buggy. I was never going to debug them to a polished level anyways. But if we're talking about a vibe coder who claims that they're taking extra care to check for the (frequent) LLM-induced errors, that's not the situation.
Note that this shouldn't be read as an endorsement of vibe coding for demos or other rough-is-acceptable code: the other ethical issues I skipped past at the start still make it unethical to use in all but a few cases (for example, I have my students use it for a single assignment so they can see for themselves how it's not all it's cracked up to be, and even then they have an option to observe a pre-recorded prompt session instead).

source: #USpol

I know that America is currently unwell and knowing it "theoretically" is one thing, having lots of colleagues and friends professionally affected is another, having our server's admin, one of the kindest, most generous people that I know, physically attacked, and their finger broken, by the LAPD, is another altogether.
https://neuromatch.soci…

heute im rahmen einer besichtigung für die universitätsgesellschaft den fiege-standort im münsteraner hafen besichtigt. sehr interessant und sehr schickes gebäude!
https://www.uni-muenster.de/Foerderer/aktuelles/archiv/2025/Unternehmen…

There are lots of elements of scaffolding, and as we change and grow and progress, our needs change. Knowing when to get input and what systems to set up is tricky, but so worth it. Here, Dr Jan Eppingstall and I talk through some of that

Relikt przeszłości — dworzec kolejowy w Dąbroszynie. Do dziś zachowały się godziny otwarcia kasy biletowej.
#Dąbroszyn #ruina #kolej