I started early in my childhood days, nobody had cellphone or internet here, my phone number was 3 digits long and my home country started to recover from 44 years of communism.

My first dev project was probably to copy game from newspaper to Atari 1300XE

Article listing was around 10 pages long and if you made mistake program didn’t run.
It took me a while I can’t remember how long but probably whole day and I was finally able to play it.

I don’t remember what was game about but later on I learned some BASIC from book and was able to color the screen and stuff like that.

I was about 6 years old.

I also remember that Atari computer had tape recorder where you put cassette to load game.
Some more complicated games were loading more then hour and you need to walk very carefully around or your walk can cause error and operation would fail.

Besides that there were national radio auditions about Atari where at the end they played code sound wave so you can record it on your cassette and then play software from radio on your Atari.

I never managed to do it cause I was living near military airport and pilots were practicing landing and starting above my home causing radio signal noise and breaking my software recoding.

I can probably say that highly accelerating plane could cause game loading problem and it’s not a joke.

Here's something not quite a rant, but relatable. And an issue. For me at least.

------

You get really proficient with a set of tools.
- Can solve things in an efficient & elegant manor.
But it's now boring.

You find some new exciting stack, research like a madman. Possessed.
Your perfectionist self, seldom doesn't want to settle.
You burn out from pressure & deadlines.
You feel inadequate, imposter syndrome settles in.

You reminisce of the easy days when you (thought) knew everything.

Decide to rebuild using that past stack.

Gets bored.

You notice something new & exciting.. loop iterates to next repetition.

garbage collectors' lifestyle matters!

Ever eyeballed the abyss of your memory leaks? Shit, garbage collectors deserve a raise.

Unsung heroes, janitorialing thru that VM like a dung beetle, silently fucking up your perf so you can do that delicious spaghetti. Indiana-jonesing the fuck out of that memory trash can and euthanizing all that disgusting heap of pointers hanging, dangling, like... well, like garbage.

At the very least they're deterministic, unlike that Markov chain we all had the displeasure of fucking up. Amen? Amen! 🙌🏻

You gotta wonder, though, what goes through their nuggin. Do they reminisce about the potential of that half-ass-written class? Do they weep for the elegance of a forgotten function bottlenecking their job? Nah, probably just counting down the nanoseconds till their next full GC cycle. Aaah, like cold beer in Saturday barbecue.

So next time your program miraculously avoids a memory error, take a moment, put your hands up in the air and say a prayer to your garbage collector.

Silently covering for your fuckups

Thee reminisce me of yond corse part at which hour smeared with poop thy did accept whither cleaning with dry pap'r