When the scope of a project is the solar system and we end up talking about the universe... for three days. I just want to rage quit the meeting. 😐

You know what makes sense? Having a reCAPTCHA on a REST API.

That's good, Windows; don't actually fix the problem, just restart it... 😐

This duck is big enough to help me debug. And take my lunch money.

Found your girlfriend, Octocat!

If I ever lose heart

The struggle is real.

Credit: https://reddit.com/r/...

That's my favorite color!

The scope of the project has changed slightly. Well, ok...

~$ cat /dev/null > src/*

Apparently, too lazy to define a function.

Learned just enough Groovy to call a Python script and pass args to it. I have no problem with that.

"We need you to write a script to consolidate changes on different pages down to a single page. By the way, we're going to randomly make changes that will break your script, not tell you, and then complain to you when it doesn't work." -- That would be better than not saying anything and doing it anyway.

When I started developing and was skeptical on my efficiency, one of the first things someone said to me was, "honestly, as long as it works, they'll be happy."

Aside from encouraging bad coding practices, would any of you give that same advice?