Neat.

We generally put this kind of thing into a chat window and have people ‘thumbs up’ the ones they want to vote for. It’s not elegant, but it’s quick and gets the job done.

Yeah. I’ve always thought timed open source was probably a sweet spot, but I don’t have a lot of trust that companies will actually follow through on the open license at the end, so it doesn’t buy my goodwill just yet.

With only 2 developers, CI/CD can be your best friend. Automate the daylights out of testing your code.

Remember to tag your regression tests in some way - any test that is preventing a production bug that actually happened needs to be marked as a ‘regression’ and treated as high priority to keep passing.

Treat all others tests as more art than science. Keep the reliable ones, toss out the brittle ones.

Look for a network traffic recording/replay library for your toolchain. Reusing integration tests as unit tests is a huge time savings.

If you have live data access, build yourself a few charts that represent a typical day. Knowing what “normal” looks like in your database can be priceless on a weird day.

Pro tip: If you draft documents in Markdown, lots of programs have a “preview” that renders perfect formatted text to paste into a Word document.

I find it saves me a ton of hassle to leave Word to the very last step, when .docx is required.

That makes me so happy.

Rarely. Require linear history for the win.