- Push directly to master, not main
- No command line args, just change the global const and recompile
- No env vars either
- Port numbers only go up to 5280, the number of feet in a mile
- All auth is just a password; tokens are minority developers, not auth, and usernames are identity politics
- No hashes – it's the gateway drug to fentanyl
- No imports. PROTECT INTERNAL DEVELOPMENT
- Exceptions are now illegal and therefore won't occur, so no need to check for them
- SOAP/XML APIs only
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
Main branches will be renamed Master
Nope Main branches will be renamed Daddy
More like Grandwizard
MAGA - Make Assembly Great Again
Arrays not starting at 1 bother me. I think the entrenched 0-based index is more important than any major push to use 1 instead, but if I could go back in time and change it I would.
It really doesn't make sense to start at 1 as the value is really the distance from the start and would screw up other parts of indexing and counters.
It would screw up existing code but doing [array.length() -1] is pretty stupid.
A lot of languages have a .last()
or negative indexer ([-1]
) to get the last item though.
For i = 0; I <= array.length; i++
i < array.length
or else you overflow.
It doesn't make sense that the fourth element is element number 3 either.
Ultimately it's just about you being used to it.
Yeah, but if we went back and time and changed it then there wouldn't be other stuff relying on it being 0-based.
Also remove null reference
What about stacks grows to higher addresses?
Im unfamiliar with this as well. If you are allocating memory for a stack, why does it matter which direction it populates data? Is this just a convention?
I ask deepseek: Downward-growing stacks** are more common in many architectures (e.g., x86, ARM). This convention originated from early computer architectures and has been carried forward for consistency.
Funny, I can't remember, , because I did a lot of assembler back in my youth.
Ah thank you so its just a convention.
Error handling should only be with "if"
Variable names must be generic and similar to each-other
Debugging is only done with prints
Version numbers must be incoherent, hard to order correctly, contain letters and jump in ways that don't align with the updates done.
Single letters or UTF8 symbols only. Emojis are encouraged.
Variable names should be var{n} where n = 0, 1, 2...
Something something the cruelty is the point.
Halfway to Lua lol