*offering sweets to a fellow at work

Colleague: Oh I'm a diabetic but What you've got here aaaaaa.....

My Brain:
Don't say it
Don't say it
Don't say it
Don't say it
Don't say it
Don't say it
Don't say it

Me: Oh come-on already One small piece won't kill you

I'm doing my CV in Vue with Bulma and everything is all nice and neat. I have a nice and neat 'skills' section that you can see pictured, and it's nice and neat. However, what is not very nice and neat is Firefox (and chrome's) print to PDF thing which ignore the nice little semi meaningless dots that I have, which is so fucking asdfghjkl;

People don't seem to know how to properly do print-debugging, so here's a simple guide:

1. A log of "aaaaaa" or "got here" isn't as helpful as you think when ALL OF THEM ARE THE FUCKING SAME. You put a descriptive label or copy verbatim the conditional statement. This saves time matching statements, allows one to watch multiple branches at once, and allows others to understand and help faster when dragged in to help.
2. When trying to see where code fucks up, before each line, paste said line into a proper print statement for your language. If there's, say, a function call or some shit, have it output something like "functionCall(varA=<varA contents>,varB=<varB contents);" Most normal lines should be like this too, but it's especially helpful for calls and comparisons.
If need be, add return values after if they're not shown in another print statement later.
This allows for a trail of execution AND the line that fucks up will be the last in the log, making finding it easier when dealing with hangs and such.
3. Putting something unique like "DEBUG: " or something in front of all statements ensures you can just search for them to ensure you're not rolling one out to production. It also separates debug output from normal output at a glance, making digging through logs faster.

Behold the monstrosity regex my transpiler produces!

/val|var|[1-9]{1,32}|\+|\-|\*|s\/s|>>|=|;|(["'])(?:(?=(\\?))\2.)*?\1|print\(|log\(|sqrt\(|input\(|strToArray\(|httpGet\(|if\(|else|{|}|s==s|s>=s|s<=s|s>s|s<s|s&&s|\|\||!|;|\(|\)|\[|\]| |\w+/gi

If there was an anime Based on developers.

==Start===

Dev : here comes my favorite browser.
Mouse : No, not until I'm here.
Hand : whattttt? What's happening??
Mind : oh NO!! I why's Internet Explorer is loading?!?

Faster Mind : it's mouse, he's behind all this. Only he's powerful enough to pull off something like this.

Time : Developer-san SAVE me!!
IE : it's too late now, if you do anything it will just slow everything down!!! Hahahah

Dev : No it won't, don't ever underestimate a true developer. It's not over yet!!
*Some keyboard key combination

Time : *screams* developerrr-saaaan!!
Hand : wait, I know it, it's happening. We can still save Time-chan.

IE : WHAT!! No, it can't be!!

Dev : here comes Ctrl+Alt+Del. Be gone....

IE : Nooooooooooooo, this isn't happening, Aaaaaa *dead*

Hand : we did it!!!

Because of coding, I'm slowly losing a life to live. aaaAaAaaaAaaAa@aaAAaa

So Google Calendar's API might return duplicate events when using nextPageToken in your requests and they don't tell you that. So I've been trying to find where the fuck my app was inserting duplicate data in the DB but it turns out it wasn't, it's just the Calendar API being a dick. Aaaaaa