bravely posting my new lineup for #myguys
seen from Türkiye

seen from United States
seen from Russia
seen from China
seen from Germany
seen from China

seen from United States
seen from United States
seen from China
seen from United States
seen from New Zealand

seen from United States
seen from United States
seen from United States

seen from Netherlands
seen from China

seen from Saudi Arabia
seen from Canada
seen from United States
seen from T1
bravely posting my new lineup for #myguys
look at my hackers dawg im going to jail
DIGITAL VIOLENCE, DIGITAL WORLD
( guys by @e8luhs )
Slimming down
Like all software metrics, "lines of code" shouldn't be applied blindly.
Today my software WIP's LoC metric is rapidly declining because I've created C++ macros to generate boilerplate code. I'm talking code I used to copy and paste every time I needed it.
This is the kind of refactoring I love, because it means less code to maintain in the future. Fewer chances for coding errors. Less scrolling through source code to find the interesting parts.
And in this case, I believe it also uncovered (and solved) a bug. So a big win all around.
But from a strict "lines of code" perspective, this would be considered a step backward.
I think my commit name is very funny
👍
a leaaaaaa for @aranui !!! she belongs to @e8luhs !!!!! had so much fun making this ^_^
The "fun" thing about reviewing and documenting your own code is that you'll occasionally find mistakes caused by small oversights or different portions of the code being made at different times.
So far I've removed like seven files and corrected a dozen little bugs that only existed in rare edge cases that nobody would think about.
To be blunt, this is more exhausting than coding the program in the first place.
Twenty one files done, forty six files to go.