The moment that I finally understood OOP.

Several teachers had already given up explaining it over and over again but one classmate took a few hours to explain.

Suddenly, after a few hours, that AH-HA! moment was there!

I've done as much OOP programming as possible since then and have explained it to others who were struggling with it as well 😊

I guess my best AHHA moment was back when I learned that good code is simple code.

When I started out I wanted to prove myself by showing of how good of a programmer I was(and which I retrospectively wasn't) , which basically meant to use every high level concept I was aware of whenever possible. Multi threading where linear execution would have been totally okay, polymorphism with x meta classes where a switch would have been enough, all that shit.

It wasn't until I had to guide the first person through that mess of useless ego stroking that I found out how much time and money I wasted by not going with the easiest approach that solves the problem.

Took me some time to fully lay off that attitude but it surely was one of the most influential moments of my career.

Take On Me

Aha! The problem that you solved after a week long of thinking was already solved in 1800 AD and the code looks 100x better and optimal than yours.

1 - when I actually got the point of OOP

2 - When I got that I could check if a number was odd or even by doing & 1

3 - (in the future) when I will understand lifetimes in rust.

For me, it was when I discovered how dynamic linking (.dll, .so) works, and why a linker is needed to run even a simple "Hello world!".

Reading this in a routine:

NOP
NOP
NOP
RET

Presented a bug as a feature to client and the how satisfied client was though made me happy. . .

Haven't used it since and hopefully never will again, but understanding recursion and keyboard input in Assembly (uni project)

After a long (4 days) sleepover with my friends, with 14 hours a day of slamming our heads against abstract registers, we could finally program the factorial and take floating numbers as input and output them on the screen. It was nothing but pain, but the moment we got it, the sky had opened before us :D

Never again

After hours of debugging a legacy binary which throwed an unknown error. Realizing that it was expecting an array starting at 1.

When it finally clicked on how to write tests first and I could actually make code progress with it.

The first AHA moment striked me when I was around 11 years old. This was the first time I ever been introduced into programming.

I've started playing around with visual basic on my own and aha moment striked when I realised I can make programs to solve math problems... But that was just a lightbulb....

The overall AHA moment happened when I had the knowledge to do so and actually started implementing text book solutions in the app and passing few values from tasks and... Results were great!

From that point I went on with programs as my math problem solver in most of my cases. This not only helped me to save time but actually writing the program helped me to get better at math.

When each layer of abstraction is peeled off from a program and I understand it down to some level.
It always gives me goosebumps thinking about how much each generation of humanity is contributing to our advancement.

The best AH-HA moment is the ones that you just can't get your mind around and then go for a coffee break.

Come back to your desk and then ... bam! There it is!

Thanks, coffee ☕

The moment I realized test cases are just super tiny applications that make use of parts of your codebase to run things and see what happens.

Today I finally proved that a pre-existing component was overwriting the output of my component. It only took 3 months to find out the proof of it.

One of biggest epiphanies came through this fundamental critique in SICP of the assignment operator. Through years of imperative programming it seems so innocent, doesn't it? But that you lose referential transparency, run into the alias problem and fundamental difficulty to determine object equality (or of their instances) - that was kind of eye opening considering all the pain I had already experienced with state in concurrency.
(It led me so far to think it's an ontological issue, that even in the discrete computing universe we have not come so much further than Zenon's paradoxa on change.)

To understand recursion, just click these links:

I was pulling background data from a job in PowerShell, and it kept coming up short from the same, final section of data that I just KNEW should be there.

Fiddled with the primary application for hours... HOURS! Then, I checked the log. There it was in all its Glory, tee'd out to the log during job execution.

What. The. Shit.

So, it seems that, since I was asynchronously pulling data in a loop keyed to the job status and had inserted a little sleep statement in the wrong place, I'd been missing the last second's worth of data. You just couldn't tell most of the time.

Nice.

5 minutes later it was working fine with a new loop/control structure. Jesus.

Biggest aha! moment was when i understood rust's borrowing and how much of a retarded piece of shit it was and then went back to scala yesterday

The "AH"-moment when as a boy discovered that with this instructions in QBasic I could literally let the thing do *anything*.
The "HA"-moment only little afterwards that I'll probably never have a clue what a worthwhile thing to make it do would be.

Hmm,
The first one was eons ago. I was coding in Pascal and discovered System interruptions. The “Ahaha” was when I realized it’s easy to store CPU state and invoke whatever the fuck I want on any memory pointer. I loved my 2 silly animations running side by side on 80286.
Most recent : Finally understanding how “Expression” works in C# and how it can be combined into a Lambda and compiler does the whole heavy lifting on types compatibility and more.

Every time gradle build breaks, and I have to waste 2 days brute forcing solution out of it.

When how bitwise operators work suddenly seemed logical, until the next time it didn't.

Getting a CodinGame puzzle's description without scraping the page.

I spent hours playing with different endpoints and changing values in postman, all to no avail. The most promising endpoint also returned user progress, which requires authentication, which requires a dummy account, which is against their ToS (it is allowed to reverse engineer the API though).

Turns out you just had to submit “null” for your user ID and it would remove the progress field.

Why is this tagged bad design?

["puzzle-id-string", user-id-as-int]

For almost anything, you POST json arrays...

Send help.

I was watching a YouTube video about c++ and the guy used player{1...n} in a game as an example for objects of a class Player.
That was A-ha for me 😅.

I never got that in grade school when teachers used fruits and animals as examples 😂.

Mine was when I finally moved from coding in statements to seeing just a little more of the picture by exposing myself to modules/classes. I still can't separate my one long index.js file into separate files (Discord bot, splitting my commands code into their own files) but I felt that progress. A pace of progress that I'm sure a glacier understands. I'm just hoping for some nudges from you Titanic's out there. ;)

Probably a veery long time ago, but being able to use what you use in if(...){} for e.g. booleans like "bool(ean) isX = a == x;".
And than reusing that value in if again and so on.

Even if it sounds trivial, there was a time where it was not and "==" was only associated with "you use that in if/while only" rather than "a == b" returns a bool(ean)/int.

Same goes for other arithmetic operators and && / || ofc.

Twas the moment while i was exposed to java on the commandline and windows editor and needed to grasp the shit to read input with bufferredReader and Inputstreamreader while my head was constantly spinning between the javadocs and the screen. In that moment my friend opened his eclipse and showed me code completion! And the fucking Screenreader class. I immediatly realized it was not only important to finish the assignment but also as fast and as lazy as possible!

When I found out on x86 you can switch back to real mode without restart to use bios services again. Just do your bit of printing and then switching back to protected mode. That was fun :) *sigh*

! a programming moment

My ah-ha moment was when i got to know that I could play metal slug on it.
I had gotten a CD consisting of neo geo ROMs on it
and that was one of my best moments in life.
I had never thought that i would have an arcade machine at home
I even invited some friends over and showed them that I had Metal Slug on my computer.

I was learning gw basic in school.

Instructor showed us how to draw a circle. I started graphics mode, set red as primary color and gave a loop to the circle, which reduced width at every iteration and turned it into an ellipse.

Woah .... That was the best Opera logo I ever saw

A while ago when I was making some EF extension functions. I was trying to make a bulk update function that used a parallel for-loop and I wanted it to accept funcs as a parameter.

Took me a while to figure out that a func and an expression are 2 different things, but when I did, oh boy did a fun world open up.

So tired of the Cookie Cutter gym goers. With there leggings under there shorts. They don’t even train legs, only upper body! And it’s really light weight at that!