I also got a strong interest in programming 1998/1999-ish and also had only a Mac at home. I emailed the guy who authored a chess application (his email was in the splash screen) over our dial up connection. He told me I would need to learn C or C++ and I had no idea how to act on that (I was 8 or 9 at the time, living in a very rural area).
4 or 5 years later I got my own laptop and installed Linux on it. Then I started learning bash and tried (and failed) to install Linux From Scratch. That did get me to a point where I could program.
This sounds a lot like myself as a kid in the around 1999/2000 after getting my parents' Performa tower as a hand-me-down.
I'd become aware that it was possible to build one's own programs, but exactly how was extremely murky. I grabbed various development tools mentioned on the internet, but as you note tutorials were nonexistent and IDEs, consoles, etc may as well have been ancient tablets written in an archaic language.
Finally I stumbled across REALBasic, I think maybe on a MacAddict shareware/demo disc, which was analogous to Visual Basic in the Windows world (though unlike VB, RB could compile binaries for both platforms). That was far more intuitive… just drag a button onto your window-canvas and double-click the button to edit its code. Examples were also much more common and easy to find on the internet and so before too long I was hitting the ceiling of what was possible in RB.
That segued nicely into Cocoa development when OS X rolled around, which brought Project Builder and similar (but far more extensive) WYSIWYG UI builder with Interface Builder. That took a lot longer to become capable with, but led me to where I am today as a mobile dev.
But: Object Pascal/Delphi is a quite powerful language and you can write really complicated stuff with it, compiled into a relatively small statically linked executable that worked just about everywhere without the need to install anything. (300-400 KB binaries seemed large at the time, little I knew what awaited us 20 years down the line.)
The need to dig and learn everything yourself definitely had some impact and provided some lower level knowledge of things many newer developers don't seem to know or care about, but I very much prefer what we have today where you're not expected to learn to read what looks like ancient Egyptian from scratch to write a basic calculator. Good riddance to those times.
I immediately started working on an ambitious space battle game. I got to the point where you could click to set waypoints for a ship, and it would try to fly a course through them, using Newtonian physics, but the navigation was incredibly naive, and always just accelerated towards the next waypoint, so eventually the ship was going so fast it crossed over the waypoint in a single time step, and would turn round and come back to it, inevitably missing is again, and so basically going into perpetual powered orbit around it. I then abandoned the project.
I only got into actual programming several years later by joining computer course during high school.
The first program I was ever able to write that involved things actually moving on a screen came a couple years later and was written on my graphing calculator. Solely because the calculator came with a big manual that documented all kinds of functions you could use in a program. And so long as you were writing only a few pixels at a time its built-in basic language was just barely good enough.