Got the other devs in my office their own debugging rubber duckies.

Some serious debugging going on here today.

If you ever lost your debugger duck, I think I know what happened to it...

I actually talked to my duck. He solved my Server 500 error which said "java.lang.NoSuchFieldError: logger". I had to purge the build .class files and recompile the application and low and behold it runs.

Why is my duck a better debugger than most actual debuggers? He didn't even go to college!

Today I became a rubber duck debugger 🐤

I was leaving from office and spotted my senior collegue sitting glued to the screen solving an issue. I sat along with him to embark on a debug adventure. I casually asked him about the issue and what might cause it. After a bit of discussion *bam* he figured out where the problem lies and solved it in an instant.

Quack quack off I run 🐤

He's not rubber. Or a duck, but still a great debugger...

Debugging is...

My debugger duck.

My new coding buddy

Maybe that's why rubber ducky needs Chuck Norris for debugging......

Credits : A Facebook page

!rant

Today, my true developer saga begins. First job as an embedded developer and I am prepared with my flaming dark themed rubber duck debugger. What could go wrong? :D

Who need ducks when you can have unicorns ?

Is there an debugger duck AI?

Just an AI to chat while you debug

Ah, the little subtle things we have to iron out as we progress from Junior Developer to Medior Developer.. things like:

- knowing the difference between a carriage return and a line feed (although having worked with analog typewriters helps) and later knowing that Unix-based systems and Windows NT-based systems implement it differently..

- knowing that serialization is important because not all computers interpret data the same way and some computers allocate 4 Bytes for a construct, others 16 Bytes.. and then we get the funkiness of transferring character sets between machines..

- knowing that a whitespace character is not only an actual space (as is known in ASCII as code 32). This one can cause even medior developers a headache, as in: why the fuck does this string function say that "hello I am a duck" and "hello I am a duck" are not the same?! Turns out then in the debugger that when you expand every character in the string you see that string1 contains 32 32 32 32 as usual.. but then string2 contains -96 -96 -96 -96 and you're like.. what the fuck..? Then you know you have to throw \\h regex at it. Haha.

- finalizing our objects and streams (although modern languages do that for us).. otherwise we have to do funky shit like trying to find what's locking a file, which is not so easy to figure out.

- figuring out why something won't work often requires you to not only break down the problem in smaller steps, to use a debugger, but sometimes it's even better to just create a proof of concept, slap some minimal code in there and debug that.. much easier.

- etc.

:)

My debugger 'duck' he has helped me out many times.

I just realized that I have actually mastered the ways of the rubber duck debugger with the help of ... stackoverflow.

I just couldn't get my head around a problem thought about it for hours.
Googled for similar solutions, but didn't find anything.

In the end, I decided I'd do something I usually wouldn't and post a question on stackoverflow.

While carefully writing out and explaining my problem, it just made click.

I had it...
It works now...