Did some stuff you learned in the fellowship or maybe in the two years you've worked here change the way you collaborate on code now?

When you're in school, when you just graduate, you get this completely mistaken idea that all there is to software engineering is, you know, writing code, making features or fixing bugs and getting it out there.

My whole purpose of life was to go to the board and get those tickets done as quickly as possible.

Just ship stuff, ship, ship, ship, ship, ship.

But there's so much more than that.

You might find that it's even not a good idea to do things that way because, well, you ship really quickly.

Okay, that sounds good.

Can you tell us about a time when you maybe had a gross moment in open source where there was an issue, something that popped up, something that you just had to get over that hump and conquer it to keep going? And share that story with our audience too, in case there's someone out there who's dealing with the gross moment right now themselves.