Another level of this dilemma:

• Pin all dependency versions – Prevents receiving security patches
• Don’t pin dependency versions – Enables supply chain attacks (see https://nesbitt.io/2026/02/03/incident-report-cve-2024-yikes.html)

That’s the security issue, right? Liar paradox detected!

Danish: // hold my beer

#define NINETY ((int) (4.5 * 20))

I know this one! https://superuser.com/a/577304/65414

Because of one smartass customer who insisted on doing exact RFC 822 validation, I implemented exactly that. And yes,

zKcknV|NGv.lI66vR#@X`QcRK4K.R`?NpA.Gc2Kqzue9.%&nb1kGWp/./#Och$RQv

is one of the test cases for a valid addr-spec. See (or generate) some others at https://github.com/mormegil-cz/rfcemailvalidator

Also, check if your PIN has been leaked as well! https://pastebin.com/Nn2ZcdfC

Exactly. The CSS construction is smart but not that ingenious. In this way, you could slap any number of fixed images there, I was hoping for some inventive transformation.

Add automatic normalization to the box (you know, you type “05” and it drops the leading zero, you type “0.70” and it drops the trailing zero, etc.) and it often gets completely impossible to write anything valid. Some banking apps do something similar. :-)

I understand the idea. But many people have hugely mistaken beliefs about what the C[++] languages are and how they work. When you write ADC EAX, R13 in assembly, that’s it. But C is not a “portable assembler”! It has its own complicated logic. You might think that by writing ++i, you are writing just some INC [i] ot whatnot. You are not. To make a silly example, writing int i=INT_MAX; ++i; you are not telling the compiler to produce INT_MIN. You are just telling it complete nonsense. And it would be better if the compiler “prevented” you from doing it, forcing you to explain yourself better.

Sure thing, see https://pivot-to-ai.com/2025/06/05/generative-ai-runs-on-gambling-addiction-just-one-more-prompt-bro/

This might work when the test really describes&tests the business rule, not when the test simply contains a mirror of the implementation with everything replaced by mocks and just checks that the implementation is what it is, conditioning all people changing the code in the future to always have to change the test as well.

On the contrary! I found out that a rewrite from scratch leads to much better code and abstractions, as you understand the problem space better. (On the other hand, beware of http://catb.org/jargon/html/S/second-system-effect.html)

I wanted to publish a tiny utility I created to GitHub (you know, it might be useful to someone else…). Before that, I wanted to some cleanup, rebasing/squashing a bit, etc. In the middle of that:

$ git checkout featurebranch
The following untracked working tree files would be overwritten by checkout:
.gitignore
.idea/…
etc...

Oh, sure, no problem…

$ rm -rf * .*
$ git checkout featurebranch
fatal: not a git repository (or any of the parent directories): .git

D’oh! (Never mind, it probably wouldn’t have been useful to anyone else, anyway.)

Its written vibe.

Related: https://stackoverflow.com/questions/5508110/why-is-this-program-erroneously-rejected-by-three-c-compilers

That’s an aladeen idea!

Tells you exactly what and at which line the problem is?

Syntax error: unmatched thing in thing from std::nonstd::__map<_Cyrillic, _$$$dollars>const basic_string<epic_mystery,mongoose_traits<char>, __default_alloc_<casual_Fridays = maybe>>

Sure, strtok is a terrible misfeature, a relic of ancient times, but it’s plainly the heritage of C, not C++ (just like e.g. strcpy). The C++ problems are things like braced initialization list having different meaning depending on the set of available constructors, or the significantly non-zero cost of various abstractions, caused by strange backward-compatible limitations of the standard/ABI definitions, or the distinctness of vector<bool> etc.

Int3 is a special single-byte (CC, if I recall correctly) form of the INT instruction (which is CD imm8, I think) to raise an interrupt. Interrupt #3 is the debugging interrupt, so by overwriting any instruction with CC, you place a breakpoint there.