Thanks for sharing this, it's quite interesting. I found a Wikipedia article on it: https://en.m.wikipedia.org/wiki/Unary_numeral_system
Apparently, as you did suggest, "base 1" is a name that is used, but is somewhat a misnomer.
The article mentions that Church encoding is a kind of unary notation, which I would not have thought of, but I guess it is.
Enjoyable little rabbit-hole to zap my productivity for the day.
You seem to have missed the important phrase "in source code", as well as the entire second part of my comment discussing that runtime functions that parse user input are different.
At the (SQL) database level, if you are using null in any sane way, it means "this value exists but is unknown". Conflating that with "this value does not exist" is very dangerous. JavaScript, the closest thing there is to a reference implementation for json serialization, drops attributes set to undefined, but preserves null. You seem to be insisting that null only means "explicit omission", but that isn't the case. Null means a variety of subtly different things in different contexts. It's perfectly fine to explicitly define null and missing as equivalent in any given protocol, but assuming it is not.
Closer to tally marks without clustering
Who calls it that? Who even uses that enough to have given it a name? Seems completely pointless...
It's been a long time, but I'm pretty sure C treats a leading zero as octal in source code. PHP and Node definitely do. Yes, it's a bad convention. It's much worse if that's being done by a runtime function that parses user input, though. I'm pretty sure I've seen that somewhere in the past, but no idea where. Doesn't seem likely to be common.
What? Your colleague sounds like they may be struggling with some serious cognitive issues, they may want to see a doctor about that. As for me, I've been living with my brain my entire life, and have kept several different sleep schedules in that time, for one reason or another, including rigid adherence to a schedule you would certainly approve of, and at no time has the basic fact that my brain works better later in the day ever changed. Some people never learn that their own circumstances and experience are not universal. Maybe try not to be one of those people.
I am definitely not at my most productive at the start of the day.
Between fascist Republicans and liberals pretending to be libertarians, I think it's a pretty clear choice. We vote to live another day.
It's better to have useful comments. Long odds are that somebody who writes comments like this absolutely isn't writing useful comments as well - in fact, I'm pretty sure I've never seen it happen. Comments like this increase cognitive overhead when reading code. Sure, I'd be happy to accept ten BS useless comments in exchange for also getting one good one, but that's not the tradeoff in reality - it's always six hundred garbage lines of comment in exchange for nothing at all. This kind of commenting usually isn't the dev's fault, though - somebody has told a junior dev that they need to comment thoroughly, without any real guidelines, and they're just trying not to get fired or whatever.
https://mediabiasfactcheck.com/popular-information/
I never heard of it, either, but sounds reliable.
But who, who is "you" in this scenario? Who do you think can just tell the court "no"? Let's be specific.