Post #877925
2026-03-30 13:03 UTC
Two very senior engineers, pairing for over an hour, to figure out that a function call had its first two arguments in the wrong order.
I'm not sure what the moral of this story is. Maybe it's that stupid stuff will trip you up, no matter how experienced you are. Or that positional arguments were a mistake. Or maybe that meatbags weren't meant to code and we really do just need to hand it all over to the AI overlords.
Replies (2)
-
@JeffGrigg@mastodon.social 2026-03-30 16:02
@plexus I'm pretty sure that at least half the calls to "assertEquals" have the value parameters backwards. 😢 Method chaining helps with that. But it is, really, just a hacky way to name parameters.
-
@mellowfish@ruby.social 2026-03-30 17:18
@plexus my hobby language only has named arguments (and also, does not have nulls) for this reason.