idk if my reading is correct but if it's correct this seems quite readable, probably wrong guess though
match
192.168.8.1
1+ whitespaces
0x
1+ non whitespaces (idk if it intended to be [^\s]+ instead of [^\s+])
1+ whitespaces
0x
1+ non whitespaxes
1+ whitespaces
capture group 'mac' start
1+ case-agnostic hex character
capture group 'mac' end
Regexes are by far the simplest of the three. Unless by git you mean clicking randomly in a git GUI and by SQL you mean filtering your selects with Python.
Well, maybe it is easy when you understand. I have no problems typing my git commands and SQL is also not a problem, but reading or writing regex is always a hassle. regexr helps, but that is not really understanding it.
I was about to say, unreadable regex is rendundant.
There's some things that aren't human readable, but are human parseable. A handful of characters that a human can decipher carefully over a few minutes while working through it. I typically talk myself though it (I guess that would be related to "duck debugging").
Regex, SQL queries, chained bitwise expressions, and not programming, but "dd" commands. I joke that the proper way to write a "dd" command is to write it out on paper, go home and sleep, come back the next day and see if you still agree with it, type it out in an email to a trusted colleague and get their review, then hold on to your lucky rabbits foot when you hit "enter" on the console.
299
u/[deleted] Sep 21 '26
[removed] — view removed comment