#101 ·
I’ve never been much for all that theoretical nonsense—just give me the code and let me build something, man 🙂
Started by bluebadger112 · · 👁 15 views · 160 replies
Gregory Smith21 said:Well, we could always do it this way.
First the Goat, then the cabbage, then the Goat back, then the Wolf, and finally the Goat. 😬
Gregory Smith21 said:It could also work this way—
First the Goat, then the cabbage, then the Goat back again, followed by the Wolf, and finally the Goat. 😬
hiddenmarlin14 said:Honestly, the Goat is the issue here; if it weren't for that one, the Wolf and the cabbage would get along just fine 🙂
Henry Evans10 said:I've never been much of a theory person—just here for the coding, man.🙂
bluebadger112 said:Look, you don't have to love it, but you absolutely have to understand it. 🙂 You need to grasp the logic behind the algorithm you're building with your code. Is it even an actual algorithm? Does it actually solve the problem at hand—you know, correctness? That’s the baseline. If you can't prove it works, how can you honestly say it's correct? Then there's the performance side of things—is there a faster way? A better way? It matters.
Henry Evans10 said:I just type a few lines and suddenly I've got a working program. 🙂
Just some if statements, a few brackets, and voilà. 🥳
Besides, why should I care about algorithms, let alone their complexity? 🙂
Chloe Cooper10 said:I just tried typing out an if-then statement with three different types of brackets, and literally nothing happened. Total bust.😢
shadowjackal82 said:I suppose this little anecdote serves as a fitting illustration:
A wife sends her software engineer husband to the grocery store and instructs him:
"Pick up a loaf of bread, and if they happen to have eggs, get ten."
The man returns from the store carrying ten loaves of bread, informing his wife:
"They had eggs."
😁
Gregory Smith21 said:I have exactly thirteen days left of posting on this forum before I disappear, and then we can catch up again in four years... assuming the same crowd is still hanging around here... 🤣
@Chloe Cooper10. Where exactly is your header, and why is there an int at the end of the function?
One simply cannot write programs this way, and frankly, I think it would be prudent to actually compile the thing if you intend to run it, wouldn't you agree?...
If it remains unclear to you why the program crashes, you should attempt to run it through a debugger and perform an analysis, though you must ensure you compile it with the -g flag so the source code remains accessible...
Gregory Smith21 said:I’ve got 13 days left on this forum before I head out. See you all in four years—assuming the same crowd is still hanging around. 🤣
@Chloe Cooper10/">@@Chloe Cooper10. Where’s your header, and why is there no int at the end of the function?
You can't write code like that. Honestly, you should probably compile it just to see if it actually runs.
If you aren't sure why it's crashing, run it through a debugger and analyze it. But first, you need to compile it with the -g flag so you don't lose the source code.
northernviper4 said:Well, I suppose it’s a bit late to be bringing up a four-year gap now, isn't it? 🤔
Sent from my Sony Xperia using Reddit
Chloe Cooper10 said:I don't believe anyone mentioned anything regarding a bell or an integer at all🐔
Where are you headed? 🍿
Gregory Smith21 said:You can't just claim you can code because you spent five minutes messing around on a keyboard and thought 🤣
Anthony Nguyen81 said::Of course.
Recursion generally operates on the principle where the first element goes in and the last one comes out, 😬
following the LIFO—or first in, last out--😬
logic. I suppose there are quite a few different combinations to consider here.😬
Gregory Smith21 said:It's essentially just LIFO—just a different way to phrase the acronym.
Gregory Smith21 said:Regardless, it’s crucial to grasp how memory operates under that principle—specifically regarding data layout when reading from or writing to a particular address.
It's similar to how those hackers writing shellcode have to inject specific ASCII characters into the instruction pointer in reverse order. 😬
Gregory Smith21 said:Life moves in certain cycles, and after various shifts in my circumstances... I suppose I have returned to the forum as of October 2023.
One cannot simply sit down to write code as if one were merely tapping away at a keyboard for mere amusement, such is not how it works...🤣
northernviper4 said:So, who's actually still here—alive or dead? 🙂
Sent from my Motorola using Reddit