I have pictures of me as a tiny toddler, playing on our family computer. I remember "working" on Microsoft Word for hours on end as a kid.

Someone is trying to launch a brute force attack on one of my servers that I set up for an old project. According to the logs, they've tried Jorgee, they've tried directly accessing the MySQL database (with the laziest passwords), and they're now on day 4 of their brute force attack against my SSH server. I'm fairly certain that they won't be getting in (not that there's anything worth getting in the first place), but what's the standard protocol for this? Do I just wait this out, or is there something I can do to break their bot? I have fail2ban enabled, and it is doing its job, but the attacker is changing their IP address with every attack.

My dad understands what I do (or maybe he thinks he understands, but close enough). My sister just thinks I'm tech support, and any Word or Netflix related problems go to me, even though I've never used modern Word, and I can't stand Netflix. My dad's fairly competent with computers, so I don't get many questions from him, other than the occasional "how do I do this probably impossible but actually kind of clever thing?"

"You'll be learning and working with C++ and Assembly."

I could very well be the only student ever to have been excited by that prospect.

I'm building a web application, and I'm currently working on the account registration code, and I could use some design advice. In your opinion, is it better to say "username/email address in use" when one or both are in use, or would it be best to specify whether the username or email address are in use? Why?

The rush when all of your tests pass on a problem you've been working at for 9 hours straight is what I live for.

In other news, fuck the change making problem, if I ever see that damn thing again, it'll be too soon.

My friend had the bright idea of making a version of bubble sort that plays a quacking sound effect on every swap. I added in different variations of the same sound effect for various conditions.

We named it "Quacksort," and one of the professors asked us to present it to the intro class.

My career has reached its peak.

My biggest dev regret is being complacent in my programming ability from way too early on. I learned a bunch of stuff from intro programming classes (which I always brushed off as "unnecessary" and "boring") because I was too ignorant to accept that writing the same Python code over and over wasn't progress. I'm way behind where someone with 7 years of programming experience should be, because I spent 4 of those years writing the same garbage.

I have 6 years of programming experience, so I'm the go-to guy at my college when someone's Python code doesn't work. The amount of unfathomably obvious problems I've fixed for people makes me wonder if some of my classmates are incapable of reading.