This has inspired me. My Instant Pot has been throwing a lot of errors lately, I bet I can rig something up…

Is the goal to keep the poop inside your body? If it’s allowed to come out and play, you could blend it with gatorade and consume it as soon as possible to minimize time spent outdoors.

The submarine is staying down there because the pilot knows the Canadian wildfires are going to set the atmosphere on fire. They need to outlast the fire and repopulate the earth with the DNA they found on silverware from Titanic survivors.

We’re a small team of 6 and follow Git Flow for branching. Every change that wants to go into the develop branch needs an approval on the pull request by one of the two senior developers on the team.

We have (virtual) meetings for any changes that require discussion; some things are difficult to quickly communicate over pull request comments.

When it comes to code style, our standard is “format it using IntelliJ”. Same with warnings – if the IDE calls it out, it’s fair game in the review. Personally, I check out every branch I’m reviewing so that I can navigate easily and enable my own warnings, which are generally strict.

Most PR comments start as questions because sometimes questionable looking code can be correct, then things go from there.

I alternate between CLion and VSCode depending on what I’m doing. CLion has nice refactoring tools, but VSCode has much better GitHub Copilot integration.