They made meow meow beans?

Yes, I always review the code, just avoid nitpicking the hell out of it.

Not really, we are a small team and we generally trust each other. Sure there are things that could have been better, but it’s not bad either.

I am definitely guilt for that, but I find this approach really productive. We use small bug fixes as an opportunity to improve the code quality. Bigger PRs often introduce new features and take a lot of time, you know the other person is tired and needs to move on, so we focus on the bigger picture, requesting changes only if there is a bug or an important structural issue.

Has anyone gone through the documents? Any interesting findings? Is it time to create a website?

So that’s the legal equivalent of the guy committing 10k changes the day before leaving the company…

Jack Dorsey, good or bad?

(bonus points if you get the community reference)

Reminds me when dayjs decided to change the duration of a month during a random bugfix. I had to update so many tests…

Now I am going to share a horror story: Multitimezone Operational Calendars

No, they are using an ORM.

Got anything to share? source/screenshots/roadmap/feature-set/mock-ups

Scientist:

That means: Either the clock works quickly or it works precisely – both are not possible at the same time.

Engineer: Explain that to my manager please!

Also, Engineer: Well, what if we accounted for error rate and fixed precision post-processing?