Aaargh....my eyes......my eyes......

Self-documenting code, high contrast… Carry on.

Probably still better than bool a; bool b; int c;...

But i, i is sacred.
- 🤔... I've never liked i and don't use it...not sure why. I keep thinking I should start but alas I just don't.
Honestly? Yes, I agree

ThisCommentsMakeItSoThatYouHateMeForWritingLikeThisSeriouslyICanNotStopPleaseSendHelp

Makes it even better that I'm on mobile so the text wrapped half way through a word.
I can read that without any issues whatsoever.
But. If. You. Put. Periods. Between. Each. Word. My brain will force a pause between every single one and I can't override it.
- Forever Ago I Ran A Minecraft Server And 2 Friends Joined And One Typed Everything They Said Like This and the other managed to misspell every single word with more than 2 letters in it. They misspelled the word "the!" According to Sir Capitalizes Every Single Word, its just much easier to type that way, which raised far more questions than answers...
Would you like a snake to replace your camel?
- Careful, Pascal doesn't like it when you call him a camel
- Best I can do instead is calling it x.

Hey, this must be that self-documenting code I keep hearing about

lgtm

merged

I'm assigning all my PRs to you, buddy, your performance metrics will be over 9000!

Obviously, we can't allow code like that - PascalCase is heresy... camelCase that shit.

snake_case gang represent

What about this?

I'd ask what I'm looking at here but feel I might regret it
- In Oct’23 a basic Text widget with Subprocess to run shell commands allowed me to take my command line fu into a different arena because Tkinter gave me special tricks. This tool (shell functions) allows me to type up GUI apps or any Python script with less effort, for my fingers and brain.
  wc newide; ksh newide | wc
  513 1671 11018 newide in pnk
  604 1987 29867 newide in python
  The blocks of color are capital letters colored using tkinter methods (tag_add & tag_configure) with a bg and fg of the same color to make it look like a lego block, it’s all ASCII. On the right, an idle clicker game/toy made with pnk.lang, also just ASCII/UTF-8. The IDE you see in the pic also was coded using functional shell language I call pnk.lang and the original first iteration of this specification is in the legacy folder in the repo below. Just me learning how to code faster in Python but in shell but in neither at this point.
  https://github.com/dislux-hapfyl/pynksh
  https://www.reddit.com/r/pnk/
  Don’t be put off by Ksh because Bash can also interpret it, since it’s just shell functions that print Python code. But I have plans to use an Xbox controller so I can move away from building with the keyboard at piecemeal rates. I will do this by abstracting away identifiers and all data we use as engineers into “dictionaries” to then transform it into a spatial system. I already done this first step! Using a basic grid with a maximum of 10 rows x 3 cols, indexing row[0-9] col[0-2], as you see there on the left side, and by using a letter I then categorize the functions of pnk(shell+python) so I can have 30 x 26[a-z] available slots; a00 b11 k22 and so on…by making it a visual shortcut that reduces cognitive load and typing for me.
  Take a closer look at my repo without dismissing it too quickly. It could seem unnecessary but maybe someone else can see what I have made as useful and how we gonna take it to higher levels of abstraction and create a new realm for making computer applications in an abstract game/IDE of art and code. Perhaps it’s that creator effect that happens when you make something for the first time that makes me see its future utility and appeal. All this was made incrementally using my own software I built from scratch. I do have a great vision and would love to speak to anyone who is interested. I also demonstrate the utility of this small tool on youtube[link in repo]. Thanks.

This has likely been done intentionally for humour's sake, but take a look at some of the names in Apple's AppKit framework, like https://developer.apple.com/documentation/appkit/nspreviewrepresentingactivityitem

That page is giving me a 403

Yea this looks productive.

Imagine how useless the LSP suggestions are.

My ASDV professor has two moods: He either names variables like this post, Or he names variables pp (for pointer pointer)

Fuck for some reason pp is giving me flashbacks to having to write using Hungarian notation variable names.

I don’t see the benefit of this long naming convention...

It still allow bug to exist... like the fact that, with this code, the player can still play with 0 Hp.

Should have been better to put a "if(health <= 0)" instead of "< 0"

Came scrolling for this ^^
It sounds like the only concern you have with code is its bugginess, which is short sights. This is unfortunately better documented code than stuff I've seen in production. Obviously no one should do this, but let's not act like there's no benefit
- Indeed, you can achieve a better result with less verbose naming convention. And choose better variable name to make it obvious than 0 Hp is death. While i don’t like having too verbose variable name (as it impacts the readability and quick understanding of the function), i’m not against that for the function name... without going too far of course!
  Best is too have proper datamodeling of the object manipulated on top of some classic basic comments. Good interface contract is also a minimum. Best is to have full datamodeling of all the services, objects, in and out interactions between them, etc.
  Documentation is a mandatory piece of the code delivery (with tests being the other important part) far too much forgotten if you don't enforce it on your teams.
I asked this question on this post on a different instance, but would there be issues being that the code compares a float to integer zero "0"?
Kreed rule.

This is getting absurd, variable names have become variable sentences.

Variable essays is the future!

Cleanest code by Unclest Bob

I approve. All code should be like this

https://xkcd.com/1960/

It’s an unwritten rule that there‘s always a fitting xkcd post

Leaning to program on 8-bit machines with 8k of RAM means that even today I abbreviate names.

Plus it was accepted wisdom that shorter variable names were faster for the BASIC interpreter.

variables don't make it to the compiled binary tho, except debug symbols of course if have those enabled (but deploying them to an embeeded system is a terrible idea, they can remain on the host system)
oh you mean on not for
- Yeah for interpreted BASIC.
  But even after moving to writing assembly language on a separate PC devkit there was still the habit of using short names.
  I think that some assemblers had limits on name size.