Someone would look at our process and say “that’s not agile!” and they might be correct, technically speaking. I don’t personally care what it’s called as long as it works.

We agree to requirements up front with our customer; we might change stuff as we go along if our customer realizes that what they asked for won’t work (this happens occasionally), which is fine, but otherwise we don’t let them change stuff around on a whim, and we don’t allow scope creep. If they want a new feature, that’s version 2 (or 3, or 4).

We don’t meet very frequently. We do check in to make sure we’re on target, and deliver features incrementally when it makes sense to do so. We do sprints. We talk about when things are working and when they aren’t, but only when we think it’s a good time to do so.

At the end of the day, you need to tailor the process to your needs and what makes sense to you and your team.

Great, now I’m a new lifeform… nervously looks around for Janeway

And you avoid making an app that you show to the customer for the first time only for them to say, “What the hell is this?” My company used waterfall for the longest time, and this happened several times. It was really frustrating.

Dude’s hair is fucking fantastic. So jelly.

OK just checked out that Hodor module. That is hilarious.

When I was a Perl programmer, I had to modify this other guy’s code, and all I could think was that this guy was writing code with job security in mind.

If by “hard to understand” you’re including trying to understand someone else’s code, Perl can be a nightmare.

We saw you from across the bar and liked your vibe. Would you like to seek glory with us back at our place?

Live wrong and perspire

Thanks so much!

We have a puzzle bowl for our dog. Works great!

KAAAAAHHHHNNNN

Which would be especially messed up if your original question was about recursion.

Does it tell you to Google the problem and then downvote you?